Migrating to AWS by Jeff Armstrong -- Read -- Imperial Library of Trantor

Index

Foreword Preface

Who This Book Is For What This Book Covers Conventions Used in This Book O’Reilly Online Learning How to Contact Us Acknowledgments

I. Migration Foundation 1. Why Should I Migrate to Amazon Web Services?

Cloud Technology Benefits

Scalability and Dynamic Consumption

Vertical scaling Horizontal scaling

Elastic Load Balancing AWS Auto Scaling

Geographic Diversity

Regions

Data proximity Data locality and privacy regulations

Availability zones AZs and disaster recovery

Easy Access to Newer Technologies Availability Increased Security

Zero trust Least privilege

Cloud Business Benefits

Reduced Expenditures and Support

Hard costs Soft costs

No Commitment Business Agility Disaster Recovery/Business Continuity Decreased Vendor Lock-in Change to Operational Expenditures

Converting Your Why into an FAQ

How to Build the FAQ Wrapping It Up

2. What Are the Risks and Their Mitigation?

Technology Risks

Security

Landing zone implementation

Account structure Baseline security and compliance monitoring Baseline logging for security groups Baseline security roles Configuration of crucial AWS services Protected logging

Least privilege implementation Shared responsibility model Legacy security patterns

Contemporary zoning Network IDS/IPS

Application Connectivity

Virtual private network Direct connect Internet

Technology Diversity

Staff assessment and training Contractors and consulting

Perception of Increased Technical Complexity

Business Risks

Reputation Staffing and Expertise Loss Contractual Obligations Cost Regulation

Resource tagging Chargeback and showback Tagging enforcement

Building Your Guiding Principles Wrapping It Up

II. Phases of Migration 3. Discovering Your Workloads

Discovery and Assessment Tooling

Server Discovery

Agent-based collector Agentless collector Instance right-sizing Disk right-sizing Application discovery Dependency mapping

Compute

Latest Instances CPU Type Relational Database Service Partial Run Rate Auto Scaling License Model

License included, or bring your own

Storage

EBS Volume Types Network File System Replacement Windows Server Replacement Instance Store Volumes

Network

Overall Outbound Bandwidth Elastic Load Balancers Classic Elastic Load Balancer Application Load Balancer Network Load Balancer

Ancillary AWS Service Charges Assessing Connectivity Requirements Wrapping It Up

4. Building Your Business Case

Estimating Your Timeline

Number of Servers Number of Servers Moved per Day Delay Buffer Employee Vacation and Holidays Putting the Equation Together

What Does a Business Case Look Like? The Narrative

Introduction FAQ Closing

The Forecast

Trimming the Fat

Refactor Redeploy Rehost Repurchase Retire Re-platform Retain

Run Rate Modeling Migration Costs

Tooling costs Consulting fees

Run Rate Modifiers

Reserved instances Savings Plans Migration percentages

Agility Savings

Automated deployment Service Catalog

Assumptions

Cost Burn-Up/Burn-Down Wrapping It Up

5. Addressing Your Operational Readiness for AWS

Why Your Operations Change After Migration Business Operations Building a Pyramid

The Foundation: Executive Sponsor The Base: IT Prototyping

Security and compliance Change management Agility

Large teams Too many cooks Process for process’s sake

Building Onto Your Base: Department Expansion Finishing the Apex

Finance Capabilities

Unconstrained Resources Misconfigured Pipelines Cost Management Lack of Chargeback/Showback

Wrapping It Up

6. Defining Your Landing Zone and Cloud Governance

Landing Zone

Account Structure

Business unit–based Environment-based Hybrid model

Recommended Accounts

Shared services Logging account Sandbox account Payment card industry data security standard

Landing Zone Deployment Methods

Cloud Governance

AWS Support Region Management Account Management

Consolidated billing Root account management

Access and Authorization

Single sign-on by federation IAM user accounts

Key Management Service Business Continuity

Bronze Silver Gold Platinum

Wrapping It Up

7. Planning Your Migration

Who Needs a Plan Agile, Waterfall, or Combination Plan Preplanning Blocker Analysis

Technology Blockers

Unsupported and outdated operating systems Unsupported hardware

Business Blockers

M&A activities Divestitures Changes in management

Vertical changes Horizontal changes

Priority shifts

Major bugs Competitive requirements

Development Methodologies Migration Tooling Selection

CloudEndure Database Migration Service DataSync Third-Party Tooling

Building Your Plan

Creating a Migration Timeline Planning Tooling Laying Down the 90% Finalizing the 90% Polishing the 10%

Wrapping It Up

8. Refactoring, Retooling, and Final Preparations

Refactoring

Potential Refactoring Targets

Applications to target Services to target

Database engine change S3 object storage Containerization Redshift data warehouse Static website Mail server

Estimating Run Rate After Refactoring

Database engine change S3 object storage Containerization Data warehouse Static website Mail server

Building the Business Case for Refactoring Final Thoughts on Refactoring

Retooling

Web Application Firewall Systems Manager CloudFront

Final Preparations Application Deep Dive and Planning

Application Status Team Bandwidth Technical Details Technical Migration Plan Testing Process Cutover Process Rollback Process

Closing

Index

← Prev
Back
Next →

← Prev
Back
Next →