The OCID of the compartment containing the IPSec connection.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
The OCID of the DRG.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
The IPSec connection's Oracle ID (OCID).
The IPSec connection's current state.
Static routes to the CPE. The CIDR must not be a multicast address or class E address.
Example: {@code 10.0.1.0/24}
The date and time the IPSec connection was created, in the format defined by RFC3339.
Example: {@code 2016-08-25T21:10:29.600Z}
The transport type used for the IPSec connection.
A connection between a DRG and CPE. This connection consists of multiple IPSec tunnels. Creating this connection is one of the steps required when setting up a Site-to-Site VPN. For more information, see Site-to-Site VPN Overview.
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.oracle.com/iaas/Content/Identity/Concepts/policygetstarted.htm).