Fargate wanted $35. Lightsail wanted $7.
Hey 👋🏽
Your first container on ECS comes with homework: a VPC, subnets in two Availability Zones, a load balancer, security groups, a certificate and a task role. Express Mode creates most of it for you now (App Runner's successor, so ECS abstraction number three), but it all lands in your account, and you have to understand it the day something breaks.
Lightsail skips the homework. You hand it an image and get an HTTPS endpoint. We put a public tool on it for $7 a month, and the diagram below shows everything we didn't have to build.
In this issue: why we picked Lightsail over Lambda and Fargate, and three AWS launches from the last two weeks.
📚 This Week's Deep DiveThe same container on ECS with Fargate and on Lightsail, side by side: 
We run the AWS Event Inspector on it, a free public tool for SNS and EventBridge payloads. One Nano node, $7 a month. On ECS with Fargate it'd be $35 or more. Why not Lambda? And how does it read from S3 without access keys? The article covers both. |
📰 This Week in AWS🔀ECS Gateway: managed ingress for ECS services
↩️CloudFormation can force a stuck rollback
💾RDS bills each snapshot on its own
|
A Lightsail container service won't replace your EKS cluster. For the small thing that just has to be online, it's a good place to start, and the image moves to ECS without a rebuild when you outgrow it.
Running something on Lightsail already? Hit reply and tell me what it is.
See you next week! 🙏
Tobi & Sandro