IPF Standard - Orphaned EBS Volume Management (2023-06-22).docx

DOCX document 30 KB Posted

Attached to
Foundation Sustainment Support, Software and Integration (FS3i)
Solicitation number
HM047625R0016_Bidder_Library
Issued by

About this file

This is an internal IPF (Integrated Platform Foundation) standard document establishing management directives for orphaned EBS (Elastic Block Store) volumes within AWS accounts. The standard addresses a recurring problem where unattached EBS volumes continue to incur charges despite no active use by EC2 instances. The document prescribes mandatory controls requiring that the DeleteOnTermination attribute be set to True for all EBS volumes attached to EC2 instances, ensuring automatic deletion upon instance termination unless an exception has been formally documented and approved by the IPF Supervisory Project Manager. For volumes intended to be retained regardless of attachment status, the DeleteOnTermination attribute must be set to False and a disposition tag must be applied to the volume identifying it as deliberately retained.

This standard document does not relate directly to the FS3i (Foundation Sustainment Support, Software and Integration) pre-solicitation notice from the National Geospatial Intelligence Agency. The FS3i notice is a bidder's library announcement providing industry access to supplemental acquisition documents including industry day event slides, consolidated Q&As, and draft RFP materials for an upcoming official solicitation. No response dates, pricing terms, or specific product/service requirements are specified in either document. The orphaned EBS volume management standard appears to be an internal operational directive for AWS infrastructure governance rather than a deliverable requirement tied to the FS3i federal contracting opportunity.

View the file

Other files

File Type Posted
(U) VCPS_Breakout_Citrix_Alignment .pptx PPTX presentation
(U)_VCPS_Breakout_Storage_Pool_2.pptx PPTX presentation
(U) NGAI 8955.6_NGA Web Property Standards & Guidelines_Update_1.pdf PDF
(U) NGAI 8040.1_Configuration Mgmt_21NOV2018.pdf PDF
(U) SFA Air High-Level As-Is SV-1.png PNG image
(U) Annex_K_Cloud_Business_Guidance_v5.2.pdf PDF
(U) DODI_5000.87 SoftwareAcqPathway.pdf PDF
(U) NGA Cybersecurity Strategy_Gold.pdf PDF
(U) NGAI 8550.1_Health and Perf Monitoring of Info Sys & Apps_2NOV2020.pdf PDF
(U) NGAI 5200.1_Info Security_Update_1.pdf PDF
(U) NGA_CTDR_Template_05122025.xlsx XLSX spreadsheet
(U) Annex_D_Enterprise_Services_v5.2.pdf PDF
(U) NGAI8010.14_Password_Management_Update_1.pdf PDF
(U) FGModProgramOverview-JUNE2022-NGA.pdf PDF
(U) IPMR_Implementation_Guide_5FEB2016.pdf PDF
(U) As-Is FG IT Governance Processes Summary Final.pdf PDF
(U) Air_TAPS_VDD_1.0.0.pdf PDF
(U) DoDI8510-01_RMF_DoD_IT_change_3.pdf PDF
(U) NGAI 5205.6_Lifecycle Protection of Geospatial Info_16OCT2018.pdf PDF
IPF Developer Environment Guidance.docx DOCX document
(U) NIST500-317 Cloud Computing Accessibility Considerations_draft.pdf PDF
FINAL_Consolidated FS3i QA 2APR 2026.xlsx XLSX spreadsheet
(U) NGAI 8010.1_Info Sys Risk Mgmt Framework_Update_1.pdf PDF
(U) OMB M-17-06_Policy for Fed Agency Pub Websites Digital Services.pdf PDF
(U) Annex_E_Lifecycle_Guidance_v5.0.pdf PDF
(U) SEAD-4-Adjudicative-Guidelines.pdf PDF
(U) TRB N01-0757_APS.pdf PDF
(U) NGAI52004_rev1_Instruction_for_Operations_Security_OPSEC.pdf PDF
(U) Gov_Furnished_Property_List_(GFP).pdf PDF
(U) NGA_Cloud_Guidance_Intro_v5.2_w_signature.pdf PDF
IPF Standard - EBS Provisioned IOPS and Throughput (2023-06-22).docx DOCX document
(U) DoD_Cloud_Computing_Sec Requirements_Guide.pdf PDF
(U) NGA_Technology_Strategy_MAY2020.pdf PDF
IPF Standard - Tagging Standards (2023-05-17).docx DOCX document
(U) NGAI 5401.1_Privacy & Civil Liberties Prog_26JAN2020.pdf PDF
(U) NGAI 8040.2_Records Mgmt Prog_21OCT2020.pdf PDF
(U) Annex_G_Cloud_Data_Guidance_v5.2.pdf PDF
(U) NGAI80102_rev7_Information_System_Security_Training.pdf PDF
(U) FS2 Aero Task Order APS CONOPS.pdf PDF
(U) NSGM3202_GFMSA_Program_Manual.pdf PDF
(U) WebDVOF to FS2 Addendum_v9.pdf PDF
(U) NGA Program Level Agile Process.docx DOCX document
(U) DOD_CIO_SW_Dev_Open_Source_Guidance_SW_26JAN2022.pdf PDF
(U) NGAI 3020.26_Continuity of Operations Program_Update_1.pdf PDF
(U) Air_ACE_GTO_VDD_v1.0.28.pdf PDF
(U) DODD8140.01_Cyberspace_Workforce_Management_5OCT2020.pdf PDF
(U) Air_AAS_VDD_v170.3.pdf PDF
(U) The_NGA_Software_Way_2022.pdf PDF
IPF Standard - S3 Object Lifecycle Management (2023-05-17).docx DOCX document
(U-FOUO) Annex_C_CAMG_Charter_v5.0.pdf PDF
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 Orphaned EBS Volume Management 2023-06-21 Purpose AWS accounts within the IPF have encountered a continuous and recurring problem of unattached (orphaned) EBS volumes existing. These volumes, while not being used by any EC2 instance, still incur a charge because they are provisioned resources. This document sets directives to prevent the situation from occurring.

Standard for Orphaned EBS Volume Management

1. Upon termination of an EC2 instance, all attached EBS volumes shall also be terminated unless an exception has been made and documented as described below.

a. The DeleteOnTermination attribute of the EBS volume shall be set to True. This can be done in the AWS console at deployment time or programmatically at any time.

2. No unattached EBS volumes shall exist unless an exception has been made and documented as described below.

a. Exceptions must be approved by the IPF Supervisory Project Manager

3. If a volume is intended to be retained regardless of its attachment status, the following settings shall be made:

a. The DeleteOnTermination attribute of the EBS volume shall be set to False. This can be done in the AWS console at deployment time or programmatically at any time.

b. A tag shall be applied to the volume with the following settings:

· TagName:Disposition
· TagValue:Volume <vol_id> is deliberately retained because <state reason> Last review on <YYYY-MM-DD>

File details come from the government source that posted it. Updated .