<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>billisonline</author><text>&amp;gt; we accidentally created an infinite event loop between two Lambdas. Racked up a several-hundred-thousand dollar bill in a couple of hours&lt;p&gt;May I ask how you dealt with this? Were you able to explain  it to Amazon support and get some of these charges forgiven? Also, how would you recommend monitoring for this type of issue with Lambda?&lt;p&gt;Btw, this reminds me a lot of one of my own early career screw-ups, where I had a batch job uploading images that was set up with unlimited retries. It failed halfway through, and the unlimited retries caused it to upload the same three images 100,000 times each. We emailed Cloudinary, the image CDN we were using, and they graciously forgave the costs we had incurred for my mistake.</text><parent_chain><item><author>calmlynarczyk</author><text>This is more just &amp;quot;missed optimization opportunities in EC2&amp;quot; than a statement about mistakes in AWS as a whole.&lt;p&gt;If you want to talk systemic AWS mistakes you can make, we accidentally created an infinite event loop between two Lambdas. Racked up a several-hundred-thousand dollar bill in a couple of hours. You can accidentally create this issue across lots of different AWS services if you don&amp;#x27;t verify you haven&amp;#x27;t created any loops between resources and don&amp;#x27;t configure scaling limitations where available. &amp;quot;Infinite&amp;quot; scaling is great until you do it when you didn&amp;#x27;t mean to.&lt;p&gt;That being said, I think AWS (can&amp;#x27;t speak for other big providers) does offer a lot of value compared to bare-metal and self-hosting. Their paradigms for things like VPCs, load balancing, and permissions management are something you end up recreating in most every project anyways, so might as well railroad that configuration process. I&amp;#x27;ve experienced how painful companies that tried to run their own infrastructure made things like DB backups and upgrades that it would be hard to go back to a non-managed DB service like RDS for anything other than a personal project.&lt;p&gt;After so many years using AWS at work, I&amp;#x27;d never consider anything besides Fargate or Lambda for compute solutions, except maybe Batch if you can&amp;#x27;t fit scheduled processes into Lambda&amp;#x27;s time&amp;#x2F;resource limitations. If you&amp;#x27;re just going to run VMs on EC2, you&amp;#x27;re better off with other providers that focus on simple VM hosting.</text></item></parent_chain></comment><story><title>Mistakes I&apos;ve Made in AWS</title><url>https://laravel-news.com/aws-mistakes</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>mfrye0</author><text>&amp;gt; If you want to talk systemic AWS mistakes you can make, we accidentally created an infinite event loop between two Lambdas. Racked up a several-hundred-thousand dollar bill in a couple of hours.&lt;p&gt;I did more or less the same thing, but with a 3rd party webhook. The bill almost killed my company.</text><parent_chain><item><author>calmlynarczyk</author><text>This is more just &amp;quot;missed optimization opportunities in EC2&amp;quot; than a statement about mistakes in AWS as a whole.&lt;p&gt;If you want to talk systemic AWS mistakes you can make, we accidentally created an infinite event loop between two Lambdas. Racked up a several-hundred-thousand dollar bill in a couple of hours. You can accidentally create this issue across lots of different AWS services if you don&amp;#x27;t verify you haven&amp;#x27;t created any loops between resources and don&amp;#x27;t configure scaling limitations where available. &amp;quot;Infinite&amp;quot; scaling is great until you do it when you didn&amp;#x27;t mean to.&lt;p&gt;That being said, I think AWS (can&amp;#x27;t speak for other big providers) does offer a lot of value compared to bare-metal and self-hosting. Their paradigms for things like VPCs, load balancing, and permissions management are something you end up recreating in most every project anyways, so might as well railroad that configuration process. I&amp;#x27;ve experienced how painful companies that tried to run their own infrastructure made things like DB backups and upgrades that it would be hard to go back to a non-managed DB service like RDS for anything other than a personal project.&lt;p&gt;After so many years using AWS at work, I&amp;#x27;d never consider anything besides Fargate or Lambda for compute solutions, except maybe Batch if you can&amp;#x27;t fit scheduled processes into Lambda&amp;#x27;s time&amp;#x2F;resource limitations. If you&amp;#x27;re just going to run VMs on EC2, you&amp;#x27;re better off with other providers that focus on simple VM hosting.</text></item></parent_chain></comment><story><title>Mistakes I&apos;ve Made in AWS</title><url>https://laravel-news.com/aws-mistakes</url></story>