VPCPeeringConnection is the Schema for the VPCPeeringConnections API. Provides a resource to manage a VPC peering connection.
Type
CRD
Group
ec2.aws.upbound.io
Version
v1beta1
apiVersion: ec2.aws.upbound.io/v1beta1
kind: VPCPeeringConnection
VPCPeeringConnectionSpec defines the desired state of VPCPeeringConnection
No description provided.
Reference to a VPC to populate peerVpcId.
Policies for referencing.
Selector for a VPC to populate peerVpcId.
Policies for selection.
Reference to a VPC in ec2 to populate vpcId.
Policies for referencing.
Selector for a VPC in ec2 to populate vpcId.
Policies for selection.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
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.
VPCPeeringConnectionStatus defines the observed state of VPCPeeringConnection.
No description provided.
An optional configuration block that allows for VPC Peering Connection options to be set for the VPC that accepts the peering connection (a maximum of one).
A optional configuration block that allows for VPC Peering Connection options to be set for the VPC that requests the peering connection (a maximum of one).
Conditions of the resource.
peerconnectionname
apiVersion: ec2.aws.upbound.io/v1beta1
kind: VPCPeeringConnection
metadata:
annotations:
meta.upbound.io/example-id: ec2/v1beta1/vpcpeeringconnectionaccepter
labels:
testing.upbound.io/example-name: vpcpeerconnectionlabel
name: peerconnectionname
spec:
forProvider:
autoAccept: false
peerOwnerId: ${data.aws_account_id}
peerRegion: eu-west-1
peerVpcIdSelector:
matchLabels:
testing.upbound.io/example-name: vpcpeerlabel
region: eu-west-1
tags:
Side: Requester
vpcIdSelector:
matchLabels:
testing.upbound.io/example-name: main
foo
apiVersion: ec2.aws.upbound.io/v1beta1
kind: VPCPeeringConnection
metadata:
annotations:
upjet.upbound.io/manual-intervention: Requires references to replaced manually.
labels:
testing.upbound.io/example-name: foo
name: foo
spec:
forProvider:
peerOwnerId: <peer-owner-id>
peerVpcIdSelector:
matchLabels:
testing.upbound.io/example-name: bar
region: us-west-1
vpcIdSelector:
matchLabels:
testing.upbound.io/example-name: foo
peerconnectionname
apiVersion: ec2.aws.upbound.io/v1beta1
kind: VPCPeeringConnection
metadata:
annotations:
meta.upbound.io/example-id: ec2/v1beta1/vpcpeeringconnectionaccepter
labels:
testing.upbound.io/example-name: vpcpeerconnectionlabel
name: peerconnectionname
spec:
forProvider:
autoAccept: true
peerOwnerId: ${data.aws_account_id}
peerVpcIdSelector:
matchLabels:
testing.upbound.io/example-name: vpcpeerlabel
region: eu-west-1
tags:
Side: Requester
vpcIdSelector:
matchLabels:
testing.upbound.io/example-name: main
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.