AWS CloudFormation

At Volta we use AWS CodePipeline and AWS CodeBuild to automatically ship new AWS Lambda services without any effort. And we do it all with AWS CloudFormation, since configuration is easier to maintain than code.

Working on a project recently, wanted an easy modern frontend to work with, decoupled from our backend. To get things going quickly, decided to go with React, Redux, redux-saga, Bootstrap.

On the backend side, Golang is a personal favourite, and wanted to minimize server overheads so went with a #serverless architecture leveraging AWS Lambda, AWS CloudFormation, Amazon DynamoDB, etc.

For IDE/tooling I tend to stick to the #JetBrains tools: WebStorm / Goland.

Obviously using Git, with GitLab private repo's for managing code/issues/etc.

We heavily use AWS CloudFormation. Every single piece of our stack is defined in a CloudFormation template. Because our infrastructure is defined in code it has become trivial to launch new regions. If needed we are able to spawn a new dedicated shard in a few minutes. In addition, AWS Parameter Store is used to hold application settings. Our largest deployment is in US-East, but we also have regions in Tokyo, Singapore and Dublin.

#InfrastructureBuildTools #BuildTestDeploy

Manually clicking around the AWS UI or scripting AWS CLI calls can be both a slow and brittle process.

We needed to be able to reconstruct CloudRepo's infrastructure in case of disaster or moving to another AWS Region.

Setting up our infrastructure with CloudFormation allows us to update it easily as well as duplicate or recreate things when the need arises. AWS CloudFormation

Opstax uses CloudFormation for anything infrastructure related! CloudFormation allows us to use infrastructure-as-code as a constant blueprint/map of our environment. It means we can accurately and efficiently deploy replicated or new infrastructure with no time wasted clicking around and no human error. AWS CloudFormation