[SEO Subhead]
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.
Please note: [Disclaimer]
Architecture Diagram
[Architecture diagram description]
Step 1
In an AWS account with SAP workloads, enable AWS Systems Manger. Systems Manager allows you to safely automate common and repetitive IT operations and management tasks.
Step 2
Create an Amazon Simple Storage Service (Amazon S3) bucket. Download the SAP systems inventory template from the GitHub repository and update with your SAP workload inventory.
Step 3
Launch the AWS CloudFormation template from the GitHub repository with the input as the S3 bucket. CloudFormation will deploy an AWS Lambda function and Amazon DynamoDB table. Upload the SAP inventory template to the S3 bucket.
Step 4
Run SAP health checks by executing the Lambda function on-demand, or schedule it periodically using Amazon EventBridge.
Step 5
The Lambda function evaluates AWS for SAP best practices and identifies any drifts or anomalies. Health checks results are written to the S3 bucket for further analysis.
Step 6
Amazon Simple Email Service (Amazon SES) sends notification emails regarding identified drifts.
Step 7
Optionally, analyze output using Amazon QuickSight. Use Amazon Q in QuickSight to query system health using natural language.
Step 1
In an AWS account with SAP workloads, enable AWS Systems Manger. Systems Manager allows you to safely automate common and repetitive IT operations and management tasks.
Step 2
Create an Amazon Simple Storage Service (Amazon S3) bucket. Download the SAP systems inventory template from the GitHub repository and update with your SAP workload inventory.
Step 3
Launch the AWS CloudFormation template from the GitHub repository with the input as the S3 bucket. CloudFormation will deploy an AWS Lambda function and Amazon DynamoDB table. Upload the SAP inventory template to the S3 bucket.
Step 4
Run SAP health checks by executing the Lambda function on-demand, or schedule it periodically using Amazon EventBridge.
Step 5
The Lambda function evaluates AWS for SAP best practices and identifies any drifts or anomalies. Health checks results are written to the S3 bucket for further analysis.
Step 6
Amazon Simple Email Service (Amazon SES) sends notification emails regarding identified drifts.
Step 7
Optionally, analyze output using Amazon QuickSight. Use Amazon Q in QuickSight to query system health using natural language.
Get Started
Deploy this Guidance
Well-Architected Pillars
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
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.
-
Operational ExcellenceRead the Operational Excellence whitepaper
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.
-
SecurityRead the Security 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.
-
ReliabilityRead the Reliability 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.
-
Performance EfficiencyRead the Performance Efficiency 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.
-
Cost OptimizationRead the Cost Optimization 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).
-
SustainabilityRead the Sustainability 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.
Related Content
[Title]
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.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.