Book Image

Optimizing Your Modernization Journey with AWS

By : Mridula Grandhi
Book Image

Optimizing Your Modernization Journey with AWS

By: Mridula Grandhi

Overview of this book

AWS cloud technologies help businesses scale and innovate, however, adopting modern architecture and applications can be a real challenge. This book is a comprehensive guide that ensures your switch to AWS services is smooth and hitch-free. It will enable you to make optimal decisions to bring out the best ROI from AWS cloud adoption. Beginning with nuances of cloud transformation on AWS, you’ll be able to plan and implement the migration steps. The book will facilitate your system modernization journey by getting you acquainted with various technical domains, namely, applications, databases, big data, analytics, networking, and security. Once you’ve learned about the different operations, budgeting, and management best practices such as the 6 Rs of migration approaches and the AWS Well-Architected Framework, you’ll be able to achieve operational excellence in cloud adoption. You’ll also learn how to deploy some of the important AWS tools and services with real-life case studies and use cases. By the end of this book, you’ll be able to successfully implement cloud migration and modernization on AWS and make decisions that best suit your organization.
Table of Contents (20 chapters)
Part 1: Migrating to the Cloud
Part 2: Cloud Modernization – Application, Data, Analytics, and IT
Part 3: Security and Networking Transformation
Part 4: Cloud Economics, Compliance, and Governance

Case study for Amazon EKS

The case study in this section covers a customer’s journey of using Amazon EKS.

The business challenge

A business chat tool company chat4business moved to a container-based architecture a few years ago. The company’s infra team was self-managing Kubernetes on Amazon EC2. However, the administrative and operational load of performing version upgrades every three months was an overhead to the company. There were issues with the tooling at the onset of Kubernetes adoption and the operational load to manage each cluster was high. The company had been using open source tools to manage its Kubernetes clusters. The infra team had to do everything including building, managing, and operating the control plane themselves. As their systems grew in scope and complexity, the operational load increased. The company needed failover risk during deployments and wanted to automate operations wherever possible in order to avoid dependency on any particular...