Skip to main content

Guidance for Automating SAP Configuration Health Checks on AWS

Overview

This Guidance shows how to automate health checks for customers who are running SAP on AWS using the traditional licensing model. Many customers are choosing RISE with SAP, where SAP handles infrastructure and technical services. For customers using the traditional licensing model with SAP on AWS, this Guidance demonstrates how to automate evaluation of the SAP landscape on AWS against 100+ health checks and architecture best practices aligned with the AWS Well-Architected Framework. It shows how to scan SAP systems automatically for configuration compliance, providing a summary view, detailed views for individual systems, and the capability to compare two systems side-by-side through an Amazon QuickSight dashboard. This empowers customers to proactively identify and remediate potential issues, confirming the SAP landscape adheres to AWS architectural best practices.

How it works

This architecture diagram demonstrates how to automate health checks based on the AWS Well-Architected Pillars to identify configuration drifts and monitor infrastructure health.

Get Started

Deploy this Guidance

Sample code

Use sample code to deploy this Guidance in your AWS account

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.

Amazon CloudWatch provides full transparency into execution logs for a comprehensive view of operations. The DynamoDB editor eliminates the need for additional user interfaces and codebase maintenance. These managed services help you focus on core business objectives without the burden of maintaining additional infrastructure.

Read the Operational Excellence whitepaper

AWS Identity and Access Management (IAM) aligns with existing organizational permissions policies, minimizing additional effort and helping ensure appropriate user access levels. IAM seamlessly integrates with this solution, providing a secure foundation while adhering to your current security practices.

Read the Security whitepaper

Lambda automatically scales to meet application needs, so that you don’t have to overprovision for future spikes in demand. This fully managed approach minimizes overhead of infrastructure management.

Read the Reliability whitepaper

Lambda helps with optimizing Python code, which is modularized and optimized to run under 200 MB memory for scalability and efficiency. This service-based approach allows the application to scale up and down seamlessly based on the number of health checks for optimal performance.

Read the Performance Efficiency whitepaper

Lambda runs code without requiring servers, eliminating the need to provision and manage Amazon Elastic Compute Cloud (Amazon EC2) instances. By optimizing Python code for Lambda, you can keep costs low, typically less than $1 USD per instance (without considering AWS Free Tier).

Read the Cost Optimization whitepaper

Managed services like Amazon S3, Lambda, and DynamoDB improve application sustainability by sharing resources across a broad customer base, maximizing resource utilization and reducing the overall infrastructure required for cloud workloads. This sustainable approach minimizes the energy and resources needed to power the solution, contributing to a more environmentally responsible cloud workload.

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.