Moving from on-premise data centers to AWS cloud
- Organizes guidance into 6 Perspectives (areas of focus)
- each perspective addresses a distinct responsibility
- so the right people across the organization prepare for the changes ahead
- the Business, People, and Governance Perspectives focus on business capabilities
- the Platform, Security, and Operations Perspectives focus on technical capabilities
- Business Perspective
- ensures that IT aligns with business needs and that IT investments link to key business results
- use CAF to create a strong business case for cloud adoption and prioritize cloud adoption initiatives
- Common roles
- Business managers
- Finance managers
- Budget owners
- Strategy stakeholders
- People Perspective
- supports development of an organization-wide change management strategy for successful cloud adoption
- use CAF to evaluate organizational structures and roles, new skill and process requirements, and identify gaps
- helps prioritize training, staffing, and organizational changes
- Common roles
- Human resources
- Staffing
- People managers
- Governance Perspective
- focuses on the skills and processes to align IT strategy with business strategy
- ensures that you maximize the business value and minimize risks
- use CAF to understand how to update the staff skills and processes necessary to ensure business governance in the cloud
- Manage and measure cloud investments to evaluate business outcomes
- Common roles
- Chief Information Officer (CIO)
- Program managers
- Enterprise architects
- Business analysts
- Portfolio managers
- Platform Perspective
- includes principles and patterns for implementing new solutions on the cloud, and migrating on-premises workloads to the cloud
- use a variety of architectural models to understand and communicate the structure of IT systems and their relationships
- describe the architecture of the target state environment in detail
- Common roles
- Chief Technology Officer (CTO)
- IT managers
- Solutions architects
- Security Perspective
- ensures that the organization meets security objectives for visibility, auditability, control, and agility
- use CAF to structure the selection and implementation of security controls that meet the organization's needs
- Common roles
- Chief Information Security Officer (CISO)
- IT security managers
- IT security analysts
- Operations Perspective
- helps you to enable, run, use, operate, and recover IT workloads to the level agreed upon with your business stakeholders
- define how day-to-day, quarter-to-quarter, and year-to-year business is conducted
- align with and support the operations of the business
- CAF helps these stakeholders define current operating procedures and identify the process changes and training needed to implement successful cloud adoption
- Common roles
- IT operations managers
- IT support managers
- Each perspective is used to uncover gaps in the organization's skills and processes
- These gaps act as inputs to create an AWS CAF Action Plan that helps guide the organization for AWS Cloud migration
- These are generally the 5 phases in the cloud migration process
- Opportunity Evaluation
- Portfolio Discovery and Planning
- Application Design
- Migration & Validation
- Operation
- https://aws.amazon.com/blogs/enterprise-strategy/214-2/
- These are 6 most common migration strategies that you can implement when migrating to the cloud
- 6 Strategies for Migration
- Rehosting
- lift-and-shift
- moving applications without changes
- eg. a large legacy migration
- helps migrate and scale quickly to meet a business case (say, save costs)
- Replatforming
- lift, tinker, and shift
- making a few cloud optimizations to realize a tangible benefit
- optimization is achieved without changing the core architecture of the application
- eg. reducing the amount of time you spend managing database instances by migrating to a database-as-a-service platform like Amazon RDS, or migrating the app to a managed platform like Amazon Elastic Beanstalk
- Repurchasing
- moving from a traditional license to a Software-as-a-Service (SaaS) model
- eg. a business might choose to implement the repurchasing strategy by migrating from a CRM system to Salesforce.com
- Refactoring/re-architecting
- reimagining how an application is architected and developed by using cloud-native features
- driven by a strong business need to add features, scale, or performance that would otherwise be difficult to achieve in the application's existing environment
- eg. migrating from a monolithic architecture to a service-oriented (or serverless) architecture to boost agility or improve business continuity
- tends to be the most expensive, but may also be the most beneficial
- Retaining
- don't move to AWS Cloud yet!
- keeping applications that are critical for the business in the source environment
- might include applications that require major refactoring before they can be migrated, or, work that can be postponed until a later time
- Retiring
- don't move to AWS Cloud
- in fact, remove applications that are no longer needed even from the source environment!
- Rehosting
- transporting large amounts of data into and out of AWS can take a very long time
- eg. A network of 1 Gbps speed moves 1 PB of data about 100 days (and likely longer)
- this is both time-consuming, and costly!
- AWS Snow Family Members
- a collection of physical devices that help to physically transport up to exabytes of data into and out of AWS
- different capacity points
- include different levels of built-in computing capabilities
- optimize for space-constrained or weight-constrained environments
- optimize for portability
- flexible networking options
- data moved to AWS Snow Family devices is automatically encrypted with 256-bit encryption keys that are managed by AWS KMS
- once received at the AWS data center, AWS verifies and copies the data (usually an S3 bucket)
- once the data migration job is complete and verified, AWS performs a secure software erasure of the device
- these devices have computing resources so as to collect and process data at the edge
- they fit into existing server racks at AWS data centers
- devices can support Amazon EC2 instances, AWS IoT Greengrass functions, and Kubernetes deployments on Amazon EKS Anywhere
- once plugged in on these server racks, you can run EC2 instances on them, cluster them, run lambda functions etc.!
- customers usually ship these devices to remote locations where computing is not available but needed
- eg. capturing of streams from IoT devices
- industrial signalling
- image compression
- video transcoding
- Three types
- AWS Snowcone
- small, rugged, and secure edge computing and data transfer device
- features 2 CPUs, 4 GB of memory, and 8 TB of usable storage
- AWS Snowball
- Snowball Edge Storage Optimized devices
- well-suited for
- large-scale data migrations
- recurring transfer workflows
- local computing with higher capacity needs
- provides 40 vCPUs, and 80 GB of RAM, 80TB HDD or 210TB NVMe capacity for Amazon S3-compatible object storage (the 210TB device only supports data migration use cases)
- well-suited for
- Snowball Edge Compute Optimized devices
- provide powerful computing resources
- well-suited for
- machine learning
- full motion video analysis
- analytics
- local computing stacks
- 104 vCPUs, an optional NVIDIA Tesla V100 GPU, 416 GiB of memory, 28 TB usable NVMe SSD capacity for Amazon S3 compatible storage or EBS-compatible block volumes. Snowball Edge Compute Optimized devices run Amazon EC2 sbe-c and sbe-g instances, which are equivalent to C5, M5a, G3, and P3 instances
- Snowball Edge Storage Optimized devices
- AWS Snowmobile
- an exabyte-scale data transfer service used to move large amounts of data to AWS.
- transfer up to 100 petabytes of data per Snowmobile, a 45-foot long ruggedized shipping container, pulled by a semi trailer truck
- AWS Snowcone
- When examining how to use AWS services and innovate, it is important to focus on the desired outcomes. You need to clearly understand
- The current state
- The desired state
- The problems you are trying to solve
- Some options you might explore in the future as you continue on your cloud journey
- Serverless Applications
- applications that don't require you to provision, maintain, or administer servers
- no need to worry about fault tolerance or availability, as AWS handles these
- if you design your architecture to trigger Lambda functions to run your code, you can bypass the need to manage a fleet of servers
- enables your developers to focus on the core product instead of managing and operating servers
- applications that don't require you to provision, maintain, or administer servers
- Artificial Intelligence
- AWS offers a variety of services powered by artificial intelligence (AI).
- convert speech to text with Amazon Transcribe
- discover patterns in text with Amazon Comprehend
- identify potentially fraudulent online activities with Amazon Fraud Detector
- Build voice and text chatbots with Amazon Lex - this service forms the core of Alexa!
- AWS offers a variety of services powered by artificial intelligence (AI).
- Machine Learning
- Traditional Machine Learning (ML) development is complex, expensive, time consuming, and error prone
- AWS offers Amazon SageMaker, Amazon Augmented AI (A2I) to remove the difficult work - empowers you to build, train, and deploy ML models quickly
- AWS DeepRacer - a 1:18 scale race carto test your reinforcement learning models!
- use it to analyze data, solve complex problems, and predict outcomes before they happen
- Other types of services
- IoT services
- AWS Ground Station - satellite communication service
- Serverless Applications
- AWS DataSync
- secure, online service that automates and accelerates moving data between on premises and AWS Storage services. DataSync can copy data between Network File System (NFS) shares, Server Message Block (SMB) shares, Hadoop Distributed File Systems (HDFS), self-managed object storage, AWS Snowcone, Amazon S3 buckets, Amazon EFS file systems etc.
- https://aws.amazon.com/datasync
- AWS Transfer Family
- seamlessly migrate, automate, and monitor file transfer workflows into and out of Amazon S3 and Amazon EFS using the SFTP, FTPS, and FTP protocols.
- quickly and securely transfer files between your partners, vendors, and customers, into and out of Amazon S3, using the AS2 protocol
- SFTP connector simplifies copying data between remote SFTP servers and Amazon S3
- https://aws.amazon.com/aws-transfer-family
- AWS Application Migration Service
- Move and improve your on-premises and cloud-based applications
- Migrate applications from any source infrastructure that runs a supported OS
- Modernize applications during migration with options such as disaster recovery and OS or license conversion
- Maintain normal business operations throughout the application replication process
- AWS Cloud Adoption Framework (AWS CAF)
- AWS Cloud Adoption Framework (AWS CAF)
- Considering a Mass Migration to the Cloud?
- 6 Strategies for Migrating Applications to the Cloud
- A Process for Mass Migrations to the Cloud
- AWS Snow Family
- AWS Snowcone
- AWS Snowball
- AWS Snowmobile
- Migrate and Modernize on AWS
- AWS Cloud Essentials - Getting Started Guide
- AWS Cloud Enterprise Strategy Blog
- Modernizing with AWS Blog
- AWS Customer Stories: Data Center Migration