Come along to this session to learn how large scale systems like SAP, Oracle, Microsoft and others are being used by enterprise customers of all shapes and sizes. In this session you will discover some of the challenges and approaches that will make you successful in deploying and operating these systems on AWS. This is a must session for enterprise customers that are looking at moving material workloads into the cloud.
3. What You Will Learn
• Walkthrough the best practice for deploying business
critical applications
• Dive deep into fault tolerant and high performance
architectures
• Learn about AWS tools that will make you successful in
deployment and operations
4. Guest Speaker – Brad Barnett
• PageUp provides ‘Unified Talent Management’ solutions
for global customers
• Runs business critical HCM applications on AWS cloud
• Sharing their experience of deploying and operating
solutions on AWS
6. What is a Business Critical Application
Any applications that is core to running your business
• Enterprise Resource Planning
• Customer Relationship Management
• Data Warehouse & Reporting
• Human Capital Management
• Procurement
• Warehousing & Logistics
7. Business Applications on AWS
Vendor Applications
SAP Business Suite, Netweaver, BusinessObjects, B1, HANA
Oracle eBusiness, PeopleSoft, Siebel, JDE, Database 11g/12c
Microsoft SharePoint, Exchange, Dynamics, SQL Server
IBM Websphere, DataStage
Infor LN, M3, Syteline, Lawson
Today AWS customers run a wide array of business applications
Companies of all sizes run business applications on AWS
10. SAP on AWS – Benefits
All SAP Business Suite & Netweaver
Leverage multi-AZ for production workloads
Wide choice of EC2 & EBS volume options
S3 provides 99.999999999% durability
Enterprise-level security
Pricing, capacity management and operations
Certified Solutions
High Availability
High Performance
Durability
Security
Flexible
11. SAP & AWS Relationship
2008 20122010 2014
SAP as a
Customer
A1/B1
BOBJ
HANA Developer Edition
HANA One
Afaria
SAP HANA Platform Edition
SAP Business Suite
Cloud Appliance Library (CAL)
CustomerAdoption
Time
RDS Solutions
Sybase IQ / ASE
SAP HANA
for B1
12. • SAP Business Suite
• SAP Business All-in-One (A1)
• SAP Netweaver
• SAP HANA Platform
• SAP BusinessObjects BI
• SAP Mobile Platform
• SAP Business One
• SAP Rapid Deployment Solutions
SAP Solutions Certified on AWS
SAP Note 1656099 has latest information regarding SAP products and
platform supported on AWS
Solutions
13. SAP Supported Platforms on AWS
Operating System
• SUSE 11
• Red Hat 6
• Window Servers 2008
Database
• SAP HANA
• Sybase ASE 15.7
• MS SQL Server 2008
• IBM DB2 9.7
• SAP MaxDB 7.8
Version numbers for OS & DB are minimum levels
All higher versions are fully supported
14. Customer Network
Public Subnet
Users
On-Premises
Systems
SAP Router
Solution
Manager
Private Subnet
Internet
Availability Zone A Availability Zone B
Amazon Virtual Private Cloud
VPN or
Direct Connect
Amazon
CloudWatch Amazon S3
Backups
DB ReplicationSAP
DEV
SAP
QAS
SAP
DR
SAP
PRD
BackupsMonitor
SAP OSS
SAP High Level Architecture on AWS
Private Subnet
NAT
16. • Use SAP QuickSizer
• Choose an EC2 instance type based
on your SAPS and memory
• Choose an EBS volume type based
on your IOPS and storage size
SAP System Sizing for AWS
17. • AWS perform SAP SD Benchmarks on EC2 instances &
publish SAPS rating
• SAPS ratings are available for C3, C4 and R3 instance
families
• General Purpose and Provisioned IOPS EBS volumes
have predictable and consistent IO performance
Choosing Right EC2 & EBS Options
18. Compute Optimized (Application)
Name vCPU
Memory
(GiB)
I/O Perf
SAPS
(2-tier)
c4.8xlarge 36 60 10 Gigabit 37,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 60 10 Gigabit 31,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 (Database)
Name vCPU
Memory
(GiB)
I/O Perf
SAPS
(2-tier)
r3.8xlarge 32 244 10 Gigabit 31,920
r3.4xlarge 16 122 High 15,960
r3.2xlarge 8 61 High 7,980
r3.xlarge 4 30.5 Moderate 3,990
r3.large 2 15 Moderate 1,995
✓ Certified for 2-Tier and 3-Tier
configurations
Mapping EC2 Instance to SAPS
19. 0
40
80
120
160
Q1Y1 Q3Y1 Q4Y1 Q2Y2 Q4Y2 Q2Y3 Q4Y3 Q2Y4 Q4Y4 Q2Y5 Q4Y5 Q2Y6 Q4Y6
Demand
Traditional
AWS
Traditional Planning Horizon
Planning
Horizon on
AWS
ComputeRequirements
SAP Capacity Planning Made Easy
20. Choosing the Right EBS Volume
EBS Volume Options
• Provisioned IOPS (PIOPS)
• General Purpose (GP2)
• Magnetic
Larger & Faster Volumes
PIOPS
• Up to 16TB, 20,000 IOPS &
320MBps
GP2
• Up to 16TB, 10,000 IOPS &
160MBps
Enable EBS-Optimised Instance for dedicated capacity to EBS I/O
& minimise network contention
22. General Purpose Provisioned IOPS Magnetic
Use Cases
S to M Databases
Most SAP Systems
Large Database
I/O intensive
Cold Storage
Storage Media SSD-backed SSD-backed Magnetic-backed
Volume Size Up to 16TB Up to 16TB 1GB- 1TB
Max IOPS 10,000 IOPS 20,000 IOPS ~100 IOPS
Read/write
Peak Throughput
160 MB/s 320 MB/s ~50-90 MB/s
Latency (Random Read) 1-2ms 1-2 ms 20-40 ms
Price (Sydney Region) $0.12/GB-Month
$.138/GB-Month
$0.072/provisioned
$0.08/GB-Month
$0.08/ 1M I/O
Use Cases for EBS Volume Options
Amazon EBS Deep Dive
youtube.com/watch?v=xtuRD2AZt3M
23. SAP High Availability – Protecting SPOF
SAP systems have well known SPOF, namely;
1. Database – primary & standby DBs cross-AZ on EC2
2. Message Server (A/SCS) – primary & enqueue replication
server
3. Kernel (/sapmnt/SID/) – NFS, DFS, Amazon EFS (just
announced)
24. Customer Network
Users
On-Premises
Systems
Private Subnet
Availability Zone A Availability Zone B
VPC
VPN or
Direct Connect
Private Subnet
App1
DB
AppN
ASCS
App1
DB
AppN
ASCS
(ENQ)
Session State
DB Replication
SAP Production HA Architecture
EBS SSD EBS SSD
SAP Production (Primary)
26. Protect SAP Application Servers
You can protect your SAP application servers
• Scale out EC2 instances
• Enable EC2 Auto Recovery on APP & DB servers
27. SAP Backup and Restore
SAP on AWS Backup and Recovery Guide provides
comprehensive information
Backup options include;
• Use existing backup software and push into S3
• Backup to EBS and create snapshots
• Push backup to S3 with AWS CLI
• Oracle Secure Backup (OSB) Cloud Module
aws.amazon.com/backup-recovery/
28. Follow SAP support guidelines in SAP Note 1656250
Summary of requirements from SAP Note
• AWS Business or Enterprise Support
• Deploy production in Amazon VPC
• Enable CloudWatch Detailed Monitoring
• Install the AWS Data Provider for SAP
Support Requirements for AWS
29. Proactively Monitor Your SAP System
• Continue to use Solution Manager Diagnostics for SAP
application monitoring
• Use existing infrastructure monitoring tools
• Use CloudWatch Logs for capturing any SAP OS-level
logs in real time
• Incorporate log analytics – Sumologic & Splunk
30. Amazon CloudWatch Logs with SAP
• Use Amazon CloudWatch Logs to monitor and store your
SAP log files
• Upload any logs from SAP server, eg dev_trace,
db_trace, background files and upload into CloudWatch
Logs in real time
• Setup alerts and send notifications via email using SNS
• Retrieve logs via AWS Console, CLI & SDK
32. Bringing Agility to SAP Deployments
SDKs & LibrariesAWS CLIAWS
Management
Console
3rd Party
Tools
JAVA
.NET
iOS
PHP
Ruby
Android
Python
Node.js
Provisioning and management of AWS using the API tools is simple
33. • Define, deploy and manage AWS resources using
JSON templates
• Consistent & repeatable outcome
AWS CloudFormation and SAP
SAP Use Cases for CloudFormation
• Deploy SOE image for new installations in minutes
• Bootstrap instance to auto install SAP pre-req packages
• Clone production for isolated error analysis
• Setup disaster recovery environment
34. Amazon Machine
Image
• SAP Software
pre-installed
• Best practices
• Configuration
CloudFormation + SAP = Benefits
36. +
AWS
CloudFormation
=
Significant reduce
time to deploy
Consistent &
repeatable outcome
Clone new SAP
systems in minutes
• AWS landscape
configuration
• Network layout
• Security Policies
Amazon Machine
Image
• SAP Software
pre-installed
• Best practices
• Configuration
CloudFormation + SAP = Benefits
37. SAP Deep Dive – Recap
• Use SAP QuickSizer for sizing
• Choose the right EC2 & EBS options
• Protect SPOF – Multi-AZ deployment
• Protect app servers using EC2 Auto Recovery
• Proactively monitor your environment
• Comply with vendor support guidelines
• Use AWS tools for deployment and management
41. ▪ 6 virtual data centers in 4 AWS regions + 1 physical DC
▪ Approx. 230 EC2 instances deployed to 4 AWS regions
▪ Approx. 10 million daily page views across all DC’s
▪ Process approx. 1 million job applications / month
Some PageUp stats...
42. ▪ SaaS multi tenant application
▪ 99.5% uptime SLA requirement
▪ Largely Microsoft stack (IIS, .Net, SQL Server)
▪ Architected securely with a dedicated SQL Server database
per client
▪ Microsoft DFS, DPM
▪ CI / CD automated deployment
▪ S3, SQS, CloudWatch, Ylastic, NewRelic, SendGrid
About the technology
43. Circa 2007
▪ Adopted a conventional strategy for regional deployment
▪ Co-location in London
▪ Realised that long distance co-lo was not great
▪ Remote hands
▪ Costly
▪ Limited redundancy
Virtualisation to the rescue.
How we got here
44. Our next move….. an AWS false start
The wins:
▪ Removed issues with physical infrastructure
▪ Cheaper
However..
▪ No change in deployment / setup methodology
▪ No change in architecture
▪ Long lived application instances (pets)
▪ Software raided magnetic volumes for SQL
How we got here
45. Other realisations
▪ Long lived applications sprout roots
▪ Hard dependencies (IP’s, servers, endpoints)
▪ Patches to get things working, one time fixes build up
▪ Long lived infrastructure rots
▪ Tendency to upgrade less often
▪ “If it ain’t broken”
▪ Big bang upgrades
▪ Higher support costs
Our AWS false start
46. The trigger to do it right
▪ Due to international growth, we required additional regional data
centres
▪ Need to move from 1 to 6 DC’s
▪ How can we do this so we don’t have to scale our ops ?
Template and automate everything
The business needs more
47. Some simple rules we followed
▪ No single points of failure without automated recovery (ASG)
▪ “1 click” automated deployment / rollback
▪ All servers running PageUp code must be disposable
▪ No servers created without bootstrap scripts
▪ Move state off servers where possible
▪ Start a pine plantation over a rain forest
What we changed
48. So what were the outcomes?
▪ Ability to deploy daily to 6 data centres in 15 minutes
▪ No need to scale our Op’s team
▪ Faster and more scalable system
▪ Reduction in repeated ops issues
▪ New sales opportunities
What we changed
49. Some SQL Server learnings
▪ EBS optimized (no brainer)
▪ Understand your IOPS
▪ Size your volumes to IOPS requirements, not space.
▪ TempDB on ephemeral
▪ Start up scripts
▪ Backup / management / file transfer actions on ephemeral.
▪ Minimize dependence on AD for authentication
▪ Consider dedicated instances
Some learnings
50. ▪ Use mirroring or Always-On (ouch $)
▪ HA synchronous mirroring is still part of SQL standard
▪ Mirror between AZ’s
▪ 3rd AZ for witness where possible
▪ Favour small instances to reduce blast radius
▪ Run tests shutting down entire AZ’s to flush out failover issues
▪ Clients may not pickup failover immediately.
▪ Ensure you are using modern SQL client connection drivers (sqlncli 10+)
▪ Ensure you disable sql network protocol named pipes
Some learnings
51. Deployment tips
▪ Break down your monolith
▪ Use AWS templating or deployment tools where possible.
▪ Test your boot strap scripts
▪ Script your stateful infrastructure setup
Some learnings
54. • Amazon.com is one of Oracle’s largest customers
• Oracle was one of the first major ISV to support AWS,
since 2007
• Oracle Secure Backup for S3 was released in 2008
• Amazon RDS for Oracle in available 2011
• Oracle Test Drives program launched in 2012
AWS Oracle Partnership
55. AWS Customers Run Oracle Applications
• Oracle eBusiness Suite
• JD Edwards Enterprise One
• PeopleSoft
• Siebel
• Oracle Fusion Applications
• Agile PLM
• Hyperion
• ATG Web Commerce
56. Oracle Database on AWS
• Oracle Database 9i, 10g, 11g and 12c fully supported on EC2
• All editions of Oracle database are supported on EC2
Enterprise
Edition
• Any Instance type
Standard
Edition
• Up to 16 cores
Standard Edition
One
• Up to 8 cores
Express Edition
• Up to 4 cores
• &
• 1 GB mem
57. Oracle Products on AWS
MySQL
Enterprise Edition
TimesTen
MySQL
Community Edition
MySQL
Standard Edition
MySQL
Cluster CGE
Oracle NoSQL Coherence
Data Guard Active Data Guard Golden Gate RMAN OSB Enterprise Manager
Oracle DB EE Oracle DB SE Oracle DB SE ONE Oracle DB XE
Oracle Fusion Middleware
58. Oracle License Portability
Oracle software licenses are fully portable to AWS EC2
• Enterprise License Agreement (ELA)
• Unlimited License Agreement (ULA)
• Business Process Outsourcing (BPO)
• Oracle Partner Network (OPN)
Processor & Socket Licensing on AWS EC2
• Standard Licenses = 0.25 core multiplier
– 1 license for 4 virtual cores on EC2
• Enterprise Licenses = 0.5 core multiplier
– 1 license for 2 virtual cores on EC2
59. Oracle Apps on AWS – Dev/Test/POC
Customer Network
Users
On-Premises
Systems
VPC
VPN or
Direct Connect
Conc
Server
Oracle
DB
App
Server
Web
Server
Public Subnet
Public Subnet
Private Subnet Private Subnet
Private Subnet Private Subnet
Availability Zone A
Availability Zone B
S3 Bucket
Backup
60. Oracle App on AWS – Production with HA
Customer Network
Users
On-Premises
Systems
VPC
VPN or
Direct Connect
Conc
Server
Oracle
DB
Primary
App
Server
Web
Server
Public Subnet Private Subnet Private Subnet
Availability Zone A
Availability Zone B
S3 Bucket
Backup
Conc
Server
Oracle
DB
Standby
App
Server
Web
Server
Active
DataGuard
Replication
Public Subnet Private Subnet Private Subnet
AS Group
AS Group
61. EBS Volumes
High Performance Oracle Database
VPC
Oracle
DB on EC2
Private Subnet
Availability Zone A
PIOPS
Boot Redo Data Volume
ASM Striped
62. Oracle Database Performance Optimisation
• High performance Oracles database needs
– High & consistent IOPS
– Low latency & high bandwidth to storage subsystem
• Build high performance database on AWS
– Use GP2 or PIOPS EBS volumes
– Enable EBS-Optimised for dedicated path to IO
• Use Oracle ASM to manage database storage across multiple
EBS volumes
63. Simplify Backups with OSB Cloud Module
• Oracle Secure Backup (OSB) allows customers to backup Oracle
Databases directly to Amazon S3 using RMAN
• Data is compressed and encrypted in flight using Oracle Advanced
Security
• S3 provides high durability & encryption at rest (CSE/SSE)
• OSB is licensed by number of concurrent backup channels
64. Amazon RDS – Offload Your Workload
VSEBS Volumes
Oracle
DB
EBS Volumes
Oracle
DB
Complexity
Oracle on EC2 Oracle on RDS
Simplify
65. Benefits Details
Platform support MySQL, SQL Server, Oracle RDBMS, Postgres
Preconfigured Get started instantly with sensible default
settings. Fully configurable
Automated Patching Keep your database platform up to date
automatically
Backups Automatic backups and point in time recovery
and full DB backups
Failover Automated failover to slave hosts in event of a
failure
Replication Easily create read-replicas of your data and
seamlessly replicate data across availability
zones
Amazon RDS Benefits
66. Migration
Backup and recovery
Patching
Configuration management
Software upgrades
Storage upgrades
Frequent server upgrades
Hardware management
Amazon RDS Drives Productivity
Schema design
Query construction
Query optimization
Focus on the app “innovation”
Offload the “muck” to AWS
67. Oracle Deep Dive – Recap
• Oracle application, database and Fusion middleware are
supported on AWS
• Oracle licenses are portable to EC2
• Offload to Amazon RDS for Oracle for simplification
• Choose the right EBS storage options & use Oracle ASM
• OSB Cloud Module for backups to S3
68. AWS Resources for Business Applications
Find more information
aws.amazon.com/business-applications
aws.amazon.com/sap
aws.amazon.com/oracle
aws.amazon.com/ibm
Also check out
aws.amazon.com/whitepapers
aws.amazon.com/architecture