Package software.amazon.awssdk.services.route53resolver.model

Interface CreateResolverEndpointRequest.Builder

    • Method Detail

      • creatorRequestId

        CreateResolverEndpointRequest.Builder creatorRequestId​(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. 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

        CreateResolverEndpointRequest.Builder name​(String 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

        CreateResolverEndpointRequest.Builder securityGroupIds​(Collection<String> 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

        CreateResolverEndpointRequest.Builder securityGroupIds​(String... 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

        CreateResolverEndpointRequest.Builder direction​(String 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:
        ResolverEndpointDirection, ResolverEndpointDirection

      • direction

        CreateResolverEndpointRequest.Builder direction​(ResolverEndpointDirection 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:
        ResolverEndpointDirection, ResolverEndpointDirection

      • ipAddresses

        CreateResolverEndpointRequest.Builder 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). 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​(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). 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.

        This is a convenience method that creates an instance of the IpAddressRequest.Builder avoiding the need to create one manually via IpAddressRequest.builder().

        When the Consumer completes, SdkBuilder.build() is called immediately and its result is passed to #ipAddresses(List).

        Parameters:
        ipAddresses - a consumer that will call methods on IpAddressRequest.Builder
        Returns:
        Returns a reference to this object so that method calls can be chained together.
        See Also:
        #ipAddresses(java.util.Collection)

      • outpostArn

        CreateResolverEndpointRequest.Builder outpostArn​(String 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 the PreferredInstanceType.
        Returns:
        Returns a reference to this object so that method calls can be chained together.

      • preferredInstanceType

        CreateResolverEndpointRequest.Builder preferredInstanceType​(String 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 the OutpostArn.
        Returns:
        Returns a reference to this object so that method calls can be chained together.

      • tags

        CreateResolverEndpointRequest.Builder tags​(Collection<Tag> 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

        CreateResolverEndpointRequest.Builder tags​(Tag... 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

        CreateResolverEndpointRequest.Builder tags​(Consumer<Tag.Builder>... 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 the Tag.Builder avoiding the need to create one manually via Tag.builder().

        When the Consumer completes, SdkBuilder.build() is called immediately and its result is passed to #tags(List).

        Parameters:
        tags - a consumer that will call methods on Tag.Builder
        Returns:
        Returns a reference to this object so that method calls can be chained together.
        See Also:
        #tags(java.util.Collection)

      • resolverEndpointType

        CreateResolverEndpointRequest.Builder resolverEndpointType​(String 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, ResolverEndpointType

      • 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:
        ResolverEndpointType, ResolverEndpointType

      • protocolsWithStrings

        CreateResolverEndpointRequest.Builder protocolsWithStrings​(Collection<String> 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.

      • protocolsWithStrings

        CreateResolverEndpointRequest.Builder protocolsWithStrings​(String... 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

        CreateResolverEndpointRequest.Builder protocols​(Collection<Protocol> 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

        CreateResolverEndpointRequest.Builder protocols​(Protocol... 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.