SAP on AWS · SAP System & Application-Server Architecture on AWS

Your Additional Application Servers (AAS) sit in two AZs for high availability (HA) and some critical batch jobs run slow. What architecture choice fixes it, and why isn't even-spreading the goal here?

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 SAP System & Application-Server Architecture on AWS

On AWS, is an 'SAP instance' the same thing as an 'EC2 instance', and what one property distinguishes them?

On the same instance (e.g. x2iedn.32xlarge), TDI v5 allows 4 TiB for HANA vs 2.7 TiB under TDI v4. What's the catch that decides which spec you can actually claim?

Choosing storage for SAP app-server volumes vs shared file systems on AWS — what's the discriminating factor, and why isn't the certified-but-pricey tier the default?

In an SAP HA setup, which component owns the SAP lock table and which keeps it from being lost on failover — and why must ERS sit where it does?

Sketching multi-AZ HA for SAP NetWeaver on AWS, what are the load-bearing pieces — and which one do people forget, breaking failover routing?

A customer wants to lift-and-shift their on-prem SAP HA stack to AWS. Which two HA solutions must you tell them are NOT supported, and what are the supported alternatives?

Start learning today

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