<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ioncoada on Medium]]></title>
        <description><![CDATA[Stories by Ioncoada on Medium]]></description>
        <link>https://medium.com/@ioncoada?source=rss-6d3ca84d77c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*g3lbGy78bNig3h7y</url>
            <title>Stories by Ioncoada on Medium</title>
            <link>https://medium.com/@ioncoada?source=rss-6d3ca84d77c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:52:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ioncoada/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My path to AWS Naming Convention]]></title>
            <link>https://medium.com/@ioncoada/avoiding-mess-aws-naming-convention-9b2a18943074?source=rss-6d3ca84d77c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b2a18943074</guid>
            <category><![CDATA[cloud-infrastructure]]></category>
            <category><![CDATA[naming-conventions]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Ioncoada]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 09:13:17 GMT</pubDate>
            <atom:updated>2026-09-21T08:28:01.132Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>There are only two hard things in Computer Science: cache invalidation and </em><strong><em>naming things</em></strong><em>.</em></blockquote><blockquote><em>Phil Karlton</em></blockquote><h3>Introduction</h3><p>Many startups begin with a strong idea and just with a small team of engineers — maybe two, three, or five and in the rush to deliver, everything is created manually in cloud, and resources are given names on the fly. At this stage, that’s completely understandable — the priority is speed, not long-term maintainability.</p><p>But as the project grows and succeeds, new engineers are hired, and complexity increases. Suddenly, questions start coming up every week: <em>Why is this resource named like that? Where can I find the staging link? What is the secret’s name?</em> Without realizing it, the lack of a clear structure begins to slow everyone down.</p><p>This is the point where a roadmap for infrastructure modernization becomes essential. And one of the very first steps on that roadmap is establishing a <strong>naming convention</strong>.</p><h3>Context Matters</h3><p>At the time of writing this article, I am in the process of creating a naming convention, but what I want to mention is that it is very important to understand your <strong>current</strong> <strong>context,</strong> such as, but not limited to:</p><ul><li>How many products does the company have</li><li>whether a centralized or decentralized infrastructure management model</li><li>single/multiple accounts</li><li>infrastructure accesses</li><li>etc, etc.</li></ul><p>Here is my case: a company that develops multiple products, shared across different AWS accounts, with common tools (e.g., CICD, observability, security)…</p><h3>The idea</h3><p>Automation becomes far more effective when built on predictable scenarios. Your responsibility is to establish that predictability upfront — otherwise, the result will be technical debt, wasted time, and unnecessary confusion.</p><h3>Benefits</h3><ul><li>Indicates the role and ownership of a resource.</li><li>Helps formalize expectations and promote consistency within an infrastructure.</li><li>Prevents name clashes when resource names must be unique.</li><li>Makes resources easier to locate.</li><li>Reduces effort to understand code and allows developers to focus on more important aspects than arguing over naming standards.</li><li>Allows sorting and filtering resources quickly.</li><li>It is a prerequisite for establishing any successful cloud governance and automated policy evaluation or enforcement.</li></ul><h3>The rules</h3><ol><li>AWS limits the name length for most of the resources to <strong>63 characters</strong>.</li><li>Use <strong>lowercase</strong> every time.</li></ol><p>Lowercase letters are faster and easier to type. The technical reason is that this avoids name collisions for systems that do not support case-sensitive names, such as DNS. Plus, typographers generally point to the fact that word shape is more distinctive with lower-case than it is with all upper-case.</p><ol><li>Use <strong>only</strong> <strong>letters</strong> and <strong>numbers</strong>.</li><li>Use <strong>hyphens </strong>( — ) to separate individual components.</li></ol><p>Hyphens are native when it comes to joining component words.This is also technically the safest choice in terms of SEO, as these are used as word delimiters for search engines.</p><p>Avoid using hyphens inside a component, for example, you <strong>won’t </strong>use api-gateway as a project name, since this would mean two distinct components; instead, use apigateway, backoffice, crm, etc,</p><ol><li>Avoid unnecessary <strong>redundancy</strong>.</li></ol><p>For instance, when provisioning an EC2 instance, there’s no need to include `ec2` in its name, just as an RDS instance doesn’t require the word database in its identifier.</p><h3>Global Naming Pattern</h3><blockquote><strong>[prefix]-[project]-[env]-[location]-[description]-[suffix]</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*YR3YuffM8jKehX7CjODiLQ.png" /></figure><p><strong>Prefix</strong></p><p>The prefix component represents a globally distinct element used to differentiate main products such as <strong><em>dogs </em></strong>( apigateway, crm , backoffice), <strong><em>cats (</em></strong> searchengine, automation ) , <strong><em>fish</em></strong>, etc.</p><p>This could be extended to team names as well, but since teams are often reorganized within the company, I recommend avoiding this approach.</p><p>Because we follow a federated model — where one AWS account may federate resources of another one or have all metrics from all accounts centralized into one solution, then this component is crucial for avoiding ambiguity.</p><p>Additionally, making it optional will create confusion about whether to start with it or not, which is not a goal in terms of filtering and sorting.</p><p><strong>Project</strong></p><p>Generalize the project component to cover workloads, applications, infrastructure tools, or other general usage.</p><p>Examples:</p><ul><li>crm</li><li>search</li><li>backoffice</li><li>sonaqube</li><li>grafana</li></ul><p><strong>Env</strong></p><p>The env component captures the environment where the resource operates, use a short form of its name..</p><p>Examples:</p><ul><li>dev — from development</li><li>stage — from staging</li><li>prod— production</li></ul><p><strong>Location</strong></p><p>The location component is required only when resources exist in multiple regions or zones.</p><p>Regional resources: use the abbreviation of the official AWS region name without hyphens.</p><p>Examples:</p><ul><li>useast1</li><li>eucentral1.</li></ul><p>Zonal resources:<strong> </strong>append the availability zone letter.</p><p>Examples:</p><ul><li>useast1a</li><li>useast1b</li><li>useast1c</li></ul><p><strong>Description</strong></p><p>The description component provides additional context for distinguishing resources of the same project but serving different roles.</p><p>Examples:</p><ul><li>A set of load balancers separated by purpose (public, private).</li><li>A group of workloads split by function (frontend, backend ).</li></ul><p><strong>Suffix</strong></p><p>Apply a suffix to distinguish a resource from others when multiple instances exist or when uniqueness is required.</p><p>Examples:</p><ul><li>Since S3 bucket names must be globally unique, you can append a suffix such as the AWS account ID (dogs-crm-prod-111111111111).</li><li>If you have multiple EC2 instances serving the same workload, you can distinguish them by adding numeric suffixes like ( `01`, `02`, `03`).</li></ul><h3>Examples</h3><p>Now, let’s look at some complete examples that illustrate how resources should be named according to the defined pattern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*Ya4LNouPmFjPnH0rIgHcNw.png" /></figure><h3>Special Cases / Exceptions</h3><p>Although the Global Naming Pattern applies to most resources, there will always be exceptions — such as projects that don’t support hyphens in their names or cases where the pattern simply doesn’t fit. In such scenarios, use a subset of the pattern and most importantly, document all deviations.</p><p><strong>AWS Secret Manager / Parameter Store / Cloudwatch Logs Groups</strong></p><p>While not an enforced restriction, AWS documentation suggests using forward slashes (/) to define hierarchical naming structures. This approach is later leveraged by tools such AWS CLI to enable path-based searches (e.g., `aws ssm get-parameters-by-path — path /fish/core/stage`).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*aBn0E9vK-hYEiVk6aoCYEA.png" /></figure><p><strong>DNS / Route53</strong></p><p>Unlike the current global naming pattern, which appears flat from left to right, the DNS structure is almost inverted: the root domain (e.g., prefix) comes last, followed by the environment (env), and so on.</p><p>This structure also makes it easier to leverage zone delegation in the future.</p><p>For example, given a technical domain mycomp.tech, we can create variations as needed by following the pattern below, replacing hyphens (-) with dots (.):</p><blockquote><strong>[suffix]-[description]-[location]-[project]-[env]-[prefix]</strong></blockquote><p>Examples:</p><ul><li>backoffice.stage.mycomp.tech</li><li>api.backoffice.stage.mycomp.tech</li><li>db.backoffice.stage.mycomp.tech</li><li>apigateway.stage.mycomp.tech</li><li>crm.stage.mycomp.tech</li><li>eucentral1.kafka.stage.mycomp.tech</li><li>grafana.ops.mycomp.tech</li><li>sonarqube.ops.mycomp.tech</li></ul><h3>Final thought</h3><p>There may never be a perfect model for every case, but once you agree on one, stick with it, as this will serve as your tool for auto-discovery.</p><p><strong>Credits</strong>: Thanks to <a href="https://x.com/stepanstipl">Stephan</a> and <a href="https://hashnode.com/@acwwat">Anthony</a> for their insights on this topic.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b2a18943074" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>