VPNConnection is the Schema for the VPNConnections API. Manages a Site-to-Site VPN connection. A Site-to-Site VPN connection is an Internet Protocol security (IPsec) VPN connection between a VPC and an on-premises network.
Type
CRD
Group
ec2.aws.upbound.io
Version
apiVersion: ec2.aws.upbound.io/v1beta1
kind: VPNConnection
VPNConnectionSpec defines the desired state of VPNConnection
No description provided.
Reference to a CustomerGateway in ec2 to populate customerGatewayId.
Policies for referencing.
Selector for a CustomerGateway in ec2 to populate customerGatewayId.
Policies for selection.
Reference to a TransitGateway in ec2 to populate transitGatewayId.
Policies for referencing.
Selector for a TransitGateway in ec2 to populate transitGatewayId.
Policies for selection.
The IKE versions that are permitted for the first VPN tunnel. Valid values are ikev1 | ikev2.
Options for logging VPN tunnel activity. See Log Options below for more details.
Options for sending VPN tunnel logs to CloudWatch. See CloudWatch Log Options below for more details.
List of one or more Diffie-Hellman group numbers that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are 2 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
One or more integrity algorithms that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
List of one or more Diffie-Hellman group numbers that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
List of one or more integrity algorithms that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
The IKE versions that are permitted for the second VPN tunnel. Valid values are ikev1 | ikev2.
Options for logging VPN tunnel activity. See Log Options below for more details.
Options for sending VPN tunnel logs to CloudWatch. See CloudWatch Log Options below for more details.
List of one or more Diffie-Hellman group numbers that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are 2 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
One or more integrity algorithms that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
List of one or more Diffie-Hellman group numbers that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
List of one or more integrity algorithms that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
Reference to a CustomerGateway in ec2 to populate type.
Policies for referencing.
Selector for a CustomerGateway in ec2 to populate type.
Policies for selection.
Reference to a VPNGateway in ec2 to populate vpnGatewayId.
Policies for referencing.
Selector for a VPNGateway in ec2 to populate vpnGatewayId.
Policies for selection.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Reference to a CustomerGateway in ec2 to populate customerGatewayId.
Policies for referencing.
Selector for a CustomerGateway in ec2 to populate customerGatewayId.
Policies for selection.
Reference to a TransitGateway in ec2 to populate transitGatewayId.
Policies for referencing.
Selector for a TransitGateway in ec2 to populate transitGatewayId.
Policies for selection.
The IKE versions that are permitted for the first VPN tunnel. Valid values are ikev1 | ikev2.
Options for logging VPN tunnel activity. See Log Options below for more details.
Options for sending VPN tunnel logs to CloudWatch. See CloudWatch Log Options below for more details.
List of one or more Diffie-Hellman group numbers that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are 2 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
One or more integrity algorithms that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
List of one or more Diffie-Hellman group numbers that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
List of one or more integrity algorithms that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
The IKE versions that are permitted for the second VPN tunnel. Valid values are ikev1 | ikev2.
Options for logging VPN tunnel activity. See Log Options below for more details.
Options for sending VPN tunnel logs to CloudWatch. See CloudWatch Log Options below for more details.
List of one or more Diffie-Hellman group numbers that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are 2 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
One or more integrity algorithms that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
List of one or more Diffie-Hellman group numbers that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
List of one or more integrity algorithms that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
Reference to a CustomerGateway in ec2 to populate type.
Policies for referencing.
Selector for a CustomerGateway in ec2 to populate type.
Policies for selection.
Reference to a VPNGateway in ec2 to populate vpnGatewayId.
Policies for referencing.
Selector for a VPNGateway in ec2 to populate vpnGatewayId.
Policies for selection.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
VPNConnectionStatus defines the observed state of VPNConnection.
No description provided.
The static routes associated with the VPN connection. Detailed below.
The IKE versions that are permitted for the first VPN tunnel. Valid values are ikev1 | ikev2.
Options for logging VPN tunnel activity. See Log Options below for more details.
Options for sending VPN tunnel logs to CloudWatch. See CloudWatch Log Options below for more details.
List of one or more Diffie-Hellman group numbers that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are 2 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
One or more integrity algorithms that are permitted for the first VPN tunnel for phase 1 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
List of one or more Diffie-Hellman group numbers that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
List of one or more integrity algorithms that are permitted for the first VPN tunnel for phase 2 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
The IKE versions that are permitted for the second VPN tunnel. Valid values are ikev1 | ikev2.
Options for logging VPN tunnel activity. See Log Options below for more details.
Options for sending VPN tunnel logs to CloudWatch. See CloudWatch Log Options below for more details.
List of one or more Diffie-Hellman group numbers that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are 2 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
One or more integrity algorithms that are permitted for the second VPN tunnel for phase 1 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
List of one or more Diffie-Hellman group numbers that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are 2 | 5 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24.
List of one or more encryption algorithms that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are AES128 | AES256 | AES128-GCM-16 | AES256-GCM-16.
List of one or more integrity algorithms that are permitted for the second VPN tunnel for phase 2 IKE negotiations. Valid values are SHA1 | SHA2-256 | SHA2-384 | SHA2-512.
Telemetry for the VPN tunnels. Detailed below.
Conditions of the resource.
main
apiVersion: ec2.aws.upbound.io/v1beta1
kind: VPNConnection
metadata:
annotations:
meta.upbound.io/example-id: ec2/v1beta1/vpnconnectionroute
labels:
testing.upbound.io/example-name: main
name: main
spec:
forProvider:
customerGatewayIdSelector:
matchLabels:
testing.upbound.io/example-name: customer_gateway
region: us-west-1
staticRoutesOnly: true
type: ipsec.1
vpnGatewayIdSelector:
matchLabels:
testing.upbound.io/example-name: vpn_gateway
example
apiVersion: ec2.aws.upbound.io/v1beta1
kind: VPNConnection
metadata:
annotations:
meta.upbound.io/example-id: ec2/v1beta1/vpnconnection
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
customerGatewayIdSelector:
matchLabels:
testing.upbound.io/example-name: example
region: us-west-1
transitGatewayIdSelector:
matchLabels:
testing.upbound.io/example-name: example
typeSelector:
matchLabels:
testing.upbound.io/example-name: example
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.