Welcome back to the drawing board! It is late 2021, and the way we provision SAP systems has just drastically changed. Do you remember the endless days when SAP Basis administrators spent hours clicking through the Software Provisioning Manager (SWPM)? Manually creating mount points, assigning storage LUNs, adjusting Linux kernel parameters for HANA, and configuring error-prone Pacemaker clusters.
Those days are officially over. With the final maturity of the AWS Launch Wizard for SAP, the concept of Infrastructure as Code (IaC) fully enters the SAP Basis realm. Today we dissect how AWS orchestrates the magic of fully automated S/4HANA provisioning under the hood.
The End of Manual SWPM
The AWS Launch Wizard is not a simple click-through path (wizard) as the name suggests, but a highly complex orchestration engine. The architect merely defines the business requirements upfront: "I need an S/4HANA system for 5,000 SAPS with High Availability."
The wizard then calculates the sizing, recommends the appropriate EC2 instances (according to SAP TDI certification), and calculates the required IOPS for EBS storage. But the true magic happens after clicking "Deploy".
Under the Hood: CloudFormation and Systems Manager (SSM)
What happens architecturally in the cloud?
-
AWS CloudFormation: The Launch Wizard generates hundreds of lines of code on-the-fly in the form of CloudFormation templates. These templates build the network: VPCs, subnets, Security Groups, and they provision the bare EC2 instances with EBS volumes configured exactly according to SAP specifications (e.g., striped logical volumes for
/hana/data). -
AWS Systems Manager (SSM): Once the infrastructure is up, SSM takes over. It acts as an agent on the operating systems (SUSE or RHEL). SSM executes scripts that automatically download the SAP software archives from an S3 bucket, unpack them, and trigger the SWPM in Silent Mode (unattended).
The Masterpiece: Automated High Availability (HA)
The biggest pain point for classic Basis admins is setting up an HA cluster across multiple data centers. The Launch Wizard completely automates this architectural monster:
-
It provisions the primary instance in Availability Zone A and the secondary in AZ B.
-
It configures HANA System Replication (HSR) synchronously between both nodes.
-
It installs the cluster software (Pacemaker, Corosync) and configures the SAP HANA Scale-Up resource agent.
-
It sets up AWS Overlay IP Routing so that in the event of a failover, the virtual IP is rewritten to the network interface of the secondary EC2 instance in fractions of a second.
What used to be a two-week consulting project now happens flawlessly in under three hours.
📢 SAP & AWS ARCHITECTURE NEWS TICKER (As of: November 2021) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🔹 Gigantic Compute: AWS has officially had the new High Memory Instances with 24 TB RAM certified by SAP. These are the largest SAP-approved bare-metal machines in the cloud. They run on Intel Xeon Scalable (Cascade Lake) processors and are aimed at the world's largest S/4HANA monoliths. 🔹 SUSE Linux 15 SP3: The Launch Wizard now supports the latest SLES for SAP Applications versions, massively increasing cluster stability through new Corosync metrics.
Conclusion for Enterprise Architects
The AWS Launch Wizard for SAP is a massive disruptor. It democratizes complex architectural knowledge. For Basis admins, this means: Core competency is finally shifting from manually typing Linux commands to understanding CloudFormation templates and SSM documents. Anyone still manually mounting LUNs in 2021 is losing valuable time that should instead be invested in optimizing application performance and BTP integration.