AWS 101 and the benefits of Migrating to the Cloud

1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Patrick Hannah, VP of Engineering,
CloudHesive
IT Palooza 2017, December 7th, 2017
AWS 101 and the Benefits of
Migrating to the Cloud

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Introduction
• Who am I?
• What’s my background?
• What do I hope to get out of this presentation?
• How am I using AWS?
• What do I love about AWS?

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Who is CloudHesive?
We offer end-to-end solutions to migrate and securely operate our customer’s mission critical applications on the cloud
• Professional Services
• Assessment (Current environment, datacenter or cloud footprint)
• Strategy (Getting to the future state)
• Migration (Environment-to-cloud, Datacenter-to-cloud)
• Implementation (Point solutions)
• Support (Break/fix and ongoing enhancement)
• DevOps Services
• Assessment
• Strategy
• Implementation (Point solutions)
• Management (Supporting infrastructure, solutions or ongoing enhancement)
• Support (Break/fix and ongoing enhancement)
• Managed Security Services (SecOps)
• Encryption as a Service (EaaS) – encryption at rest and in flight
• End Point Security as a Service
• Threat Management
• SOC II Type 2 Validated
• Next Generation Managed Services
• Leveraging our Professional, DevOps and Managed Security Services
• Single payer billing
• Intelligent operations and automation
• AWS Audited

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What are we going to talk about?
• Use Cases
• Where to Start
• Approach
• Service Selection
• Resources
• Conclusion

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use Cases – You’ve probably heard of these
• Public Facing – eCommerce, Marketing, Web Hosting etc.
• Off the shelf software (Magento, Wordpress), heavily customized
• Starting to see DevOps Adoption
• Sensitive to scaling and security
• SaaS
• Home grown, can be either legacy (eg. written decades ago, never refactored) or “next generation” (microservices,
etc).
• Next generation users adopt new technologies and methodologies (first to Cloud, DevOps, etc.)
• Sensitive to scaling, security and cost
• Legacy Applications
• Shrink wrap software, supporting business (back office) operations
• Home grown, purpose built
• “The person who set this up isn’t here anymore”
• Data Analytics
• First to Cloud

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use Cases – But what about these?
• Enterprise
• Commercial software, thousands of users
• Infrastructure
• “Hands off” management of supporting infrastructure (for example, patching) + supporting
infrastructure itself (for example Active Directory)
• Desktop
• Hosted applications + Desktops
• Contact Center
• Hosted contact center
• Media
• Acquisition, transcoding, storage & streaming

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use Case - eCommerce
Customer Challenges:
• 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.
Solutions Provided:
• Assessed current technology footprint and produced a proposed architecture for deployment on the public cloud, ensuring the ability to recover in a disaster as well as be
highly available.
• Deployed infrastructure based on the developed architecture on SoftLayer and 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.
Benefits to the customer:
• 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.
Technology Utilized:
• Linux and Windows on AWS and SoftLayer
• Octopus Deploy
• .NET

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use Case - SaaS
Customer Challenges:
• 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.
Solutions Provided:
• 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 load balancers deployed as virtual machines).
• 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.
Benefits to the customer:
• 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.
• Innovates and deploys feature sets in a shorter timeframe.
Technology Utilized:
• Windows .Net , MSSQL on AWS

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Use Case – End User Computing
Customer Challenges:
• Customer had a mix of hardware, spread across multiple geographies, to support their customer base, making maintenance and support a challenge, as hardware was not
always in stock or had differing characteristics.
• Customer was over overbuilding their XenApp farms and supporting infrastructure (such as virtualization platforms, servers, storage and network infrastructure) in order to
handle peak customer demand.
• Customer had space capacity in other datacenters, which was intended to support disaster recovery of their primary datacenters, but was otherwise unused.
Solutions Provided:
• Assessment of on-premise datacenter infrastructure and total cost of ownership analysis between on-premise, Hybrid Cloud and Public Cloud solutions, providing the ability
to achieve cost savings on AWS.
• Development of datacenter consolidation roadmap along with execution of telephony Proof of Concept on AWS to aid in datacenter consolidation.
• Deployment of Citrix XenApp and XenDesktop on Hybrid Cloud and Public Cloud as well as development and implementation of Citrix XenApp and XenDesktop auto-scaling
(6.5 and 7.5+) to solve both scaling and disaster recovery challenges.
Benefits to the customer:
• Decreased operational cost and increased scalability - capacity can be provisioned on-demand rather than having to follow typical hardware procurement cycles.
• Decreased customer onboarding and offboarding cost – being the customer is in the contact center and business process outsourcing space, they encounter customer churn
and for each customer being onboarded or offboarded, there is a cost (in terms of effort) that is mitigated through automation of provisioning and deprovisioning.
Technology Utilized:
• Windows on AWS
• Citrix XenApp/XenDesktop and Netscaler

10. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Where do I start?
• Documentation available from AWS
• Documentation
• Community/Meetups/Github
• Wizards/Targeted E-Mails
• Reference Architecture/Quickstarts
• Ecosystem/Marketplace/Partners
• Best Practices/Trusted Advisor/PHD/Targeted E-Mails
• AWS Support
• AWS Training & Certification
• Interacting with AWS
• AWS Console
• AWS CLI, Tools, Tookits, SDKs and Mobile SDKs
• AWS Billing and Cost Management
• Keep Up to Date
• Blogs
• Whats New

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Adoption Approach
• Pick an Application to Migrate
• Document the Application
• Review the AWS service offerings
• Take a look at the Reference Architectures published by AWS
• Take a look at the AWS Marketplace
• Do the work (starting with non Production)
• Review (did you miss something), Document, Lessons Learned
• Move Production
• Review (did you miss something), Document, Lessons Learned

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Virtual Machines? Containers? Functions?
Virtual Machines
• AMI
• Patching
• Multi-threaded/Multi-task
• Hours to Months
• Per VM/Per Hour
Containers
• Container File
• Versioning
• Multi-threaded/Single-task
• Minutes to Days
• Per VM/Per Hour
Functions
• Code
• Versioning
• Single-threaded/Single-task
• Microseconds to Seconds
• Per Memory/Second/Per Request (Free Tier)

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Storage?
• Amazon S3 – large objects
• Amazon Glacier – archive data
• Amazon CloudFront – content distribution
• Amazon DynamoDB – simple non-relational data
• Amazon EC2 Ephemeral Storage – transient data
• Amazon EBS – persistent block storage with snapshots
• Amazon RDS – Automated, managed MySQL
• Amazon Redshift – Data warehouse workloads

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Enterprise Licensing
EC2
• AWS Instance Cost includes OS License
• Any additional software can be acquired through standard channels (direct, reseller, etc.) or through the AWS Marketplace
• AWS also offers preinstalled versions and editions of MSSQL as part of the AWS Instance Cost
RDS
• MSSQL or Oracle can be licensed through AWS, included as part of the AWS RDS cost or customers can supply their own
licenses (minimum of 27% savings for MSSQL)
Workspaces
• AWS Workspace Cost includes OS License
• Can bring your own license
Dedicated Hosts
• Host ID, Socket, Core Visibility
• Permits BYOL of Operating System License
• Supports Socket/Core based licensing where Software Licensing Agreements are not Cloud Aware
• Bare Metal in Preview

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Windows? Yes!
Infrastructure
• EC2 – Windows 2003 - 2016
• SSM – Windows Agent
• ECS – .net Core
• RDS – MSSQL
• Lambda – c#
• Elastic Beanstalk – .net
• OpsWorks – Chef for Windows
Enterprise
• Directory Service – AD compatible and AD directories
• Route53 - DNS
• CloudHSM – CryptoAPI
• WorkDocs – Windows Clients
• WorkMail – Outlook Clients
• Workspaces – Windows Clients + Windows Desktops
• AppStream 2.0 – Windows Clients + Windows Desktops
• Storage Gateway – iSCSI initiators
Development
• AWS CodeStar – Visual Studio Integration
• AWS CodeDeploy – Windows Agent
• X-Ray - .net
• Cloud9
• Tools/Toolkit for PowerShell/Visual Studio, SDKs (.net), CLI (Windows)

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Typical Stack
• Route53 (DNS) – feature rich
• CloudFront (Content Delivery Network)
• S3 (Object Storage, ideal for Static Content) – 3 flavors
• ELB (Load Balancing)
• ASG (Auto Scaling)
• EC2 (Virtual Servers)
• RDS (Managed Database) – numerous flavors
• ElastiCache (Managed Cache)
• SES (SMTP Gateway)

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Approaches
• Deploy existing apps in AWS with minimal re-design
• Good strategy if starting out on AWS, or if application can’t be re-
architected due to cost or resource constraints
• Primarily use core services such as EC2, EBS, VPC
Lift-and-shift
• Evolve architecture for existing app to leverage AWS services
• Gain cost and performance benefits from using AWS services such
as RDS, SQS, and so on
Cloud-optimized
• Architect app to be cloud-native from the outset
• Leverage the full AWS portfolio
• Truly gain all the benefits of AWS (security, scalability, cost,
durability, low operational burden, etc)
Cloud-native
architecture

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Options
• AWS Application Discovery Service – Agent based application discovery
• AWS Database Migration Service – Migration and replication of
same/disparate database platforms
• AWS Import/Export – BYOD “sneakernet” migration
• AWS Migration Hub – Ties Application Discovery and Server Migration
together
• AWS Server Migration Service – VMWare + Hyper-V integrated server
migration + replication
• AWS Schema Conversion Tool – Migration of same/disparate database
schemas
• AWS Snowball – 80 TB hardened storage device for “sneakernet” migration
• vmimport + vCenter Addon – VM Image or ISO import as an EBS Snapshot
or AMI

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Reference Architecture
• Simplified PDFs depicting, at a high level, an application
use case
• Deployment Guides provide detailed information around
deploying a specific application
• CloudFormation Templates provide deployment
templates to alleviate much of the manual work

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Marketplace
• Thousands of products/services available on the AWS
Marketplace to support DevOps needs
• Some delivered as services, some delivered as stacks
• Our approach is to partner with “one of each”, which
helps augment AWS’ offering and expand our
capabilities (many customers are already invested in a
solution
• Often, products traditionally deployed on-premise can be
found on the AWS Marketplace in pre-build appliance
images or CloudFormation Templates

21. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cloud Adoption Framework
• Business Stakeholders
• Business
• People
• Governance
• Technology Stakeholders
• Platform
• Security
• Operations

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Well Architected Framework (Five Pillars)
• Operational Excellence
• Security
• Reliability
• Performance Efficiency
• Cost Optimization

23. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Themes
• Design for failure and nothing fails
• Build security in every layer
• Leverage different storage options
• Implement elasticity
• Think parallel
• Loose coupling sets you free
• Don’t fear constraints

24. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Conclusion
• Plan out your migration
• Don’t unnecessarily overcomplicate (eg. start with one application, not an
entire datacenter)
• Know the application you are migrating
• Don’t forget interdependencies
• Be open to new ideas
• Utilize the vast AWS knowledge sources
• Define success criteria and benchmarks
• Document along the way
• AWS Adoption is an on-going process
• Evangelize

25. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Further Learning
• Getting Started: https://aws.amazon.com/getting-started
• General Reference: http://docs.aws.amazon.com/general/latest/gr
• Global Infrastructure: https://aws.amazon.com/about-aws/global-infrastructure/
• FAQs: https://aws.amazon.com/faqs
• Documentation: https://aws.amazon.com/documentation/
• Architecture: https://aws.amazon.com/architecture
• Whitepapers: https://aws.amazon.com/whitepapers
• Security: https://aws.amazon.com/security
• Blog: https://aws.amazon.com/blogs
• Service Specific Pages: https://aws.amazon.com/service
• SlideShare: http://www.slideshare.net/AmazonWebServices
• Github: https://github.com/aws and https://github.com/awslabs

26. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Meetups
• Boca Raton: https://www.meetup.com/awsflorida/
• Doral: https://www.meetup.com/AWSUserGroupDoral/
• Fort Lauderdale: https://www.meetup.com/South-Florida-Amazon-Web-Services-Meetup/
• Jacksonville: https://www.meetup.com/AWS-User-Groups-of-Florida-Jacksonville/
• Miami: https://www.meetup.com/Miami-AWS-Users-Group/
• Miami Beach: https://www.meetup.com/aws-user-group-miami/
• Orlando: https://www.meetup.com/Orlando-AWS-Users-Group/
• Palm Beach Gardens: https://www.meetup.com/AWS-Users-Group-of-Florida-Palm-Beach-
Gardens/
• Tampa: https://www.meetup.com/Tampa-AWS-Users-Group/
• Montevideo, Uruguay: https://www.meetup.com/Meetup-de-Amazon-Web-Services-AWS-en-
Montevideo/
• Asuncion, Paraguay: https://www.meetup.com/Meetup-de-Amazon-Web-Services-en-Asuncion/
• South Florida Jenkins Area Meetup: https://www.meetup.com/South-Florida-Jenkins-Area-
Meetup/

27. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Thank you!
sales@cloudhesive.com | https://cloudhesive.com