![]() Each Amazon Web Services account is scoped to one partition. When granting access, the hosted zone and the Amazon VPC must belong to the same partition. Then the account thatĬreated the VPC must submit an AssociateVPCWithHostedZone request. Hosted zone must first submit a CreateVPCAssociationAuthorization request. Zone that was created by using a different account, the Amazon Web Services account that created the private ![]() If you want to associate a VPC that was created by using one Amazon Web Services account with a private hosted To perform the association, the VPC and the private hosted zone must already exist. associateVPCWithHostedZone public AssociateVPCWithHostedZoneResult associateVPCWithHostedZone( AssociateVPCWithHostedZoneRequest request)Īssociates an Amazon VPC with a private hosted zone.InvalidInputException - The input is not valid. InvalidKMSArnException - The KeyManagementServiceArn that you specified isn't valid to use with DNSSEC signing. ![]() In the hosted zone, change the status to enableĭNSSEC or disable DNSSEC. InvalidSigningStatusException - Your hosted zone status isn't valid for this operation. ![]() InvalidKeySigningKeyStatusException - The key-signing key (KSK) status isn't valid or another KSK has the status INTERNAL_FAILURE. NoSuchKeySigningKeyException - The specified key-signing key (KSK) doesn't exist. Throws: ConcurrentModificationException - Another user submitted a request to create, update, or delete the object at the same time that you did. Specified by: activateKeySigningKey in interface AmazonRoute53 Parameters: activateKeySigningKeyRequest - Returns: Result of the ActivateKeySigningKey operation returned by the service. Activates a key-signing key (KSK) so that it can be used for signing by DNSSEC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |