5. Our Approach – Quick Wins
• Start with quick wins
• Quickly show value to the business; use the success story to evangelize
• Move from theory to real-world
• Show incremental improvement with minimal/no change to operations
• What works a quick win?
• Applications with minimal dependencies or dependencies that can be
reproduced with minimal lifting
• Use Case Specific: Contact Center, End User Computing, Media
• Platform Specific:Web Applications
6. Our Approach – Assessments
• Preliminary Assessment
• Typically performed before the execution of a Statement ofWork
• Understand drivers, applications, inventory, constraints and success criteria
• Any immediate opportunities for improvement?
• Detailed Assessment
• First step after execution of a Statement ofWork
• Understand application dependencies (service <-> service, software, etc.)
• Understand order of operations for migration and approach
7. Our Approach – Migration
• Destination (Landing Zone) Planning and Implementation
• Prepare AWS accounts to meet customer specific Security, Networking, IAM,
Directory and Architecture needs
• Prepare customer organization for shift to AWS
• Ensure processes are in place to support migration
• Migration Planning/Migration Start
• Plan migration sprints (again by dependency and type of migration)
• Execute migration sprints
• Measure migration sprints
8. Our Approach – Post
• Post Migration
• Customer Enablement
• Customer CCoE
• Managed Services
9. Customer Reference
• Industry
• Construction
• Application
• Capital program and project management software
• Challenge:
• Customer previously relied on three separate colocation providers in two countries to support their customer base
• Customer had a mix of hardware deployed and was leveraging various infrastructure components (virtualization, server, storage and
network) that were prone to failure, non performant or incapable of scaling
• Customer’s technical operations team was spending most of their time maintaining hardware, rather than supporting the business
11. Customer Reference – After, Day 1
• Approach
• Performed an initial assessment of their infrastructure footprint and built a proof of concept on AWS, proving technical capability of the platform, and
utilizing AWS managed/abstracted services in lieu of traditional infrastructure solutions (such as elastic load balancing in place of f5s)
• Performed a phased migration, starting with their Disaster Recovery site, moving on to their Primary site after successful Disaster Recovery testing and
finally, non-critical services and environments
• Solved customer defined data residency requirements by deploying customer’s infrastructure in AWS GovCloud (in under a month) as well as AWS Canada
(within one week of public GA)
• Provided ongoing operational and security monitoring and management of infrastructure, implementing custom automation solutions where required
• Results
• Customer is able to respond to growth of their customer base without procuring additional hardware
• Customer is able to manage their entire software development lifecycle on a single infrastructure platform
• Customer is able to introduce new services into their product and consume new services in AWS without heavy lifting
• Customer is able to innovate and deploy feature sets in a shorter timeframe
12. Customer Reference – After, Day 365
• Challenge
• Frequent operational intervention required to keep servers healthy
• Application, Middle and PersistenceTiers Operating System Dated (2008 R2)
• DatabaseTier Dated (2008 R2 SP3)
• Approach
• Implemented orchestration to restart services when certain thresholds were crossed
• Application and MiddleTier Servers were phased out (ELB) with new servers (2012) phased in
• New database servers provisioned (2012), moving to Always On Availability Groups
• Results
• Less operational overhead; less downtime
• Able to take advantage of new IIS features, newWindows Features, and ensure a mid-term roadmap to support
• Able to take advantage of new SQL features, newWindows Features, ensure a mid-term roadmap to support and provide for better
high availability/load distribution options
13. Customer Reference
• Industry
• Retail
• Application
• Oracle Commerce Platform (eCommerce)
• Challenge
• Oracle announced that they would be shutting down the legacy datacenters used to host Oracle Commerce Platform customers
• Migration timeline was extremely tight; platform infrastructure specifics were unknown
• Customer required assurance that appropriate security controls were deployed to protect the environment
• Tight integration to third parties, corporate datacenters, and retail infrastructure required detailed coordination
• Existing deployment process needed to be maintained to ensure the continued ability to deploy while maintaining the integrity of
the environment
15. Customer Reference – After
• Day 1
• Launched new instances with corresponding Operating SystemVersions (2008 R2)
• Deployed corresponding MSSQL Edition,Version, SP
• Data migration test run
• Data migration cutover
• Mirroring setup
• Day 365
• Launched new instances with newer Operating SystemVersions (2016)
• Deployed newer MSSQL Edition,Version, SP (SQL 2012)
• Data migration test run
• Clustering setup
• Data migration cutover
16. Customer Reference
• Industry
• Travel & Hospitality
• Application
• eCommerce, Internet Booking Engine
• Challenge
• Customer’s internal infrastructure team was unable to keep up with requests from the business, for
example, new applications would wait months before infrastructure was available to support them
• Customer’s infrastructure was unable to scale to support their customers’ unanticipated peak demands
(being in the travel and hospitality industry, sales would drive traffic to their site)
• Customer wanted to be able to deploy new releases on-demand rather than wait for their
configuration management team to deploy
18. Customer Reference – After, Day 1
• Approach
• Assessed current technology footprint and produced a proposed architecture for deployment on the public cloud,
ensuring the ability to account for high availability requirements
• Deployed infrastructure based on the developed architecture on AWS
• Developed and benchmarked a cloud agnostic auto-scaling solution with automated deployments, allowing for on-
demand releases and the ability to bring new workers online within 15 minutes
• Results
• Faster customer onboarding – new customer infrastructure can be provisioned in less than a day
• Ability to quickly respond to unanticipated peak volume periods – less than 1 hour versus what was previously 8
hours
• Faster application performance – newer hardware and services (elastic load balancing) designed for performance at
scale
• Increased uptime – high availability and disaster recovery are inherently built into AWS
19. Customer Reference – After, Day 365
• Challenge
• Since initial deployment, general availability of OS and DB versions has changed
• Since initial deployment,
• Since initial deployment, customer’s global footprint has increased
• Approach
• App tier is as easy as changing AMI in Launch Configuration
• RDS can be upgraded in-place
• AdditionalAWS services can be leveraged for bootstrapping (SSM)
• Results
• Latest IIS and Operating system features available to application
• Latest SQL features available to application
• Less customization of supporting infrastructure; lower maintenance burden (technical debt)
20. Conclusion
• There are excellent models for the adoption of AWS and migration of
on-premises based services to AWS that can be adopted to your
organization
• AWS services allow you to ease into AWS – starting from lift ‘n’ shift
to optimized workloads to serverless
