AWS Certified SAP on AWS - Specialty

To meet the requirements of minimizing cost and maximizing operational efficiency, use SAP Software Update Manager (SUM) Database Migration Option (DMO) with System Move to re-architect the enterprise's initial system to SAP S/4HANA and to change the platform to AWS. Then, consolidate the two systems from the acquired companies with this SAP S/4HANA system using the Selective Data Transition approach with SAP Data Management and Landscape Transformation (DMLT). This approach allows selective data migration, ensuring only necessary data is moved, which reduces the complexity and cost while optimizing the migration process.

The correct approach to resolving the error related to SAP session handling and distribution of requests involves maintaining persistence by using session cookies and enabling session stickiness (session affinity) on the Application Load Balancer (ALB). The primary role of the ALB is to distribute incoming traffic across multiple instances, in this case, the two SAP Web Dispatchers. By configuring the ALB to maintain session stickiness, it ensures that all subsequent requests from the same user are directed to the same SAP Web Dispatcher, thereby resolving issues related to session handling. This setup is essential because the ALB is responsible for managing how requests are distributed among the web dispatchers, and without session stickiness, the user's session could be disrupted when requests are balanced across different dispatchers. Therefore, enabling session stickiness on the ALB is the most appropriate solution.

The most scalable solution for the given requirements is to use AWS Transit Gateway to connect the VPCs and on-premises networks together. AWS Transit Gateway acts as a hub that controls how traffic is routed among all the connected networks. It allows for the interconnection of thousands of VPCs and on-premises networks, providing a centralized and simplified network architecture. Additionally, AWS Transit Gateway supports inter-Region peering, which facilitates connectivity across different AWS Regions. This ensures that the overlay IP address used for high availability is accessible from multiple locations, including more than 25 VPCs, other AWS Regions, and the on-premises environment.

The most operationally efficient solution to ensure SAP backups are encrypted and only authorized team members can decrypt them is to use the AWS Backint Agent for SAP HANA with AWS Key Management Service (AWS KMS). Using AWS KMS allows you to create and manage encryption keys easily while ensuring that only the specified team members have decryption permissions through a key policy. This automated approach minimizes operational overhead and leverages AWS managed services to handle encryption securely.

The most cost-effective solution to meet the requirements of making production backups highly available for restore in case of on-premises server unavailability is to take a backup of the production servers, implement an Amazon S3 File Gateway, create file shares using the S3 File Gateway, and copy the backup files to the file shares through NFS and SMB. Mapping backup files directly to Amazon S3 and configuring an S3 Lifecycle policy to send the backup files to S3 Glacier based on the company's data retention policy provides a highly available, durable, and cost-effective storage solution.