What if deploying your app felt like dropping a file into a folder?
That was my goal for this project. I built a small pipeline on AWS where I upload a .zip to an S3 bucket, and a few seconds later the new version of my game is live on an EC2 server. No SSH session. No Jenkins. No clicking "Deploy".
The app is Neon Snake , a tiny HTML/JS snake game. The interesting part isn't the game, it's the plumbing around it.
The architecture
The flow:
I upload neon-snake-game.zip to an S3 bucket .
S3 fires an "object created" event .
That event triggers a Lambda function (I called it SnakeDeployer ).
Lambda calls AWS Systems Manager (SSM) Run Command and sends a shell script to my server.
The SSM Agent on the EC2 instance runs the script: download the zip from S3, unpack it into the nginx web root, restart nginx.
CloudWatch and the Run Command history keep a record of every deployment.
Here's the same idea as a quick sketch:
Why SSM instead of SSH?
This is the part I liked most.…