AWS SDK Version 3 for .NET
API Reference

AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.

Associates an Amazon VPC with a private hosted zone.

To perform the association, the VPC and the private hosted zone must already exist. You can't convert a public hosted zone into a private hosted zone.

If you want to associate a VPC that was created by using one AWS account with a private hosted zone that was created by using a different account, the AWS account that created the private hosted zone must first submit a CreateVPCAssociationAuthorization request. Then the account that created the VPC must submit an AssociateVPCWithHostedZone request.


For .NET Core and PCL this operation is only available in asynchronous form. Please refer to AssociateVPCWithHostedZoneAsync.

Namespace: Amazon.Route53
Assembly: AWSSDK.Route53.dll
Version: 3.x.y.z


public virtual AssociateVPCWithHostedZoneResponse AssociateVPCWithHostedZone(
         AssociateVPCWithHostedZoneRequest request
Type: Amazon.Route53.Model.AssociateVPCWithHostedZoneRequest

Container for the necessary parameters to execute the AssociateVPCWithHostedZone service method.

Return Value
The response from the AssociateVPCWithHostedZone service method, as returned by Route53.


ConflictingDomainExistsException The cause of this error depends on whether you're trying to create a public or a private hosted zone: Public hosted zone: Two hosted zones that have the same name or that have a parent/child relationship ( and can't have any common name servers. You tried to create a hosted zone that has the same name as an existing hosted zone or that's the parent or child of an existing hosted zone, and you specified a delegation set that shares one or more name servers with the existing hosted zone. For more information, see CreateReusableDelegationSet. Private hosted zone: You specified an Amazon VPC that you're already using for another hosted zone, and the domain that you specified for one of the hosted zones is a subdomain of the domain that you specified for the other hosted zone. For example, you can't use the same Amazon VPC for the hosted zones for and
InvalidInputException The input is not valid.
InvalidVPCIdException The VPC ID that you specified either isn't a valid ID or the current account is not authorized to access this VPC.
LimitsExceededException This operation can't be completed either because the current account has reached the limit on reusable delegation sets that it can create or because you've reached the limit on the number of Amazon VPCs that you can associate with a private hosted zone. To get the current limit on the number of reusable delegation sets, see GetAccountLimit. To get the current limit on the number of Amazon VPCs that you can associate with a private hosted zone, see GetHostedZoneLimit. To request a higher limit, create a case with the AWS Support Center.
NoSuchHostedZoneException No hosted zone exists with the ID that you specified.
NotAuthorizedException Associating the specified VPC with the specified hosted zone has not been authorized.
PublicZoneVPCAssociationException You're trying to associate a VPC with a public hosted zone. Amazon Route 53 doesn't support associating a VPC with a public hosted zone.


The following example associates the VPC with ID vpc-1a2b3c4d with the hosted zone with ID Z3M3LMPEXAMPLE.

To associate a VPC with a hosted zone

var response = client.AssociateVPCWithHostedZone(new AssociateVPCWithHostedZoneRequest 
    Comment = "",
    HostedZoneId = "Z3M3LMPEXAMPLE",
    VPC = new VPC {
        VPCId = "vpc-1a2b3c4d",
        VPCRegion = "us-east-2"

ChangeInfo changeInfo = response.ChangeInfo;


Version Information

.NET Framework:
Supported in: 4.5, 4.0, 3.5

Portable Class Library:
Supported in: Windows Store Apps
Supported in: Windows Phone 8.1
Supported in: Xamarin Android
Supported in: Xamarin iOS (Unified)
Supported in: Xamarin.Forms

See Also