Boot camp - Migration to AWS
-
Upload
amazon-web-services -
Category
Business
-
view
3.115 -
download
5
Transcript of Boot camp - Migration to AWS
Migration to AWSWorkload Qualification for the Cloud
Partner Solution Architect – Dinah [email protected]
Building a Cloud StrategyCloud Benefit
sZero upfront investment
On-demand provisioning
Instant scalability
Auto scaling and elasticity
Pay as you go
Removes undifferentiated heavy lifting
Developer productivity
Automation
CloudStrategy
New applications
Build a Cloud-Ready
Design
Existing Applications
“No-brainer to move” Apps
Planned Phased Migration
Startup or
SMB Firmor
Large Enterprise
Typical Fortune 100 Enterprise Customer Multiple, diverse business units
Complex environment latent with legacy process and siloed
Leadership is a mix between tenured executives and new change agents
Politically charged
Conservative and risk averse security posture
Proud of their “Private Cloud”
Minimal experience leveraging true cloud services, but with spots of exposure
Portfolio of hundreds or thousands of small applications and a few large
applications
Where to Start
Cohesive approach (Sales, Partners, SA, ProServe & Support) Remember that technology is only a piece of the puzzle Obtain Executive Sponsorship (Client & AWS) Identify and grow champions Leverage assets from Cloud Adoption Framework Present a Solution, not pieces and Parts Value Sell
THINK BIG!
App Migration Patterns
• Virtual Machine Import– Bulk migration using VM Import or 3rd party tools– Garbage in, garbage out
• Manual Clean Install– Often quickest way to deploy the application one-time– Works-of-art that can’t be recreated
• Automated Deployment – Highly repeatable process– Requires scale to get return on investment
Cloud Migration: A Phase-Driven Strategy
http://aws.amazon.com/whitepapersOur Focus Today
Recommend !
Application Migration Methodology
Improvement
AWS
Clou
d Ad
opti
on F
ram
ewor
k (C
AF)
Initiate Discover Design Migrate Integrate Validate Operate Optimize
Analysis Operations
Strategy Transition Design
AWS
Mig
ratio
n Pr
oces
s
Application Analysis
Migration Design
(Planning)Migration Integration Validation
Operate/ Optimize
Business Strategy
& Objectives
Continuous Migration Evaluation and FeedbackContinuous Migration Evaluation and Feedback
App Migration Iterative Sprint
Migration Factory
Prioritized Migration List
Migration Candidates
Migrated Applications
Application Portfolio Discovery
Migration Initiation
· Execution Plan· Process & tools
refinement
· Capture Infrastructure· Move Apps/Infra/Data· RightSizing AWS Resources
· Application Integration· Infrastructure Integration· Operational Integration
· Functional Validation· Secure ACL· BU Acceptance
· Monitoring· Optimization· Support
· Services Enablement· Baseline Foundations· Architect Target Env
· App Portfolio Assessment
· Build Pipeline
90% Automation 30% Automation50% Automation50% Automation 50% Automation
· Cloud Fit Assessment· App Selection &
Prioritization
Step 1 of 6: Classifying your IT AssetsDashboard
Report
CRM
Search
DB
logs
ServiceLDAP
AuthWeb
EngineOLAP
ERP
List all your IT assetsIdentify upward and downward dependenciesStart classifying your IT assets into different categories:
– Applications with Top Secret, Secret, or Public data sets
– Applications with low, medium and high compliance requirements
– Applications that are internal-only, partner-only or customer-facing
– Applications with low, medium and high coupling
– Applications with strict vs. relaxed licensing
Stack rank your IT assets and select the low-hanging fruit first
• Search for under-utilized IT assets• Applications that has immediate business need to scale• Applications that are running out of capacity• Easiest to move today• That Builds support within your organization and creates
awareness and excitement
Step 2 of 6 : Know TCO Cost AssumptionsPricing Model One-time Upfront Monthly
AWS Co-lo On-Site AWS Co-lo On-Site
Server Hardware 0 $$$ $$ $$ 0 0
Network Hardware 0 $$ $$ 0 0 0
Hardware Maintenance 0 $$ $$ 0 0 0
Software OS 0 $$ $$ $ 0 0
Power and Cooling and Data Center Efficiency 0 0 $$ 0 0 $
Data Center/co-lo Space 0 $$ $$ 0 0 0
Personnel 0 $$ $$ $ $$ $$$
Storage and Redundancy 0 $$ $$ $ 0 0
Bandwidth $ $$ $ $$ $ $
Resource Management Software 0 0 0 $$ $ 0
Total
Step 3 of 6: Security and Compliance Assessment
Involve your Security
Teams early in the process
· You own the data, not AWS.· You choose which geographic location to store the data. It doesn’t move
unless you decide to move it.· You should consider the sensitivity of your data and decide if and how you will
encrypt your data while it is in transit and while it is at rest.· Many of your IT, Risk, Compliance and Audit requirements can be met by
AWS Reports (SAS 70) and external certifications (IS27001, PCI, FISMA)..AWS Certification list continues to grow
· You can download or delete your data whenever you like.· You can set highly granular permissions to manage access of a user to specific
service operations, data, and resources in the cloud for greater security control.
Step 4 of 6: Technical Assessment of your app
• Cloud-readiness Criteria Checklist– Hardware
• CPU• Memory• Network• Specialized hardware
– Software• OS, Virtualization• Database
– Security• VPN-related• Security Hardware
– Storage• Block-level, Blob, Key-value
Picking Optimal Workloads•Low Up-Down Dependencies are Good
– Web Front (or SaaS): database, indexer, login, authentication, billing, payment (few 3rd party)
– Back-end: workflow systems, logging and reporting systems and ERP or CRM systems
•Best Candidates = low dependencies– Examples: Backup, Batch Processing, Log
Processing, Test & Dev., Content management system (share point), demos, training, pre-sales
– Tip: Deprioritize applications that require specialized hardware to function (for example, mainframe or specialized encryption hardware).
•Non Technical Criteria– Underutilized Assets
– Business urgency to scale (lost revenue, competitive advantage)
– Running out of capacity
– Need to scale – unpredictable or random peak workloads
– Global footprint and consistency needed (marketing, transaction systems)
– In-house IT expertise is stretched
– Cash flow sensitive business
– Competitive pressures
– Application Owner Unhappy with Central IT (slow)
Prioritize the List, Key Questions•Prioritize Candidates
– Maximize the exposure (compute, storage, network, database)
– Build support and awareness with key stakeholders
– Map to stakeholder motivations/incentives
•Ability to Leverage– Resource Management Tools
– Resource Configuration Tools
– System Management Tools
– Integration Tools
•Key Questions (with your SA)– Will architecture map to cloud, what needs to be
modified?
– Can the application be virtualized; special H/W requirements
– Is your app software license friendly for the cloud?
– Is migration effort low….high?
– What needs/must be on premise vs. cloud
– What are the latency, bandwidth requirements?
– Is Identity, security, compliance possible? What does it take.
– Licensing restrictions – BYOL, Utility, SaaS
Proof of Concept?•Get your feet wet with AWS
– Learning AWS
– Build Reference architecture
– Represent a microcosm of your app
– Be aware of the security features
•Build a Prototype/Pilot– Build support in the organization
– Validate the technology; mini-POC
– Perform benchmarks and set expectations
– Assess if it helps you make a case to move fast
• Free Tier: The free tier can be used for anything you want to run in the cloud: launch new applications, test existing applications in the cloud, or simply gain hands-on experience with AWS. http://aws.amazon.com/free/
• AWS Essentials and AWS Architecture Training– Great way to understand AWS Services
– Learn together in a group
• Leverage QwikLab: Over 30 self-paced labs to practice, test and learn about latest AWS services
https://run.qwiklab.com/
Common 1st and 2nd Workloads•Dev & Test (iterate)• Web Apps (tightly-coupled)• Content Management (SharePoint)• Backup, Archival (stand-alone, Glacier
@.001)• E-Commerce• Big Data Projects (cost prohibitive)• IT Operations (internal) – Help Desk,
Directory• Virtualized Apps
• Production• Mobile• PowerView• DR, Warm Stand-By, Hybrid• CRM• Business Intelligence• Continuous Integration, Continuous
Development (Agile Development)
Migration Strategy – Two Scenarios•Forklift Candidates
– Stateless
– Tightly coupled
– Self-contained
– Low-latency b/n tiers
•Move to Cloud Model Easy– Physical > Amazon EC2 (AMI)
– Fileserver > Amazon S3, Amazon EBS
– Firewall > Security Group
• Helps shrink your physical footprint and operational burden
•Phased Migration Candidates– On-premise: for compliance reason
– On-premise: Data security
•For Web App Example (Hybrid)– Batch, Log, Indexing > Cloud
– Customer-facing is > On Premise
– Requires some components to be “cloud aware” (e.g. data-ingestion)
– Requires temporary “wrappers” to enable on premise and cloud apps communicate with each other.
– VPN tunnels between legacy on premise and cloud components
… Often a phased approach is the better long term strategy
Step 5 of 6: Define your Success Criteria
Cloud has never been just
about saving money
“ “· Developer Productivity· Business Agility· Reduced Time to Market· Data center efficiency· Redundancy· Chargeback and Billing· Eliminates “Heavy lifting”· Foundation of 21st century architectures· Reduced waste/recycle· Hardware upgrades· Less number of 24/7 Personnel
Step 5 of 6: Define your Success CriteriaSuccess Criteria Old New Examples on
How to Measure
Cost (CapEx) $1M $300K 60% savings in CapEx over next 2 years
Cost (OpEx) $20K/Year $10K/Year Server-to-Staff ratio improved by 2x4 maintenance contracts discontinued
Hardware procurement efficiency
10 machines in 7 months
100 machines in 5 minutes 3000% faster to get resources
Time to market 9 months 1 month 80% faster in launching new products
Reliability unknown Redundant 40% reduction in hardware-related support calls
Availability 99.99% uptime 99.999 uptime 20% reduction in operational support calls
Flexibility Fixed Stack Any Stack Not locked into particular hardware vendor or platform or technology
New Opportunities 10 projects backlog 0 backlog, 5 new projects identified 25 new projects initiated in 3 months CEO
CFO
CFO
LOB
VP-IT
VP-IT
Building a Cloud Adoption Pattern
http://d0.awsstatic.com/whitepapers/aws_cloud_adoption_framework.pdf
Limits, Biases
(rethink)ProcessMaturity
BusinessPeople
Security
Platform
Operations Parking Lot
(reconsider)
Step 6 of 6: Invest in Proof of Concept Early
Proof of concept will
answer tons of questions
quickly
·Get feet wet with Amazon Web Services– Learning AWS
– Build reference architecture
– Be aware of the security features
·Build a Prototype/Pilot– Build support within organization
– Validate the technology
– Test legacy software in the cloud
– Perform benchmarks and set expectations
http://awstestdrive.com
Exercise: Resources and Next Steps• Identify a scenario you believe has applications:
– That are “no-brainer”– That are early optimal candidates– That require a more careful phased migration
• Read the AWS Migration White Paper• Share the White Paper
– Have a TCO conversation; suggest a preliminary Solution Architect conversation
• Think Free Tier or a QwikLab• Think PoC; identify a few success metrics
Further Reading
Cloud Migrationhttp://media.amazonwebservices.com/CloudMigration-main.pdf
RDS Migration Toolhttps://s3-us-west-2.amazonaws.com/rdmt/AmazonRDSMigrationToolUserGuide.pdf
Strategies for migrating oracle databasehttps://d0.awsstatic.com/whitepapers/strategies-for-migrating-oracle-database-to-aws.pdf
Quiz!
For existing on premise workloads good early AWS cloud candidates are those that : Early PoC candidates should be:
a) workloads with multiple dependencies
b) Small workloads that will mimic a key use case
c) That could motivate multiple stakeholders
d) Those that can show a clear ROI
a) Have reached capacity thresholdsb) Have significant unutilized
resourcesc) Have a unique hardware
requirementd) Are customer facing and revenue
generating
1 2