steampipe plugin install oci

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_created
from
oci_core_boot_volume;
select
id as volume_id,
display_name,
lifecycle_state,
time_created
from
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_created
from
oci_core_boot_volume
where
lifecycle_state = 'FAULTY';
select
id as boot_volume_id,
display_name,
lifecycle_state,
time_created
from
oci_core_boot_volume
where
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_gbs
from
oci_core_boot_volume
where
size_in_gbs > 1024;
select
id as boot_volume_id,
display_name,
lifecycle_state,
size_in_gbs
from
oci_core_boot_volume
where
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_created
from
oci_core_boot_volume
where
kms_key_id is null;
select
id as boot_volume_id,
display_name,
lifecycle_state,
time_created
from
oci_core_boot_volume
where
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_created
from
oci_core_boot_volume
where
kms_key_id is not null;
select
id as boot_volume_id,
display_name,
lifecycle_state,
time_created
from
oci_core_boot_volume
where
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_id
from
oci_core_boot_volume
where
compartment_id = tenant_id;
select
id as boot_volume_id,
display_name,
lifecycle_state,
tenant_id,
compartment_id
from
oci_core_boot_volume
where
compartment_id = tenant_id;

Query examples

Schema for oci_core_boot_volume

NameTypeOperatorsDescription
_ctxjsonbSteampipe context in JSON form, e.g. connection_name.
auto_tuned_vpus_per_gbbigintThe number of Volume Performance Units per GB that this boot volume is effectively tuned to when it's idle.
availability_domaintext=The availability domain of the boot volume.
compartment_idtext=The OCID of the compartment in Tenant in which the resource is located.
defined_tagsjsonbDefined 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_nametextA user-friendly name.
freeform_tagsjsonbFree-form tags for resource. This tags can be applied by any user with permissions on the resource.
idtext=The OCID of the boot volume.
is_auto_tune_enabledbooleanSpecifies whether the auto-tune performance is enabled for this boot volume.
is_hydratedbooleanSpecifies whether the boot volume's data has finished copying from the source boot volume or boot volume backup.
kms_key_idtextThe OCID of the Key Management key which is the master encryption key for the boot volume.
lifecycle_statetextThe current state of a boot volume.
regiontextThe OCI region in which the resource is located.
size_in_gbsbigintThe size of the boot volume in GBs.
size_in_mbsbigintThe size of the boot volume in MBs.
source_detailsjsonbThe boot volume source, either an existing volume in the same availability domain or a volume backup.
system_tagsjsonbSystem tags for resource. System tags can be viewed by users, but can only be created by the system.
tagsjsonbA map of tags for the resource.
tenant_idtextThe OCID of the Tenant in which the resource is located.
tenant_nametextThe name of the Tenant in which the resource is located.
time_createdtimestamp with time zoneThe date and time the boot volume was created.
titletextTitle of the resource.
volume_backup_policy_assignment_idtextThe OCID of the volume backup policy assignment.
volume_backup_policy_idtextThe OCID of the volume backup policy that has been assigned to the volume.
volume_group_idtext=The OCID of the source volume group.
vpus_per_gbbigintThe 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