Tagging repositories in Amazon CodeCommit - Amazon CodeCommit
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Tagging repositories in Amazon CodeCommit

A tag is a custom attribute label that you or Amazon assigns to an Amazon resource. Amazon tags are different from Git tags, which can be applied to commits. Each Amazon tag has two parts:

  • A tag key (for example, CostCenter, Environment, Project, or Secret). Tag keys are case sensitive.

  • An optional field known as a tag value (for example, 111122223333, Production, or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag values are case sensitive.

Together these are known as key-value pairs. For limits on the number of tags you can have on a repository and restrictions on tag keys and values, see Limits.

Tags help you identify and organize your Amazon resources. Many Amazon services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to a CodeCommit repository that you assign to an Amazon S3 bucket. For more information about tagging strategies, see Tagging Amazon Resources.

In CodeCommit, the primary resource is a repository. You can use the CodeCommit console, the Amazon CLI, CodeCommit APIs, or Amazon SDKs to add, manage, and remove tags for a repository. In addition to identifying, organizing, and tracking your repository with tags, you can use tags in IAM policies to help control who can view and interact with your repository. For examples of tag-based access policies, see Example 5: Deny or allow actions on repositories with tags.