CBL-IPF_Orphaned_EBS_Volume_Management_(2023-06-22).docx
DOCX document 29 KB Posted
- Attached to
- FS3i-RFI
- Solicitation number
- FS3i-TBD
About this file
This document is an UNCLASSIFIED policy that provides directives for managing orphaned Elastic Block Store (EBS) volumes in AWS accounts within the Integrated Program Office (IPF). The key points are:
-
Upon termination of an EC2 instance, all attached EBS volumes must also be terminated unless an exception is approved and documented. The DeleteOnTermination attribute of the EBS volume should be set to True.
-
No unattached EBS volumes are allowed to exist unless an approved exception is documented. Exceptions must be approved by the IPF Supervisory Project Manager.
-
If a volume is intended to be retained, the DeleteOnTermination attribute must be set to False and a specific tag must be applied to the volume.
The related federal contract opportunity is an RFI (FS3i-RFI) issued by the National Geospatial-Intelligence Agency (NGA) seeking information on providing sustainment, support, software, and integration services for the current Foundation Geospatial-Intelligence (FG) system baseline and future integrated capabilities.
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 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 policy sets directives to prevent the situation from occurring.
Policy 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 .