ip_sec_connections
Creates, updates, deletes, gets or lists an ip_sec_connections resource.
Overview​
| Name | ip_sec_connections |
| Type | Resource |
| Id | oci.network.ip_sec_connections |
Fields​
The following fields are returned by SELECT queries:
- get
- list
The information was retrieved.
| Name | Datatype | Description |
|---|---|---|
id | string | The IPSec connection's Oracle ID ([OCID](/iaas/Content/General/Concepts/identifiers.htm)). |
compartmentId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the compartment containing the IPSec connection. |
cpeId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the [Cpe](#/en/iaas/latest/Cpe/) object. |
cpeLocalIdentifier | string | Your identifier for your CPE device. Can be either an IP address or a hostname (specifically, the fully qualified domain name (FQDN)). The type of identifier here must correspond to the value for cpeLocalIdentifierType. If you don't provide a value when creating the IPSec connection, the ipAddress attribute for the [Cpe](#/en/iaas/latest/Cpe/) object specified by cpeId is used as the cpeLocalIdentifier. For information about why you'd provide this value, see [If Your CPE Is Behind a NAT Device](/iaas/Content/Network/Tasks/overviewIPsec.htm#nat). Example IP address: 10.0.3.3 Example hostname: cpe.example.com |
cpeLocalIdentifierType | string | The type of identifier for your CPE device. The value here must correspond to the value for cpeLocalIdentifier. (IP_ADDRESS, HOSTNAME) |
definedTags | object | Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see [Resource Tags](/iaas/Content/General/Concepts/resourcetags.htm). Example: {"Operations": {"CostCenter": "42"}} |
displayName | string | A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information. |
drgId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the DRG. |
freeformTags | object | 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](/iaas/Content/General/Concepts/resourcetags.htm). Example: {"Department": "Finance"} |
lifecycleState | string | The IPSec connection's current state. (PROVISIONING, AVAILABLE, TERMINATING, TERMINATED) |
staticRoutes | array | Static routes to the CPE. The CIDR must not be a multicast address or class E address. Used for routing a given IPSec tunnel's traffic only if the tunnel is using static routing. If you configure at least one tunnel to use static routing, then you must provide at least one valid static route. If you configure both tunnels to use BGP dynamic routing, you can provide an empty list for the static routes. The CIDR can be either IPv4 or IPv6. IPv6 addressing is supported for all commercial and government regions. See [IPv6 Addresses](/iaas/Content/Network/Concepts/ipv6.htm). Example: 10.0.1.0/24 Example: 2001:db8::/32 |
timeCreated | string (date-time) | The date and time the IPSec connection was created, in the format defined by [RFC3339](https:​//tools.ietf.org/html/rfc3339). Example: 2016-08-25T21:10:29.600Z |
transportType | string | The transport type used for the IPSec connection. (INTERNET, FASTCONNECT) (default: INTERNET) |
A connection between a DRG and CPE. This connection consists of multiple IPSec<br />tunnels. Creating this connection is one of the steps required when setting up<br />a Site-to-Site VPN.<br /><br />Important: Each tunnel in an IPSec connection can use either static routing or BGP dynamic<br />routing (see the [IPSecConnectionTunnel](#/en/iaas/latest/IPSecConnectionTunnel/) object's<br />routing attribute). Originally only static routing was supported and<br />every IPSec connection was required to have at least one static route configured.<br />To maintain backward compatibility in the API when support for BPG dynamic routing was introduced,<br />the API accepts an empty list of static routes if you configure both of the IPSec tunnels to use<br />BGP dynamic routing. If you switch a tunnel's routing from BGP to STATIC, you must first<br />ensure that the IPSec connection is configured with at least one valid CIDR block static route.<br />Oracle uses the IPSec connection's static routes when routing a tunnel's traffic only<br />if that tunnel's routing attribute = STATIC. Otherwise the static routes are ignored.<br /><br />For more information about the workflow for setting up an IPSec connection, see<br />[Site-to-Site VPN Overview](/iaas/Content/Network/Tasks/overviewIPsec.htm).<br /><br />To use any of the API operations, you must be authorized in an IAM policy. If you're not authorized,<br />talk to an administrator. If you're an administrator who needs to write policies to give users access, see<br />[Getting Started with Policies](/iaas/Content/Identity/Concepts/policygetstarted.htm).<br />
| Name | Datatype | Description |
|---|---|---|
id | string | The IPSec connection's Oracle ID ([OCID](/iaas/Content/General/Concepts/identifiers.htm)). |
compartmentId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the compartment containing the IPSec connection. |
cpeId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the [Cpe](#/en/iaas/latest/Cpe/) object. |
cpeLocalIdentifier | string | Your identifier for your CPE device. Can be either an IP address or a hostname (specifically, the fully qualified domain name (FQDN)). The type of identifier here must correspond to the value for cpeLocalIdentifierType. If you don't provide a value when creating the IPSec connection, the ipAddress attribute for the [Cpe](#/en/iaas/latest/Cpe/) object specified by cpeId is used as the cpeLocalIdentifier. For information about why you'd provide this value, see [If Your CPE Is Behind a NAT Device](/iaas/Content/Network/Tasks/overviewIPsec.htm#nat). Example IP address: 10.0.3.3 Example hostname: cpe.example.com |
cpeLocalIdentifierType | string | The type of identifier for your CPE device. The value here must correspond to the value for cpeLocalIdentifier. (IP_ADDRESS, HOSTNAME) |
definedTags | object | Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see [Resource Tags](/iaas/Content/General/Concepts/resourcetags.htm). Example: {"Operations": {"CostCenter": "42"}} |
displayName | string | A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information. |
drgId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the DRG. |
freeformTags | object | 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](/iaas/Content/General/Concepts/resourcetags.htm). Example: {"Department": "Finance"} |
lifecycleState | string | The IPSec connection's current state. (PROVISIONING, AVAILABLE, TERMINATING, TERMINATED) |
staticRoutes | array | Static routes to the CPE. The CIDR must not be a multicast address or class E address. Used for routing a given IPSec tunnel's traffic only if the tunnel is using static routing. If you configure at least one tunnel to use static routing, then you must provide at least one valid static route. If you configure both tunnels to use BGP dynamic routing, you can provide an empty list for the static routes. The CIDR can be either IPv4 or IPv6. IPv6 addressing is supported for all commercial and government regions. See [IPv6 Addresses](/iaas/Content/Network/Concepts/ipv6.htm). Example: 10.0.1.0/24 Example: 2001:db8::/32 |
timeCreated | string (date-time) | The date and time the IPSec connection was created, in the format defined by [RFC3339](https:​//tools.ietf.org/html/rfc3339). Example: 2016-08-25T21:10:29.600Z |
transportType | string | The transport type used for the IPSec connection. (INTERNET, FASTCONNECT) (default: INTERNET) |
Methods​
The following methods are available for this resource:
| Name | Accessible by | Required Params | Optional Params | Description |
|---|---|---|---|---|
get | select | ipscId, region | Gets the specified IPSec connection's basic information, including the static routes for the<br />on-premises router. If you want the status of the connection (whether it's up or down), use<br />[GetIPSecConnectionTunnel](#/en/iaas/latest/IPSecConnectionTunnel/GetIPSecConnectionTunnel).<br /> | |
list | select | compartmentId, region | drgId, cpeId, limit, page | Lists the IPSec connections for the specified compartment. You can filter the<br />results by DRG or CPE.<br /> |
create | insert | region, compartmentId, drgId, cpeId | opc-retry-token | Creates a new IPSec connection between the specified DRG and CPE. For more information, see<br />[Site-to-Site VPN Overview](/iaas/Content/Network/Tasks/overviewIPsec.htm).<br /><br />If you configure at least one tunnel to use static routing, then in the request you must provide<br />at least one valid static route (you're allowed a maximum of 10). For example: 10.0.0.0/16.<br />If you configure both tunnels to use BGP dynamic routing, you can provide an empty list for<br />the static routes. For more information, see the important note in<br />[IPSecConnection](#/en/iaas/latest/IPSecConnection/).<br /><br />For the purposes of access control, you must provide the [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the compartment where you want the<br />IPSec connection to reside. Notice that the IPSec connection doesn't have to be in the same compartment<br />as the DRG, CPE, or other Networking Service components. If you're not sure which compartment to<br />use, put the IPSec connection in the same compartment as the DRG. For more information about<br />compartments and access control, see<br />[Overview of the IAM Service](/iaas/Content/Identity/Concepts/overview.htm).<br /><br />You may optionally specify a display name for the IPSec connection, otherwise a default is provided.<br />It does not have to be unique, and you can change it. Avoid entering confidential information.<br /><br />After creating the IPSec connection, you need to configure your on-premises router<br />with tunnel-specific information. For tunnel status and the required configuration information, see:<br /><br /> * [IPSecConnectionTunnel](#/en/iaas/latest/IPSecConnectionTunnel/)<br /> * [IPSecConnectionTunnelSharedSecret](#/en/iaas/latest/IPSecConnectionTunnelSharedSecret/)<br /><br />For each tunnel, you need the IP address of Oracle's VPN headend and the shared secret<br />(that is, the pre-shared key). For more information, see<br />[CPE Configuration](/iaas/Content/Network/Tasks/configuringCPE.htm).<br /> |
update | update | ipscId, region | if-match | Updates the specified IPSec connection.<br /><br />To update an individual IPSec tunnel's attributes, use<br />[UpdateIPSecConnectionTunnel](#/en/iaas/latest/IPSecConnectionTunnel/UpdateIPSecConnectionTunnel).<br /> |
delete | delete | ipscId, region | if-match | Deletes the specified IPSec connection. If your goal is to disable the Site-to-Site VPN between your VCN and<br />on-premises network, it's easiest to simply detach the DRG but keep all the Site-to-Site VPN components intact.<br />If you were to delete all the components and then later need to create an Site-to-Site VPN again, you would<br />need to configure your on-premises router again with the new information returned from<br />[CreateIPSecConnection](#/en/iaas/latest/IPSecConnection/CreateIPSecConnection).<br /><br />This is an asynchronous operation. The connection's lifecycleState will change to TERMINATING temporarily<br />until the connection is completely removed.<br /> |
change_compartment | exec | ipscId, region, compartmentId | opc-request-id, opc-retry-token | Moves an IPSec connection into a different compartment within the same tenancy. For information<br />about moving resources between compartments, see<br />[Moving Resources to a Different Compartment](/iaas/Content/Identity/Tasks/managingcompartments.htm#moveRes).<br /> |
Parameters​
Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.
| Name | Datatype | Description |
|---|---|---|
compartmentId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the compartment. |
ipscId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the IPSec connection. |
region | string | OCI region identifier (e.g. us-ashburn-1, ap-sydney-1); resolves from OCI_REGION when not supplied in the query. (default: us-ashburn-1, x-stackQL-envVar: OCI_REGION) |
cpeId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the CPE. |
drgId | string | The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the DRG. |
if-match | string | For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value. |
limit | integer | For list pagination. The maximum number of results per page, or items to return in a paginated "List" call. For important details about how pagination works, see [List Pagination](/iaas/Content/API/Concepts/usingapi.htm#nine). Example: 50 |
opc-request-id | string | Unique identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. |
opc-retry-token | string | A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected). |
page | string | For list pagination. The value of the opc-next-page response header from the previous "List" call. For important details about how pagination works, see [List Pagination](/iaas/Content/API/Concepts/usingapi.htm#nine). |
SELECT examples​
- get
- list
Gets the specified IPSec connection's basic information, including the static routes for the<br />on-premises router. If you want the status of the connection (whether it's up or down), use<br />[GetIPSecConnectionTunnel](#/en/iaas/latest/IPSecConnectionTunnel/GetIPSecConnectionTunnel).<br />
SELECT
id,
compartmentId,
cpeId,
cpeLocalIdentifier,
cpeLocalIdentifierType,
definedTags,
displayName,
drgId,
freeformTags,
lifecycleState,
staticRoutes,
timeCreated,
transportType
FROM oci.network.ip_sec_connections
WHERE ipscId = '{{ ipscId }}' -- required
AND region = '{{ region }}' -- required
;
Lists the IPSec connections for the specified compartment. You can filter the<br />results by DRG or CPE.<br />
SELECT
id,
compartmentId,
cpeId,
cpeLocalIdentifier,
cpeLocalIdentifierType,
definedTags,
displayName,
drgId,
freeformTags,
lifecycleState,
staticRoutes,
timeCreated,
transportType
FROM oci.network.ip_sec_connections
WHERE compartmentId = '{{ compartmentId }}' -- required
AND region = '{{ region }}' -- required
AND drgId = '{{ drgId }}'
AND cpeId = '{{ cpeId }}'
AND limit = '{{ limit }}'
AND page = '{{ page }}'
;
INSERT examples​
- create
- Manifest
Creates a new IPSec connection between the specified DRG and CPE. For more information, see<br />[Site-to-Site VPN Overview](/iaas/Content/Network/Tasks/overviewIPsec.htm).<br /><br />If you configure at least one tunnel to use static routing, then in the request you must provide<br />at least one valid static route (you're allowed a maximum of 10). For example: 10.0.0.0/16.<br />If you configure both tunnels to use BGP dynamic routing, you can provide an empty list for<br />the static routes. For more information, see the important note in<br />[IPSecConnection](#/en/iaas/latest/IPSecConnection/).<br /><br />For the purposes of access control, you must provide the [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the compartment where you want the<br />IPSec connection to reside. Notice that the IPSec connection doesn't have to be in the same compartment<br />as the DRG, CPE, or other Networking Service components. If you're not sure which compartment to<br />use, put the IPSec connection in the same compartment as the DRG. For more information about<br />compartments and access control, see<br />[Overview of the IAM Service](/iaas/Content/Identity/Concepts/overview.htm).<br /><br />You may optionally specify a display name for the IPSec connection, otherwise a default is provided.<br />It does not have to be unique, and you can change it. Avoid entering confidential information.<br /><br />After creating the IPSec connection, you need to configure your on-premises router<br />with tunnel-specific information. For tunnel status and the required configuration information, see:<br /><br /> * [IPSecConnectionTunnel](#/en/iaas/latest/IPSecConnectionTunnel/)<br /> * [IPSecConnectionTunnelSharedSecret](#/en/iaas/latest/IPSecConnectionTunnelSharedSecret/)<br /><br />For each tunnel, you need the IP address of Oracle's VPN headend and the shared secret<br />(that is, the pre-shared key). For more information, see<br />[CPE Configuration](/iaas/Content/Network/Tasks/configuringCPE.htm).<br />
INSERT INTO oci.network.ip_sec_connections (
compartmentId,
cpeId,
cpeLocalIdentifier,
cpeLocalIdentifierType,
definedTags,
displayName,
drgId,
freeformTags,
staticRoutes,
tunnelConfiguration,
region,
opc-retry-token
)
SELECT
'{{ compartmentId }}' /* required */,
'{{ cpeId }}' /* required */,
'{{ cpeLocalIdentifier }}',
'{{ cpeLocalIdentifierType }}',
'{{ definedTags }}',
'{{ displayName }}',
'{{ drgId }}' /* required */,
'{{ freeformTags }}',
'{{ staticRoutes }}',
'{{ tunnelConfiguration }}',
'{{ region }}',
'{{ opc-retry-token }}'
RETURNING
id,
compartmentId,
cpeId,
cpeLocalIdentifier,
cpeLocalIdentifierType,
definedTags,
displayName,
drgId,
freeformTags,
lifecycleState,
staticRoutes,
timeCreated,
transportType
;
# Description fields are for documentation purposes
- name: ip_sec_connections
props:
- name: region
value: "{{ region }}"
description: Required parameter for the ip_sec_connections resource.
- name: compartmentId
value: "{{ compartmentId }}"
description: |
The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the compartment to contain the IPSec connection.
- name: cpeId
value: "{{ cpeId }}"
description: |
The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the [Cpe](#/en/iaas/latest/Cpe/) object.
- name: cpeLocalIdentifier
value: "{{ cpeLocalIdentifier }}"
description: |
Your identifier for your CPE device. Can be either an IP address or a hostname (specifically, the
fully qualified domain name (FQDN)). The type of identifier you provide here must correspond
to the value for `cpeLocalIdentifierType`.
If you don't provide a value, the `ipAddress` attribute for the [Cpe](#/en/iaas/latest/Cpe/)
object specified by `cpeId` is used as the `cpeLocalIdentifier`.
For information about why you'd provide this value, see
[If Your CPE Is Behind a NAT Device](/iaas/Content/Network/Tasks/overviewIPsec.htm#nat).
Example IP address: `10.0.3.3`
Example hostname: `cpe.example.com`
- name: cpeLocalIdentifierType
value: "{{ cpeLocalIdentifierType }}"
description: |
The type of identifier for your CPE device. The value you provide here must correspond to the value
for `cpeLocalIdentifier`.
valid_values: ['IP_ADDRESS', 'HOSTNAME']
- name: definedTags
value: "{{ definedTags }}"
description: |
Defined tags for this resource. Each key is predefined and scoped to a
namespace. For more information, see [Resource Tags](/iaas/Content/General/Concepts/resourcetags.htm).
Example: `{"Operations": {"CostCenter": "42"}}`
- name: displayName
value: "{{ displayName }}"
description: |
A user-friendly name. Does not have to be unique, and it's changeable.
Avoid entering confidential information.
- name: drgId
value: "{{ drgId }}"
description: |
The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the DRG.
- name: freeformTags
value: "{{ freeformTags }}"
description: |
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](/iaas/Content/General/Concepts/resourcetags.htm).
Example: `{"Department": "Finance"}`
- name: staticRoutes
value:
- "{{ staticRoutes }}"
description: |
Static routes to the CPE. A static route's CIDR must not be a
multicast address or class E address.
Used for routing a given IPSec tunnel's traffic only if the tunnel
is using static routing. If you configure at least one tunnel to use static routing, then
you must provide at least one valid static route. If you configure both
tunnels to use BGP dynamic routing, you can provide an empty list for the static routes.
For more information, see the important note in [IPSecConnection](#/en/iaas/latest/IPSecConnection/).
The CIDR can be either IPv4 or IPv6. IPv6 addressing is supported for all commercial and government regions.
See [IPv6 Addresses](/iaas/Content/Network/Concepts/ipv6.htm).
Example: `10.0.1.0/24`
Example: `2001:db8::/32`
- name: tunnelConfiguration
description: |
Information for creating the individual tunnels in the IPSec connection. You can provide a
maximum of 2 `tunnelConfiguration` objects in the array (one for each of the
two tunnels).
value:
- associatedVirtualCircuits: "{{ associatedVirtualCircuits }}"
bgpSessionConfig:
customerBgpAsn: "{{ customerBgpAsn }}"
customerInterfaceIp: "{{ customerInterfaceIp }}"
customerInterfaceIpv6: "{{ customerInterfaceIpv6 }}"
oracleInterfaceIp: "{{ oracleInterfaceIp }}"
oracleInterfaceIpv6: "{{ oracleInterfaceIpv6 }}"
displayName: "{{ displayName }}"
dpdConfig:
dpdMode: "{{ dpdMode }}"
dpdTimeoutInSec: {{ dpdTimeoutInSec }}
drgRouteTableId: "{{ drgRouteTableId }}"
encryptionDomainConfig:
cpeTrafficSelector:
- "{{ cpeTrafficSelector }}"
oracleTrafficSelector:
- "{{ oracleTrafficSelector }}"
natTranslationEnabled: "{{ natTranslationEnabled }}"
oracleInitiation: "{{ oracleInitiation }}"
oracleTunnelIp: "{{ oracleTunnelIp }}"
phaseOneConfig:
authenticationAlgorithm: "{{ authenticationAlgorithm }}"
diffieHelmanGroup: "{{ diffieHelmanGroup }}"
encryptionAlgorithm: "{{ encryptionAlgorithm }}"
isCustomPhaseOneConfig: {{ isCustomPhaseOneConfig }}
lifetimeInSeconds: {{ lifetimeInSeconds }}
phaseTwoConfig:
authenticationAlgorithm: "{{ authenticationAlgorithm }}"
encryptionAlgorithm: "{{ encryptionAlgorithm }}"
isCustomPhaseTwoConfig: {{ isCustomPhaseTwoConfig }}
isPfsEnabled: {{ isPfsEnabled }}
lifetimeInSeconds: {{ lifetimeInSeconds }}
pfsDhGroup: "{{ pfsDhGroup }}"
routing: "{{ routing }}"
sharedSecret: "{{ sharedSecret }}"
- name: opc-retry-token
value: "{{ opc-retry-token }}"
description: A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
description: A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
UPDATE examples​
- update
Updates the specified IPSec connection.<br /><br />To update an individual IPSec tunnel's attributes, use<br />[UpdateIPSecConnectionTunnel](#/en/iaas/latest/IPSecConnectionTunnel/UpdateIPSecConnectionTunnel).<br />
UPDATE oci.network.ip_sec_connections
SET
cpeLocalIdentifier = '{{ cpeLocalIdentifier }}',
cpeLocalIdentifierType = '{{ cpeLocalIdentifierType }}',
definedTags = '{{ definedTags }}',
displayName = '{{ displayName }}',
freeformTags = '{{ freeformTags }}',
staticRoutes = '{{ staticRoutes }}'
WHERE
ipscId = '{{ ipscId }}' --required
AND region = '{{ region }}' --required
AND if-match = '{{ if-match}}'
RETURNING
id,
compartmentId,
cpeId,
cpeLocalIdentifier,
cpeLocalIdentifierType,
definedTags,
displayName,
drgId,
freeformTags,
lifecycleState,
staticRoutes,
timeCreated,
transportType;
DELETE examples​
- delete
Deletes the specified IPSec connection. If your goal is to disable the Site-to-Site VPN between your VCN and<br />on-premises network, it's easiest to simply detach the DRG but keep all the Site-to-Site VPN components intact.<br />If you were to delete all the components and then later need to create an Site-to-Site VPN again, you would<br />need to configure your on-premises router again with the new information returned from<br />[CreateIPSecConnection](#/en/iaas/latest/IPSecConnection/CreateIPSecConnection).<br /><br />This is an asynchronous operation. The connection's lifecycleState will change to TERMINATING temporarily<br />until the connection is completely removed.<br />
DELETE FROM oci.network.ip_sec_connections
WHERE ipscId = '{{ ipscId }}' --required
AND region = '{{ region }}' --required
AND if-match = '{{ if-match }}'
;
Lifecycle Methods​
- change_compartment
Moves an IPSec connection into a different compartment within the same tenancy. For information<br />about moving resources between compartments, see<br />[Moving Resources to a Different Compartment](/iaas/Content/Identity/Tasks/managingcompartments.htm#moveRes).<br />
EXEC oci.network.ip_sec_connections.change_compartment
@ipscId='{{ ipscId }}' --required,
@region='{{ region }}' --required,
@opc-request-id='{{ opc-request-id }}',
@opc-retry-token='{{ opc-retry-token }}'
@@json=
'{
"compartmentId": "{{ compartmentId }}"
}'
;