Per my previous post Amazon ECS is really easy to get started with. Once you do get started, there are a lot of things you can do with it that might require additional steps (e.g. service discovery). Below is a list of some of my favorite blog posts on this subject. More to come soon… Amazon ECS Monitor Cluster State with Amazon ECS Event Stream This blog post includes a Python Lambda function that’s triggered by Amazon CloudWatch Events whenever there’s a ECS cluster container state change
Containers seem to be everywhere these days, so I decided to jump on the bandwagon. Below is a step-by-step guide on how to quickly get started with Amazon ECS. Most of the commands were taken straight from the ECS-CLI tutorial found here. Setup the CLI ecs-cli installation instructions On a Mac sudo curl -o /usr/local/bin/ecs-cli https://s3.amazonaws.com/amazon-ecs-cli/ecs-cli-darwin-amd64-latest On Linux sudo curl -o /usr/local/bin/ecs-cli https://s3.amazonaws.com/amazon-ecs-cli/ecs-cli-linux-amd64-latest Chmod permissions sudo chmod +x /usr/local/bin/ecs-cli Follow the steps described here to configure the ecs-cli.
I’ve come to a point where I don’t want to manage the infrastructure hosting my websites. I think it’s a reasonable conclusion, given that I can use AWS to get this done without a sweat. A lot of today’s websites don’t really need to be written in PHP (or any other server-side language). Most sites are just online contact cards, with one small exception – they still want to allow you, the visitor, to send them an email from their “contact page”.
The nice thing about Amazon S3 (there are a lot of nice things about it, but I’ll concentrate on just a couple for now) is that you can store pretty much any amount of data on it. But the part which eludes most is that you can turn your bucket into a website with just a couple of commands. This gives you the 11 9’s of durability and 4 9’s of availability out-of-the-box without any additional tweaking of the configuration and without creating a single restart script.
When you’re working with JWT tokens, you need to verify their validity. Below is a small snippet of code to verify your RS256-signed tokens (note that I purposefully stored the jwks.json file locally so as not to make the HTTP request every time a token needs to be verified (which is every time a request comes in). For the purposes of this demo, I used the following 2 repos: https://github.com/auth0/jwks-rsa-javahttps://github.com/jwtk/jjwt