Skip to main content

resolver_endpoints

Creates, updates, deletes or gets a resolver_endpoint resource or lists resolver_endpoints in a region

Overview

Nameresolver_endpoints
TypeResource
DescriptionResource type definition for AWS::Route53Resolver::ResolverEndpoint
Idawscc.route53resolver.resolver_endpoints

Fields

NameDatatypeDescription
arnstringThe Amazon Resource Name (ARN) of the resolver endpoint, such as arn:aws:route53resolver:us-east-1:123456789012:resolver-endpoint/resolver-endpoint-a1bzhi.
directionstringIndicates whether the Resolver endpoint allows inbound or outbound DNS queries:<br />- INBOUND: allows DNS queries to your VPC from your network <br />- OUTBOUND: allows DNS queries from your VPC to your network <br />- INBOUND&#95;DELEGATION: allows DNS queries to your VPC from your network with authoritative answers from private hosted zones
host_vpc_idstringThe ID of the VPC that you want to create the resolver endpoint in.
ip_address_countstringThe number of IP addresses that the resolver endpoint can use for DNS queries.
ip_addressesarrayThe 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.
namestringA friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console.
outpost_arnstringThe ARN (Amazon Resource Name) for the Outpost.
preferred_instance_typestringThe Amazon EC2 instance type.
protocolsarrayProtocols used for the endpoint. DoH-FIPS is applicable for inbound endpoints only.
resolver_endpoint_idstringThe ID of the resolver endpoint.
resolver_endpoint_typestringThe Resolver endpoint IP address type.
security_group_idsarrayThe ID of one or more security groups that control access to this VPC. The security group must include one or more inbound rules (for inbound endpoints) or outbound rules (for outbound 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.
tagsarrayAn array of key-value pairs to apply to this resource.
regionstringAWS region.

For more information, see AWS::Route53Resolver::ResolverEndpoint.

Methods

NameResourceAccessible byRequired Params
create_resourceresolver_endpointsINSERTDirection, IpAddresses, SecurityGroupIds, region
delete_resourceresolver_endpointsDELETEIdentifier, region
update_resourceresolver_endpointsUPDATEIdentifier, PatchDocument, region
list_resourcesresolver_endpoints_list_onlySELECTregion
get_resourceresolver_endpointsSELECTIdentifier, region

SELECT examples

Gets all properties from an individual resolver_endpoint.

SELECT
region,
arn,
direction,
host_vpc_id,
ip_address_count,
ip_addresses,
name,
outpost_arn,
preferred_instance_type,
protocols,
resolver_endpoint_id,
resolver_endpoint_type,
security_group_ids,
tags
FROM awscc.route53resolver.resolver_endpoints
WHERE
region = 'us-east-1' AND
Identifier = '{{ resolver_endpoint_id }}';

INSERT example

Use the following StackQL query and manifest file to create a new resolver_endpoint resource, using stack-deploy.

/*+ create */
INSERT INTO awscc.route53resolver.resolver_endpoints (
Direction,
IpAddresses,
SecurityGroupIds,
region
)
SELECT
'{{ direction }}',
'{{ ip_addresses }}',
'{{ security_group_ids }}',
'{{ region }}';

UPDATE example

Use the following StackQL query and manifest file to update a resolver_endpoint resource, using stack-deploy.

/*+ update */
UPDATE awscc.route53resolver.resolver_endpoints
SET PatchDocument = string('{{ {
"IpAddresses": ip_addresses,
"Name": name,
"Protocols": protocols,
"ResolverEndpointType": resolver_endpoint_type,
"Tags": tags
} | generate_patch_document }}')
WHERE
region = '{{ region }}' AND
Identifier = '{{ resolver_endpoint_id }}';

DELETE example

/*+ delete */
DELETE FROM awscc.route53resolver.resolver_endpoints
WHERE
Identifier = '{{ resolver_endpoint_id }}' AND
region = 'us-east-1';

Permissions

To operate on the resolver_endpoints resource, the following permissions are required:

route53resolver:CreateResolverEndpoint,
route53resolver:GetResolverEndpoint,
route53resolver:ListResolverEndpointIpAddresses,
route53resolver:ListTagsForResource,
route53resolver:TagResource,
route53resolver:UntagResource,
ec2:CreateNetworkInterface,
ec2:DescribeNetworkInterfaces,
ec2:DescribeSubnets,
ec2:DescribeSecurityGroups,
ec2:DescribeVpcs