AWS CloudFormation

AWS CloudFormation

DevOps / Build, Test, Deploy / Infrastructure Build Tools

Decision at Tillable about AWS CloudFormation, AWS Elastic Load Balancing (ELB), Amazon EC2, Amazon S3, Terraform

Avatar of 1jkunz1
DevOps Engineer at Tillable ·

We use Terraform because we needed a way to automate the process of building and deploying feature branches. We wanted to hide the complexity such that when a dev creates a PR, it triggers a build and deployment without the dev having to worry about any of the 'plumbing' going on behind the scenes. Terraform allows us to automate the process of provisioning DNS records, Amazon S3 buckets, Amazon EC2 instances and AWS Elastic Load Balancing (ELB)'s. It also makes it easy to tear it all down when finished. We also like that it supports multiple clouds, which is why we chose to use it over AWS CloudFormation.

9 upvotes·16.2K views

Decision about GitLab, Git, WebStorm, Amazon DynamoDB, AWS CloudFormation, AWS Lambda, Go, Bootstrap, redux-saga, Redux, React, JetBrains, Serverless

Avatar of devalias
Hack. Dev. Transcend. ·

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.js, redux-saga, Bootstrap.

On the backend side, Go 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.

5 upvotes·1 comment·17.5K views

Decision at CloudvCard about AWS CloudFormation, Amazon CloudFront, Amazon Route 53, CloudFlare

Avatar of bramzor
Founder at CloudvCard ·

Yesterday we moved away from using CloudFlare towards Amazon Route 53 for a few reasons. Although CloudFlare is a great platform, once you reach almost a 100% AWS Service integration, it makes it hard to still use CloudFlare in the stack. Also being able to use Aliases for DNS makes it faster because instead of doing a CNAME and an A record lookup, you will be able to receive the A records from the end services directly. We always loved working with CloudFlare , especially for DNS as we already used Amazon CloudFront for CDN. But having everything within AWS makes it "cleaner" when deploying automatically using AWS CloudFormation. All that aside, the main reason for moving towards Amazon Route 53 for DNS is the ability to do geolocation and latency based DNS responses. Doing this outside the AWS console would increase the complexity.

5 upvotes·2.2K views

Decision about AWS CloudFormation, Google Cloud Deployment Manager, Terraform

Avatar of sungchun12

I use Terraform because it hits the level of abstraction pocket of being high-level and flexible, and is agnostic to cloud platforms. Creating complex infrastructure components for a solution with a UI console is tedious to repeat. Using low-level APIs are usually specific to cloud platforms, and you still have to build your own tooling for deploying, state management, and destroying infrastructure.

However, Terraform is usually slower to implement new services compared to cloud-specific APIs. It's worth the trade-off though, especially if you're multi-cloud. I heard someone say, "We want to preference a cloud, not lock in to one." Terraform builds on that claim.

Terraform Google Cloud Deployment Manager AWS CloudFormation

4 upvotes·6.8K views

Decision at Tillable about AWS CloudFormation

Avatar of 1jkunz1
DevOps Engineer at Tillable ·

We use AWS CloudFormation because we needed a way to quickly and efficiently create & deploy lambda functions. We found two frameworks that work nicely as 'syntactic sugar' on top of CloudFormation - One of them being AWS SAM, and the other being Serverless Framework. We currently use the Serverless Framework because of it's multi-cloud capabilities.

4 upvotes·2.7K views

Decision at Qrvey about AWS CodePipeline, AWS CloudFormation, Amazon Elasticsearch Service, AWS Fargate, Amazon DynamoDB

Avatar of amitbhatnagar
Chief Architect at Qrvey ·

At Qrvey we moved from a SaaS application running in AWS to a deployed model where we would deploy the complete infrastructure and code to a customer's AWS account. This created a unique challenge as we were Cloud Native and hence were using a lot of AWS Services like Amazon DynamoDB, AWS Fargate , Amazon Elasticsearch Service, etc. We decided to first build AWS CloudFormation templates to convert all our infrastructure into code. Then created a AWS CloudFormation template that would first generate a AWS CodePipeline into a customer's AWS account. This pipeline would then deploy our Infrastructure AWS CloudFormation template and the code on that Infrastructure. This simplified and completely automated our upgrade process as well.

3 upvotes·6.2K views

Decision at Volta Industries about AWS CloudFormation, AWS Lambda, AWS CodeBuild, AWS CodePipeline

Avatar of cazzer
Lead Software Engineer ·

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.

2 upvotes·4K views

Decision at CloudRepo about AWS CloudFormation

Avatar of 64BitChris
Founder at CloudRepo ·

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

1 upvote·549 views

Decision at Flux Work about AWS CloudFormation

Avatar of broom9
Computer Science, Bachelor at Flux ·

Manage infrastructure as codes. Native AWS solution so it has better support to AWS resources than Terraform, also can leverage AWS Business Support. AWS CloudFormation

1 upvote·20 views

Decision at Opstax Ltd about AWS CloudFormation

Avatar of opstax

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

1 upvote·15 views