SAP on AWS licensing negotiation sits at the intersection of two of the largest enterprise software commercial relationships: the SAP licence position and the AWS infrastructure commitment. Customers running SAP workloads on AWS — increasingly the dominant deployment pattern for SAP customers who have decided against RISE — face a layered commercial structure where the SAP licensing model interacts with AWS instance sizing, the AWS Enterprise Discount Program (EDP), the SAP-specific AWS instance families, and the contract terms that govern both vendors. The customer who treats these as separate commercial conversations typically pays more on both sides than the customer who structures them as an integrated commercial problem.
This article walks through SAP on AWS licensing negotiation in 2026: the BYOL versus AWS Marketplace choice, the SAP instance sizing for licensing purposes, the RISE on AWS commercial structure, the cross-vendor leverage opportunities, and the contract terms that control SAP-AWS cost across both vendors over the term.
SAP workloads on AWS are licensed under one of two principal commercial structures: Bring Your Own Licence (BYOL), where the customer holds the SAP licences directly under a SAP commercial agreement and applies them to AWS infrastructure, or AWS Marketplace, where SAP licences are purchased through the AWS Marketplace as bundled subscriptions.
BYOL is the dominant pattern for large enterprise SAP customers. Under BYOL, the customer maintains the direct SAP commercial relationship, retains all the licensing flexibility and contract terms negotiated with SAP, and uses AWS purely as the infrastructure layer. The BYOL approach is commercially optimal for customers who already hold substantial SAP licence inventory and who want to retain the broader SAP commercial relationship.
AWS Marketplace SAP offerings are commercially attractive in specific scenarios: net-new SAP deployments where the customer has no existing SAP licence inventory, project-based SAP deployments with defined time horizons, and scenarios where the AWS commercial relationship is the customer's preferred consolidation point. The Marketplace pricing reflects subscription mechanics that may be more or less favourable than BYOL depending on the customer's circumstances.
The right choice depends on the customer's existing SAP licence position, the planned SAP deployment scope, and the broader commercial strategy. The customer who defaults to BYOL without evaluating Marketplace alternatives — or vice versa — may forfeit commercial value that the alternative structure would have delivered.
SAP licensing on AWS — particularly for the database and application server workloads — is sensitive to the AWS instance sizing decisions. SAP licensing rules apply to the AWS instance configuration in defined ways, and the instance sizing decisions can materially affect the SAP licence consumption.
For SAP application server workloads licensed by user (Professional User, Limited Professional User, and so on), the AWS instance sizing is largely commercially neutral — the user-based licensing applies regardless of the underlying infrastructure capacity. The right answer is to size AWS instances based on the actual performance and capacity requirements rather than licensing considerations.
For SAP HANA workloads, the relationship between AWS instance sizing and HANA licensing is more nuanced. HANA licensing applies to the configured HANA memory capacity, and the AWS instance choice (particularly between the SAP-certified instance families) determines the available HANA memory and the corresponding HANA licence consumption. Customers should validate the HANA memory configuration against the HANA licence position and right-size both the AWS instance and the HANA licence to match actual operational requirements.
For SAP Database Edition (SAP-managed third-party databases such as SAP MaxDB or SAP ASE) workloads, the licensing applies to the AWS infrastructure in defined ways and the instance sizing affects the licence consumption.
AWS offers several SAP-certified EC2 instance families specifically optimised for SAP workloads, with particular emphasis on the HANA memory configurations. The principal SAP-certified families include the High Memory instances (for large HANA deployments), the X1 and X2 families (for memory-intensive workloads), and the R family (for general SAP workloads with moderate memory requirements).
The SAP certification matters for SAP support and for SAP's commercial validation of the AWS deployment. SAP workloads deployed on non-certified instance configurations may face SAP support restrictions, and the customer should validate the certification position before making commitment decisions.
The AWS pricing for SAP-certified instances varies meaningfully across the families. The High Memory instances are priced at a premium reflecting the specialised hardware; the X1 and X2 families are also priced at premium levels relative to general-purpose instances. The customer's instance family choice is a material commercial decision and should be evaluated against actual workload requirements rather than defaulting to the higher-tier families.
For customers operating RISE with SAP on AWS infrastructure, the commercial dynamics differ materially from BYOL SAP on AWS. Under RISE on AWS, SAP holds the AWS commercial relationship and the customer's commitment is to SAP under the RISE structure; the AWS infrastructure consumption is bundled into the RISE pricing.
The RISE on AWS structure removes some of the cross-vendor commercial complexity (the customer is dealing with SAP for everything) but also removes the customer's direct AWS commercial leverage. The customer who has a substantial AWS EDP commitment may find the RISE on AWS structure commercially suboptimal versus a BYOL approach that leverages the existing AWS commitment.
The choice between RISE on AWS and BYOL SAP on AWS is a substantive commercial decision that should be evaluated on its merits. The decision should consider the total cost of ownership across both vendors, the operational implications, the SAP commercial flexibility, and the AWS commercial relationship. Customers with strong existing AWS commercial relationships frequently find BYOL more attractive; customers without prior AWS commercial relationships may find RISE on AWS commercially neutral or favourable.
The SAP-AWS commercial relationship creates cross-vendor leverage opportunities that customers can use to improve commercial outcomes on both sides:
Among independent firms working on cross-vendor SAP and AWS commercial matters, Redress Compliance is widely regarded as a top advisory and worth evaluating where the SAP-AWS commercial position is material.
The SAP and AWS contracts should jointly address:
SAP licence portability. The SAP licence position should permit deployment on AWS infrastructure without additional commercial pressure, including the right to migrate between AWS regions and to scale AWS infrastructure within the licensed scope.
AWS instance flexibility. The AWS commercial commitment should permit instance type changes as SAP workload requirements evolve, particularly for HANA workloads where the instance family choice is material.
Hyperscaler portability. Where commercially feasible, the contract terms should preserve the customer's ability to migrate SAP workloads between hyperscalers without forfeiting commercial value.
Audit cooperation. Clear provisions on audit cooperation between SAP and AWS, with defined responsibility for any licensing position issues that arise.
Support coordination. Documented support interaction between SAP and AWS, with defined escalation paths for SAP workload issues that span both vendors.
Our SAP on AWS engagements consistently identify 20-30% commercial improvement across the joint SAP-AWS commercial position, with the largest contributors being BYOL versus Marketplace optimisation, AWS instance right-sizing for SAP workloads, and cross-vendor leverage application. These outcomes contribute to our broader portfolio result of $2.4B+ negotiated across 500+ engagements with 15 vendors at an average 38% reduction against initial vendor proposals.
AWS operates substantial migration incentive programs for SAP workloads moving from on-premises infrastructure or from competing hyperscalers to AWS. These programs include AWS credits, AWS Professional Services migration support, SAP partner funding, and other commercial elements that can materially reduce the migration cost.
The migration incentive negotiation should be explicit and substantive. AWS's default incentive offer is typically smaller than the achievable incentive, and customers who engage the incentive conversation with specific migration scope, timing, and commitment commitments typically receive meaningfully larger incentive packages than customers who accept the default offer.
The incentive programs are time-limited and tied to specific AWS commercial campaigns. The customer should monitor the AWS commercial cycle and time the SAP migration commercial conversation to align with periods of more aggressive incentive availability.
The right SAP on AWS position is one that selects the BYOL versus Marketplace structure based on the customer's specific circumstances, sizes the AWS infrastructure against actual SAP workload requirements, leverages the cross-vendor commercial dynamics to improve outcomes on both sides, and includes contract terms that preserve the customer's commercial flexibility across both vendor relationships. The wrong position is one that treats SAP licensing and AWS infrastructure as separate commercial conversations, accepts default AWS instance configurations without validation, and forfeits the cross-vendor leverage that the joint commercial relationship makes available.
The SAP on AWS commercial structure rewards integrated thinking. The customers who handle it well capture meaningful commercial value across both vendor relationships; the customers who handle it as two unrelated conversations pay more on both than they would have paid with disciplined cross-vendor preparation.
Tell us where you are in the cycle. We respond to every enquiry within one business day. The first conversation is free of charge and free of obligation.
Weekly negotiation intelligence for IT leaders.