SAP on AWS · Resilience: HA, DR & Service Levels for SAP

Your SAP stack has an app server at 99.5% and a HANA DB across availability zoness (AZs) at 99.99%. A colleague says the composite service level agreement (SLA) is 99.5% (the weakest link). Why is that wrong, and which way does the real number move?

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 Resilience: HA, DR & Service Levels for SAP

The business signed for 99.95% S/4HANA uptime. Your AWS infrastructure SLAs all clear that bar. Why can you still breach the business-uptime SLA, and what closes the gap?

Name the four single-region HA/DR patterns for SAP and the one property that separates the 99.5% pair from the 99.99% / ~0-RPO pair.

If a single AWS transit center inside a region fails, do instances in one AZ lose connectivity to another AZ? Why or why not, and what does the answer let you trust?

An auditor asks who is accountable when S/4HANA is unavailable: AWS's service service level agreement (SLA) or the MSP's SLA. How do the two differ in scope, and which one covers a misconfiguration outage?

An architect quotes the EC2 99.99% region SLA to justify running SAP Central Services on one instance. Why is that a misread of what the 99.99% covers, and what SLA does the lone instance actually carry?

A holiday outage costs $1,000/hour in lost revenue on a service that bills $100/month. How much does the AWS SLA credit return, and what's the lesson about using credits as a risk hedge?

Start learning today

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