The Rise Of The Tag Nazis

Tag Nazi Meaning

What about it? Consciously or subconsciously, you could be one.

With the increased complexity and size of the infrastructure on AWS, it is difficult for technology and management teams to track accountability of the cloud in terms of cost visibility, asset management, and governance without proper tagging in place.

Increased Cloud Costs

Due to improper tagging practices, there will be lack of visibility into who is spending how much and for what, leading to unidentified cloud costs. This further leads to bill shock. Above all, a lot of time is spent on understanding cloud cost of the cloud infrastructure.

Unaccounted Assets

Non-uniform or poorly tagged resources/services on the cloud also lead to time wastage during critical situations. This further leads to an engineer inefficiently looking for a resource during an incident — meaning more downtime of your services/applications running on the architecture and poor customer experience and loss of revenue.

Lack of Governance

Inconsistent tags can also cause security, compliance and business risks. One of the example being lack of visibility and understanding of resources/services that house critical data, which can be either customer data or internal data.

That is why asset tagging is one of the ways how technology teams get visibility across the cloud infrastructure. AWS provides this service to enable its users to create and manage tags that make it easier to manage, search for, and filter resources in an AWS architecture.

With the issues at hand, some management team has resorted to enforced termination of resources with improper tags or no tags in the AWS environment, destroying the work done by employees.

Solution at hand

The first step is to understand and pinpoint resources that have not been tagged, which can be done through a simple workflow on the Workflow Editor.

Here’s discussion on Reddit about “How do you enforce tagging policies in your AWS account?”

Collaborate

Involve teams to understand how and what problems affect them and collaborate on setting and understanding cloud KPIs that needs to be tracked.

Create Schema for Tags

After understanding the cloud KPIs and affected teams, create a schema for tags which cover all the concerns of the teams as well as of the management.

Here’s a discussion about the tagging scheme on Reddit and some suggestions by AWS.

Enforcing Policies

You can start enforcing the schemas defined earlier and choose from a set of policies which could terminate, suspend, or notify incorrectly tagged resources. This allows you to adjust schemas to match the business needs and limit exposure.

Outcome

If we talk strictly in terms of cloud visibility, you could end up with following advantages depending upon the tagging scheme on which you have decided:

  • Cost Control
  • Asset Accountability
  • Application Tracking
  • Configuration Tracking
  • Security Visibility
  • More based on the tagging scheme

Final Thoughts: It’s great if you have taken measures to collaborate with your Dev team, educated them on the benefits of using standardized tags, created schemas and created policies. Thing again: have you been a “Tag Nazi” all the way long, micromanaging your Dev teams’ code lines??!! In this digital age where tooling and automation have seeped into the DNA of every company, why not standardize as well as regulate tagging principles and automate them too under compliance?

TotalCloud is a visual cloud infrastructure management platform. It enables the user to view the AWS architecture from the tags perspective and gain more infrastructural visibility.

The Rise Of The Tag Nazis

Smart Scheduling at your fingertips

Go from simple to smart, real-time AWS resource scheduling to save cost and increase team productivity.

Learn More
More Posts

You Might Also Like

AWS Use Case Files
Launch EC2 Instances with CloudFormation
CloudFormation is the gateway to Infrastructure-as-code for AWS users. Learn how you can deploy Cloudformation templates through Totalcloud workflows and increase your customization.
June 25, 2020
Hrishikesh
AWS Use Case Files
JIRA Triggered Cloud Management
What if cloud management were as easy as raising a JIRA ticket? Almost every DevOps team uses JIRA as a standard means of issue tracking & task management. It’s a given that it would be a seamless process if you could also integrate your cloud processes with it.
June 16, 2020
Hrishikesh
AWS Use Case Files
Totalcloud Launches New Temporary Rightsizing Feature
You can't always shut down your EC2 machine outside of business hours since some machines are needed up for longer periods. Totalcloud's new downgrade feature lets you optimize your costs by letting you downgrade your machines in a fixed schedule.
June 8, 2020
Hrishikesh
AWS Use Case Files
S3 Cost Saving: Archiving Compressed S3 Data into Glacier
We've devised a new workflow to cut your archiving costs. Simplify the storage, compression, and transfer of your S3 data into S3 Glacier with 1 workflow and 8 nodes.
June 8, 2020
Hrishikesh
AWS Use Case Files
Creating a 3-tier Application With Totalcloud’s Code-Free Workflows
As part of a new request by a customer, we've developed a workflow to deploy 3-tier applications much faster. Utilising merely 3 workflows to achieve a result that would have you scripting and troubleshooting for hours. This post gives you an idea of how this workflow functions, the services being used, and how you can benefit from it.
June 2, 2020
Hrishikesh
AWS Tips & Tricks
Componentized Cloud Management: The way ahead for Cloud Automation
When something gets complex, our primary approach is to break it down — even cloud management. If you’re a part of a growing company that uses the cloud, you can see your infrastructure becoming more…
May 29, 2020
Sayonee