AWS::Route53Resolver::ResolverEndpointCreates a Resolver endpoint. There are two types of Resolver endpoints, inbound and outbound:. - An *inbound Resolver endpoint* forwards DNS queries to the DNS service for a VPC from your network. - An *outbound Resolver endpoint* forwards DNS queries from the DNS service for a VPC to your network. > - You cannot update `ResolverEndpointType` and `IpAddresses` in the same request. > - When you update a dual-stack IP address, you must update both IP addresses. You can’t update only an IPv4 or IPv6 and keep an existing IP address.
import { CfnResolverEndpoint } from 'aws-cdk-lib/aws-route53resolver';Or use the module namespace:
import * as route53resolver from 'aws-cdk-lib/aws-route53resolver';
// route53resolver.CfnResolverEndpointConfiguration passed to the constructor as CfnResolverEndpointProps.
directionRequiredstringIndicates whether the Resolver endpoint allows inbound or outbound DNS queries:. - `INBOUND` : allows DNS queries to your VPC from your network - `OUTBOUND` : allows DNS queries from your VPC to your network - `INBOUND_DELEGATION` : Resolver delegates queries to Route 53 private hosted zones from your network.
ipAddressesRequiredIResolvable | IResolvable | IpAddressRequestProperty[]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. > Even though the minimum is 1, Route 53 requires that you create at least two.
securityGroupIdsRequiredstring[]The 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.
nameOptionalstringA friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console.
outpostArnOptionalstringThe ARN (Amazon Resource Name) for the Outpost.
preferredInstanceTypeOptionalstringThe Amazon EC2 instance type.
protocolsOptionalstring[]Protocols used for the endpoint. DoH-FIPS is applicable for a default inbound endpoints only. For an inbound endpoint you can apply the protocols as follows: - Do53 and DoH in combination. - Do53 and DoH-FIPS in combination. - Do53 alone. - DoH alone. - DoH-FIPS alone. - None, which is treated as Do53. For a delegation inbound endpoint you can use Do53 only. For an outbound endpoint you can apply the protocols as follows: - Do53 and DoH in combination. - Do53 alone. - DoH alone. - None, which is treated as Do53.
resolverEndpointTypeOptionalstringThe Resolver endpoint IP address type.
rniEnhancedMetricsEnabledOptionalboolean | IResolvableIndicates whether RNI enhanced metrics are enabled for the Resolver endpoint. When enabled, one-minute granular metrics are published in CloudWatch for each RNI associated with this endpoint. When disabled, these metrics are not published.
tagsOptionalCfnTag[]Route 53 Resolver doesn't support updating tags through CloudFormation.
targetNameServerMetricsEnabledOptionalboolean | IResolvableIndicates whether target name server metrics are enabled for the outbound Resolver endpoint. When enabled, one-minute granular metrics are published in CloudWatch for each target name server associated with this endpoint. When disabled, these metrics are not published. This feature is not supported for inbound Resolver endpoint.
This L1 construct maps directly to the following CloudFormation resource type.
Our bi-weekly newsletter teaches hands-on AWS fundamentals. No certification fluff - just practical knowledge.
Subscribe to Newsletteraws-route53resolverAWS::Route53Resolver::ResolverEndpoint