Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Skip to main content

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.

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.