SAP on AWS · Operating SAP on AWS

An internal (Pattern-2) SAProuter is recovered by EC2 host auto-recovery in one case and relaunched in a new AZ in another. Why does only one of these force a change on the external SAProuter?

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 Operating SAP on AWS

You enforce EC2 access for SAP project teams with tag-based ABAC. Why is that not enough on its own, and what does an SCP add?

Your SAP-on-AWS deployment runs on default (Basic) CloudWatch monitoring. Why will that fail the SAP support requirement, and what changes?

Why does running SAP on AWS need a SAProuter, and what constraint does its Elastic IP impose on DR design?

What distinguishes Pattern-2 SAProuter deployment from Pattern 1, and what is true of its internal SAProuters?

How do you keep a Pattern-1 SAProuter available across instance, AZ, and region failures, and what step is easy to skip at each tier?

You want a single-pane view of all SAP systems on AWS. When do you reach for Systems Manager Application Manager vs CloudWatch Resource Health?

Start learning today

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