Hacker News Reader

If you're doing anything in the cloud, yes, it is a very good idea to configure one for your project. It really isn't too complicated to set one up, and there are a lot of good articles to walk you through it.

DevOps pro tip: Take the time to script out your VPC configuration, and then don't think about it again. You'll thank yourself later for having a more secure, and scalable solution, that you can reuse for various projects, or on new jobs.

View on HN

At work, we have a Terraform module that receives a few input parameters and generates a VPC that complies with all of our corporate security guidelines. The module isn't complicated, and it ensures that we get it right every time.

We do this for every commonly-used AWS resource -- S3 buckets, SQS queues, etc. It eliminates most of the risk of misconfiguration, allows our infrastructure changes to be code-reviewed and unit tested, and eliminates a lot of the fiddly crap work associated with setting up something on AWS.

I do some volunteer IT work for the nonprofit makerspace in my town, and I obviously don't have access to my employer's tool chain if I have to work in their AWS account. It really is a night-and-day difference.

Reply on news.ycombinator.com