Luciano Mammino PRO
Cloud developer, entrepreneur, fighter, butterfly maker! #nodejs #javascript - Author of https://www.nodejsdesignpatterns.com , Founder of https://fullstackbulletin.com
Luciano Mammino (@loige)
Let's take the monolith to the cloud 🚀
2022-03-01
Get the slides! 👇
I'm Luciano 👋
👨💻 Senior Architect @ fourTheorem (Dublin 🇮🇪)
📔 Co-Author of Node.js Design Patterns 👉
We are business focused technologists that deliver.
Accelerated Serverless | AI as a Service | Platform Modernisation
We are hiring
do you want to work with us?
I co-host a podcast about AWS with @eoins!
Pleaze, subscribe 😇
Story time
Story time
Story time
Story time
Business Summary
👩⚖️ SaaS CMS for legal practices
👨💼1 founder + 🥷1 developer
💸 Bootstrapped business
🙌 Good MVP, getting attention in the market
💪 Started a TRIAL with a big customer
Current problems
📈 The company is growing
⚖️ but the technology does not scale!
📦 1 monolithic server
🔥 Frequent failures = 🤬 unhappy customers
😥 The business is at risk!
Desired State
⚖️ More reliable & scalable infrastructure
👌 Minimal amount of change required*
* the team is not skilled with the cloud & containers, we need to keep cognitive load low
🤔
"I heard that the cloud is great but we don't have the time and the skills to re-architect everything as micro-services!"
🧐
What can we
recommend?
⛏
Let's start to
dig deeper!
Example use cases
-
A user logs in the application and they should be able to see all their previously uploaded legal documents
-
A user can upload new documents and organize them by providing specific tags (client id, case number, etc.)
-
A user might search for documents containing specific keywords or tags
Current Architecture*
* a beautiful monolith ❤️
Can we take the monolith to the cloud and make it resilient & scalable?
Target architecture
🧐
Let's get more specific...*
* Mostly AWS from here
Target architecture on AWS
✋
Let's pause
for a second...
🤔
What is the cloud, really?
... a little more involved
than that! 😅
☁️ The "cloud" is built...
- To scale
- To be resilient
OK, but how?! 😒
Region
A physical location around the world (e.g. North Virginia, Ireland or Sydney) where AWS hosts a group of data centers.
Regions help to provision infrastructure that is closer to the customers, so that our applications can have low latency and feel responsive.
Availability Zone (AZ)
Discrete data center with redundant power, networking, and connectivity in an AWS Region.
Data centers in different availability zones are disjointed from one another, so if there’s a serious outage, that’s rarely affecting more than one availability zone at the same time.
Availability Zone (AZ)
It’s good practice to spread redundant infrastructure across different availability zones in a given region to guarantee high availability.
VPC
A virtual (private) network provisioned in a given region for a given AWS account.
It is logically isolated from other virtual networks in AWS.
Every VPC has a range of private IP addresses organised in one or more subnets.
Subnet
A range of IPs in a given VPC and in a given availability zone that can be used to spin up and connect resources within the network.
Subnets can be public or private.
A public subnet can be used to run instances that can have a public IP assigned to them and can be reachable from outside the VPC itself.
Subnet
It’s good practice to keep front-facing servers (or load balancers) in public subnets and keep everything else (backend services, databases, etc.) in private subnets.
Traffic between subnets can be enabled through routing tables to allow for instance a load balancer in a public subnet to forward traffic to backend instances in a private subnet.
Quick Recap
- Region: physical location with data centers
- Availability Zone: data center in a region
- VPC: a virtual private network in a region
- Subnet: range of IPs in a VPC in a given AZ
Region
AZ1
AZ2
AZ3
VPC
Subnet
Resource
(e.g. EC2 instance)
✏️ TODO List
☐ Create an AWS account
☐ Select a region
☐ Create and configure a VPC
Our VPC
✏️ TODO List
☑︎ Create an AWS account
☑︎ Select a region
☑︎ Create and configure a VPC
✏️ TODO List
☐ Load Balancer
☐ EC2
☐ S3
☐ RDS
☐ ElastiCache
☐ Route 53
Application Load Balancer (ALB)
The entry point to all the application traffic.
Layer 7 Load Balancer (HTTP, HTTPS, WebSocket, gRPC).
Highly available: replicated in all our public subnets.
Application Load Balancer (ALB)
Scalable: can handle millions of request per second.
Managed service: we don't need to configure the OS or install software patches.
Can be integrated with ACM (AWS Certificate Manager) to support HTTPS.
Application Load Balancer (ALB)
Target group
Application Load Balancer (ALB)
Target group
🔥
/health
✅
❌
/health
/health
✅
Unhealty targets
won't get any traffic
Application Load Balancer (ALB)
Targets can be added dynamically.
We can scale targets automatically using autoscaling groups.
E.g. Add or remove instances based on num requests in-flight or on avg CPU of the current instances.
How does it scale?
Being a managed service, scalability is mostly handled out of the box by AWS.
Resiliency
A load balancer can distribute traffic to multiple AZs, so if one of them becomes unavailable it will keep distributing traffic to the remaining ones.
✏️ TODO List
☑︎ Load Balancer
☐ EC2
☐ S3
☐ RDS
☐ ElastiCache
☐ Route 53
EC2 - Virtual Machine
Virtual machine running all the necessary software for the service (Nginx, Node.js, app code, etc.)
They need to use Security Groups (allow traffic) and IAM Roles (allow them to access other AWS resources like S3).
EC2 - Virtual Machine
We will need to provision multiple machines dynamically.
Challenges:
- Consistency
- 🐮 Cattle vs 🙀 Pet mindset
- Stateless applications
Consistency
All our virtual machines have to be the same: we need to build an AMI (Amazon Machine Image).
An AMI contains OS, libraries, software and source code.
You can use an AMI to start a new instance.
Consistency
While we can build an AMI manually, it's better to use tools to automate the work:
🐮 Cattle vs 🙀 Pet mindset
Once an instance has been launched we shouldn't change it anymore (e.g update the OS, install new softare, update the code, etc.)
If we need to change something, we build a new image and deploy new instances.
Instances are disposable!
Stateless
We are load balancing traffic so a user might be served by different instances during their session.
A single instance should not store any state (e.g. user sessions, uploaded files, etc.)
State should be stored outside instances (ElastiCache, S3, RDS, etc).
Stateless
Making an application stateless might require a good amount of code change.
A shortcut to this might be to enable sticky sessions in the ALB, but it's not recommended for scalability and resiliency.
How does it scale?
Every instance will be able to handle a certain number of requests per second.
We can scale by adding more instances when the traffic grows.
Resiliency
We should have at least 1 instance per availability zone.
If there is an AWS outage, the instances on the healthy availability zone will keep handling requests.
We can use an autoscaling group to make sure that unhealthy instances are replaced.
✏️ TODO List
☑︎ Load Balancer
☑︎ EC2
☐ S3
☐ RDS
☐ ElastiCache
☐ Route 53
Simple Storage Service (S3)
One of the very first AWS services and (probably) the most famous one.
Object storage service: Allows you to store any amount of data durably.
You need to use the SDK to read and write data.
Simple Storage Service (S3)
Data can be organised in logical containers called Buckets.
Key/value model: Inside a bucket you can store data by providing a key and the content.
Simple Storage Service (S3)
const AWS = require('aws-sdk')
const s3 = new AWS.S3()
const params = {
Bucket: 'my-bucket',
Key: 'my-first-s3-file.txt',
Body: Buffer.from('Hello, AWS')
}
s3.upload(params, (err) => {
if (err) {
console.error(err)
} else {
console.log('Upload successful')
}
})Simple Storage Service (S3)
Too much code to change?
A first migration could be done by using a something like s3fs-fuse to create a "virtual filesystem" that allows you to read/write to S3 seamlessly.
How does it scale?
S3 is a managed service which automatically scales to thousands of read/write operations per second.
Resiliency
S3 is provisioned in multiple AZs by default and it makes multiple copies of your data.
All of this happens transparently, no special configuration required.
✏️ TODO List
☑︎ Load Balancer
☑︎ EC2
☑︎ S3
☐ RDS
☐ ElastiCache
☐ Route 53
Relational Database Service (RDS)
Managed relational database service for MySql, PostgreSQL, MariaDB, Oracle & SQL Server.
Being a managed service, AWS takes care of most common concerns like backups and updates (configurable).
How does it scale?
RDS PostgreSQL supports Read Replicas: you can provision additional instances to which you can distribute heavy read-only queries.
Resiliency
RDS PostgreSQL can be configured to work in Multi-AZ mode: this means that there will be one or two standby copies of the database in different AZs.
If the primary DB instance or the primary AZ have an outage, one of the standby copies are promoted to become "the primary" instance.
Resiliency
Failover is fast but not instantaneous (60-120 seconds), so we need to make sure to plan for possible connectivity failures in your app and show clear error messages to the users.
✏️ TODO List
☑︎ Load Balancer
☑︎ EC2
☑︎ S3
☑︎ RDS
☐ ElastiCache
☐ Route 53
ElastiCache
Managed in-memory caching service supporting Redis and Memcached.
Meant to be used for use cases that don't require durability like data cache, session stores, gaming leaderboards, streaming, and analytics.
AWS takes care of maintenance.
How does it scale?
A single instance of Redis (with enough memory) can scale to significant amounts of traffic.
If you need more, you can run ElastiCache Redis in Cluster Mode and shard your data across multiple Redis instances.
Resiliency
ElastiCache Redis can operate in Multi-AZ mode.
Similarly to RDS, in case of failures, there might be some downtime while the new master is promoted.
We need to make sure the app accounts for Redis connection failures.
✏️ TODO List
☑︎ Load Balancer
☑︎ EC2
☑︎ S3
☑︎ RDS
☑︎ ElastiCache
☐ Route 53
Route53
Highly available and scalable cloud DNS service.
Can be used to direct traffic on a given domain to our Application Load Balancer.
✏️ TODO List
☑︎ Load Balancer
☑︎ EC2
☑︎ S3
☑︎ RDS
☑︎ ElastiCache
☑︎ Route 53
Infrastructure as Code (IaaC)
We could provision everything "manually" from the web console, but...
- It will be hard to create consistent environments for development and QA
- It will be hard to change things incrementally
- How would we test and review changes before applying them in production?
Infrastructure as Code (IaaC)
It's better to define all the infrastructure using code. There are several tools that can help us with that:
{
"AWSTemplateFormatVersion" : "2010-09-09",
"Description" : "AWS CloudFormation Sample Template EC2InstanceWithSecurityGroupSample: Create an Amazon EC2 instance running the Amazon Linux AMI. The AMI is chosen based on the region in which the stack is run. This example creates an EC2 security group for the instance to give you SSH access. **WARNING** This template creates an Amazon EC2 instance. You will be billed for the AWS resources used if you create a stack from this template.",
"Parameters" : {
"KeyName": {
"Description" : "Name of an existing EC2 KeyPair to enable SSH access to the instance",
"Type": "AWS::EC2::KeyPair::KeyName",
"ConstraintDescription" : "must be the name of an existing EC2 KeyPair."
},
"InstanceType" : {
"Description" : "WebServer EC2 instance type",
"Type" : "String",
"Default" : "t2.small",
"AllowedValues" : [ "t1.micro", "t2.nano", "t2.micro", "t2.small", "t2.medium", "t2.large", "m1.small", "m1.medium", "m1.large", "m1.xlarge", "m2.xlarge", "m2.2xlarge", "m2.4xlarge", "m3.medium", "m3.large", "m3.xlarge", "m3.2xlarge", "m4.large", "m4.xlarge", "m4.2xlarge", "m4.4xlarge", "m4.10xlarge", "c1.medium", "c1.xlarge", "c3.large", "c3.xlarge", "c3.2xlarge", "c3.4xlarge", "c3.8xlarge", "c4.large", "c4.xlarge", "c4.2xlarge", "c4.4xlarge", "c4.8xlarge", "g2.2xlarge", "g2.8xlarge", "r3.large", "r3.xlarge", "r3.2xlarge", "r3.4xlarge", "r3.8xlarge", "i2.xlarge", "i2.2xlarge", "i2.4xlarge", "i2.8xlarge", "d2.xlarge", "d2.2xlarge", "d2.4xlarge", "d2.8xlarge", "hi1.4xlarge", "hs1.8xlarge", "cr1.8xlarge", "cc2.8xlarge", "cg1.4xlarge"]
,
"ConstraintDescription" : "must be a valid EC2 instance type."
},
"SSHLocation" : {
"Description" : "The IP address range that can be used to SSH to the EC2 instances",
"Type": "String",
"MinLength": "9",
"MaxLength": "18",
"Default": "0.0.0.0/0",
"AllowedPattern": "(\\d{1,3})\\.(\\d{1,3})\\.(\\d{1,3})\\.(\\d{1,3})/(\\d{1,2})",
"ConstraintDescription": "must be a valid IP CIDR range of the form x.x.x.x/x."
}
},
"Mappings" : {
"AWSInstanceType2Arch" : {
"t1.micro" : { "Arch" : "HVM64" },
"t2.nano" : { "Arch" : "HVM64" },
"t2.micro" : { "Arch" : "HVM64" },
"t2.small" : { "Arch" : "HVM64" },
"t2.medium" : { "Arch" : "HVM64" },
"t2.large" : { "Arch" : "HVM64" },
"m1.small" : { "Arch" : "HVM64" },
"m1.medium" : { "Arch" : "HVM64" },
"m1.large" : { "Arch" : "HVM64" },
"m1.xlarge" : { "Arch" : "HVM64" },
"m2.xlarge" : { "Arch" : "HVM64" },
"m2.2xlarge" : { "Arch" : "HVM64" },
"m2.4xlarge" : { "Arch" : "HVM64" },
"m3.medium" : { "Arch" : "HVM64" },
"m3.large" : { "Arch" : "HVM64" },
"m3.xlarge" : { "Arch" : "HVM64" },
"m3.2xlarge" : { "Arch" : "HVM64" },
"m4.large" : { "Arch" : "HVM64" },
"m4.xlarge" : { "Arch" : "HVM64" },
"m4.2xlarge" : { "Arch" : "HVM64" },
"m4.4xlarge" : { "Arch" : "HVM64" },
"m4.10xlarge" : { "Arch" : "HVM64" },
"c1.medium" : { "Arch" : "HVM64" },
"c1.xlarge" : { "Arch" : "HVM64" },
"c3.large" : { "Arch" : "HVM64" },
"c3.xlarge" : { "Arch" : "HVM64" },
"c3.2xlarge" : { "Arch" : "HVM64" },
"c3.4xlarge" : { "Arch" : "HVM64" },
"c3.8xlarge" : { "Arch" : "HVM64" },
"c4.large" : { "Arch" : "HVM64" },
"c4.xlarge" : { "Arch" : "HVM64" },
"c4.2xlarge" : { "Arch" : "HVM64" },
"c4.4xlarge" : { "Arch" : "HVM64" },
"c4.8xlarge" : { "Arch" : "HVM64" },
"g2.2xlarge" : { "Arch" : "HVMG2" },
"g2.8xlarge" : { "Arch" : "HVMG2" },
"r3.large" : { "Arch" : "HVM64" },
"r3.xlarge" : { "Arch" : "HVM64" },
"r3.2xlarge" : { "Arch" : "HVM64" },
"r3.4xlarge" : { "Arch" : "HVM64" },
"r3.8xlarge" : { "Arch" : "HVM64" },
"i2.xlarge" : { "Arch" : "HVM64" },
"i2.2xlarge" : { "Arch" : "HVM64" },
"i2.4xlarge" : { "Arch" : "HVM64" },
"i2.8xlarge" : { "Arch" : "HVM64" },
"d2.xlarge" : { "Arch" : "HVM64" },
"d2.2xlarge" : { "Arch" : "HVM64" },
"d2.4xlarge" : { "Arch" : "HVM64" },
"d2.8xlarge" : { "Arch" : "HVM64" },
"hi1.4xlarge" : { "Arch" : "HVM64" },
"hs1.8xlarge" : { "Arch" : "HVM64" },
"cr1.8xlarge" : { "Arch" : "HVM64" },
"cc2.8xlarge" : { "Arch" : "HVM64" }
},
"AWSInstanceType2NATArch" : {
"t1.micro" : { "Arch" : "NATHVM64" },
"t2.nano" : { "Arch" : "NATHVM64" },
"t2.micro" : { "Arch" : "NATHVM64" },
"t2.small" : { "Arch" : "NATHVM64" },
"t2.medium" : { "Arch" : "NATHVM64" },
"t2.large" : { "Arch" : "NATHVM64" },
"m1.small" : { "Arch" : "NATHVM64" },
"m1.medium" : { "Arch" : "NATHVM64" },
"m1.large" : { "Arch" : "NATHVM64" },
"m1.xlarge" : { "Arch" : "NATHVM64" },
"m2.xlarge" : { "Arch" : "NATHVM64" },
"m2.2xlarge" : { "Arch" : "NATHVM64" },
"m2.4xlarge" : { "Arch" : "NATHVM64" },
"m3.medium" : { "Arch" : "NATHVM64" },
"m3.large" : { "Arch" : "NATHVM64" },
"m3.xlarge" : { "Arch" : "NATHVM64" },
"m3.2xlarge" : { "Arch" : "NATHVM64" },
"m4.large" : { "Arch" : "NATHVM64" },
"m4.xlarge" : { "Arch" : "NATHVM64" },
"m4.2xlarge" : { "Arch" : "NATHVM64" },
"m4.4xlarge" : { "Arch" : "NATHVM64" },
"m4.10xlarge" : { "Arch" : "NATHVM64" },
"c1.medium" : { "Arch" : "NATHVM64" },
"c1.xlarge" : { "Arch" : "NATHVM64" },
"c3.large" : { "Arch" : "NATHVM64" },
"c3.xlarge" : { "Arch" : "NATHVM64" },
"c3.2xlarge" : { "Arch" : "NATHVM64" },
"c3.4xlarge" : { "Arch" : "NATHVM64" },
"c3.8xlarge" : { "Arch" : "NATHVM64" },
"c4.large" : { "Arch" : "NATHVM64" },
"c4.xlarge" : { "Arch" : "NATHVM64" },
"c4.2xlarge" : { "Arch" : "NATHVM64" },
"c4.4xlarge" : { "Arch" : "NATHVM64" },
"c4.8xlarge" : { "Arch" : "NATHVM64" },
"g2.2xlarge" : { "Arch" : "NATHVMG2" },
"g2.8xlarge" : { "Arch" : "NATHVMG2" },
"r3.large" : { "Arch" : "NATHVM64" },
"r3.xlarge" : { "Arch" : "NATHVM64" },
"r3.2xlarge" : { "Arch" : "NATHVM64" },
"r3.4xlarge" : { "Arch" : "NATHVM64" },
"r3.8xlarge" : { "Arch" : "NATHVM64" },
"i2.xlarge" : { "Arch" : "NATHVM64" },
"i2.2xlarge" : { "Arch" : "NATHVM64" },
"i2.4xlarge" : { "Arch" : "NATHVM64" },
"i2.8xlarge" : { "Arch" : "NATHVM64" },
"d2.xlarge" : { "Arch" : "NATHVM64" },
"d2.2xlarge" : { "Arch" : "NATHVM64" },
"d2.4xlarge" : { "Arch" : "NATHVM64" },
"d2.8xlarge" : { "Arch" : "NATHVM64" },
"hi1.4xlarge" : { "Arch" : "NATHVM64" },
"hs1.8xlarge" : { "Arch" : "NATHVM64" },
"cr1.8xlarge" : { "Arch" : "NATHVM64" },
"cc2.8xlarge" : { "Arch" : "NATHVM64" }
}
,
"AWSRegionArch2AMI" : {
"af-south-1" : {"HVM64" : "ami-064cc455f8a1ef504", "HVMG2" : "NOT_SUPPORTED"},
"ap-east-1" : {"HVM64" : "ami-f85b1989", "HVMG2" : "NOT_SUPPORTED"},
"ap-northeast-1" : {"HVM64" : "ami-0b2c2a754d5b4da22", "HVMG2" : "ami-09d0e0e099ecabba2"},
"ap-northeast-2" : {"HVM64" : "ami-0493ab99920f410fc", "HVMG2" : "NOT_SUPPORTED"},
"ap-northeast-3" : {"HVM64" : "ami-01344f6f63a4decc1", "HVMG2" : "NOT_SUPPORTED"},
"ap-south-1" : {"HVM64" : "ami-03cfb5e1fb4fac428", "HVMG2" : "ami-0244c1d42815af84a"},
"ap-southeast-1" : {"HVM64" : "ami-0ba35dc9caf73d1c7", "HVMG2" : "ami-0e46ce0d6a87dc979"},
"ap-southeast-2" : {"HVM64" : "ami-0ae99b503e8694028", "HVMG2" : "ami-0c0ab057a101d8ff2"},
"ca-central-1" : {"HVM64" : "ami-0803e21a2ec22f953", "HVMG2" : "NOT_SUPPORTED"},
"cn-north-1" : {"HVM64" : "ami-07a3f215cc90c889c", "HVMG2" : "NOT_SUPPORTED"},
"cn-northwest-1" : {"HVM64" : "ami-0a3b3b10f714a0ff4", "HVMG2" : "NOT_SUPPORTED"},
"eu-central-1" : {"HVM64" : "ami-0474863011a7d1541", "HVMG2" : "ami-0aa1822e3eb913a11"},
"eu-north-1" : {"HVM64" : "ami-0de4b8910494dba0f", "HVMG2" : "ami-32d55b4c"},
"eu-south-1" : {"HVM64" : "ami-08427144fe9ebdef6", "HVMG2" : "NOT_SUPPORTED"},
"eu-west-1" : {"HVM64" : "ami-015232c01a82b847b", "HVMG2" : "ami-0d5299b1c6112c3c7"},
"eu-west-2" : {"HVM64" : "ami-0765d48d7e15beb93", "HVMG2" : "NOT_SUPPORTED"},
"eu-west-3" : {"HVM64" : "ami-0caf07637eda19d9c", "HVMG2" : "NOT_SUPPORTED"},
"me-south-1" : {"HVM64" : "ami-0744743d80915b497", "HVMG2" : "NOT_SUPPORTED"},
"sa-east-1" : {"HVM64" : "ami-0a52e8a6018e92bb0", "HVMG2" : "NOT_SUPPORTED"},
"us-east-1" : {"HVM64" : "ami-032930428bf1abbff", "HVMG2" : "ami-0aeb704d503081ea6"},
"us-east-2" : {"HVM64" : "ami-027cab9a7bf0155df", "HVMG2" : "NOT_SUPPORTED"},
"us-west-1" : {"HVM64" : "ami-088c153f74339f34c", "HVMG2" : "ami-0a7fc72dc0e51aa77"},
"us-west-2" : {"HVM64" : "ami-01fee56b22f308154", "HVMG2" : "ami-0fe84a5b4563d8f27"}
}
},
"Resources" : {
"EC2Instance" : {
"Type" : "AWS::EC2::Instance",
"Properties" : {
"InstanceType" : { "Ref" : "InstanceType" },
"SecurityGroups" : [ { "Ref" : "InstanceSecurityGroup" } ],
"KeyName" : { "Ref" : "KeyName" },
"ImageId" : { "Fn::FindInMap" : [ "AWSRegionArch2AMI", { "Ref" : "AWS::Region" },
{ "Fn::FindInMap" : [ "AWSInstanceType2Arch", { "Ref" : "InstanceType" }, "Arch" ] } ] }
}
},
"InstanceSecurityGroup" : {
"Type" : "AWS::EC2::SecurityGroup",
"Properties" : {
"GroupDescription" : "Enable SSH access via port 22",
"SecurityGroupIngress" : [ {
"IpProtocol" : "tcp",
"FromPort" : "22",
"ToPort" : "22",
"CidrIp" : { "Ref" : "SSHLocation"}
} ]
}
}
},
"Outputs" : {
"InstanceId" : {
"Description" : "InstanceId of the newly created EC2 instance",
"Value" : { "Ref" : "EC2Instance" }
},
"AZ" : {
"Description" : "Availability Zone of the newly created EC2 instance",
"Value" : { "Fn::GetAtt" : [ "EC2Instance", "AvailabilityZone" ] }
},
"PublicDNS" : {
"Description" : "Public DNSName of the newly created EC2 instance",
"Value" : { "Fn::GetAtt" : [ "EC2Instance", "PublicDnsName" ] }
},
"PublicIP" : {
"Description" : "Public IP address of the newly created EC2 instance",
"Value" : { "Fn::GetAtt" : [ "EC2Instance", "PublicIp" ] }
}
}
}Example of CloudFormation template
import * as cdk from '@aws-cdk/core'
import * as ec2 from '@aws-cdk/aws-ec2'
export class CdkUbuntuEc2Stack extends cdk.Stack {
constructor (scope: cdk.Construct, id: string, props?: cdk.StackProps) {
super(scope, id, {
env: {
account: process.env.CDK_DEPLOY_ACCOUNT || process.env.CDK_DEFAULT_ACCOUNT,
region: process.env.CDK_DEPLOY_REGION || process.env.CDK_DEFAULT_REGION
},
...props
})
const defaultVpc = ec2.Vpc.fromLookup(this, 'VPC', {
isDefault: true
})
const userData = ec2.UserData.forLinux()
userData.addCommands(
'apt-get update -y',
'apt-get install -y git awscli ec2-instance-connect',
'until git clone https://github.com/aws-quickstart/quickstart-linux-utilities.git; do echo "Retrying"; done',
'cd /quickstart-linux-utilities',
'source quickstart-cfn-tools.source',
'qs_update-os || qs_err',
'qs_bootstrap_pip || qs_err',
'qs_aws-cfn-bootstrap || qs_err',
'mkdir -p /opt/aws/bin',
'ln -s /usr/local/bin/cfn-* /opt/aws/bin/'
)
const machineImage = ec2.MachineImage.fromSSMParameter(
'/aws/service/canonical/ubuntu/server/focal/stable/current/amd64/hvm/ebs-gp2/ami-id',
ec2.OperatingSystemType.LINUX,
userData
)
const myVmSecurityGroup = new ec2.SecurityGroup(this, 'myVmSecurityGroup', {
vpc: defaultVpc
})
myVmSecurityGroup.addIngressRule(ec2.Peer.anyIpv4(), ec2.Port.tcp(80), 'httpIpv4')
myVmSecurityGroup.addIngressRule(ec2.Peer.anyIpv6(), ec2.Port.tcp(80), 'httpIpv6')
const myVm = new ec2.Instance(this, 'myVm', {
// the type of instance to deploy (e.g. a 't2.micro')
instanceType: new ec2.InstanceType('t2.micro'),
// the id of the image to use for the instance
machineImage: machineImage,
// A reference to the object representing the VPC
// you want to deploy the instance into
vpc: defaultVpc,
// security group
securityGroup: myVmSecurityGroup,
// init script
init: ec2.CloudFormationInit.fromElements(
ec2.InitCommand.shellCommand('sudo apt-get install -y nginx')
)
// ... more configuration can go here
})
// this will print the URL to our web server as output
const webVmUrl = new cdk.CfnOutput(this, 'webVmUrl', {
value: `http://${myVm.instancePublicIp}/`,
description: 'The URL of our instance',
exportName: 'webVmUrl'
})
}
}Example of a CDK stack (TypeScript)
An article about CDK (with examples)
Switch over
Switch over
🙀 How do we migrate the data?
😥 How do we switch the traffic to the new infrastructure?
Streamlined data migration
Update the "old" code-base to save every new file also to S3.
Copy all the existing file to the S3 bucket (S3 sync).
Streamlined data migration
AWS Database Migration service allows you to replicate all the data from the old database to the new one.
It will also keep the 2 Databases in sync during the switch over!
Switching traffic
Request a new certificate using AWS Certificate Manager (ACM).
Can be validated by email or DNS.
Point your DNS to the new Load Balancer in AWS!
WE ARE LIVE! 🎉
Now what?
New challenges 🤨
- Observability
- Testing
- Building & Deployment
New opportunities 😊
- We can scale dynamically!
- As the team grows and the system gets more complicated we can start to think about micro-services.
- We can start to play with other AWS services (E.g. SQS + Lambda for background task processing).
💸 Cost
💸 Cost
| Load Balancer | $ 24.24 |
| EC2 (6 instances) | $ 85.87 |
| ElastiCache Redis (3 instances) | $ 78.84 |
| RDS PostgreSQL (3 instances) | $ 155.48 |
| S3 (1TB) | $ 32.55 |
| TOT | $ 376.98 |
💸 Cost
- Cost estimates are always a bit of a "gamble"...
- I selected some arbitrary instance sizes (EC2, RDS, ElastiCache).
- I am not accounting for auto-scaling.
- I am not accounting for network traffic.
- Better to look at cost in production and try to optimise when needed.
- Rule of thumb: try to balance cost with your revenue.
- Rule of thumb (2): consider the total cost of ownership!
✏️ Bonus: a TODO list for the migration
☐ Create an AWS Account
☐ Select a tool for IaaC
☐ Create and configure a VPC in a region (3 AZs, Public / Private subnets)
☐ Create an S3 bucket
☐ Update the old codebase to save every new file to S3
☐ Copy all the existing files to S3
☐ Spin up the database in RDS (Multi-AZ)
☐ Migrate the data using Database Migration Service
☐ Provision the ElastiCache Redis Cluster (Multi-AZ)
☐ Create an AMI for the application
☐ Create a security groups and an IAM policy for EC2
☐ Make the application stateless
☐ Create an health check endpoint
☐ Create an autoscaling group to spin up the instances
☐ Create a certificate in ACM
☐ Provision an Application Load Balancer (public subnets)
☐ Configure Https, Targets and Health Checks
☐ Configure Route53
☐ Traffic switch-over through DNS 🤞
📝 Great guide to cloud migrations: 6 strategies for migrating applications to the cloud
The cloud is a journey
not a destination
The cloud is a journey
not a destination
Thank you!
Let's take the monolith to the cloud 🚀
By Luciano Mammino
Let's take the monolith to the cloud 🚀
How can you take an existing monolith to the cloud with very minimal effort? In this talk we will explore an architecture that can help you to achieve that while focusing on scalability and resilience.
