Table: oci_core_boot_volume - Query OCI Core Boot Volumes using SQL
A Boot Volume in Oracle Cloud Infrastructure (OCI) Core service is a type of block storage volume that contains the image used to boot a Compute instance. These volumes are reliable and durable with built-in repair capabilities. Boot Volumes are designed for high performance and can be easily backed up, cloned or expanded, as needed.
Table Usage Guide
The oci_core_boot_volume
table provides insights into Boot Volumes within OCI Core service. As a cloud administrator, explore Boot Volume-specific details through this table, including its configuration, performance, and associated metadata. Utilize it to uncover information about Boot Volumes, such as their state, size, and the attached instances, to ensure optimal configuration and performance.
Examples
Basic info
Explore which boot volumes are in different lifecycle states and when they were created. This can help in managing and tracking the resources effectively.
select id as volume_id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volume;
select id as volume_id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volume;
List boot volumes with faulty state
Explore which boot volumes are in a faulty state, helping you quickly identify and address potential issues to maintain optimal system performance.
select id as boot_volume_id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volumewhere lifecycle_state = 'FAULTY';
select id as boot_volume_id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volumewhere lifecycle_state = 'FAULTY';
List boot volumes with size greater than 1024 GB
Explore which boot volumes exceed a size of 1024 GB to manage storage allocation and optimize resource utilization.
select id as boot_volume_id, display_name, lifecycle_state, size_in_gbsfrom oci_core_boot_volumewhere size_in_gbs > 1024;
select id as boot_volume_id, display_name, lifecycle_state, size_in_gbsfrom oci_core_boot_volumewhere size_in_gbs > 1024;
List boot volumes with Oracle managed encryption
Discover the segments that have boot volumes managed by Oracle without encryption. This can help identify potential security risks and areas that may need enhanced data protection. Note: Volumes are encrypted by default with Oracle managed encryption key
select id as boot_volume_id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volumewhere kms_key_id is null;
select id as boot_volume_id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volumewhere kms_key_id is null;
List boot volumes with customer managed encryption
Gain insights into the boot volumes that have been encrypted using customer-managed keys. This is useful for ensuring compliance with security policies requiring user-managed encryption.
select id as boot_volume_id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volumewhere kms_key_id is not null;
select id as boot_volume_id, display_name, lifecycle_state, time_createdfrom oci_core_boot_volumewhere kms_key_id is not null;
List boot volumes created in the root compartment
Explore which boot volumes have been created in the root compartment of your infrastructure. This can be useful to manage storage resources and ensure efficient use of space.
select id as boot_volume_id, display_name, lifecycle_state, tenant_id, compartment_idfrom oci_core_boot_volumewhere compartment_id = tenant_id;
select id as boot_volume_id, display_name, lifecycle_state, tenant_id, compartment_idfrom oci_core_boot_volumewhere compartment_id = tenant_id;
Query examples
- blockstorage_boot_volume_1_year
- blockstorage_boot_volume_24_hrs
- blockstorage_boot_volume_30_days
- blockstorage_boot_volume_365_days
- blockstorage_boot_volume_90_days
- blockstorage_boot_volume_age_report
- blockstorage_boot_volume_backup_policies_for_blockstorage_boot_volume
- blockstorage_boot_volume_backup_policy_schedules
- blockstorage_boot_volume_by_compartment
- blockstorage_boot_volume_by_creation_month
- blockstorage_boot_volume_by_region
- blockstorage_boot_volume_by_tenancy
- blockstorage_boot_volume_count
- blockstorage_boot_volume_customer_managed_encryption_count
- blockstorage_boot_volume_default_backup_policies_for_blockstorage_boot_volume
- blockstorage_boot_volume_default_encrypted_volumes_count
- blockstorage_boot_volume_encryption
- blockstorage_boot_volume_encryption_report
- blockstorage_boot_volume_input
- blockstorage_boot_volume_overview
- blockstorage_boot_volume_storage
- blockstorage_boot_volume_storage_by_compartment
- blockstorage_boot_volume_storage_by_creation_month
- blockstorage_boot_volume_storage_by_encryption_type
- blockstorage_boot_volume_storage_by_region
- blockstorage_boot_volume_storage_by_tenancy
- blockstorage_boot_volume_storage_total
- blockstorage_boot_volume_tags
- blockstorage_boot_volume_unattached_count
- blockstorage_boot_volume_unattached_report
- blockstorage_boot_volume_vpu
- blockstorage_boot_volume_with_no_backups_count
- blockstorage_boot_volumes_for_kms_key
- kms_keys_for_blockstorage_boot_volume
- kms_vaults_for_blockstorage_boot_volume
- source_blockstorage_boot_volume_clones_for_blockstorage_boot_volume
- target_blockstorage_boot_volume_clones_for_blockstorage_boot_volume
Control examples
Schema for oci_core_boot_volume
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
auto_tuned_vpus_per_gb | bigint | The number of Volume Performance Units per GB that this boot volume is effectively tuned to when it's idle. | |
availability_domain | text | = | The availability domain of the boot volume. |
compartment_id | text | = | The OCID of the compartment in Tenant in which the resource is located. |
defined_tags | jsonb | Defined tags for resource. Defined tags are set up in your tenancy by an administrator. Only users granted permission to work with the defined tags can apply them to resources. | |
display_name | text | A user-friendly name. | |
freeform_tags | jsonb | Free-form tags for resource. This tags can be applied by any user with permissions on the resource. | |
id | text | = | The OCID of the boot volume. |
is_auto_tune_enabled | boolean | Specifies whether the auto-tune performance is enabled for this boot volume. | |
is_hydrated | boolean | Specifies whether the boot volume's data has finished copying from the source boot volume or boot volume backup. | |
kms_key_id | text | The OCID of the Key Management key which is the master encryption key for the boot volume. | |
lifecycle_state | text | The current state of a boot volume. | |
region | text | The OCI region in which the resource is located. | |
size_in_gbs | bigint | The size of the boot volume in GBs. | |
size_in_mbs | bigint | The size of the boot volume in MBs. | |
source_details | jsonb | The boot volume source, either an existing volume in the same availability domain or a volume backup. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
system_tags | jsonb | System tags for resource. System tags can be viewed by users, but can only be created by the system. | |
tags | jsonb | A map of tags for the resource. | |
tenant_id | text | =, !=, ~~, ~~*, !~~, !~~* | The OCID of the Tenant in which the resource is located. |
tenant_name | text | The name of the Tenant in which the resource is located. | |
time_created | timestamp with time zone | The date and time the boot volume was created. | |
title | text | Title of the resource. | |
volume_backup_policy_assignment_id | text | The OCID of the volume backup policy assignment. | |
volume_backup_policy_id | text | The OCID of the volume backup policy that has been assigned to the volume. | |
volume_group_id | text | = | The OCID of the source volume group. |
vpus_per_gb | bigint | The number of volume performance units (VPUs) that will be applied to this boot volume per GB,representing the Block Volume service's elastic performance options. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- oci
You can pass the configuration to the command with the --config
argument:
steampipe_export_oci --config '<your_config>' oci_core_boot_volume