Interface CreateResolverEndpointRequest.Builder
- All Superinterfaces:
AwsRequest.Builder
,Buildable
,CopyableBuilder<CreateResolverEndpointRequest.Builder,
,CreateResolverEndpointRequest> Route53ResolverRequest.Builder
,SdkBuilder<CreateResolverEndpointRequest.Builder,
,CreateResolverEndpointRequest> SdkPojo
,SdkRequest.Builder
- Enclosing class:
CreateResolverEndpointRequest
-
Method Summary
Modifier and TypeMethodDescriptioncreatorRequestId
(String creatorRequestId) A unique string that identifies the request and that allows failed requests to be retried without the risk of running the operation twice.Specify the applicable value:direction
(ResolverEndpointDirection direction) Specify the applicable value:ipAddresses
(Collection<IpAddressRequest> 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).ipAddresses
(Consumer<IpAddressRequest.Builder>... 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).ipAddresses
(IpAddressRequest... 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).A friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console.outpostArn
(String outpostArn) The Amazon Resource Name (ARN) of the Outpost.overrideConfiguration
(Consumer<AwsRequestOverrideConfiguration.Builder> builderConsumer) Add an optional request override configuration.overrideConfiguration
(AwsRequestOverrideConfiguration overrideConfiguration) Add an optional request override configuration.preferredInstanceType
(String preferredInstanceType) The instance type.protocols
(Collection<Protocol> protocols) The protocols you want to use for the endpoint.The protocols you want to use for the endpoint.protocolsWithStrings
(String... protocols) The protocols you want to use for the endpoint.protocolsWithStrings
(Collection<String> protocols) The protocols you want to use for the endpoint.resolverEndpointType
(String resolverEndpointType) For the endpoint type you can choose either IPv4, IPv6, or dual-stack.resolverEndpointType
(ResolverEndpointType resolverEndpointType) For the endpoint type you can choose either IPv4, IPv6, or dual-stack.securityGroupIds
(String... securityGroupIds) The ID of one or more security groups that you want to use to control access to this VPC.securityGroupIds
(Collection<String> securityGroupIds) The ID of one or more security groups that you want to use to control access to this VPC.tags
(Collection<Tag> tags) A list of the tag keys and values that you want to associate with the endpoint.tags
(Consumer<Tag.Builder>... tags) A list of the tag keys and values that you want to associate with the endpoint.A list of the tag keys and values that you want to associate with the endpoint.Methods inherited from interface software.amazon.awssdk.awscore.AwsRequest.Builder
overrideConfiguration
Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder
copy
Methods inherited from interface software.amazon.awssdk.services.route53resolver.model.Route53ResolverRequest.Builder
build
Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder
applyMutation, build
Methods inherited from interface software.amazon.awssdk.core.SdkPojo
equalsBySdkFields, sdkFields
-
Method Details
-
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.- Parameters:
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.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
name
A friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console.
- Parameters:
name
- A friendly name that lets you easily find a configuration in the Resolver dashboard in the Route 53 console.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
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.
Some security group rules will cause your connection to be tracked. For outbound resolver endpoint, it can potentially impact the maximum queries per second from outbound endpoint to your target name server. For inbound resolver endpoint, it can bring down the overall maximum queries per second per IP address to as low as 1500. To avoid connection tracking caused by security group, see Untracked connections.
- Parameters:
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.Some security group rules will cause your connection to be tracked. For outbound resolver endpoint, it can potentially impact the maximum queries per second from outbound endpoint to your target name server. For inbound resolver endpoint, it can bring down the overall maximum queries per second per IP address to as low as 1500. To avoid connection tracking caused by security group, see Untracked connections.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
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.
Some security group rules will cause your connection to be tracked. For outbound resolver endpoint, it can potentially impact the maximum queries per second from outbound endpoint to your target name server. For inbound resolver endpoint, it can bring down the overall maximum queries per second per IP address to as low as 1500. To avoid connection tracking caused by security group, see Untracked connections.
- Parameters:
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.Some security group rules will cause your connection to be tracked. For outbound resolver endpoint, it can potentially impact the maximum queries per second from outbound endpoint to your target name server. For inbound resolver endpoint, it can bring down the overall maximum queries per second per IP address to as low as 1500. To avoid connection tracking caused by security group, see Untracked connections.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
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
- Parameters:
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
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-
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
- Parameters:
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
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
-
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.
Even though the minimum is 1, Route 53 requires that you create at least two.
- Parameters:
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.Even though the minimum is 1, Route 53 requires that you create at least two.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
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.
Even though the minimum is 1, Route 53 requires that you create at least two.
- Parameters:
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.Even though the minimum is 1, Route 53 requires that you create at least two.
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
ipAddresses
CreateResolverEndpointRequest.Builder ipAddresses(Consumer<IpAddressRequest.Builder>... 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.
Even though the minimum is 1, Route 53 requires that you create at least two.
IpAddressRequest.Builder
avoiding the need to create one manually viaIpAddressRequest.builder()
.When the
Consumer
completes,SdkBuilder.build()
is called immediately and its result is passed toipAddresses(List<IpAddressRequest>)
.- Parameters:
ipAddresses
- a consumer that will call methods onIpAddressRequest.Builder
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
outpostArn
The Amazon Resource Name (ARN) of the Outpost. If you specify this, you must also specify a value for the
PreferredInstanceType
.- Parameters:
outpostArn
- The Amazon Resource Name (ARN) of the Outpost. If you specify this, you must also specify a value for thePreferredInstanceType
.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
preferredInstanceType
The instance type. If you specify this, you must also specify a value for the
OutpostArn
.- Parameters:
preferredInstanceType
- The instance type. If you specify this, you must also specify a value for theOutpostArn
.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
tags
A list of the tag keys and values that you want to associate with the endpoint.
- Parameters:
tags
- A list of the tag keys and values that you want to associate with the endpoint.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
tags
A list of the tag keys and values that you want to associate with the endpoint.
- Parameters:
tags
- A list of the tag keys and values that you want to associate with the endpoint.- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
tags
A list of the tag keys and values that you want to associate with the endpoint.
This is a convenience method that creates an instance of theTag.Builder
avoiding the need to create one manually viaTag.builder()
.When the
Consumer
completes,SdkBuilder.build()
is called immediately and its result is passed totags(List<Tag>)
.- Parameters:
tags
- a consumer that will call methods onTag.Builder
- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
resolverEndpointType
For the endpoint type you can choose either IPv4, IPv6, or dual-stack. A dual-stack endpoint means that it will resolve via both IPv4 and IPv6. This endpoint type is applied to all IP addresses.
- Parameters:
resolverEndpointType
- For the endpoint type you can choose either IPv4, IPv6, or dual-stack. A dual-stack endpoint means that it will resolve via both IPv4 and IPv6. This endpoint type is applied to all IP addresses.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
resolverEndpointType
CreateResolverEndpointRequest.Builder resolverEndpointType(ResolverEndpointType resolverEndpointType) For the endpoint type you can choose either IPv4, IPv6, or dual-stack. A dual-stack endpoint means that it will resolve via both IPv4 and IPv6. This endpoint type is applied to all IP addresses.
- Parameters:
resolverEndpointType
- For the endpoint type you can choose either IPv4, IPv6, or dual-stack. A dual-stack endpoint means that it will resolve via both IPv4 and IPv6. This endpoint type is applied to all IP addresses.- Returns:
- Returns a reference to this object so that method calls can be chained together.
- See Also:
-
protocolsWithStrings
The protocols you want to use for the endpoint. DoH-FIPS is applicable for 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 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.
- Parameters:
protocols
- The protocols you want to use for the endpoint. DoH-FIPS is applicable for 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 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.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
-
protocolsWithStrings
The protocols you want to use for the endpoint. DoH-FIPS is applicable for 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 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.
- Parameters:
protocols
- The protocols you want to use for the endpoint. DoH-FIPS is applicable for 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 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.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
-
protocols
The protocols you want to use for the endpoint. DoH-FIPS is applicable for 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 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.
- Parameters:
protocols
- The protocols you want to use for the endpoint. DoH-FIPS is applicable for 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 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.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
-
protocols
The protocols you want to use for the endpoint. DoH-FIPS is applicable for 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 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.
- Parameters:
protocols
- The protocols you want to use for the endpoint. DoH-FIPS is applicable for 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 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.
-
- Returns:
- Returns a reference to this object so that method calls can be chained together.
-
-
overrideConfiguration
CreateResolverEndpointRequest.Builder overrideConfiguration(AwsRequestOverrideConfiguration overrideConfiguration) Description copied from interface:AwsRequest.Builder
Add an optional request override configuration.- Specified by:
overrideConfiguration
in interfaceAwsRequest.Builder
- Parameters:
overrideConfiguration
- The override configuration.- Returns:
- This object for method chaining.
-
overrideConfiguration
CreateResolverEndpointRequest.Builder overrideConfiguration(Consumer<AwsRequestOverrideConfiguration.Builder> builderConsumer) Description copied from interface:AwsRequest.Builder
Add an optional request override configuration.- Specified by:
overrideConfiguration
in interfaceAwsRequest.Builder
- Parameters:
builderConsumer
- AConsumer
to which an emptyAwsRequestOverrideConfiguration.Builder
will be given.- Returns:
- This object for method chaining.
-