NetworkConfig / VpcConfig | VpcTemplatesConfig / InterfaceEndpointConfig

VPC interface endpoint configuration. Use this configuration to define interface endpoints for your VPC. Interface endpoints powered by AWS PrivateLink to connect your VPC to AWS services as if they were in your VPC, without the use of an internet gateway.

Example

defaultPolicy: Default
endpoints: []
subnets: []

Hierarchy

  • InterfaceEndpointConfig

Implements

Constructors

Properties

allowedCidrs: undefined | string[] = undefined

(OPTIONAL) An array of source CIDRs allowed to communicate with the endpoints.

Remarks

These CIDRs are used to create ingress rules in a security group that is created and attached to the interface endpoints. By default, all traffic (0.0.0.0/0) is allowed.

Use CIDR notation, i.e. 10.0.0.0/16

central: undefined | boolean = undefined

(OPTIONAL) Enable to define interface endpoints as centralized endpoints.

Remarks

Endpoints defined as centralized endpoints will have Route 53 private hosted zones created for each of them. These hosted zones are associated with any VPCs configured with the useCentralEndpoints property enabled.

NOTE: You may only define one centralized endpoint VPC per region.

For additional information on this pattern, please refer to our FAQ.

defaultPolicy: string = ''

The friendly name of the default policy for the interface endpoints.

Remarks

This is the logical name property of the endpoint policy as defined in network-config.yaml.

See

EndpointPolicyConfig

An array of VPC interface endpoint services to be deployed.

See

InterfaceEndpointServiceConfig

subnets: string[] = []

An array of the friendly names of VPC subnets for the endpoints to be deployed.

Remarks

This is the logical name property of the VPC subnet as defined in network-config.yaml.

See

SubnetConfig

Generated using TypeDoc