SAP on AWS · AWS Well-Architected Framework & the SAP Lens

Name the six pillars of the AWS Well-Architected Framework.

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in AWS Well-Architected Framework & the SAP Lens

An SAP architect secures the network perimeter heavily but leaves the EC2 OS, the DB, and IAM relatively open, reasoning the firewall is enough. Which Security-pillar principle is being violated, and why does it matter?

A reporting SAP system that was never reviewed under the SAP Lens has just been redesignated business-critical and now needs HA — but it's already in production. Is it too late to run an SAP Lens review, and where do these reviews pay off most?

Why does moving SAP transports in small weekly batches beat a single large monthly transport window, even though weekly means more change events?

How is a Sustainability-pillar goal like "less compute/storage per SAP transaction" different from a Cost Optimization goal, given both push you to use fewer resources?

You can deliver the same total SAPS with either three large SAP application servers or nine smaller ones. Why is the larger fleet of smaller servers the more resilient choice?

You can technically mount Amazon S3 to an EC2 instance. Why does "mechanical sympathy" tell you NOT to put database files on it?

Start learning today

Free to start — download the app or use it in your browser.