AWS mistakes to avoid

Re:AWS mistakes to avoid by nzoschke on Saturday December 26, 2015 @05:37PM (#10795536)

I am asking this question often.

We are using very advanced CloudFormation in the open source Convox platform.

I have touched every corner of CF including lots of Custom Resources.

Right now we are using the golang template tools and tests to generate our templates.

But I have lots of needs and ideas for improving this. A CF template compiler and simulator should be possible, giving us all tons of confidence in making template changes and therefore any infrastructure update.

I have some sketches that I haven't published yet.

And I strongly believe CF is the best tool in this space if you're all in on AWS. Let Amazon be responsible for operating a transactional infrastructure mutation service. It's ridiculously hard to do this right.

If you want to brainstorm some ideas send me a message :)

[ Parent | on HN ]

Re:AWS mistakes to avoid by wise_young_man on Saturday December 26, 2015 @06:15PM (#10795633)

One of the things that I thought would be neat is an open source CloudFormation that could work for multiple cloud vendors, possibly using a driver pattern.

Also, you might want to update your HN profile with contact info.

[ Parent | on HN ]

Re:AWS mistakes to avoid by nzoschke on Saturday December 26, 2015 @07:12PM (#10795802)

Thanks, I updated my profile with contact info.

Terraform is awesome if you want an OSS project to manage multiple cloud vendors.

But I think that infrastructure change management is a really hard problem and the state of the art solution is how AWS runs CloudFormation as a managed service.

Once it's set up properly, it's amazing watching what CloudFormation can do. It can execute updating 20 instances to roll out a new AMI, and then roll the whole operation back on demand or if a failure happens. All with no application downtime in the cluster!

[ Parent | on HN ]