Table: oci_core_drg - Query OCI Core Dynamic Routing Gateways using SQL
Dynamic Routing Gateways (DRGs) are virtual routers that provide a path for private network traffic between your Virtual Cloud Network (VCN) and networks outside the VCN. A DRG is a critical component for creating a site-to-site VPN connection, or a connection that uses Oracle Cloud Infrastructure FastConnect. DRGs provide a secure and reliable connection to your workloads in the Oracle Cloud.
Table Usage Guide
The oci_core_drg
table gives insights into Dynamic Routing Gateways within Oracle Cloud Infrastructure's Core Services. As a network administrator, you can delve into details about each DRG, including its state, lifecycle details, and associated compartment. Use this table to manage and monitor your DRGs, ensuring secure and efficient connections between your VCN and external networks.
Examples
Basic info
Gain insights into your Oracle Cloud Infrastructure by examining the lifecycle state and creation time of each resource. This can be useful for tracking resource usage and understanding the overall health and status of your infrastructure.
select display_name, id, lifecycle_state, time_createdfrom oci_core_drg;
select display_name, id, lifecycle_state, time_createdfrom oci_core_drg;
List unavailable dynamic routing gateways
Determine the areas in which dynamic routing gateways are not currently available. This is beneficial to quickly identify and address any network connectivity issues.
select display_name, id, lifecycle_statefrom oci_core_drgwhere lifecycle_state <> 'AVAILABLE';
select display_name, id, lifecycle_statefrom oci_core_drgwhere lifecycle_state <> 'AVAILABLE';
Count of dynamic routing gateways per region
Explore the distribution of dynamic routing gateways across different regions. This can help in managing network traffic and ensuring efficient data routing.
select region, count(*) drg_countfrom oci_core_drggroup by region;
select region, count(*) drg_countfrom oci_core_drggroup by region;
Schema for oci_core_drg
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
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. Does not have to be unique, and it's changeable. | |
freeform_tags | jsonb | Free-form tags for resource. This tags can be applied by any user with permissions on the resource. | |
id | text | = | The DRG's Oracle ID (OCID). |
lifecycle_state | text | The DRG's current state. | |
region | text | The OCI region in which the resource is located. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
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 DRG was created. | |
title | text | Title of the resource. |
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_drg