CBL-IPF_Tagging_Standards_(2023-05-17).docx
DOCX document 33 KB Posted
- Attached to
- FS3i-RFI
- Solicitation number
- FS3i-TBD
About this file
This document contains IPF Policy Tagging Standards that define a simple tagging standard to be applied to all EC2 and RDS resources within the IPF. The tagging standards address common questions and provide a set of standard tags to enable cost allocation and oversight activities. The policy requires mandatory tags for FundingSource, BillingPOC, Org, Project, and AdminTeam, as well as an optional Disposition tag. Each tag has a defined format, objective, and examples provided.
The related federal contract opportunity is a Request for Information (RFI) from the National Geospatial-Intelligence Agency (NGA) for sustainment, support, software and integration services for the current Foundation Geospatial-Intelligence (FG) system baseline and future integrated capabilities. The RFI does not provide specifics on the products or services required, response dates, award dates, pricing terms, set asides, or incumbents. It simply states that NGA is seeking information from interested contractors.
View the file
Other files
Show all 25
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 Policy Tagging Standards 2023-05-17 Purpose This policy 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 policy only applies to EC2 and RDS.
Policy 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 .