Skip to main content

Ripple - Automatic Tag Key Addition

How to automatically detect and add active AWS Cost Allocation Tag keys to a Billing Group in Ripple.

Written by Alphaus Support Team
Updated today

Overview

This guide walks you through how to automatically detect and add active AWS Cost Allocation Tags to the relevant Billing Groups in Ripple.

This feature allows you to leverage the tags configured in AWS to automate and streamline resource classification within Billing Groups. It eliminates the need to manually add resources to Billing Groups, significantly reducing the time and effort required in environments where tags are consistently applied.


Use Cases

  • When a common tag naming convention is used across multiple accounts or projects, resources can be automatically linked to the appropriate Billing Group based on the matching tags.

  • Automate the monthly resource classification process that was previously done manually.

  • Reduce operational overhead as part of a FinOps tag strategy.


How to Configure

  1. From the left menu, click Account/Group > Billing Group

  2. Select Resources > Enable automatic tag key addition

  3. From the list, select the account(s) from which you want tags to be automatically detected and applied. Multiple accounts can be selected

  4. Click Save to complete the configuration — from this point on, active AWS Cost Allocation Tags for the selected accounts will be automatically detected and the corresponding resources will be added to the Billing Group


Important Notes

  1. Tags must be activated as Cost Allocation Tags on the AWS side for this feature to work

  2. Tags that are inactive or associated with no incurred costs will not be detected

  3. Resources that are not classified by any tag will still need to be added manually

  4. If a tagged resource has its tag changed or removed, the change will be reflected at the next Billing Group recalculation


Need More Help?

If any errors occur during the process or if you have any questions, please reach out to us:

Did this answer your question?