Skip to main content

Guidance for SAP Data Integration and Management on AWS

Overview

This Guidance provides the essential data foundation for empowering customers to build data and analytics solutions. It shows how to integrate data from SAP ERP source systems and AWS in real-time or batch mode, with change data capture, using AWS services, SAP products, and AWS Partner Solutions. This Guidance includes an overview reference architecture showing how to ingest SAP systems to AWS in addition to five detailed architectural patterns that complement SAP-supported mechanisms (such as OData, ODP, SLT, and BTP) using AWS services, SAP products, and AWS Partner Solutions.

How it works

Overview of Architecture Patterns

This architecture diagram shows the pattern options for ingesting SAP systems to AWS. For detailed architecture patterns, open the other tabs.

Architecture diagram showing how SAP source systems integrate with AWS Cloud managed and instance-based services, including Amazon AppFlow, AWS Glue, SAP Datasphere, SAP Data Services, and SAP SLT, as well as landing in AWS Analytics Services such as Amazon S3, Redshift, Kinesis, and RDS.

AWS Managed Services

This architecture diagram shows how to ingest SAP data to AWS using AWS glue. For the other architecture patterns, open the other tabs.

Diagram illustrating data integration between SAP systems and AWS services using AWS Glue, Amazon AppFlow, and AWS Analytics Services, with security and monitoring via AWS Secrets Manager and IAM.

AWS Partner Solution by BryteFlow

This architecture diagram shows how to ingest SAP data to AWS using the Partner Solution: BryteFlow SAP Data Lake Builder.

Diagram illustrating SAP data extraction and processing on AWS, showing application-level and database-level data extraction feeding into an EC2 instance with BryteFlow SAP Data Lake Builder, supported by AWS services like S3, Redshift, and security tools.

SAP Datasphere and Data Services

This architecture diagram shows how to ingest SAP data to AWS using SAP Datasphere or SAP Data Services.

Architecture diagram illustrating SAP data integration and management using AWS cloud services, SAP Datasphere, Amazon S3, Amazon Redshift, and SAP Data Services.

How it works (continued)

SAP SLT

This architecture diagram shows how to ingest SAP data to AWS using SAP SLT.

Diagram showing data flow from SAP systems to AWS Cloud services via SAP SLT, connecting to Amazon RDS, Amazon Kinesis, and Amazon S3.

SAP NetWeaver Add-On Solution by SNP

This architecture diagram shows how to use SAP NetWeaver add-on solution SNP Glue to extract data from SAP to AWS.

Architecture diagram illustrating SAP data integration and management using AWS Netweaver and SNP Glue add-on, showing the flow of data from SAP BW and SAP ERP sources to AWS Cloud analytics services including Amazon S3, Amazon Redshift, and Amazon RDS.

Deploy with confidence

Ready to deploy? Review the sample code on GitHub for detailed deployment instructions to deploy as-is or customize to fit your needs. 

Go to sample code

Well-Architected Pillars

The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.

AWS CloudFormation automates the deployment process, while CloudWatch provides observability, tracking, and tracing capabilities. The entire solution can be deployed using CloudFormation, which helps automate deployments across development, quality assurance, and production accounts. This automation can be integrated into your development pipeline, enabling iterative development and consistent deployments across your SAP landscape.

Read the Operational Excellence whitepaper

IAM secures AWS Glue and Amazon AppFlow through permission controls and authentication. These managed services access only specified data. Amazon AppFlow facilitates access to SAP workloads. Data is encrypted in transit and at rest. AWS CloudTrail logs API calls for auditing. S3 buckets and cross-region replication can store data. For enhanced security, run Amazon AppFlow over AWS PrivateLink with Elastic Load Balancing and SSL termination using AWS Certificate Manager.

Read the Security whitepaper

Amazon AppFlow and AWS Glue can reliably move large volumes of data without breaking it down into batches. Amazon S3 provides industry-leading scalability, data availability, security, and performance for SAP data export and import. PrivateLink is a regional service, and as part of the Amazon AppFlow setup using PrivateLink, you will set up at least 50 percent of Availability Zones in the Region (minimum two Availability Zones per Region), providing an additional level of redundancy for ELB.

Read the Reliability whitepaper

The SAP operational data provisioning framework captures changed data. Parallelization features in Amazon AppFlow and AWS Partner Solutions like BryteFlow and SNP enable customers to choose the number of parallel processes to run in the background, parallelizing large data volumes. Amazon S3 offers improved throughput with multi-part uploads through supported data integration mechanisms. The parallelization capabilities and seamless integration with Amazon S3 allow for efficient and scalable data ingestion from SAP systems into AWS.

Read the Performance Efficiency whitepaper

By using serverless technologies like Amazon AppFlow or AWS Glue and Amazon EC2 auto scaling, you only pay for the resources you consume. To optimize costs further, extract only the required business data groups by leveraging semantic data models (for example, BW extractors or CDS views). Minimize the number of flows based on your reporting granularity needs. Implement housekeeping by setting up data tiering or deletion in Amazon S3 for old or unwanted data.

Read the Cost Optimization whitepaper

Data extraction workloads can be scheduled or invoked in real-time, eliminating the need for underlying infrastructure to run continuously. Using serverless and auto-scaling services is a sustainable approach for data extraction workloads, as these components activate only when needed. By leveraging managed services and dynamic scaling, you minimize the environmental impact of backend services. Adopt new options for Amazon AppFlow as they become available to optimize the volume and frequency of extraction.

Read the Sustainability whitepaper

Disclaimer

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.