<story><title>Cloud services like AWS or Google Cloud Platform may be the wrong choice</title><url>https://www.karlsutt.com/articles/you-should-not-be-using-aws/</url></story><parent_chain><item><author>Octabrain</author><text>&amp;gt; - Terraform to create the API gateway, database, lambdas, queues, Route 53 records: 1 week&lt;p&gt;- Terraform to create the IAM policies: 4 weeks&lt;p&gt;Perhaps it&amp;#x27;s because I am very familiar with the aforementioned tool and cloud but 5 weeks for writing those resources gives me the impresion of:&lt;p&gt;1. Lack of experience on AWS.&lt;p&gt;2. Lack of experience with Terraform.&lt;p&gt;3. Both.&lt;p&gt;I don&amp;#x27;t want to sound arrogant by any means but a Terraform project for something like that, documented, with its CI and applying changes via CD, would take me 4 days being generous.</text></item></parent_chain><comment><author>marcus_holmes</author><text>I got handed a Terraform project for a GCP-based service. Simple dev, staging, prod environment. Secrets managed by secret manager, SQL Run without a public IP address for prod (but accessible via SSH for admins).&lt;p&gt;I more or less gave up after a month of beating my head on the brick wall. We hired an expert. Took him another month to get it all more or less sorted. There were still aspects that we wanted that we could not get Terraform&amp;#x2F;GCP to do.&lt;p&gt;In the end, we dropped Terraform and went back to modifying the GCP manually.</text></comment>
<story><title>Cloud services like AWS or Google Cloud Platform may be the wrong choice</title><url>https://www.karlsutt.com/articles/you-should-not-be-using-aws/</url></story><parent_chain><item><author>Octabrain</author><text>&amp;gt; - Terraform to create the API gateway, database, lambdas, queues, Route 53 records: 1 week&lt;p&gt;- Terraform to create the IAM policies: 4 weeks&lt;p&gt;Perhaps it&amp;#x27;s because I am very familiar with the aforementioned tool and cloud but 5 weeks for writing those resources gives me the impresion of:&lt;p&gt;1. Lack of experience on AWS.&lt;p&gt;2. Lack of experience with Terraform.&lt;p&gt;3. Both.&lt;p&gt;I don&amp;#x27;t want to sound arrogant by any means but a Terraform project for something like that, documented, with its CI and applying changes via CD, would take me 4 days being generous.</text></item></parent_chain><comment><author>throwaway2016a</author><text>Same, I do it routinely and maybe the first time I ever did it, it took me a week but after that it was fast. But I may be being generous.&lt;p&gt;The only thing that could make that tough is if you put the Lambdas in a VPC. That can get tricky because you have to plan out subnets and whatnot but still not a week.&lt;p&gt;The AWS documentation is also extremely good with regards to what properties are on each resource. I can&amp;#x27;t speak for Terraform since I usually use CloudFormation &amp;#x2F; SAM directly. Maybe it&amp;#x27;s a Terraform problem?</text></comment>