Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CreateTransitGatewayConnectPeerRequest

import type { CreateTransitGatewayConnectPeerRequest } from "https://aws-api.deno.dev/v0.3/services/ec2.ts?docs=full";
interface CreateTransitGatewayConnectPeerRequest {
DryRun?: boolean | null;
InsideCidrBlocks: string[];
PeerAddress: string;
TagSpecifications?: TagSpecification[] | null;
TransitGatewayAddress?: string | null;
TransitGatewayAttachmentId: string;
}

§Properties

§

The BGP options for the Connect peer.

§
DryRun?: boolean | null
[src]

Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation.

§
InsideCidrBlocks: string[]
[src]

The range of inside IP addresses that are used for BGP peering. You must specify a size /29 IPv4 CIDR block from the 169.254.0.0/16 range. The first address from the range must be configured on the appliance as the BGP IP address. You can also optionally specify a size /125 IPv6 CIDR block from the fd00::/8 range.

§
PeerAddress: string
[src]

The peer IP address (GRE outer IP address) on the appliance side of the Connect peer.

§
TagSpecifications?: TagSpecification[] | null
[src]

The tags to apply to the Connect peer.

§
TransitGatewayAddress?: string | null
[src]

The peer IP address (GRE outer IP address) on the transit gateway side of the Connect peer, which must be specified from a transit gateway CIDR block. If not specified, Amazon automatically assigns the first available IP address from the transit gateway CIDR block.

§
TransitGatewayAttachmentId: string
[src]

The ID of the Connect attachment.