<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sustainability on My AWS Rocks!</title><link>https://myaws.name/tags/sustainability/</link><description>Recent content in Sustainability 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/sustainability/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></channel></rss>