In order to increase business agility and reduce costs, a large number of enterprise customers are moving their entire SAP landscapes, including their production environments, to AWS. Some examples of enterprise customers running their core businesses on AWS are BP, Kellogg’s, Brooks Brothers, AIG, and Ingram-Micro. In this session, hear how customers are running mission-critical workloads on AWS, and understand how we guide Fortune 50 companies as they rapidly adopt emerging technologies and accelerate greater innovation on AWS.
8. 1405002
8
1405002
8
• Bread and butter is computer hardware distribution
• Shipping and invoicing physical things
• Inventory management and logistics
• Cloud doesn’t involve physical things
• Significant technical and organizational autonomy
• Operate cloud marketplaces around the world
10. 1405002
10
1405002
10
• Decades of experience shipping, and invoicing boxes
• Business tools had no concept of monthly subscription
• Cloudblue is core of cloud unit tech stack
− Formerly Odin System Automation
• New SAP deployment required for subscription model
Why SAP?
11. 1405002
11
1405002
11
• Cloud first mandate
• Only AWS supported production HANA workload in VM
(at the time – not the case now)
• Familiarity with the platform
• Cost, both savings and flexibility
Why AWS?
16. 1405002
16
1405002
16
• Several designs were considered, including with HA
• Cost was a factor, paired with a clear eyed understanding of true
business need.
• SAP not needed to transact means we have scope to lower
costs by sacrificing RTO.
• Design explicitly allows for additional components required for
HA solution.
DR without HA? That’s weird …
17. 1405002
17
1405002
17
• Primary HANA DB replicates to secondary via HSR
• Incron configured on primary DB to watch for incremental
and transaction logs
− As soon as filesystem event is seen, upload file to a local Amazon
S3 bucket
− Amazon S3 cross-region replication copies file to Ohio
• Weekly HANA backup is timed before weekly AMI backup
HANA DR in Depth
18. 1405002
18
1405002
18
• Went to war with the army we had
− Deep host level config management
− Limited IaaS automation
• Deployed hosts with custom scripts and CSV
• SAP infrastructure doesn’t change much
• Host level management more important after day 1
IaaS Automation
19. 1405002
19
1405002
19
• SAP managed by Basis team, not puppet
• Puppetized components include:
− Integration with Active Directory
− Host firewall
− Backups
• Automation boundary follows team responsibility boundary
Puppetized SAP?
21. 1405002
21
1405002
21
• Cloud BU given technical and organizational autonomy
− Customer facing services
− Internal corporate IT
• Great approach for reducing red tape
• Can make it hard to work together
Different Business Units, Different Perspectives
22. 1405002
22
1405002
22
• Unfamiliarity with the capabilities of cloud services
• Assumptions about capabilities they expect
• Unaware of capabilities they haven’t encountered
• Especially problematic when dealing with security policies
Talking Past Each Other
23. 1405002
23
1405002
23
• Flexibility and trust goes a long way
• Support from executive management
− Approval for non-standard solutions
• Phone calls and video conferences
− Harder to say no face to face
Making It Work
24. 1405002
24
1405002
24
• Watch out for bikeshedding
− Build twice
− Keep one
• On-premises mindset encourages careful analysis
• Try running twice the environment for a week instead
Remember the Cloud’s Elastic
25. 1405002
25
1405002
25
• Automate for long-term management
• Always consider if the extra effort is wasted effort
• Assume good intentions
• Less talking, more doing
Thanks!
26. 26Confidential and proprietary information of Ingram Micro Inc. — Do not distribute or duplicate without Ingram Micro's express written permission. 26