<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cost on My AWS Rocks!</title><link>https://myaws.name/tags/cost/</link><description>Recent content in Cost on My AWS Rocks!</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 13 Oct 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://myaws.name/tags/cost/index.xml" rel="self" type="application/rss+xml"/><item><title>Cost Savings and Sustainability</title><link>https://myaws.name/why-cost-optimisation-and-sustainability/</link><pubDate>Sun, 13 Oct 2024 00:00:00 +0000</pubDate><guid>https://myaws.name/why-cost-optimisation-and-sustainability/</guid><description>&lt;p&gt;In this post I will look at why I find it hard to understand why people have to focus specifically on cost-optimisation and sustainability initiatives rather than them being part of everyday design and build activities.&lt;/p&gt;
&lt;p&gt;I am not implying these two items are not relevant, I am also not saying they shouldn&amp;rsquo;t be in the Well-Architected Framework.&lt;/p&gt;
&lt;p&gt;What I am saying is that, if you do the first 4 pillars (Operational Excellence, Security, Reliability, Performance Efficiency) well, then most of the benefits should have already been achieved and there should not be a need to perform &amp;ldquo;Cost Optimizations&amp;rdquo; or &amp;ldquo;Sustainability Audits&amp;rdquo; of your AWS estate. There might be some tweaks and improvements but the base level of &amp;ldquo;Well-Architected&amp;rdquo; for those pillars should have been achieved.&lt;/p&gt;</description></item><item><title>Wait! IP4 has a cost?</title><link>https://myaws.name/wait-ip4-has-a-cost/</link><pubDate>Sun, 11 Aug 2024 00:00:00 +0000</pubDate><guid>https://myaws.name/wait-ip4-has-a-cost/</guid><description>&lt;p&gt;&lt;strong&gt;Caveat:&lt;/strong&gt; I started this post in April because lots of people were shocked at the cost appearing on their bill. I got half way and though it wasn&amp;rsquo;t worth publishing as the chatter would die down. However 4 months later I am still  seeing people ask what can they do about IPv4 costs so thought I&amp;rsquo;d finish it off.&lt;/p&gt;
&lt;p&gt;So you will know, or should know, that the 1st February 2024 saw AWS introduce charges for all public IPv4 addresses in use within an AWS account.&lt;/p&gt;</description></item><item><title>My bill is how much‽</title><link>https://myaws.name/my-bill-is-how-much/</link><pubDate>Thu, 21 Dec 2023 00:00:00 +0000</pubDate><guid>https://myaws.name/my-bill-is-how-much/</guid><description>&lt;p&gt;One of the most common post by newcomers to AWS seems to be bill shock or unexpected charges.&lt;/p&gt;
&lt;p&gt;Some of this is from using a service with out knowing the costs or forgetting to shut something down and incurring costs for longer than planned.&lt;/p&gt;
&lt;p&gt;Some however is where accounts have been compromised and resources used by someone else.&lt;/p&gt;
&lt;p&gt;So what can you do to prevent this?&lt;/p&gt;
&lt;p&gt;This article will look at ways of securing your account and managing your costs. It is a high level article and doesn&amp;rsquo;t go into every service mentioned in detail, however it should give you enough to protect yourself and point you to further resources.&lt;/p&gt;</description></item></channel></rss>