SAP RISE on AWS deployment guide.

A buyer side reference for SAP RISE deployments that target Amazon Web Services as the hyperscaler underlay. Commercial mechanics, architecture choices and the checks to run before signature.

RISE with SAP allows three hyperscaler underlays. Amazon Web Services is the most common selection in regulated industries.

The choice is not just technical. RISE on AWS carries a specific commercial and operational shape that differs from RISE on Azure or Google Cloud.

This page is the buyer side reference for the checks to run before signing a RISE on AWS deal.

How RISE on AWS actually works

Who runs what

• SAP runs the S/4HANA application, the HANA database and the BTP overlay.
• AWS provides the compute, storage and network underlay under its agreement with SAP.
• You own the integration plane, the master data and the custom code in the BTP overlay.

Regions and residency

AWS region availability under RISE is not the full AWS region list.

Confirm your residency region in the CVR. A region not listed in the CVR is not a commitment.

Commercial mechanics that change on AWS

What is bundled

• Compute and storage for the S/4HANA workload.
• Standard backup retention to AWS S3 cold tiers.
• Network ingress and egress within a defined cap.
• Disaster recovery to a second AWS region inside the contracted RPO.

The egress cap

RISE on AWS includes an egress cap that is not always explicit on the order form.

Cross check the cap against your real integration volume from non SAP systems.

True up and true down

RISE on AWS commitments can include a true up if S/4HANA workload grows.

Insist on a true down right at each anniversary as a counter to the seller default.

RISE on AWS is a commercial deal first and a hyperscaler deal second. Read the CVR before the cloud architecture slide.

Architecture choices to model before signature

High availability and disaster recovery

Multi availability zone HA is standard. Cross region DR is an add on in most CVR templates.

Validate the RPO and RTO numbers against your business continuity policy, not against the seller marketing slide.

Integration pattern

• AWS S3 and Lambda integrations need an explicit data exchange path.
• PrivateLink is the typical clean pattern for internal AWS workloads.
• Public internet integration is allowed but rarely the right design.

Custom code and BTP

Custom code that ran on premise does not move untouched.

Plan the BTP overlay scope and the ABAP cloud development model alongside the move.

Buyer side checks before signature

Region and residency confirmation

• Region listed in the CVR by name, not just by geography.
• Residency clause stating data does not leave the region.
• Failover region named in writing for disaster recovery.

Exit path

Confirm the data export format and the assistance commitment on exit.

An exit clause without a defined assistance scope is not a real exit clause.

Suggested reading

• RISE on Azure Deployment Guide. Cross vendor reading from the wider library.
• SAP RISE Negotiation Guide. Cross vendor reading from the wider library.
• SAP BTP Pricing and Licensing. Cross vendor reading from the wider library.

What to do next

1. Confirm the AWS region for production and DR in the CVR by name.
2. Validate the egress cap against your real integration volume.
3. Define RPO and RTO in writing inside the order form.
4. Plan the BTP overlay and custom code path before commit.
5. Add a true down right and an uplift cap at each anniversary.
6. Confirm exit clause assistance scope and data export format.
7. Brief security, infrastructure and finance jointly before signing.

Frequently asked questions

Do we buy AWS directly under RISE on AWS?

No. The commercial relationship runs through SAP. AWS provides the underlay under its own agreement with SAP. You do not get an AWS bill for the RISE compute.

Is every AWS region available under RISE?

No. SAP supports a subset of AWS regions for RISE. Confirm your target region in the CVR before commitment.

How is egress handled?

RISE on AWS includes a defined egress cap inside the bundle. Volume above the cap is billable. Model against your real integration pattern, not the seller default.

Can we mix RISE on AWS with native AWS services?

Yes. The most common pattern is PrivateLink between the RISE landscape and your native AWS workloads. Plan it before commitment.

What happens at exit?

Exit clauses cover data export and a defined assistance period. Confirm the assistance scope in writing. An exit clause without scope is not enforceable in practice.