CreateResolverEndpointRequest

import type { CreateResolverEndpointRequest } from "https://aws-api.deno.dev/v0.4/services/route53resolver.ts?docs=full";

interface CreateResolverEndpointRequest {

CreatorRequestId: string;

Direction: ResolverEndpointDirection;

IpAddresses: IpAddressRequest[];

Name?: string | null;

SecurityGroupIds: string[];

Tags?: Tag[] | null;

}

§Properties

CreatorRequestId: string

[src]

A unique string that identifies the request and that allows failed requests to be retried without the risk of running the operation twice. CreatorRequestId can be any unique string, for example, a date/time stamp.

Direction: ResolverEndpointDirection

[src]

Specify the applicable value:

INBOUND: Resolver forwards DNS queries to the DNS service for a VPC from your network
OUTBOUND: Resolver forwards DNS queries from the DNS service for a VPC to your network

IpAddresses: IpAddressRequest[]

[src]

The subnets and IP addresses in your VPC that DNS queries originate from (for outbound endpoints) or that you forward DNS queries to (for inbound endpoints). The subnet ID uniquely identifies a VPC.

Name?: string | null

[src]

A friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console.

SecurityGroupIds: string[]

[src]

The ID of one or more security groups that you want to use to control access to this VPC. The security group that you specify must include one or more inbound rules (for inbound Resolver endpoints) or outbound rules (for outbound Resolver endpoints). Inbound and outbound rules must allow TCP and UDP access. For inbound access, open port 53. For outbound access, open the port that you're using for DNS queries on your network.

Tags?: Tag[] | null

[src]

A list of the tag keys and values that you want to associate with the endpoint.