This document describes the typical deployment scenario of the Avantra for AWS.
Avantra is intended to manage small to large-scale SAP system environments. As more and more customers transfer SAP workloads to AWS, running Avantra itself in AWS is one of the common use cases, and with Avantra for AWS we leverage all the benefits AWS provides also for Avantra itself.
Within this guide we will describe the setup of Avantra in an environment where SAP workloads are deployed in AWS VPCs as well as on-premise, given there is network connectivity between your on-premise networks and the AWS VPCs.
Avantra consists of a central component, the Avantra Server and decentralised Avantra Agents, each of which is installed on a server (first of all AWS EC2 instances in this context) hosting e.g. SAP Application Servers.
Within this guide, we will describe the setup of the Avantra Server by means of Avantra for AWS, an all-in-one Multi-AZ failover setup based on an Amazon Machine Image (AMI), an EC2 launch template and a scaling group, a very small EFS distributed file system, an RDS service as a data store, Elastic Load Balancers and other AWS services, combined into a single AWS CloudFormation template.
In addition, we will describe how to deploy Avantra Agents on EC2 instances (and on-premise servers) running either RHEL or SLES using the AWS Systems Manager, and how to synchronize the Avantra inventory with these EC2 instances.
The setup of Avantra for AWS will take about 20 minutes, and given you are using the AWS Systems Manager, deploying Avantra Agents and connecting to the Avantra Server will take another 20 minutes.
You can also integrate the Avantra Notification Managemt with the Amazon Simple Notification Service and the Amazon Simple Email Service.
Optionally, you can set up snapshot copies to a different AWS Region or even AWS Account for enhanced failover scenarios.