aws-cf-templates VS aws-cloudformation-reference

I think any of the common proxy platforms would work, the example code just happens to be for HAProxy. Managing ECS isn't that hard once you get it stood up. https://github.com/widdix/aws-cf-templates widdix provides a ton of reference cloud formation templates that cover most aspects of running aws infrastructure. We run everything through cloud formation and it is self-scaling and self-healing. System manager can automate patch management as well.

https://www.stackery.io/registry/?repo=https://github.com/wi...

Finally, if you’re feeling nostalgic for winter, this example from Symphonia is a lab for benchmarking Lambda cold starts for Java runtimes so that you can better understand how they behave and plan configurations accordingly.

For anyone reading this and wondering how to build all of this infrastructure, I do have some templates that would be a good starting point. For the versioned S3 bucket to hold deployment packages, I suggest using this template. For an API that uses a Lambda function for computing, I suggest using this template. It also contains the correct parameters to use a deployment package from a versioned S3 bucket. For anyone trying to learn AWS and wanting some additional help figuring things out, please don’t hesitate to get in contact with me. I would be more than happy to help out where I can!

Sure! My blog is https://thomasstep.com/ and the repo where I keep a bunch of CloudFormation templates is https://github.com/thomasstep/aws-cloudformation-reference

This template is also available in my aws-cloudformation-reference repository. I also made a video of me creating the template in case the process of building and deploying something like this from scratch is of interest.

A few months ago I had heard about AWS Fargate as a serverless computing platform for containers. I had good experiences with AWS's other serverless offerings and I wanted to get into containers more so Fargate seemed like a good next learning opportunity. I remember trying to spin a few resources up just to start messing around with the platform. At the end of the day, I ended up with an ECS cluster and some misconfigured services. I didn't realize that there were multiple different resources needed just to get a simple API container up and running. I recently worked through creating an ECS cluster, load balancer, Fargate service, and task definition with CloudFormation. I also made a video out of building the template and debugging along the way here's part 1 and here's part 2 (I apologize for the quiet audio). In the end, I created one template for the ECS cluster, load balancer, and other shared resources that could be shared across multiple Fargate services, one template for the Fargate service, task definition, and load balancer listener, and a tiny Dockerized hello world app.

Creating a VPC feels like a rite of passage of sorts to AWS. VPC stands for Virtual Private Cloud, and every AWS account comes with a default VPC already created for us when we get there. VPCs are a way to keep cloud resources isolated. I recently created a CloudFormation template for a basic VPC and I wanted to share a few different pieces that went into building it. Having a basic understanding of networking will probably be beneficial to understand these concepts.

I have been updating my CloudFormation reference repo on GitHub lately, and I wanted to bring up one of the newly added templates. This template builds a serverless RDS instance, generates a password for that instance, adds a secret to Secrets Manager, and allows for an instance to be built off of an existing snapshot. I also took a screen capture of me building and debugging that template that is available on YouTube if you care to watch how I built it.