IPF Standard - Tagging Standards (2023-05-17).docx
DOCX document 34 KB Posted
- Solicitation number
- HM047625R0016_Bidder_Library
About this file
This is a tagging standards document for cloud infrastructure resources within the Integrated Processing Facility (IPF). The document establishes mandatory tagging conventions for Amazon Web Services (AWS) EC2 and RDS resources to enable consistent cost allocation and oversight across all IPF accounts. The standard defines six tagging categories: FundingSource (the organization paying for the resource), BillingPOC (group email for the paying organization's point of contact), Org (the resource-owning organization, which may differ from FundingSource), Project (the consuming project), AdminTeam (the team responsible for configuration, operation, and maintenance), and Disposition (conditional tag explaining resource status). Five of these tags are mandatory, while Disposition is conditional based on organizational need. Tag values must follow specific formats, including hierarchical structures using colons and commas for multiple entries, with detailed examples provided (such as "NGA:S:SFN" for FundingSource and emails separated by colons for contact fields).
The standard applies specifically to EC2 and RDS resources but does not preclude organizations from implementing additional tags according to their business requirements. The document emphasizes exact matching of tag names and schemas to ensure predictable, uniform cost allocation and oversight activities across all accounts. This tagging framework was established by the National Geospatial Intelligence Agency (NGA) on May 17, 2023, and serves as a foundational governance standard for cloud resource management within the IPF environment.
View the file
Other files
Show 40 more
Latest 50 of 80 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
UNCLASSIFIED
IPF Standard Tagging Standards 2023-05-17 Purpose This document defines a simple tagging standard to be applied to all EC2 and RDS resources within the IPF. It addresses questions that are common to all accounts and does not prevent any organization from using additional tags as their business needs dictate. The goal is to apply a set of standard tags so that cost allocation and oversight activities can be conducted in a predictable and uniform manner. While all resources in AWS can be tagged, at this time the standard only applies to EC2 and RDS.
Standard for Tagging Standards Tags and tag values must exactly match the names and schemas described in this section.
1. FundingSource
a. Description: The organization that pays for the resource. Probably same as Org.
b. Objective: Cost Allocation
c. Requirement: Mandatory
d. Value format: Agency:Top Level Division:Office
e. If there are multiple offices, list them as a CSV string.
f. Example: NGA:S:SFN
2. BillingPOC
a. Description: Group email for the organization that pays for the resource. This is the POC within FundingSource.
b. Objective: Cost Allocation
c. Requirement: Mandatory
d. Value format: Email addresses separated by colons. The first entry should be an org box or distribution list, not an individual.
e. Example: some-orgainization@nga.mil:somebody@nga.mil
3. Org
a. Description: The organization that owns the resource. Probably same as FundingSource. There may be cases where the owner and the payer are not the same organization.
b. Objective: Cost Allocation
c. Requirement: Mandatory
d. Value format: Agency:Top Level Division:Office
e. If there are multiple offices, list them as a CSV string.
f. Example: NGA:S:SFN,NGA:S:SFG
4. Project
a. Description: The project that consumes the resource.
b. Objective: Cost Allocation
c. Requirement: Mandatory
d. Value format: Defined and enforced by organization
5. AdminTeam
a. Description: The team that is administratively responsible for the resource.
b. Objective: Identify who does the configuration, operation, and maintenance.
c. Requirement: Mandatory
d. Value format: Email addresses separated by colons. The first entry should be an org box or distribution list, not an individual.
e. Example: some-orgainization@nga.mil:somebody@nga.mil
6. Disposition
a. Description: Explains the reason for the state of the resource.
b. Objective: Resource status
c. Requirement: Conditional
d. Value format: Defined and enforced by organization
e. Example: This resource appears to be overprovisioned but is intentionally set this way because reasons. Re-evaluate on YYYY-MM-DD.
File details come from the government source that posted it. Updated .