CBL-IPF_EBS_Provisioned_IOPS_and_Throughput_(2023-06-22).docx

UNCLASSIFIED

IPF Policy EBS Provisioned IOPS and Throughput 2023-06-22 Purpose Historically within IPF, metrics of disk utilization has not been shown to support the use io1 volume types or gp3 volume types with increased performance settings. These volume types and configurations have resulted in unnecessary spending. There are some cases where those configurations are warranted, but they are few. This policy aims to set an expectation that EBS volumes will be provisioned at minimum and default configurations while allowing for an increase in performance settings for situations where increased performance is shown to be needed.

Policy for EBS Provisioned IOPS and Throughput

1. The default EBS type for all EC2 instances will be gp3, where available.

a. If gp3 is not available, gp2 will be the default volume type.

2. For gp3 volumes, the default baseline of 3000 IOPS and 125 MiB/s throughput will be used unless an exception has been made.

3. For gp3 volumes that require performance greater than 3000 IOPS or 125 MiB/s throughput:

a. Approval must be obtained from the IPF Supervisory Project Manager

b. Metrics must be shown to demonstrate the need for the elevated level of performance.

c. The volume will be tagged as follows:

· TagName: Disposition

· TagValue: Use of increased performance configuration (IOPS: <NNN> / Throughput: <NNN>) approved by <Name and Org> on <YYYY-MM-DD>

4. Volume type io1 will not be used unless an exception has been made.

5. For io1 volumes:

a. Approval must be obtained from the IPF Supervisory Project Manager.

b. Metrics must be shown to demonstrate the need for the elevated level of performance.

c. The volume will be tagged as follows:

· TagName: Disposition

· TagValue: Use of io1 volume type with PIOPS set to <NNN> approved by <Name and Org> on <YYYY-MM-DD>

6. Programs are allowed to use less costly volume types at their discretion.