Tagging strategy: start with these 5 recommendations

Filipe Barretto • May 22, 2024

An efficient tagging strategy is one of the most important items for infrastructure management among many other decisions to achieve efficient cloud management and adopt a FinOps framework. Despite its critical role, many companies still falter in maintaining even a minimum level of organization in this area. This challenge often stems from a lack of information and the difficulty of cultural change among employees, often by attempting to start on an overly ambitious scale.


With this issue in mind, here are 5 recommendations on how to gradually progress in this area and to increase the likelihood of success.


You may also read:
>> Success story: Cloud costs drop 35% with tagging strategy and resource optimization for logistics leader


1. Define basic and mandatory tagging


One of the most common mistakes at the outset of this journey is attempting to implement too many mandatory tags. This can lead to frustration and decreased engagement, as it burdens a team not yet accustomed to such tasks. To mitigate this challenge, we recommend starting with a few essential tags:


  • Application
  • Environment (for example, Production, Homologation, and Development)
  • Cost Center
  • Owner

In addition to defining tagging keys, it’s essential to establish standards for tagging values. Take the term “production” for example. Policies will not be effective if team members use variations such as ‘prod’ or ‘Production’. Therefore, adopting a company-wide standard is crucial for consistency.


2. Choose a single account to initiate policy implementation


To garner support over time, it’s ideal to select one account, potentially the one with the highest spending, to begin enforcing the tagging policy. This approach ensures a smoother transition, rather than abruptly changing procedures overnight.


For instance, on AWS, you can utilize Tagging Policies to establish mandatory rules.


3. Require new resources’ creation with tags


Ideally, all new features should be developed using Infrastructure as Code (IaC), with tagging rules already established. This should be the long-term goal. However, initially, it will be time-consuming to review existing resources and apply tags to all of them. As a first step, it is recommended to require new resources to be created with tags. This will prevent the problem from worsening and initiate the shift in culture and processes.


4. Review the most expensive resources and implement the tagging strategy


Now that we’ve established the rules and the new features in our main account have been created with tags, it’s time to deal with the past. The question arises: where to start? The answer is simple: start where the impact is greatest.


When examining spending on the account, identify the services with the highest costs and prioritize the review and implementation of tags. Over time, you will have a clearer understanding of the company’s main expenses, gradually covering all resources.


5. Spread this practice throughout the company


Once the tagging pilot is up and running in one account, likely, teams will naturally start adopting it in other accounts. Now it’s time to make the tagging policy mandatory, following the same sequence of requiring new features to be created with tags first and then reviewing the biggest problem areas in each account.


By following this process, there is a great chance that, in a few months, you will be much more successful in implementing tagging policies in your company. In this FinOps Foundation podcast, Sarah Kula and Svetlana Pogrebny from the Canadian Institute for Health Information share their learnings, mistakes, and successes in implementing a tagging strategy, following a very similar working model. In a matter of months, they managed to achieve something they hadn’t done in years.


In summary, when organizations follow these 5 steps before using a tagging strategy, they can make a bigger difference with kindness. This step-by-step method doesn’t just make things work better and use resources smarter, it also creates a supportive atmosphere for growth and success in meeting cloud management goals. Start now!


Filipe Barretto
Filipe Barretto is AWS Practice Leader at e-Core and AWS Community Hero. Today, his main goal is to help companies better use cloud computing technologies to stand out.

LET'S CONNECT

Ready to unlock your team's potential?


e-Core

We combine global expertise with emerging technologies to help companies like yours create innovative digital products, modernize technology platforms, and improve efficiency in digital operations.


You may also be interested in:

