As a software developer, I spend enough time dealing with infrastructure, cloud services, containers, deployments, and all the other fun things that come with getting software into production.
So when I’m working on a personal project?
Sometimes I just want the damn thing to work.
That’s one of the reasons I keep coming back to AWS Lightsail.
Is it the most powerful way to host something? No.
Is it the fanciest?
Definitely not.
But when I have a random project that I want to throw online without turning the hosting infrastructure into a project of its own, Lightsail is incredibly convenient.
Sometimes Simple Is Better
AWS is ridiculously powerful.
It’s also ridiculously easy to turn something simple into an architecture diagram with 47 boxes.
EC2, ECS, EKS, Lambda, RDS, API Gateway, CloudFront, Route 53, load balancers, VPCs, security groups…
There’s a service for basically everything.
That’s fantastic when you’re building something that actually needs those things.
But my random side project with twelve users probably doesn’t need a Kubernetes cluster.
Sometimes I need:
Server. Database. IP address. Done.
That’s where Lightsail shines for me.
The Pricing Is Easy to Understand
One of my favorite things about Lightsail is that I can look at the plans and immediately understand approximately what my little experiment is going to cost me every month.
That’s important for personal projects.
I’m not sitting there trying to calculate compute time, storage requests, network traffic and fifteen other things just to figure out whether the dumb idea I came up with at 11 PM is going to cost me $5 or $50 a month.
Pick a plan.
Pay a predictable monthly price.
Move on.
For a hobby project, that’s exactly what I want.
I Can Have Something Running Really Quickly
This is probably the biggest reason I like Lightsail.
If I decide I want a Linux server, I can spin one up and have it running in a couple of minutes.
SSH into it.
Install what I need.
Pull down my application.
Point a domain at it.
And suddenly the random thing I was building locally is sitting on the internet.
There’s something satisfying about that.
Could I automate the entire process?
Absolutely.
Could I build a proper CI/CD pipeline, containerize everything, deploy it through infrastructure-as-code, add monitoring, configure autoscaling and make a beautiful architecture diagram?
Yep.
But that’s also how my two-hour experiment turns into a three-week infrastructure project.
Sometimes I just want to build the thing.
It’s Still AWS
This is another big advantage for me.
Lightsail makes things simple, but you’re still inside the AWS ecosystem.
If my little side project eventually becomes something more serious, I haven’t necessarily painted myself into a corner.
Maybe eventually I need S3.
Maybe I need CloudFront.
Maybe the database needs to move somewhere else.
Maybe the application actually gets enough traffic that I need to rethink the architecture.
At that point I can start introducing other AWS services where they actually make sense.
I don’t have to design for a million users before I’ve even found user number two.
It’s Great for WordPress Too
GTEDB is actually a perfect example of the kind of thing I’m talking about.
I don’t need some elaborate cloud architecture to run a personal WordPress blog.
I need WordPress.
Lightsail gives me an incredibly straightforward way to get a WordPress instance running without spending an afternoon manually configuring everything from scratch.
And that’s really the recurring theme here:
I want to spend my free time working on the project, not the infrastructure supporting the project.
There are absolutely managed WordPress hosts that make things even easier, and there are plenty of reasons someone might choose one of those instead.
But I already know AWS.
Lightsail gives me enough control to mess around when I want to while still keeping things simple.
That’s a pretty nice middle ground.
Not Everything Needs to Be Enterprise Architecture
I think developers—including myself—occasionally fall into this trap.
We know how to build complicated systems, so sometimes we feel like we should build complicated systems.
You start a little side project and suddenly you’re thinking:
“Well, obviously auth should be its own service…”
Then:
“Maybe I should put everything in Docker.”
And five minutes later:
“You know, Kubernetes would make scaling easier…”
Scaling what?!
Nobody is using the thing yet.
I’ve definitely had to remind myself of this while working on personal projects.
Build the application first.
Solve the problems you actually have.
If you eventually have a scaling problem, congratulations—that probably means your random side project actually became successful.
You can deal with it then.
Lightsail Isn’t Always the Answer
Obviously, Lightsail isn’t the right choice for everything.
There are cheaper hosting providers. There are platforms that make deployment even easier. Serverless architectures can make a lot of sense for certain applications. Containers can be the right answer. Sometimes you really do need the flexibility of EC2 or the scalability of a larger AWS architecture.
And if I were designing infrastructure for a serious production application, my requirements would probably be completely different.
But that’s not what I’m talking about.
I’m talking about the project I started Saturday morning because I had an idea and wanted to see if I could make it work.
For those projects, I don’t necessarily want the best possible infrastructure.
I want infrastructure that gets out of my way.
Just Let Me Build Stuff
That’s ultimately why I like AWS Lightsail.
It’s boring.
And I mean that as a compliment.
I can spin up a server, deploy something, give it an IP address, point a domain at it and get back to whatever I was actually trying to build.
If the project grows, I can worry about the rest later.
Until then?
I’ll happily take boring infrastructure.
My side project doesn’t need to be architected like Netflix. It just needs to be online.
