Check for Volume Performance Units (VPUs)

Risk Level: Medium (should be achieved)

Rule ID: OCI-BlockVolume-003

Ensure that Volume Performance Units (VPUs) in your OCI Block Volumes settings are configured appropriately for workload requirements by choosing a VPU/GB performance tier that satisfies your application's needed IOPS and throughput, while simultaneously balancing that performance against the corresponding cost implications. The desired VPU value must be defined in the rule settings, in your TrendAI Vision One™ Cloud Risk Management Dashboard. The VPU values allowed by Oracle Cloud Infrastructure (OCI) are 0 (Lower Cost), 10 (Balanced), 20 (Higher Performance), and 30-120 (Ultra High Performance).

Performance
efficiency

Accurate Volume Performance Unit (VPU) configuration eliminates performance bottlenecks caused by slow volume storage and ensures you only pay for the I/O capacity your workload actually utilizes.

Audit

To determine if your OCI Block Volume's performance configuration is compliant, perform the following operations:

Using OCI Console

Sign into your TrendAI Vision One™ account to access Cloud Risk Management, access Check for Volume Performance Units (VPUs) rule settings, and identify the Block Volume VPU value approved by your organization.
Sign in to your Oracle Cloud Infrastructure (OCI) account.
Navigate to Block Storage console available at https://cloud.oracle.com/block-storage/.
In the left navigation panel, choose Block Volumes, and select an OCI compartment from the Compartment dropdown menu, next to Applied filters, to list the Block Volumes provisioned in that compartment.
Click on the name (link) of the Block Volume that you want to examine, listed in the Name column.
Select the Details tab to access the general configuration information available for the selected volume.
In the Performance section, check the Performance attribute for the VPU/GB value to identify the Volume Performance Unit (VPU) configured for the selected volume. If the VPU/GB value is different than the one allowed by your organization and identified in step no. 1, the performance configuration of the selected OCI Block Volume is non-compliant because it's not using the approved Volume Performance Unit (VPU) value.

Using OCI CLI

Sign into your TrendAI Vision One™ account to access Cloud Risk Management, access Check for Volume Performance Units (VPUs) rule settings, and identify the Block Volume VPU value approved by your organization.
Run iam compartment list command (Windows/macOS/Linux) with output query filters to list the ID of each compartment available in your Oracle Cloud Infrastructure (OCI) account:
```
oci iam compartment list
	--all
	--include-root
	--query 'data[]."id"'
```

The command output should return the requested OCI compartment identifiers (OCIDs):

[
	"ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
	"ocid1.compartment.oc1..abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd"
]

Run bv volume list command (Windows/macOS/Linux) with the ID of the OCI compartment that you want to examine as the identifier parameter, the list the ID of each Block Volume provisioned in the selected OCI compartment:
```
oci bv volume list
	--compartment-id 'ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
	--all
	--query 'data[]."id"'
```

The command output should return the requested volume IDs:

[
	"ocid1.volume.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
	"ocid1.volume.oc1.ap-sydney-1.aaaabbbbccccddddabcdabcd1234abcd1234abcd1234abcd1234abcd1234"
]

Run bv volume get command (Windows/macOS/Linux) with the name of the OCI Block Volume that you want to examine as the identifier parameter and custom output filters to determine the performance configuration (VPUs per GB) for the selected volume:
```
oci bv volume get
	--volume-id 'ocid1.volume.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
	--query 'data."vpus-per-gb"'
```
The command output should return the VPU/GB value configured for the selected volume:
```
10
```
Compare the VPU/GB value returned by the bv volume get command output with the one allowed by your organization, identified in step no. 1. If the VPU/GB value is different than the one allowed by your organization and identified in step no. 1, the performance configuration of the selected OCI Block Volume is non-compliant because it's not using the approved Volume Performance Unit (VPU) value.

Remediation / Resolution

To ensure that your OCI Block Volume VPUs are configured appropriately for workload requirements, perform the following operations:

Using OCI Console

Sign in to your Oracle Cloud Infrastructure (OCI) account.
Navigate to Block Storage console available at https://cloud.oracle.com/block-storage/.
In the left navigation panel, choose Block Volumes, and select an OCI compartment from the Compartment dropdown menu, next to Applied filters, to list the Block Volumes provisioned in that compartment.
Click on the name (link) of the Block Volume that you want to configure, listed in the Name column.
Choose Edit from the page top menu to update the performance configuration for the selected volume.
In the Target volume performance section, select the Volume Performance Unit (VPU) value approved by your organization from the VPUs type dropdown list, and choose Update to apply the configuration changes. Select Close to return to the OCI Block Volume page.

Using OCI CLI

Run iam compartment list command (Windows/macOS/Linux) with output query filters to list the ID of each compartment available in your Oracle Cloud Infrastructure (OCI) account:
```
oci iam compartment list
	--all
	--include-root
	--query 'data[]."id"'
```

The command output should return the requested OCI compartment identifiers (OCIDs):

[
	"ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
	"ocid1.compartment.oc1..abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd"
]

Run bv volume list command (Windows/macOS/Linux) with the ID of the OCI compartment that you want to examine as the identifier parameter, the list the ID of each Block Volume provisioned in the selected OCI compartment:
```
oci bv volume list
	--compartment-id 'ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
	--all
	--query 'data[]."id"'
```

The command output should return the requested volume IDs:

[
	"ocid1.volume.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
	"ocid1.volume.oc1.ap-sydney-1.aaaabbbbccccddddabcdabcd1234abcd1234abcd1234abcd1234abcd1234"
]

Run bv volume update command (Windows/macOS/Linux) with the name of the OCI Block Volume that you want to configure as the identifier parameter, to set the Volume Performance Unit (VPU) value approved by your organization for the selected volume:
```
oci bv volume update
	--volume-id 'ocid1.volume.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd'
	--vpus-per-gb 20
```

The command output should return the configuration information available for the modified OCI Block Volume:

{
	"data": {
		"availability-domain": "ABCD:AP-SYDNEY-1-AD-1",
		"block-volume-replicas": null,
		"cluster-placement-group-id": null,
		"compartment-id": "ocid1.tenancy.oc1..aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
		"defined-tags": {},
		"display-name": "cc-project5-instance-block-volume",
		"freeform-tags": {},
		"id": "ocid1.volume.oc1.ap-sydney-1.aaaabbbbccccddddabcd1234abcd1234abcd1234abcd1234abcd1234abcd",
		"is-auto-tune-enabled": true,
		"is-hydrated": true,
		"is-reservations-enabled": false,
		"kms-key-id": null,
		"lifecycle-state": "PROVISIONING",
		"size-in-gbs": 50,
		"size-in-mbs": 51200,
		"source-details": null,
		"system-tags": {},
		"time-created": "2025-10-15T10:00:00.778000+00:00",
		"volume-group-id": null,
		"vpus-per-gb": 20
	}
}

References

Oracle Cloud Infrastructure Documentation
Overview of Block Volume
Block Volume Performance

Oracle Cloud Infrastructure CLI Documentation
compartment list
volume list
volume get
volume update

Publication date Nov 10, 2025

Audit

Using OCI Console

Using OCI CLI

Remediation / Resolution

Using OCI Console

Using OCI CLI

References

Related OCI-BlockVolume rules