Por e-Core 31 de julho de 2025
Energisa modernized 70 systems by migrating to AWS with e-Core’s support, gaining scalability, availability, and performance in the energy sector.
Por e-Core 22 de julho de 2025
A strategic approach to modernizing code At e-Core, we often partner with organizations whose software technically “works” in production, but just barely. Over time, shifting teams, competing priorities, and tight deadlines lead to codebases that are fragile, expensive to maintain, and risky to enhance. In this context, software refactoring becomes more than a technical task. It’s a business strategy that preserves continuity while unlocking future growth. Defining refactoring: Evolution without disruption Software refactoring is the disciplined restructuring of existing code, improving readability, modularity, and performance, without altering its external behavior. Unlike a full rewrite, refactoring delivers incremental value by: Accelerating feature delivery through cleaner, more modular code. Reducing operational risk by eliminating brittleness and regressions. Lowering total cost of ownership by making enhancements less labor-intensive. Why refactoring matters for business  Healthy codebases have a direct business impact: Faster Time-to-Market: Modular components support parallel development and faster releases. Greater resilience: Decoupled services isolate failures and simplify maintenance. Easier onboarding: Clear architecture and design patterns help new developers ramp up quickly. Sustainable cost savings: Less firefighting, fewer regressions, and lower maintenance overhead. What may look like a simple “cleanup” is often the first step toward digital reinvention. Refactoring techniques In enterprise environments built on Java, C#, or Python, we apply proven object-oriented refactoring techniques to increase cohesion and extensibility: Class decoupling: Split monolithic classes into focused, single-responsibility components. SOLID principles: Apply interface segregation and dependency inversion to stabilize architecture. Composition over inheritance: Build flexible, interchangeable structures. Testability enhancements : Isolate side effects and inject dependencies for better test coverage. These techniques form the foundation of our incremental software refactoring roadmaps. Beyond OO: Choosing the right tools for each paradigm Modern languages blend programming paradigms. We help clients apply the right tools to the right problems: Functional patterns in Python to create concise, side-effect-free data pipelines. Kotlin/Scala hybrids that combine OO structure with expressive functional constructs. C# LINQ and Async for declarative data queries and scalable concurrency. This multi-paradigm approach ensures that systems remain robust, flexible, and expressive. A refactoring story: From debt to differentiation Case Study: Regional logistics provider
Por e-Core 16 de julho de 2025
Background Ricksoft is known for its popular work and project management apps on the Atlassian Marketplace, including WBS Gantt-Chart for Jira and Excel-like Bulk Issue Editor for Jira. Originating in Japan, the company has grown to serve over 8,000 customers worldwide through nine apps. Their tools are trusted by some of the world’s most innovative companies to boost productivity and manage complex work. By 2019, Ricksoft was seeing growing demand from customers in the Americas and Europe, and needed to scale its support operation beyond Japan. To serve new markets effectively, they had to provide fast, high-quality service in English and across time zones, while maintaining the responsiveness and care that defined their brand. That’s when they turned to e-Core. Our approach We designed a support solution based on three key principles: timezone alignment, consistent high-quality service, and cultural alignment . To get things right from the start, our analysts flew to Japan for in-depth training. They didn’t just learn the products; they learned how Ricksoft works , communicates, and supports customers. Once training wrapped, we built the support operation around Ricksoft’s priorities: timely responses, consistency, and a thoughtful, human tone. We created detailed documentation and a clear process for hiring and onboarding, ensuring every new analyst could step into the role with confidence and alignment. We also introduced monthly updates to the knowledge base and took responsibility for keeping existing articles relevant. That work paid off: most tickets are now resolved in just two to three exchanges , and self-service performance has improved across the board. Today, Ricksoft holds a satisfaction rate of 89 percent and a CSAT of 4.63 out of 5 , well above industry averages. As new analysts joined over the years and support expanded to more products, the service quality remained consistent. “We place great confidence in e-Core’s hiring decisions,” says Alessandro Cristiano, Support Manager at Ricksoft. “They understand how we work, and their mission, values, and culture attract good talent. We had five different generations of agents in seven years, and the work was consistent all the time.” Building long-term value through support. To make support even more impactful, we set up a feedback loop between support and product. Recurring issues and feature requests are flagged and shared with product managers, turning support into a valuable channel to inform product strategy. Tone and empathy matter, too. Ricksoft’s brand is rooted in respect, clarity, and thoughtful communication. We greet returning customers by name, tailor our closings, and have consistently met their SLA targets—with 99% first-response compliance within 12 hours or less. “What is special about e-Core is that they listen first,” Cristiano says. “They don’t try to mold things just for efficiency if it doesn’t work for you. First, they absorb your culture, and then transform it.” To strengthen Ricksoft’s presence in the Atlassian Marketplace , we introduced a post-ticket review request process. That simple step led to more customer reviews, better app ratings, and increased visibility. “We’re now at the top search results, which helps increase our app installs, and ultimately our revenue,” says Cristiano. We also monitor Ricksoft-related activity in the Atlassian Community. When their apps are mentioned, our team responds quickly and accurately, helping Ricksoft remain visible, helpful, and credible in the ecosystem .