ActivateKeySigningKey
Activates a key-signing key (KSK) so that it can be used for signing by DNSSEC. This
operation changes the KSK status to ACTIVE
.
Request Syntax
POST /2013-04-01/keysigningkey/HostedZoneId
/Name
/activate HTTP/1.1
URI Request Parameters
The request uses the following URI parameters.
- HostedZoneId
-
A unique string used to identify a hosted zone.
Length Constraints: Maximum length of 32.
Required: Yes
- Name
-
A string used to identify a key-signing key (KSK).
Name
can include numbers, letters, and underscores (_).Name
must be unique for each key-signing key in the same hosted zone.Length Constraints: Minimum length of 3. Maximum length of 128.
Required: Yes
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 200
<?xml version="1.0" encoding="UTF-8"?>
<ActivateKeySigningKeyResponse>
<ChangeInfo>
<Comment>string</Comment>
<Id>string</Id>
<Status>string</Status>
<SubmittedAt>timestamp</SubmittedAt>
</ChangeInfo>
</ActivateKeySigningKeyResponse>
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in XML format by the service.
- ActivateKeySigningKeyResponse
-
Root level tag for the ActivateKeySigningKeyResponse parameters.
Required: Yes
- ChangeInfo
-
A complex type that describes change information about changes made to your hosted zone.
Type: ChangeInfo object
Errors
For information about the errors that are common to all actions, see Common Errors.
- ConcurrentModification
-
Another user submitted a request to create, update, or delete the object at the same time that you did. Retry the request.
HTTP Status Code: 400
- InvalidInput
-
The input is not valid.
HTTP Status Code: 400
- InvalidKeySigningKeyStatus
-
The key-signing key (KSK) status isn't valid or another KSK has the status
INTERNAL_FAILURE
.HTTP Status Code: 400
- InvalidKMSArn
-
The KeyManagementServiceArn that you specified isn't valid to use with DNSSEC signing.
HTTP Status Code: 400
- InvalidSigningStatus
-
Your hosted zone status isn't valid for this operation. In the hosted zone, change the status to enable
DNSSEC
or disableDNSSEC
.HTTP Status Code: 400
- NoSuchKeySigningKey
-
The specified key-signing key (KSK) doesn't exist.
HTTP Status Code: 404
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: