<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Best Practices on Adam Divall</title>
    <link>/categories/best-practices/</link>
    <description>Recent content in Best Practices on Adam Divall</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 28 Oct 2023 19:25:42 +0100</lastBuildDate>
    <atom:link href="/categories/best-practices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tagging Strategies for AWS</title>
      <link>/article/best-practices/tagging-strategies/</link>
      <pubDate>Sat, 28 Oct 2023 19:25:42 +0100</pubDate>
      <guid>/article/best-practices/tagging-strategies/</guid>
      <description>&lt;h2 id=&#34;what-are-tags--why-do-we-need-them&#34;&gt;What are tags &amp;amp; why do we need them?&lt;/h2&gt;&#xA;&lt;p&gt;Amazon Web Services (AWS) allows you to assign metadata to many of your AWS resources in the form of tags. Each tag is a simple label consisting of a key and an optional value to store information about the resource or data retained on that resource. Implementing a consistent tagging strategy can make it easier to filter and search for resources, monitor cost and usage, as well as manage your AWS environment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
