© 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Steven Jones, Sr. Manager, Solutions Architecture
March 17th, 2015
Best Practices for Deploying SAP Workloads on AWS
SAP on AWS
All SAP Business Suite and NetWeaver Applications(FI, HR, BI/BW, SRM, Solman, SAP PO, etc)
Leverage Multi-AZ for Production Workloads
x86 Intel Processor based systems with up to 32vCPUs x 244GIB RAM, SSD backed storage for 10’s of thousands of IOPS
S3 Storage provides 99.999999999 durability
Enterprise level security
Pricing, Sizing, Management and Operations
SAP Supported Platform
High Availability
High Performance
High Durability
Secured platform
Flexible
1 http://aws.amazon.com/whitepapers/vms-sap-tco/
SAP & AWS Relationship - Key Milestones
2008 2012 2010 2014
SAP as aCustomer
A1/B1 BOBJ
HANA Developer Edition
HANA One
Afaria
SAP HANA Platform Edition
SAP Business SuiteSAP Cloud Appliance Library (CAL)
Cus
tom
er A
dopt
ion
Time
RDS Solutions
Sybase IQ / ASE SAP HANA for B1
Backup / Recovery
Deploy
Operate
DR
/ H
AScale
Arc
hite
ctur
eAWS
Leverage
Faster
Efficiently
Agi
le
Cost Efficient
AWS Enables SAP Customers to
Easily
Rel
iabl
e
Security
Architected for Enterprise Security RequirementsCertifications and accreditations for
workloads that matter
“The Amazon Virtual Private Cloud
[Amazon VPC] was a unique option that
offered an additional level of security and
an ability to integrate with other aspects
of our infrastructure.”
AWS Shared Responsibility Model
Facilities
Physical security
Compute infrastructure
Storage infrastructure
Network infrastructure
Virtualization layer (EC2)
Hardened service endpoints
Rich IAM capabilities
Network configuration
Security groups
OS firewalls
Operating systems
Applications
Proper service configuration
AuthN & acct management
Authorization policies
+ =
Customer
. •Scope of responsibility depends on the type of service offered by AWS: Infrastructure, Container, Abstracted Services•Understanding who is responsible for what is critical to ensuring your AWS data and systems are secure!
More secure and
compliant systems
than any one entity
could achieve on its
own at scale
Sizing and Performance
When sizing the HANA appliance, main memory is the most important resource. Sizing
methods vary depending on the implementation scenario. In general the following
methods apply:
•New Implementation: Use the SAP QuickSizer (http://service.sap.com/quicksizer)
•Migrating an Existing SAP Netweaver Business Warehouse System: Use the new ABAP
sizing report for SAP NetWeaver BW described in SAP note 1736976*
(http://service.sap.com/sap/support/notes/1736976)
•Migrating an Existing SAP Business Suite System to HANA: See SAP note 1872170* (
http://service.sap.com/sap/support/notes/1872170) to estimate the main memory requirements
of the HANA virtual appliance.
* SAP ID Required
If memory requirements for the SAP HANA solution exceed the available memory of a single AWS instance, you can deploy a scale-out solution consisting of multiple instances as long as the SAP solution you are deploying supports a scale-out configuration.
Compute Optimized
Name vCPUMemory (GiB)
I/O Perf
SAPS
c4.8xlarge 36 6010
Gigabit37,950
c4.4xlarge 16 30 High 19,030
c4.2xlarge 8 15 High 9,515
c4.xlarge 4 7.5 High 4,758
c4.large 2 3.75 Moderate 2,379
c3.8xlarge 32 6010
Gigabit31,830
c3.4xlarge 16 30 High 15,915
c3.2xlarge 8 15 High 7,958
c3.xlarge 4 7.5 High 3,979
c3.large 2 3.75 Moderate 1,989
Memory Optimized
Name vCPUMemory (GiB)
I/O Perf
SAPS
r3.8xlarge
32 24410
Gigabit31,920
r3.4xlarge
16 122 High 15,960
r3.2xlarge
8 61 High 7,980
r3.xlarge 4 30.5Moderat
e3,990
r3.large 2 15Moderat
e1,995
Use in 2-Tier and 3-Tier Configurations Certified Instances for SAP HANA Cluster Networking Available EBS Optimized Instances Enhanced Networking
• Follow standard Amazon EBS performance best practices outlined in the Amazon EC2 User Guide
• Amazon EBS General Purpose (SSD) volumes are recommended for most SAP system types
• Use EBS-optimized or 10 gigabit network instances for production systems
General Purpose (SSD) Provisioned IOPS (SSD) Magnetic
Recommend use casesBoot volumes
Small to med DBsMost SAP Systems
Extreme I/O intensive Large DBs Cold storage
Storage media SSD-backed SSD-backed Magnetic-backedVolume size 1GB- 1TB 1GB- 1TB 1GB- 1TB
Max IOPS per volume 3 IOPS/GB Burst up to 3000 IOPS 4,000 IOPS ~100 IOPS
Read and write peak throughput 128 MB/s 128 MB/s ~50-90 MB/s Max I/O per node(16k) 48,000 48,000 48,000
Peak throughput node 800 MB/s 800 MB/s 800MB/sLatency (random read) 1-2ms 1-2 ms 20-40 ms
API name gp2 io1 standard
Price* $.10/GB-Month $.125/GB-Month $.065/provisioned IOPS $.05/GB-Month $.05/ 1M I/O
General Purpose (SSD) Provisioned IOPS (SSD) Magnetic
Recommend use casesBoot volumes
Small to med DBsMost SAP Systems
Extreme I/O intensive Large DBs Cold storage
Storage media SSD-backed SSD-backed Magnetic-backedVolume size Up to 16TB Up to 16TB 1GB- 1TB
Max IOPS per volume 10,000 IOPS 20,000 IOPS ~100 IOPSRead and write peak throughput
per volume 160 MB/s 320 MB/s ~50-90 MB/s
Max I/O per node(16k) 48,000 48,000 48,000Peak throughput node 800 MB/s 800 MB/s 800MB/sLatency (random read) 1-2ms 1-2 ms 20-40 ms
API name gp2 io1 standard
Price* $.10/GB-Month $.125/GB-Month $.065/provisioned IOPS $.05/GB-Month $.05/ 1M I/O
Amazon EBS larger and faster volume types
Amazon EBS Deep Dive:https://www.youtube.com/watch?v=xtuRD2AZt3M
SAP Sizing made easy
Traditional Planning Horizon
Planning Horizon onAWS
Com
pute
Req
uire
men
ts
Physical Host XPhysical Host X
AWS HypervisorAWS Hypervisor
Virtual Machine
Physical HostPhysical Hardware
YPhysical Hardware
Y
AWS HypervisorAWS Hypervisor
SAP ECCVirtual Machine
SAP ECCVirtual Machine
• Running • Shutdown • SAP Virtual
Machine is unavailable
• Issue API Call to start Virtual Machine
• SAP Virtual Machine started on a new physical host
• EBS persistent Volumes are mapped by default
SAP ECCSAP ECC
Physical Host YPhysical Host Y
AWS HypervisorAWS Hypervisor
SAP ECCSAP ECC
• Running (new host)
What about Hardware Refreshes?
Change Instance type
using AWS Console or
API CallPhysical Hardware
XPhysical Hardware
X
AWS HypervisorAWS Hypervisor
SAP ECCSAP ECC
• Hardware upgrades in minutes!• No data migration required• Retain same IP addressing (VPC)
High Availability & Disaster Recovery
11 RegionsN. VirginiaN. CaliforniaOregonGovCloud USIrelandFrankfurtSingaporeTokyoSydneySao PauloChina*
11 RegionsN. VirginiaN. CaliforniaOregonGovCloud USIrelandFrankfurtSingaporeTokyoSydneySao PauloChina*
http://aws.amazon.com/about-aws/globalinfrastructure
AWS Global Infrastructure
28 Availability Zones
51 Edge Locations
28 Availability Zones
51 Edge Locations
* Limited public release
• Distinct locations engineered to be insulated from failures in other Availability Zones
• Connected via an inexpensive, low latency network
• An independent collection of AWS services in a defined geographical location
• Foundation for meeting location dependent privacy and compliance requirements
• Customer has full control. AWS does not move customer’s resources
• Contains two or more Availability Zones
AWS Regions and Availability Zones
Region
Availability Zone
Availability Zone
A
Availability Zone
B
Availability Zone
C
Sample US Region
Physical Host XPhysical Host X
AWS HypervisorAWS Hypervisor
Virtual Machine
Physical HostPhysical Hardware
YPhysical Hardware
Y
AWS HypervisorAWS Hypervisor
SAPVirtual Machine
SAPVirtual Machine
• Running • Host/Hypervisor Failure or loss of network connectivity
• SAP Virtual Machine is unavailable
Auto recovery for EC2
•SAP Virtual Machine started on a new physical host•EBS persistent volumes are mapped by default
SAPSAP
Physical Host YPhysical Host Y
AWS HypervisorAWS Hypervisor
SAP Virtual Machine
SAP Virtual Machine
• Running (new host)
Leverage AWS spare capacity for SAP High Availability
Physical Hardware X
Physical Hardware X
AWS HypervisorAWS Hypervisor
SAPSAP
Result:•Better uptime numbers, no waiting for hardware repairs•Leverage hardware spares at no cost
Cloud Watch Alarm
Detect & Trigger
Multiple Data Center High Availability
Availability Zone
A
Availability Zone
B
Availability Zone
C
Sample US Region
Multi-Region Deployments for Disaster Recovery
SAP environments can also be deployed in a multi-region deployment model as AWS Regions are dispersed and located in separate geographic areas.
Backup and Recovery of SAP Systems on AWS
The SAP on AWS Backup and Recovery Guide provides an overview of how to backup SAP systems running on AWS. The guide focuses on the essential differences in backing up SAP systems on AWS as compared to traditional infrastructure
Backup Options:
•Create Amazon Machine Image (AMI)
•EBS Snapshots
•Backup to EBS
•Push backup to S3 with AWS Command Line Tools
•RMAN direct to S3 with encryption via Oracle Secure backup (OSB)
Deploying SAP Systems
Deploying new SAP systems from scratch
The process to install an SAP solution on an Amazon EC2 instance is very similar to the process for any other physical or virtual server.
• Download SAP Software directly from service marketplace to installation or bastion host.
• Use EBS volume to maintain a repo of installation software
• Leverage installation and operations guides @ http://aws.sap.com/sap
• SAPInst & Download Manager require X Windows environment on Linux. (i.e. NoMachine)
• Use Windows Server or Amazon Workspaces instance as jump station
Deploying new SAP systems from scratch - Tips
Deploying new SAP systems from prebuilt images
Certain SAP solutions are available as pre-built images on Amazon EC2. A pre-built SAP system image contains a pre-installed and pre-configured SAP system that can be rapidly provisioned.
Deploying SAP HANA Systems (BYOL)
Networking
Amazon Virtual Private Cloud (VPC)
A private, isolated section of the AWS cloud where you can launch resources in a virtual network that you define
VPC
Enables connectivity between your network and VPC via a VPN or dedicated connection. Simplifies end user access and system integration
Amazon VPC Deep Dive:https://www.youtube.com/watch?v=HexrVfuIY1k
VPC
VPN Connection
AWS Direct Connect
VPN Connection •Encrypted IPsec hardware VPN connection between your network and VPC•Can create multiple VPN connections to one VPC•Fast and simple to setup
Internet
AWS Direct Connect•Dedicated network connection between your network and VPC•Can reduce network costs, increase bandwidth throughput, and provide a more consistent network experience•1 Gbps or 10 Gbps ports
Network requirements vary depending on deployment scenarioExample: Kellogg Accelerated TPM Hybrid Application Footprint
Corporate Data Center
Virtual Private Cloud
Availability Zone
VPC Subnet
BW ABAP 7.31 / NW JAVA 7.40
BW ABAP
2 X 244GB nodes
Internet
SAP OSS
BA
C
A = Virtual Private GatewayB = Customer GatewayC = Ipsec VPN Tunnel
SAP HANA
SAP HANA
BI-JAVA
SAP CRM SAP APO
Oracle DB Oracle DB
Users
Direct RFC Calls
Data Loads
Testing Network Bandwidth/Latency
Niping – Tool provide by SAP to test network latency and Bandwidth*
Start up Two sessions:
Receive Side: niping –s –P 3298
Send Side: niping –c –H hostname.domain –P 3298 –B kilobytes -L numloops
*See OSS Note 799428 for download information
Support and Monitoring
Support and Monitoring
To ensure full support of SAP solutions on AWS, you must follow the guidelines in SAP note # 1656250.
• AWS Business or Enterprise Support
• VPC required for production systems
• Amazon CloudWatch Detailed Monitoring must be enabled on each Amazon EC2 instance to ensure that the required AWS metrics are provided in one-minute intervals
• Install the AWS Data Provider for SAP
AWS Data Provider for SAP
Used by SAP DB/OS Cockpit and SAP Support to analyze performance issues
The data providers gathers:• AWS specific information
about instance type, instance id etc.
• Key system configuration (number of processors, main memory, disks etc.)
• Enhanced performance metrics
SAP OSS Note 1656250 - SAP on AWS Support prerequisites
SAP on AWS Support Notes
SAP OSS Support Queues for AWS
BC-OP-LNX-AWS (Linux)
BC-OP-NT-AWS (Windows)
XX-PART-AWS (AWS General)
SAP Note Description
1964437 SAP HANA on AWS: Supported AWS EC2 Products
1656099 SAP Applications on AWS: Supported DB/OS and EC2 Products
1588667 SAP on AWS: Overview of related SAP Notes and Web-Links
1656250 SAP on AWS: Support Prerequisites
1798212 Support for SAP HANA One
1758890 SAP HANA: Information needed by Product/Development Support
2058870 SAP B1: Version for SAP HANA on Public IaaS
Bringing Agility to SAP Landscapes
Provisioning and Management of AWS resources is completely self-service using the AWS API
AWS Resource Provisioning and Management
SDKs & LibrariesAWS CLIAWSManagement
Console
3rd PartyTools
JAVA.NETiOSPHP
RubyAndroidPythonNode.js
AWS CloudFormation
Enables the provisioning and management of a group of integrated AWS resources
Stacks of AWS resources are defined, deployed and managed in a single template file using JSON
SAP Use Cases•Provision complete SAP landscapes from a single template•Define and provision entire DR environment from a pre-defined and tested template
+
AWS CloudFormation
=Significant reduction in time for deployments from weeks to minutes with consistency, repeatability, & reliability
• Landscape configuration• Network layout• Security Policies• …
Amazon Machine Image (AMI)
• Software Installations
• Best practices• Configuration• …
Operate SAP Environments Differently
• Deploy infrastructure in minutes vs. weeks/months• Create additional environments for parallel testing efforts with
no long term cost burden• Run temporary stress test environments, then decommission• Frequently test disaster recovery processes without impacting
existing systems• Build once, deploy globally• Combine with other AWS services to derive additional value• Ability to scale on-demand
Scaling SAP Systems in a big way
111 SAP HANA Instances (1,776
CPU Cores) 8M Rows loaded per second (60
Billion Total) 220ms single node query (600
Million Rows) 330ms for federated query (60
Billion rows) Throughput of 3 million queries per
hour
Additional Details: http://bit.ly/scale-hana-aws
Customer Examples
Kellogg Uses AWS to Save $900,000 over 5 Years Over Using On-premises Infrastructure
Kellogg produces breakfast foods for more than 180 companies worldwide, with annual revenue of almost $15 B.
Using AWS saves us
$900,000 in infrastructure
costs alone, and lets us run
dozens of simulations a day
so we can reduce trade
spend. It’s a win-win.
• Needed a better way to track and model promotional costs (“trade spend”) to improve the bottom line—and needed to be able to run more than 1 trade-spend simulation/day
• Running SAP Accelerated Trade Promotion Planning (TPM) – Powered by SAP HANA
• By using SAP HANA on AWS, Kellogg estimates it will save $900,000 over 5 years versus traditional on-premises infrastructure alternatives
• Increased business agility: Company can run dozens of trade spend simulations each day, and decreases deployment time by 30x
• Leveraged existing SAP HANA software license investment on AWS
• Familiarity and Accessibility of the AWS platform enabled engineers to easily apply their existing knowledge and infrastructure skills
Stover McIlwainSenior Director of IT Infrastructure Engineering
”
“
SAP Business SuiteBackground
Hoya specializes in advanced optical technology and their finance department was serving about 100 subsidiaries WW. Hoya began looking for a cost effective, elastic and high performance environment to support their business and their current “private” cloud environment could not deliver this.
Additional Criteria:Security, SLA’s clearly defined, external audits in place, global footprint , highly reliable infrastructure
The Implementation:Cloud provider Selection: 0.5 monthsDR environment set-up, test and run : 1 monthMigration of production system: 48 hours
Customer Stated Benefits:
Speed and agility: rapid response to business requirements including M&A
Cost: 50-60% cost reduction, but when Hoya considered TCO they estimate about a 80-90% cost saving versus “private” cloud
Saved 50-60% on a cost basis
Estimated to save 80-90% on a TCO basis
Migrated production systems in 48 hours
Entire process from going to market for a cloud provider to full production about less than two months including testing and migration
SAP Implementation AWS Onboarding SAP OS/DB Migrations
SAP POCs SAP Sizing Architecture Planning
SAP Evaluations Performance Tuning SAP High Availability
SAP Hosting Backup & Recovery Account Management
Disaster Recovery DB Administration SAP BASIS
24/7 Help Desk OS Admin & Patching SAP Upgrades
APN SAP partners provide a variety of SAP specific services on top of the AWS platform
Consulting Services:
Managed Services:
AWS Partner Network: SAP Partners
http://aws.amazon.com/sap
Whitepapers and guides SAP Notes Support information AWS SAP Partners
Where to find resources for SAP on AWS
SAP HANA on AWS “Pilot” Program Offer• Customers may receive up to US$1,000 in AWS
Promotional Credits to evaluate SAP HANA on AWS.
• The credit will help fund AWS infrastructure costs for customers to trial SAP HANA through a choice of deployment methods:
• The SAP Business Warehouse (BW) Trial: http://www.saphana.com/bwonhanatrial
• The SAP ERP on HANA (SoH) Trial: http://try.saphana.com/erp
• The AWS Quick Start for SAP HANA: http://aws.amazon.com/quickstart
More information, including terms at: http://aws.amazon.com/sap/saphana/pilot
Thank you!
