Tag Policy

Last updated 11 days ago

Tag Policy

The Tag Policy tab provides billing tag configuration features to help accurately categorize and allocate your organization's cloud costs. You can define policy-based tag keys and acceptable tag values in advance to enable cost tracking by various criteria, such as team, project, or product.

Configured billing tags are integrated with OpsNow’s Analysis and Budget features, making it possible to visualize cloud usage by team or department using showback and chargeback models. You can also monitor the real-time activation status of each tag’s AWS Cost Allocation, and apply the same tag policies retroactively to past resources using the Backfill feature.

Click [Add Billing Tag] to add a billing tag. A new row will be added to the list, and you can add up to 20 billing tags.
The available tag keys are listed. Click the drop-down menu to select the tag you want to use as a billing tag.
Select a Tag Key to activate the Tag Value field. From the corresponding list of values for the selected tag key, choose the required Tag Value. Multiple selections are allowed.
The tag’s status is displayed as ‘Active’ or ‘Inactive’ based on the Cost Allocation Tag status in the AWS console. Only active tags will be linked to and collect AWS cost assignment tag information in OpsNow, and will be shown in the required tag table. To update the status, click the button next to ‘AWS Cost Allocation Status’ and edit the settings.
To delete a tag, click the [X] delete button to remove the row from the required billing tag list.
Click [Cancel] to exit the operation and return to the previous screen.
Click the [Save] button to finalize the required tag settings.
By clicking [Backfill Tags], you can retroactively apply tags to historical data, even after activating the Cost Allocation Tag. Tag data will be backfilled starting from the selected month, based on the current saved state of the Cost Allocation Tag. In AWS cost management, retroactive tagging is supported for up to 12 months, allowing for accurate cost analysis by applying tags to previous billing data.

*Note:

Tags can only be backfilled if they were previously assigned to the resource.
- Backfilling is only possible for periods when the tag was already applied to the resource.
- For example, if a Project tag was applied to a resource in June 2023 and later activated as a billing tag in November 2023, you can use backfill to retroactively apply the tag to cost data starting from June 2023. However, since the tag did not exist on the resource before May 2023, cost data for that period cannot be tagged.
A backfill request can be submitted once every 24 hours.
- You cannot submit a new request while a previous backfill operation is still in progress.
Backfill applies the current activation status of a tag retroactively.
- You can use Backfill to either activate or deactivate a tag for past data.
- For example, if the Team tag was previously active but is now deactivated, submitting a Backfill request will remove the tag from historical data as well.
Backfill results are not applied immediately.
- Even after the backfill process is completed, it may take up to 24 hours for the changes to be reflected in the service.

PreviousTag Group NextHistory

Last updated 11 days ago

Click [Add Billing Tag] to add a billing tag. A new row will be added to the list, and you can add up to 20 billing tags.
The available tag keys are listed. Click the drop-down menu to select the tag you want to use as a billing tag.
Select a Tag Key to activate the Tag Value field. From the corresponding list of values for the selected tag key, choose the required Tag Value. Multiple selections are allowed.
The tag’s status is displayed as ‘Active’ or ‘Inactive’ based on the Cost Allocation Tag status in the AWS console. Only active tags will be linked to and collect AWS cost assignment tag information in OpsNow, and will be shown in the required tag table. To update the status, click the button next to ‘AWS Cost Allocation Status’ and edit the settings.
To delete a tag, click the [X] delete button to remove the row from the required billing tag list.
Click [Cancel] to exit the operation and return to the previous screen.
Click the [Save] button to finalize the required tag settings.
By clicking [Backfill Tags], you can retroactively apply tags to historical data, even after activating the Cost Allocation Tag. Tag data will be backfilled starting from the selected month, based on the current saved state of the Cost Allocation Tag. In AWS cost management, retroactive tagging is supported for up to 12 months, allowing for accurate cost analysis by applying tags to previous billing data.

*Note:

Tags can only be backfilled if they were previously assigned to the resource.
- Backfilling is only possible for periods when the tag was already applied to the resource.
- For example, if a Project tag was applied to a resource in June 2023 and later activated as a billing tag in November 2023, you can use backfill to retroactively apply the tag to cost data starting from June 2023. However, since the tag did not exist on the resource before May 2023, cost data for that period cannot be tagged.
A backfill request can be submitted once every 24 hours.
- You cannot submit a new request while a previous backfill operation is still in progress.
Backfill applies the current activation status of a tag retroactively.
- You can use Backfill to either activate or deactivate a tag for past data.
- For example, if the Team tag was previously active but is now deactivated, submitting a Backfill request will remove the tag from historical data as well.
Backfill results are not applied immediately.
- Even after the backfill process is completed, it may take up to 24 hours for the changes to be reflected in the service.