What is Oracle Cloud Infrastructure Tagging?
The Oracle Cloud Infrastructure Tagging enables you to tag resources in any organizational scheme that you choose, so you can better organize, control, manage, and report on cloud resources. Administrators can find, control access, and perform bulk actions on a set of resources identified by tags.
How do I setup my tenancy for tagging?
Tagging is a platform service and available to all tenants. There is no setup required to enable tagging for a tenancy - you can use it today.
What are the advantages of using tags?
When you have many resources in your tenancy or a compartment, it becomes harder to track resources used for specific purposes, report on them, or take bulk actions on them. Tags help address these needs. Tags can be used in the Identity and Access Management (IAM) policy language to constrain who can apply tags. Defined tags can be created to control their application and help ensure consistent usage. Lists of resources tagged with specific keys can be retrieved from any service, and these lists can then be used in reports or scripts to take action on particular resources.
What's the pricing for this feature?
There is no charge for Oracle Cloud Infrastructure Tagging.
What is a tag?
A tag has two parts: A key and a value. For example, in "Environment=Production" the word Environment is the Key, and Production is the value. In most tagging systems the key and value are strings without any constraints. Oracle supports both free-form tags, and defined tags where the Key has a schema that restricts the values that may be used.
What are the different types of Tags?
There are two types of tags: free-form tags and defined tags.
- Free-form tags do not have any constraints or defined schema. Anyone who has access to a resource can use free-form tags. You can retrieve free-form tags on a resource, but you cannot use policy to control the application of free-form tags.
- Defined tags. These tags have a defined schema that restricts the values of tags, improves consistency of usage, and helps prevent accidental spamming of tags. Individual users can be granted or denied permissions for defined tags.
How can I tag my resources?
You can tag resources by using the Oracle Cloud Infrastructure console, CLI, or SDK. Tags can also be applied when creating resources. For example, your organization could apply a "cost center" tag when launching new compute instances.
Can tagging enhance my scripts?
Yes. Tagging allows you to easily write scripts that target batches of machines with tags. For example, you could write a script to create backups for only those compute instances that have a tag of Backup=priority.
What resources can I tag?
This list of resources I can tag includes: compute instances, console histories, instance images, instance console connections, VCNs, route-tables, security-lists, dhcp options, subnets, private ips, block storage volumes, volume backups, policies, groups, users, compartments, and your tenancy. The most up to date list may be found in documentation.
Can I modify or remove a tag that has been applied to a resource?
Yes, if you have use permission to the resource and the tag definition, you can modify or remove a tag that has been applied to it.
If I retire a tag definition, will those tags be removed from all existing resources that may have been tagged?
No, if you retire a tag key definition, the tag key definition may not be used on new resources. However, if you have current resources with that tags, they will continue to have the retired tag associated with the resource. You will have to remove the tags individually.
Can I script the application of tags to resources?
Yes. You can use our command line interface to apply tags to resources. You can also use our SDK to automate the management of tags.
Can Oracle Cloud Infrastructure help prevent tag spam?
Yes. By using defined tags, you can prevent the accidental tag spam of many misspelled tags (e.g. env, Environment, Enviro). Defined tags also support a policy which can restrict who can apply tags or change their value. Oracle Cloud Infrastructure provides a robust way to control and govern the use of tags.
How do I keep just anyone from randomly assigning or creating tags?
Tagging integrates with our Authorization System giving you policy controls to enable restrictions of tag manipulation.
What are the limits for tags?
|Description||Min Limit||Max Limit|
|Free-form tags per resource||0||10|
|Defined tags per resource||0||64|
|Length of tag namespace or key||1||100|
|Length of tag value||0||256|
|Number of tags per namespace||0||100|
|Namespaces per Tenancy||0||100|
The maximum size of a Tag on a resource is 5KB.
How many of my defined tags can be used for cost tracking?
10 defined tags maximum per resource can be used for cost tracking.
At what level (i.e. user, group, etc.) can I assign cost tracking tags?
You can tag costs by user, group, project, department or any other metadata that you choose.
How long will it take from initial tagging to seeing the data in MyServices?
It varies but it may take up to 4 hours for the cost tracking tag data to show up in MyServices.
Where can I see the breakdown of my costs by tag?
Go to the MyServices portal and select Account Management from the Dashboard. Then click on the filter link and you should see cost tracking tags in the filter drop down box.
What resources support cost tracking tags?
The following resources support cost tracking tags: Oracle Cloud Infrastructure Compute, Database, Autonomous Data Warehouse, Autonomous Transaction Processing, Object Storage, and Block Volumes.