AWS for SAP

Discusses access patterns for SAP applications that require access to and from both internal and external sources. Access from external sources may be controlled (they may involve known external parties) or uncontrolled (they may be publicly accessible)—this post covers both scenarios. This is the third post in the series on VPC subnet zoning patterns.

Describes the Amazon Route 53 agent, which enables on-premises users to access an SAP HANA database that is protected by SUSE Linux Enterprise High Availability Extension (SLES HAE) in the AWS Cloud. The agent provides this functionality by dispatching users through Amazon Route 53.

Describes how the collaboration between itelligence and AWS enables customers to attain the benefits of the AWS Cloud (like elasticity, resiliency, security and global scale) in combination with the SAP implementation and operational expertise provided by itelligence.

Discusses how traditional application network zoning can be mapped to AWS. This is the second post in the series on VPC subnet zoning patterns.

Explains how you can use the SAP Rapid Migration Test program (also known as FAST, which stands for Fast AWS and SAP Transformation) to migrate your on-premises SAP applications (SAP ECC and SAP Business Warehouse) running on a non-HANA database to SAP HANA or SAP ASE on AWS.

If you are considering moving your SAP workloads to AWS, you’re probably wondering what your SAP architecture would look like on AWS, how different it would be to run SAP on AWS vs. running it on premises or in your private cloud, and how your business might benefit from migrating to AWS. This introductory article helps you prepare to migrate and operate your SAP workloads on AWS.

This is the first blog post in a 3-part series about VPC subnet zoning patterns for SAP on AWS. It summarizes ways in which SAP applications may be accessed, and covers possible architecture patterns for the first category of applications–those that are accessible only internally.

Discusses how you can use the database migration option (DMO), which is a feature of the SAP Software Update Manager (SUM) tool, to migrate your on-premises anyDB database to SAP HANA on AWS.

Are you planning to migrate your SAP applications to the SAP HANA platform or start a new implementation with SAP HANA? If so, you might be wondering what options AWS provides to run your SAP HANA workloads. This post discusses the core infrastructure components required for SAP HANA and the building blocks that AWS provides to help you build your virtual appliance for SAP HANA on AWS.

AWS has worked with SAP to certify additional scale-out architectures for SAP Business Warehouse on HANA and can now support workloads requiring up to 4 TB of memory. This sets the record for SAP HANA scale-out nodes in the cloud, and validates AWS is an ideal solution for enterprise customers to cost effectively run SAP HANA. Find out more in this blog post.