<story><title>Please fix the AWS free tier before somebody gets hurt</title><url>https://cloudirregular.substack.com/p/please-fix-the-aws-free-tier-before</url></story><parent_chain><item><author>swiftcoder</author><text>I&amp;#x27;m also going to point out, as a former AWS engineer, that 
&amp;quot;too hard&amp;quot; isn&amp;#x27;t in the AWS engineering vocabulary. If an AWS engineer were to dismiss something as &amp;quot;too hard&amp;quot;, they&amp;#x27;d be on the fast track to a performance-improvement-plan.&lt;p&gt;The problem isn&amp;#x27;t that it&amp;#x27;s too hard. It&amp;#x27;s that it isn&amp;#x27;t a business priority. As soon as it becomes prioritised, a legion of very smart AWS engineers will solve it.</text></item><item><author>jiggawatts</author><text>Everyone: PLEASE stop making the argument that it&amp;#x27;s &amp;quot;too hard&amp;quot; or even &amp;quot;impossible&amp;quot; to implement spending limits.&lt;p&gt;As the article points out: Every other cloud does this! They all have non-production subscription types with hard spending limits.&lt;p&gt;There&amp;#x27;s a difference between &amp;quot;unable&amp;quot; and &amp;quot;unwilling&amp;quot;.&lt;p&gt;The people that refuse to understand the difference are the same people that don&amp;#x27;t understand that &amp;quot;unsupported&amp;quot; isn&amp;#x27;t synonymous with &amp;quot;cannot be made to function&amp;quot;.&lt;p&gt;Don&amp;#x27;t be that person.&lt;p&gt;If you have a large account and you&amp;#x27;re in regular contact with an AWS sales representative, &lt;i&gt;pressure them&lt;/i&gt; into making this happen. Even if you work for Megacorp with a $$$ budget, keep in mind that your &lt;i&gt;future hires&lt;/i&gt; need to start somewhere, need to be able to learn on their own, and need to do so &lt;i&gt;safely&lt;/i&gt;.&lt;p&gt;Don&amp;#x27;t walk down the same path as IBM&amp;#x27;s mainframes, where no student anywhere ever has been able to learn on their own, making it a dead-end for corporations who pay billions for this platform. You, or your company will eventually pay this price if AWS keeps this IBM-like behaviour up.&lt;p&gt;Think of the big picture, not just your own immediate personal situation.&lt;p&gt;Apply this pressure yourself, because the students you want to hire next year can&amp;#x27;t.</text></item></parent_chain><comment><author>crispyambulance</author><text>As an antidote to the &amp;quot;nothing is too hard&amp;quot; flex...&lt;p&gt;Everything has trade-off&amp;#x27;s. When a responsible person says something is &amp;quot;too hard&amp;quot; it&amp;#x27;s because they&amp;#x27;ve evaluated the consequences and have deemed them too costly in terms of time, resources, cost, maintenance, or strategy&amp;#x2F;lost-opportunity. Some things really are &amp;quot;too hard&amp;quot;.&lt;p&gt;I agree it&amp;#x27;s not too hard technically but am surprised at your contradictory suggestion AWS would deploy &amp;quot;a legion of very smart engineers&amp;quot; to solve it if they decided to implement that ordinary feature. How smart are they?&lt;p&gt;I suspect the truth here is a bit more ugly. AWS doesn&amp;#x27;t want to do it because they see the pocket-change taken from accidental mishaps as a net positive. They don&amp;#x27;t care if it inflicts suffering on students and novices. Sure, they&amp;#x27;ll fix individual cases if they&amp;#x27;re shamed publicly or if the individual contacts them in exactly the right way, but at the end of the day, it&amp;#x27;s more money in their pocket. For every 200 dollar oopsie that gets charged back, how many go silently paid in humiliation and hardship?</text></comment>
<story><title>Please fix the AWS free tier before somebody gets hurt</title><url>https://cloudirregular.substack.com/p/please-fix-the-aws-free-tier-before</url></story><parent_chain><item><author>swiftcoder</author><text>I&amp;#x27;m also going to point out, as a former AWS engineer, that 
&amp;quot;too hard&amp;quot; isn&amp;#x27;t in the AWS engineering vocabulary. If an AWS engineer were to dismiss something as &amp;quot;too hard&amp;quot;, they&amp;#x27;d be on the fast track to a performance-improvement-plan.&lt;p&gt;The problem isn&amp;#x27;t that it&amp;#x27;s too hard. It&amp;#x27;s that it isn&amp;#x27;t a business priority. As soon as it becomes prioritised, a legion of very smart AWS engineers will solve it.</text></item><item><author>jiggawatts</author><text>Everyone: PLEASE stop making the argument that it&amp;#x27;s &amp;quot;too hard&amp;quot; or even &amp;quot;impossible&amp;quot; to implement spending limits.&lt;p&gt;As the article points out: Every other cloud does this! They all have non-production subscription types with hard spending limits.&lt;p&gt;There&amp;#x27;s a difference between &amp;quot;unable&amp;quot; and &amp;quot;unwilling&amp;quot;.&lt;p&gt;The people that refuse to understand the difference are the same people that don&amp;#x27;t understand that &amp;quot;unsupported&amp;quot; isn&amp;#x27;t synonymous with &amp;quot;cannot be made to function&amp;quot;.&lt;p&gt;Don&amp;#x27;t be that person.&lt;p&gt;If you have a large account and you&amp;#x27;re in regular contact with an AWS sales representative, &lt;i&gt;pressure them&lt;/i&gt; into making this happen. Even if you work for Megacorp with a $$$ budget, keep in mind that your &lt;i&gt;future hires&lt;/i&gt; need to start somewhere, need to be able to learn on their own, and need to do so &lt;i&gt;safely&lt;/i&gt;.&lt;p&gt;Don&amp;#x27;t walk down the same path as IBM&amp;#x27;s mainframes, where no student anywhere ever has been able to learn on their own, making it a dead-end for corporations who pay billions for this platform. You, or your company will eventually pay this price if AWS keeps this IBM-like behaviour up.&lt;p&gt;Think of the big picture, not just your own immediate personal situation.&lt;p&gt;Apply this pressure yourself, because the students you want to hire next year can&amp;#x27;t.</text></item></parent_chain><comment><author>AtomicOrbital</author><text>You are correct, which makes it even more pernicious that Amazon chooses to not fix this ... profits at any cost is not a long term benefit ...  the longer AWS fails to fix this more folks will tend to lean toward the competition especially Azure ... I have been a unix&amp;#x2F;linux server side developer since the beginning and always use a linux laptop so no fan of Microsoft however their Azure platform is lightyears ahead of AWS ... its obvious the AWS console web front end needs a wholescale rewrite from the bottom up ... again as you say its not a priority probably because all big consumers never use the AWS console as they have written their own automation layer atop the AWS SDK</text></comment>