pub struct VpcPeeringConnectionResult {
pub accept_status: Output<String>,
pub accepter: Output<VpcPeeringConnectionAccepter>,
pub auto_accept: Output<Option<bool>>,
pub peer_owner_id: Output<String>,
pub peer_region: Output<String>,
pub peer_vpc_id: Output<String>,
pub requester: Output<VpcPeeringConnectionRequester>,
pub tags: Output<Option<HashMap<String, String>>>,
pub tags_all: Output<HashMap<String, String>>,
pub vpc_id: Output<String>,
}
Fields§
§accept_status: Output<String>
The status of the VPC Peering Connection request.
accepter: Output<VpcPeeringConnectionAccepter>
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).
auto_accept: Output<Option<bool>>
Accept the peering (both VPCs need to be in the same AWS account and region).
peer_owner_id: Output<String>
The AWS account ID of the target peer VPC. Defaults to the account ID the [AWS provider][1] is currently connected to, so must be managed if connecting cross-account.
peer_region: Output<String>
The region of the accepter VPC of the VPC Peering Connection. auto_accept
must be false
,
and use the aws.ec2.VpcPeeringConnectionAccepter
to manage the accepter side.
peer_vpc_id: Output<String>
The ID of the target VPC with which you are creating the VPC Peering Connection.
requester: Output<VpcPeeringConnectionRequester>
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).
A map of tags to assign to the resource. .If configured with a provider default_tags
configuration block present, tags with matching keys will overwrite those defined at the provider-level.
A map of tags assigned to the resource, including those inherited from the provider default_tags
configuration block.
vpc_id: Output<String>
The ID of the requester VPC.