The OCID of the compartment that contains the RPC.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
The OCID of the DRG that this RPC belongs to.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The OCID of the RPC.
Whether the VCN at the other end of the peering is in a different tenancy.
Example: {@code false}
The RPC's current lifecycle state.
If this RPC is peered, this value is the OCID of the other RPC.
If this RPC is peered, this value is the region that contains the other RPC.
Example: {@code us-ashburn-1}
If this RPC is peered, this value is the OCID of the other RPC's tenancy.
Whether the RPC is peered with another RPC. {@code NEW} means the RPC has not yet been peered. {@code PENDING} means the peering is being established. {@code REVOKED} means the RPC at the other end of the peering has been deleted.
The date and time the RPC was created, in the format defined by RFC3339.
Example: {@code 2016-08-25T21:10:29.600Z}
A remote peering connection (RPC) is an object on a DRG that lets the VCN that is attached to the DRG peer with a VCN in a different region. Peering means that the two VCNs can communicate using private IP addresses, but without the traffic traversing the internet or routing through your on-premises network. For more information, see VCN Peering.
To use any of the API operations, you must be authorized in an IAM policy. If you're not authorized, talk to an administrator. If you're an administrator who needs to write policies to give users access, see [Getting Started with Policies](https://docs.cloud.oracle.com/iaas/Content/Identity/Concepts/policygetstarted.htm).