See: newCreateResolverEndpoint smart constructor.

Create a value of CreateResolverEndpoint with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:name:CreateResolverEndpoint', createResolverEndpoint_name - A friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console.

$sel:tags:CreateResolverEndpoint', createResolverEndpoint_tags - A list of the tag keys and values that you want to associate with the endpoint.

$sel:creatorRequestId:CreateResolverEndpoint', createResolverEndpoint_creatorRequestId - 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.

$sel:securityGroupIds:CreateResolverEndpoint', createResolverEndpoint_securityGroupIds - 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.

$sel:direction:CreateResolverEndpoint', createResolverEndpoint_direction - 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

$sel:ipAddresses:CreateResolverEndpoint', createResolverEndpoint_ipAddresses - 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.

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

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

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.

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.

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

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.

See: newCreateResolverEndpointResponse smart constructor.

Create a value of CreateResolverEndpointResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:resolverEndpoint:CreateResolverEndpointResponse', createResolverEndpointResponse_resolverEndpoint - Information about the CreateResolverEndpoint request, including the status of the request.

$sel:httpStatus:CreateResolverEndpointResponse', createResolverEndpointResponse_httpStatus - The response's http status code.

Information about the CreateResolverEndpoint request, including the status of the request.

The response's http status code.