diff --git a/CHANGELOG.md b/CHANGELOG.md
index ddbbc95b6b3..78a2b400d89 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,16 @@
+Release v1.40.33 (2021-08-30)
+===
+
+### Service Client Updates
+* `service/cloudformation`: Updates service API and documentation
+ * AWS CloudFormation allows you to iteratively develop your applications when failures are encountered without rolling back successfully provisioned resources. By specifying stack failure options, you can troubleshoot resources in a CREATE_FAILED or UPDATE_FAILED status.
+* `service/codebuild`: Updates service documentation
+ * Documentation updates for CodeBuild
+* `service/firehose`: Updates service API and documentation
+ * This release adds the Dynamic Partitioning feature to Kinesis Data Firehose service for S3 destinations.
+* `service/kms`: Updates service API, documentation, and examples
+ * This release has changes to KMS nomenclature to remove the word master from both the "Customer master key" and "CMK" abbreviation and replace those naming conventions with "KMS key".
+
Release v1.40.32 (2021-08-27)
===
diff --git a/aws/version.go b/aws/version.go
index 3629bf74987..c3c3c248088 100644
--- a/aws/version.go
+++ b/aws/version.go
@@ -5,4 +5,4 @@ package aws
const SDKName = "aws-sdk-go"
// SDKVersion is the version of this SDK
-const SDKVersion = "1.40.32"
+const SDKVersion = "1.40.33"
diff --git a/models/apis/cloudformation/2010-05-15/api-2.json b/models/apis/cloudformation/2010-05-15/api-2.json
index 9f9c53fa32c..d5038c2e88c 100644
--- a/models/apis/cloudformation/2010-05-15/api-2.json
+++ b/models/apis/cloudformation/2010-05-15/api-2.json
@@ -798,6 +798,21 @@
],
"idempotent":true
},
+ "RollbackStack":{
+ "name":"RollbackStack",
+ "http":{
+ "method":"POST",
+ "requestUri":"/"
+ },
+ "input":{"shape":"RollbackStackInput"},
+ "output":{
+ "shape":"RollbackStackOutput",
+ "resultWrapper":"RollbackStackResult"
+ },
+ "errors":[
+ {"shape":"TokenAlreadyExistsException"}
+ ]
+ },
"SetStackPolicy":{
"name":"SetStackPolicy",
"http":{
@@ -1901,7 +1916,8 @@
"members":{
"ChangeSetName":{"shape":"ChangeSetNameOrId"},
"StackName":{"shape":"StackNameOrId"},
- "ClientRequestToken":{"shape":"ClientRequestToken"}
+ "ClientRequestToken":{"shape":"ClientRequestToken"},
+ "DisableRollback":{"shape":"DisableRollback"}
}
},
"ExecuteChangeSetOutput":{
@@ -2880,7 +2896,13 @@
"IMPORT_IN_PROGRESS",
"IMPORT_ROLLBACK_IN_PROGRESS",
"IMPORT_ROLLBACK_FAILED",
- "IMPORT_ROLLBACK_COMPLETE"
+ "IMPORT_ROLLBACK_COMPLETE",
+ "UPDATE_ROLLBACK_IN_PROGRESS",
+ "UPDATE_ROLLBACK_COMPLETE",
+ "UPDATE_ROLLBACK_FAILED",
+ "ROLLBACK_IN_PROGRESS",
+ "ROLLBACK_COMPLETE",
+ "ROLLBACK_FAILED"
]
},
"ResourceStatusReason":{"type":"string"},
@@ -2952,6 +2974,21 @@
"MonitoringTimeInMinutes":{"shape":"MonitoringTimeInMinutes"}
}
},
+ "RollbackStackInput":{
+ "type":"structure",
+ "required":["StackName"],
+ "members":{
+ "StackName":{"shape":"StackNameOrId"},
+ "RoleARN":{"shape":"RoleARN"},
+ "ClientRequestToken":{"shape":"ClientRequestToken"}
+ }
+ },
+ "RollbackStackOutput":{
+ "type":"structure",
+ "members":{
+ "StackId":{"shape":"StackId"}
+ }
+ },
"RollbackTrigger":{
"type":"structure",
"required":[
@@ -3605,6 +3642,7 @@
"UPDATE_IN_PROGRESS",
"UPDATE_COMPLETE_CLEANUP_IN_PROGRESS",
"UPDATE_COMPLETE",
+ "UPDATE_FAILED",
"UPDATE_ROLLBACK_IN_PROGRESS",
"UPDATE_ROLLBACK_FAILED",
"UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS",
@@ -3990,6 +4028,7 @@
"StackPolicyURL":{"shape":"StackPolicyURL"},
"NotificationARNs":{"shape":"NotificationARNs"},
"Tags":{"shape":"Tags"},
+ "DisableRollback":{"shape":"DisableRollback"},
"ClientRequestToken":{"shape":"ClientRequestToken"}
}
},
diff --git a/models/apis/cloudformation/2010-05-15/docs-2.json b/models/apis/cloudformation/2010-05-15/docs-2.json
index 20d4d0b3c85..2a209c55618 100644
--- a/models/apis/cloudformation/2010-05-15/docs-2.json
+++ b/models/apis/cloudformation/2010-05-15/docs-2.json
@@ -13,15 +13,15 @@
"DeactivateType": "
Deactivates a public extension that was previously activated in this account and region.
Once deactivated, an extension cannot be used in any CloudFormation operation. This includes stack update operations where the stack template includes the extension, even if no updates are being made to the extension. In addition, deactivated extensions are not automatically updated if a new version of the extension is released.
",
"DeleteChangeSet": "Deletes the specified change set. Deleting change sets ensures that no one executes the wrong change set.
If the call successfully completes, CloudFormation successfully deleted the change set.
If IncludeNestedStacks
specifies True
during the creation of the nested change set, then DeleteChangeSet
will delete all change sets that belong to the stacks hierarchy and will also delete all change sets for nested stacks with the status of REVIEW_IN_PROGRESS
.
",
"DeleteStack": "Deletes a specified stack. Once the call completes successfully, stack deletion starts. Deleted stacks do not show up in the DescribeStacks API if the deletion has been completed successfully.
",
- "DeleteStackInstances": "Deletes stack instances for the specified accounts, in the specified Regions.
",
- "DeleteStackSet": "Deletes a stack set. Before you can delete a stack set, all of its member stack instances must be deleted. For more information about how to do this, see DeleteStackInstances.
",
+ "DeleteStackInstances": "Deletes stack instances for the specified accounts, in the specified Regions.
",
+ "DeleteStackSet": "Deletes a stack set. Before you can delete a stack set, all of its member stack instances must be deleted. For more information about how to do this, see DeleteStackInstances.
",
"DeregisterType": "Marks an extension or extension version as DEPRECATED
in the CloudFormation registry, removing it from active use. Deprecated extensions or extension versions cannot be used in CloudFormation operations.
To deregister an entire extension, you must individually deregister all active versions of that extension. If an extension has only a single active version, deregistering that version results in the extension itself being deregistered and marked as deprecated in the registry.
You cannot deregister the default version of an extension if there are other active version of that extension. If you do deregister the default version of an extension, the textensionype itself is deregistered as well and marked as deprecated.
To view the deprecation status of an extension or extension version, use DescribeType.
",
"DescribeAccountLimits": "Retrieves your account's CloudFormation limits, such as the maximum number of stacks that you can create in your account. For more information about account limits, see CloudFormation Limits in the CloudFormation User Guide.
",
"DescribeChangeSet": "Returns the inputs for the change set and a list of changes that CloudFormation will make if you execute the change set. For more information, see Updating Stacks Using Change Sets in the CloudFormation User Guide.
",
"DescribePublisher": "Returns information about a CloudFormation extension publisher.
If you do not supply a PublisherId
, and you have registered as an extension publisher, DescribePublisher
returns information about your own publisher account.
For more information on registering as a publisher, see:
",
"DescribeStackDriftDetectionStatus": "Returns information about a stack drift detection operation. A stack drift detection operation detects whether a stack's actual configuration differs, or has drifted, from it's expected configuration, as defined in the stack template and any values specified as template parameters. A stack is considered to have drifted if one or more of its resources have drifted. For more information on stack and resource drift, see Detecting Unregulated Configuration Changes to Stacks and Resources.
Use DetectStackDrift to initiate a stack drift detection operation. DetectStackDrift
returns a StackDriftDetectionId
you can use to monitor the progress of the operation using DescribeStackDriftDetectionStatus
. Once the drift detection operation has completed, use DescribeStackResourceDrifts to return drift information about the stack and its resources.
",
"DescribeStackEvents": "Returns all stack related events for a specified stack in reverse chronological order. For more information about a stack's event history, go to Stacks in the CloudFormation User Guide.
You can list events for stacks that have failed to create or have been deleted by specifying the unique stack identifier (stack ID).
",
- "DescribeStackInstance": "Returns the stack instance that's associated with the specified stack set, account, and Region.
For a list of stack instances that are associated with a specific stack set, use ListStackInstances.
",
+ "DescribeStackInstance": "Returns the stack instance that's associated with the specified stack set, Amazon Web Services account, and Region.
For a list of stack instances that are associated with a specific stack set, use ListStackInstances.
",
"DescribeStackResource": "Returns a description of the specified resource in the specified stack.
For deleted stacks, DescribeStackResource returns resource information for up to 90 days after the stack has been deleted.
",
"DescribeStackResourceDrifts": "Returns drift information for the resources that have been checked for drift in the specified stack. This includes actual and expected configuration values for resources where CloudFormation detects configuration drift.
For a given stack, there will be one StackResourceDrift
for each stack resource that has been checked for drift. Resources that have not yet been checked for drift are not included. Resources that do not currently support drift detection are not checked, and so not included. For a list of resources that support drift detection, see Resources that Support Drift Detection.
Use DetectStackResourceDrift to detect drift on individual resources, or DetectStackDrift to detect drift on all supported resources for a given stack.
",
"DescribeStackResources": "Returns Amazon Web Services resource descriptions for running and deleted stacks. If StackName
is specified, all the associated resources that are part of the stack are returned. If PhysicalResourceId
is specified, the associated resources of the stack that the resource belongs to are returned.
Only the first 100 resources will be returned. If your stack has more resources than this, you should use ListStackResources
instead.
For deleted stacks, DescribeStackResources
returns resource information for up to 90 days after the stack has been deleted.
You must specify either StackName
or PhysicalResourceId
, but not both. In addition, you can specify LogicalResourceId
to filter the returned result. For more information about resources, the LogicalResourceId
and PhysicalResourceId
, go to the CloudFormation User Guide.
A ValidationError
is returned if you specify both StackName
and PhysicalResourceId
in the same request.
",
@@ -36,25 +36,26 @@
"EstimateTemplateCost": "Returns the estimated monthly cost of a template. The return value is an Amazon Web Services Simple Monthly Calculator URL with a query string that describes the resources required to run the template.
",
"ExecuteChangeSet": "Updates a stack using the input information that was provided when the specified change set was created. After the call successfully completes, CloudFormation starts updating the stack. Use the DescribeStacks action to view the status of the update.
When you execute a change set, CloudFormation deletes all other change sets associated with the stack because they aren't valid for the updated stack.
If a stack policy is associated with the stack, CloudFormation enforces the policy during the update. You can't specify a temporary stack policy that overrides the current policy.
To create a change set for the entire stack hierachy, IncludeNestedStacks
must have been set to True
.
",
"GetStackPolicy": "Returns the stack policy for a specified stack. If a stack doesn't have a policy, a null value is returned.
",
- "GetTemplate": "Returns the template body for a specified stack. You can get the template for running or deleted stacks.
For deleted stacks, GetTemplate returns the template for up to 90 days after the stack has been deleted.
If the template does not exist, a ValidationError
is returned.
",
+ "GetTemplate": "Returns the template body for a specified stack. You can get the template for running or deleted stacks.
For deleted stacks, GetTemplate returns the template for up to 90 days after the stack has been deleted.
If the template does not exist, a ValidationError
is returned.
",
"GetTemplateSummary": "Returns information about a new or existing template. The GetTemplateSummary
action is useful for viewing parameter information, such as default parameter values and parameter types, before you create or update a stack or stack set.
You can use the GetTemplateSummary
action when you submit a template, or you can get template information for a stack set, or a running or deleted stack.
For deleted stacks, GetTemplateSummary
returns the template information for up to 90 days after the stack has been deleted. If the template does not exist, a ValidationError
is returned.
",
"ImportStacksToStackSet": "Import existing stacks into a new stack sets. Use the stack import operation to import up to 10 stacks into a new stack set in the same account as the source stack or in a different administrator account and Region, by specifying the stack ID of the stack you intend to import.
ImportStacksToStackSet
is only supported by self-managed permissions.
",
"ListChangeSets": "Returns the ID and status of each active change set for a stack. For example, CloudFormation lists change sets that are in the CREATE_IN_PROGRESS
or CREATE_PENDING
state.
",
- "ListExports": "Lists all exported output values in the account and Region in which you call this action. Use this action to see the exported output values that you can import into other stacks. To import values, use the Fn::ImportValue
function.
For more information, see CloudFormation Export Stack Output Values.
",
- "ListImports": "Lists all stacks that are importing an exported output value. To modify or remove an exported output value, first use this action to see which stacks are using it. To see the exported output values in your account, see ListExports.
For more information about importing an exported output value, see the Fn::ImportValue
function.
",
- "ListStackInstances": "Returns summary information about stack instances that are associated with the specified stack set. You can filter for stack instances that are associated with a specific account name or Region, or that have a specific status.
",
+ "ListExports": "Lists all exported output values in the account and Region in which you call this action. Use this action to see the exported output values that you can import into other stacks. To import values, use the Fn::ImportValue
function.
For more information, see CloudFormation Export Stack Output Values.
",
+ "ListImports": "Lists all stacks that are importing an exported output value. To modify or remove an exported output value, first use this action to see which stacks are using it. To see the exported output values in your account, see ListExports.
For more information about importing an exported output value, see the Fn::ImportValue
function.
",
+ "ListStackInstances": "Returns summary information about stack instances that are associated with the specified stack set. You can filter for stack instances that are associated with a specific Amazon Web Services account name or Region, or that have a specific status.
",
"ListStackResources": "Returns descriptions of all resources of the specified stack.
For deleted stacks, ListStackResources returns resource information for up to 90 days after the stack has been deleted.
",
"ListStackSetOperationResults": "Returns summary information about the results of a stack set operation.
",
"ListStackSetOperations": "Returns summary information about operations performed on a stack set.
",
- "ListStackSets": "Returns summary information about stack sets that are associated with the user.
-
[Self-managed permissions] If you set the CallAs
parameter to SELF
while signed in to your account, ListStackSets
returns all self-managed stack sets in your account.
-
[Service-managed permissions] If you set the CallAs
parameter to SELF
while signed in to the organization's management account, ListStackSets
returns all stack sets in the management account.
-
[Service-managed permissions] If you set the CallAs
parameter to DELEGATED_ADMIN
while signed in to your member account, ListStackSets
returns all stack sets with service-managed permissions in the management account.
",
+ "ListStackSets": "Returns summary information about stack sets that are associated with the user.
-
[Self-managed permissions] If you set the CallAs
parameter to SELF
while signed in to your Amazon Web Services account, ListStackSets
returns all self-managed stack sets in your Amazon Web Services account.
-
[Service-managed permissions] If you set the CallAs
parameter to SELF
while signed in to the organization's management account, ListStackSets
returns all stack sets in the management account.
-
[Service-managed permissions] If you set the CallAs
parameter to DELEGATED_ADMIN
while signed in to your member account, ListStackSets
returns all stack sets with service-managed permissions in the management account.
",
"ListStacks": "Returns the summary information for stacks whose status matches the specified StackStatusFilter. Summary information for stacks that have been deleted is kept for 90 days after the stack is deleted. If no StackStatusFilter is specified, summary information for all stacks is returned (including existing stacks and stacks that have been deleted).
",
"ListTypeRegistrations": "Returns a list of registration tokens for the specified extension(s).
",
"ListTypeVersions": "Returns summary information about the versions of an extension.
",
"ListTypes": "Returns summary information about extension that have been registered with CloudFormation.
",
"PublishType": "Publishes the specified extension to the CloudFormation registry as a public extension in this region. Public extensions are available for use by all CloudFormation users. For more information on publishing extensions, see Publishing extensions to make them available for public use in the CloudFormation CLI User Guide.
To publish an extension, you must be registered as a publisher with CloudFormation. For more information, see RegisterPublisher.
",
"RecordHandlerProgress": "Reports progress of a resource handler to CloudFormation.
Reserved for use by the CloudFormation CLI. Do not use this API in your code.
",
- "RegisterPublisher": "Registers your account as a publisher of public extensions in the CloudFormation registry. Public extensions are available for use by all CloudFormation users. This publisher ID applies to your account in all Regions.
For information on requirements for registering as a public extension publisher, see Registering your account to publish CloudFormation extensions in the CloudFormation CLI User Guide.
",
- "RegisterType": "Registers an extension with the CloudFormation service. Registering an extension makes it available for use in CloudFormation templates in your account, and includes:
-
Validating the extension schema
-
Determining which handlers, if any, have been specified for the extension
-
Making the extension available for use in your account
For more information on how to develop extensions and ready them for registeration, see Creating Resource Providers in the CloudFormation CLI User Guide.
You can have a maximum of 50 resource extension versions registered at a time. This maximum is per account and per region. Use DeregisterType to deregister specific extension versions if necessary.
Once you have initiated a registration request using RegisterType
, you can use DescribeTypeRegistration
to monitor the progress of the registration request.
Once you have registered a private extension in your account and region, use SetTypeConfiguration to specify configuration properties for the extension. For more information, see Configuring extensions at the account level in the CloudFormation User Guide.
",
+ "RegisterPublisher": "Registers your account as a publisher of public extensions in the CloudFormation registry. Public extensions are available for use by all CloudFormation users. This publisher ID applies to your account in all Amazon Web Services Regions.
For information on requirements for registering as a public extension publisher, see Registering your account to publish CloudFormation extensions in the CloudFormation CLI User Guide.
",
+ "RegisterType": "Registers an extension with the CloudFormation service. Registering an extension makes it available for use in CloudFormation templates in your Amazon Web Services account, and includes:
-
Validating the extension schema
-
Determining which handlers, if any, have been specified for the extension
-
Making the extension available for use in your account
For more information on how to develop extensions and ready them for registeration, see Creating Resource Providers in the CloudFormation CLI User Guide.
You can have a maximum of 50 resource extension versions registered at a time. This maximum is per account and per region. Use DeregisterType to deregister specific extension versions if necessary.
Once you have initiated a registration request using RegisterType
, you can use DescribeTypeRegistration
to monitor the progress of the registration request.
Once you have registered a private extension in your account and region, use SetTypeConfiguration to specify configuration properties for the extension. For more information, see Configuring extensions at the account level in the CloudFormation User Guide.
",
+ "RollbackStack": "When specifying RollbackStack
, you preserve the state of previously provisioned resources when an operation fails. You can check the status of the stack through the DescribeStacks API.
Rolls back the specified stack to the last known stable state from CREATE_FAILED
or UPDATE_FAILED
stack statuses.
This operation will delete a stack if it doesn't contain a last known stable state. A last known stable state includes any status in a *_COMPLETE
. This includes the following stack statuses.
-
CREATE_COMPLETE
-
UPDATE_COMPLETE
-
UPDATE_ROLLBACK_COMPLETE
-
IMPORT_COMPLETE
-
IMPORT_ROLLBACK_COMPLETE
",
"SetStackPolicy": "Sets a stack policy for a specified stack.
",
"SetTypeConfiguration": "Specifies the configuration data for a registered CloudFormation extension, in the given account and region.
To view the current configuration data for an extension, refer to the ConfigurationSchema
element of DescribeType. For more information, see Configuring extensions at the account level in the CloudFormation User Guide.
It is strongly recommended that you use dynamic references to restrict sensitive configuration definitions, such as third-party credentials. For more details on dynamic references, see Using dynamic references to specify template values in the CloudFormation User Guide.
",
"SetTypeDefaultVersion": "Specify the default version of an extension. The default version of an extension will be used in CloudFormation operations.
",
@@ -64,7 +65,7 @@
"UpdateStack": "Updates a stack as specified in the template. After the call completes successfully, the stack update starts. You can check the status of the stack via the DescribeStacks action.
To get a copy of the template for an existing stack, you can use the GetTemplate action.
For more information about creating an update template, updating a stack, and monitoring the progress of the update, see Updating a Stack.
",
"UpdateStackInstances": "Updates the parameter values for stack instances for the specified accounts, within the specified Regions. A stack instance refers to a stack in a specific account and Region.
You can only update stack instances in Regions and accounts where they already exist; to create additional stack instances, use CreateStackInstances.
During stack set updates, any parameters overridden for a stack instance are not updated, but retain their overridden value.
You can only update the parameter values that are specified in the stack set; to add or delete a parameter itself, use UpdateStackSet to update the stack set template. If you add a parameter to a template, before you can override the parameter value specified in the stack set you must first use UpdateStackSet to update all stack instances with the updated template and parameter value specified in the stack set. Once a stack instance has been updated with the new parameter, you can then override the parameter value using UpdateStackInstances
.
",
"UpdateStackSet": "Updates the stack set, and associated stack instances in the specified accounts and Regions.
Even if the stack set operation created by updating the stack set fails (completely or partially, below or above a specified failure tolerance), the stack set is updated with your changes. Subsequent CreateStackInstances calls on the specified stack set use the updated stack set.
",
- "UpdateTerminationProtection": "Updates termination protection for the specified stack. If a user attempts to delete a stack with termination protection enabled, the operation fails and the stack remains unchanged. For more information, see Protecting a Stack From Being Deleted in the CloudFormation User Guide.
For nested stacks, termination protection is set on the root stack and cannot be changed directly on the nested stack.
",
+ "UpdateTerminationProtection": "Updates termination protection for the specified stack. If a user attempts to delete a stack with termination protection enabled, the operation fails and the stack remains unchanged. For more information, see Protecting a Stack From Being Deleted in the CloudFormation User Guide.
For nested stacks, termination protection is set on the root stack and cannot be changed directly on the nested stack.
",
"ValidateTemplate": "Validates a specified template. CloudFormation first checks if the template is valid JSON. If it isn't, CloudFormation checks if the template is valid YAML. If both these checks fail, CloudFormation returns a template validation error.
"
},
"shapes": {
@@ -78,11 +79,11 @@
"base": null,
"refs": {
"AccountList$member": null,
- "DescribeStackInstanceInput$StackInstanceAccount": "The ID of an account that's associated with this stack instance.
",
- "ListStackInstancesInput$StackInstanceAccount": "The name of the account that you want to list stack instances for.
",
- "StackInstance$Account": "[Self-managed permissions] The name of the account that the stack instance is associated with.
",
- "StackInstanceSummary$Account": "[Self-managed permissions] The name of the account that the stack instance is associated with.
",
- "StackSetOperationResultSummary$Account": "[Self-managed permissions] The name of the account for this operation result.
"
+ "DescribeStackInstanceInput$StackInstanceAccount": "The ID of an Amazon Web Services account that's associated with this stack instance.
",
+ "ListStackInstancesInput$StackInstanceAccount": "The name of the Amazon Web Services account that you want to list stack instances for.
",
+ "StackInstance$Account": "[Self-managed permissions] The name of the Amazon Web Services account that the stack instance is associated with.
",
+ "StackInstanceSummary$Account": "[Self-managed permissions] The name of the Amazon Web Services account that the stack instance is associated with.
",
+ "StackSetOperationResultSummary$Account": "[Self-managed permissions] The name of the Amazon Web Services account for this operation result.
"
}
},
"AccountGateResult": {
@@ -118,10 +119,10 @@
"AccountList": {
"base": null,
"refs": {
- "CreateStackInstancesInput$Accounts": "[Self-managed permissions] The names of one or more accounts that you want to create stack instances in the specified Region(s) for.
You can specify Accounts
or DeploymentTargets
, but not both.
",
- "DeleteStackInstancesInput$Accounts": "[Self-managed permissions] The names of the accounts that you want to delete stack instances for.
You can specify Accounts
or DeploymentTargets
, but not both.
",
- "DeploymentTargets$Accounts": "The names of one or more accounts for which you want to deploy stack set updates.
",
- "UpdateStackInstancesInput$Accounts": "[Self-managed permissions] The names of one or more accounts for which you want to update parameter values for stack instances. The overridden parameter values will be applied to all stack instances in the specified accounts and Regions.
You can specify Accounts
or DeploymentTargets
, but not both.
",
+ "CreateStackInstancesInput$Accounts": "[Self-managed permissions] The names of one or more Amazon Web Services accounts that you want to create stack instances in the specified Region(s) for.
You can specify Accounts
or DeploymentTargets
, but not both.
",
+ "DeleteStackInstancesInput$Accounts": "[Self-managed permissions] The names of the Amazon Web Services accounts that you want to delete stack instances for.
You can specify Accounts
or DeploymentTargets
, but not both.
",
+ "DeploymentTargets$Accounts": "The names of one or more Amazon Web Services accounts for which you want to deploy stack set updates.
",
+ "UpdateStackInstancesInput$Accounts": "[Self-managed permissions] The names of one or more Amazon Web Services accounts for which you want to update parameter values for stack instances. The overridden parameter values will be applied to all stack instances in the specified accounts and Regions.
You can specify Accounts
or DeploymentTargets
, but not both.
",
"UpdateStackSetInput$Accounts": "[Self-managed permissions] The accounts in which to update associated stack instances. If you specify accounts, you must also specify the Regions in which to update stack set instances.
To update all the stack instances associated with this stack set, do not specify the Accounts
or Regions
properties.
If the stack set update includes changes to the template (that is, if the TemplateBody
or TemplateURL
properties are specified), or the Parameters
property, CloudFormation marks all stack instances with a status of OUTDATED
prior to updating the stack instances in the specified accounts and Regions. If the stack set update does not include changes to the template or parameters, CloudFormation updates the stack instances in the specified accounts and Regions, while leaving all other stack instances with their existing stack instance status.
"
}
},
@@ -228,23 +229,23 @@
"CallAs": {
"base": null,
"refs": {
- "CreateStackInstancesInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "CreateStackSetInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
To create a stack set with service-managed permissions while signed in to the management account, specify SELF
.
-
To create a stack set with service-managed permissions while signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated admin in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
Stack sets with service-managed permissions are created in the management account, including stack sets that are created by delegated administrators.
",
- "DeleteStackInstancesInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "DeleteStackSetInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "DescribeStackInstanceInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "DescribeStackSetInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "DescribeStackSetOperationInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "DetectStackSetDriftInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "GetTemplateSummaryInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "CreateStackInstancesInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "CreateStackSetInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
To create a stack set with service-managed permissions while signed in to the management account, specify SELF
.
-
To create a stack set with service-managed permissions while signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated admin in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
Stack sets with service-managed permissions are created in the management account, including stack sets that are created by delegated administrators.
",
+ "DeleteStackInstancesInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "DeleteStackSetInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "DescribeStackInstanceInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "DescribeStackSetInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "DescribeStackSetOperationInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "DetectStackSetDriftInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "GetTemplateSummaryInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
"ImportStacksToStackSetInput$CallAs": "By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
For service managed stack sets, specify DELEGATED_ADMIN
.
",
- "ListStackInstancesInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "ListStackSetOperationResultsInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "ListStackSetOperationsInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "ListStackSetsInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "StopStackSetOperationInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "UpdateStackInstancesInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
- "UpdateStackSetInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
"
+ "ListStackInstancesInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "ListStackSetOperationResultsInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "ListStackSetOperationsInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "ListStackSetsInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "StopStackSetOperationInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "UpdateStackInstancesInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
",
+ "UpdateStackSetInput$CallAs": "[Service-managed permissions] Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account.
By default, SELF
is specified. Use SELF
for stack sets with self-managed permissions.
-
If you are signed in to the management account, specify SELF
.
-
If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN
.
Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
"
}
},
"CancelUpdateStackInput": {
@@ -255,15 +256,15 @@
"Capabilities": {
"base": null,
"refs": {
- "CreateChangeSetInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to create the stack.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually creating the stack. If your stack template contains one or more macros, and you choose to create a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.
This capacity does not apply to creating change sets, and specifying it when creating change sets has no effect.
If you want to create a stack from a stack template that contains macros and nested stacks, you must create or update the stack directly from the template using the CreateStack or UpdateStack action, and specifying this capability.
For more information on macros, see Using CloudFormation Macros to Perform Custom Processing on Templates.
",
- "CreateStackInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to create the stack.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually creating the stack. If your stack template contains one or more macros, and you choose to create a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.
If you want to create a stack from a stack template that contains macros and nested stacks, you must create the stack directly from the template using this capability.
You should only create stacks directly from a stack template that contains macros if you know what processing the macro performs.
Each macro relies on an underlying Lambda service function for processing stack templates. Be aware that the Lambda function owner can update the function operation without CloudFormation being notified.
For more information, see Using CloudFormation Macros to Perform Custom Processing on Templates.
",
- "CreateStackSetInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack set template contains certain capabilities in order for CloudFormation to create the stack set and related stack instances.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your account; for example, by creating new Identity and Access Management (IAM) users. For those stack sets, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some templates reference macros. If your stack set template references one or more macros, you must create the stack set directly from the processed template, without first reviewing the resulting changes in a change set. To create the stack set directly, you must acknowledge this capability. For more information, see Using CloudFormation Macros to Perform Custom Processing on Templates.
Stack sets with service-managed permissions do not currently support the use of macros in templates. (This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.) Even if you specify this capability for a stack set with service-managed permissions, if you reference a macro in your template the stack set operation will fail.
",
+ "CreateChangeSetInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to create the stack.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually creating the stack. If your stack template contains one or more macros, and you choose to create a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.
This capacity does not apply to creating change sets, and specifying it when creating change sets has no effect.
If you want to create a stack from a stack template that contains macros and nested stacks, you must create or update the stack directly from the template using the CreateStack or UpdateStack action, and specifying this capability.
For more information on macros, see Using CloudFormation Macros to Perform Custom Processing on Templates.
",
+ "CreateStackInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to create the stack.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually creating the stack. If your stack template contains one or more macros, and you choose to create a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.
If you want to create a stack from a stack template that contains macros and nested stacks, you must create the stack directly from the template using this capability.
You should only create stacks directly from a stack template that contains macros if you know what processing the macro performs.
Each macro relies on an underlying Lambda service function for processing stack templates. Be aware that the Lambda function owner can update the function operation without CloudFormation being notified.
For more information, see Using CloudFormation Macros to Perform Custom Processing on Templates.
",
+ "CreateStackSetInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack set template contains certain capabilities in order for CloudFormation to create the stack set and related stack instances.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stack sets, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some templates reference macros. If your stack set template references one or more macros, you must create the stack set directly from the processed template, without first reviewing the resulting changes in a change set. To create the stack set directly, you must acknowledge this capability. For more information, see Using CloudFormation Macros to Perform Custom Processing on Templates.
Stack sets with service-managed permissions do not currently support the use of macros in templates. (This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.) Even if you specify this capability for a stack set with service-managed permissions, if you reference a macro in your template the stack set operation will fail.
",
"DescribeChangeSetOutput$Capabilities": "If you execute the change set, the list of capabilities that were explicitly acknowledged when the change set was created.
",
"GetTemplateSummaryOutput$Capabilities": "The capabilities found within the template. If your template contains IAM resources, you must specify the CAPABILITY_IAM or CAPABILITY_NAMED_IAM value for this parameter when you use the CreateStack or UpdateStack actions with your template; otherwise, those actions return an InsufficientCapabilities error.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
",
"Stack$Capabilities": "The capabilities allowed in the stack.
",
- "StackSet$Capabilities": "The capabilities that are allowed in the stack set. Some stack set templates might include resources that can affect permissions in your account—for example, by creating new Identity and Access Management (IAM) users. For more information, see Acknowledging IAM Resources in CloudFormation Templates.
",
- "UpdateStackInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to update the stack.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually updating the stack. If your stack template contains one or more macros, and you choose to update a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.
If you want to update a stack from a stack template that contains macros and nested stacks, you must update the stack directly from the template using this capability.
You should only update stacks directly from a stack template that contains macros if you know what processing the macro performs.
Each macro relies on an underlying Lambda service function for processing stack templates. Be aware that the Lambda function owner can update the function operation without CloudFormation being notified.
For more information, see Using CloudFormation Macros to Perform Custom Processing on Templates.
",
- "UpdateStackSetInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to update the stack set and its associated stack instances.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your account; for example, by creating new Identity and Access Management (IAM) users. For those stacks sets, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some templates reference macros. If your stack set template references one or more macros, you must update the stack set directly from the processed template, without first reviewing the resulting changes in a change set. To update the stack set directly, you must acknowledge this capability. For more information, see Using CloudFormation Macros to Perform Custom Processing on Templates.
Stack sets with service-managed permissions do not currently support the use of macros in templates. (This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.) Even if you specify this capability for a stack set with service-managed permissions, if you reference a macro in your template the stack set operation will fail.
",
+ "StackSet$Capabilities": "The capabilities that are allowed in the stack set. Some stack set templates might include resources that can affect permissions in your Amazon Web Services account—for example, by creating new Identity and Access Management (IAM) users. For more information, see Acknowledging IAM Resources in CloudFormation Templates.
",
+ "UpdateStackInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to update the stack.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually updating the stack. If your stack template contains one or more macros, and you choose to update a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.
If you want to update a stack from a stack template that contains macros and nested stacks, you must update the stack directly from the template using this capability.
You should only update stacks directly from a stack template that contains macros if you know what processing the macro performs.
Each macro relies on an underlying Lambda service function for processing stack templates. Be aware that the Lambda function owner can update the function operation without CloudFormation being notified.
For more information, see Using CloudFormation Macros to Perform Custom Processing on Templates.
",
+ "UpdateStackSetInput$Capabilities": "In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to update the stack set and its associated stack instances.
-
CAPABILITY_IAM
and CAPABILITY_NAMED_IAM
Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stacks sets, you must explicitly acknowledge this by specifying one of these capabilities.
The following IAM resources require you to specify either the CAPABILITY_IAM
or CAPABILITY_NAMED_IAM
capability.
-
If you have IAM resources, you can specify either capability.
-
If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM
.
-
If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
error.
If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
-
CAPABILITY_AUTO_EXPAND
Some templates reference macros. If your stack set template references one or more macros, you must update the stack set directly from the processed template, without first reviewing the resulting changes in a change set. To update the stack set directly, you must acknowledge this capability. For more information, see Using CloudFormation Macros to Perform Custom Processing on Templates.
Stack sets with service-managed permissions do not currently support the use of macros in templates. (This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation.) Even if you specify this capability for a stack set with service-managed permissions, if you reference a macro in your template the stack set operation will fail.
",
"ValidateTemplateOutput$Capabilities": "The capabilities found within the template. If your template contains IAM resources, you must specify the CAPABILITY_IAM or CAPABILITY_NAMED_IAM value for this parameter when you use the CreateStack or UpdateStack actions with your template; otherwise, those actions return an InsufficientCapabilities error.
For more information, see Acknowledging IAM Resources in CloudFormation Templates.
"
}
},
@@ -396,11 +397,11 @@
"CancelUpdateStackInput$ClientRequestToken": "A unique identifier for this CancelUpdateStack
request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to cancel an update on a stack with the same name. You might retry CancelUpdateStack
requests to ensure that CloudFormation successfully received them.
",
"ContinueUpdateRollbackInput$ClientRequestToken": "A unique identifier for this ContinueUpdateRollback
request. Specify this token if you plan to retry requests so that CloudFormationknows that you're not attempting to continue the rollback to a stack with the same name. You might retry ContinueUpdateRollback
requests to ensure that CloudFormation successfully received them.
",
"CreateStackInput$ClientRequestToken": "A unique identifier for this CreateStack
request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to create a stack with the same name. You might retry CreateStack
requests to ensure that CloudFormation successfully received them.
All events triggered by a given stack operation are assigned the same client request token, which you can use to track operations. For example, if you execute a CreateStack
operation with the token token1
, then all the StackEvents
generated by that operation will have ClientRequestToken
set as token1
.
In the console, stack operations display the client request token on the Events tab. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you easily identify the stack operation . For example, if you create a stack using the console, each stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
",
- "CreateStackInstancesInput$OperationId": "The unique identifier for this stack set operation.
The operation ID also functions as an idempotency token, to ensure that CloudFormation performs the stack set operation only once, even if you retry the request multiple times. You might retry stack set operation requests to ensure that CloudFormation successfully received them.
If you don't specify an operation ID, the SDK generates one automatically.
Repeating this stack set operation with a new operation ID retries all stack instances whose status is OUTDATED
.
",
+ "CreateStackInstancesInput$OperationId": "The unique identifier for this stack set operation.
The operation ID also functions as an idempotency token, to ensure that CloudFormation performs the stack set operation only once, even if you retry the request multiple times. You might retry stack set operation requests to ensure that CloudFormation successfully received them.
If you don't specify an operation ID, the SDK generates one automatically.
Repeating this stack set operation with a new operation ID retries all stack instances whose status is OUTDATED
.
",
"CreateStackInstancesOutput$OperationId": "The unique identifier for this stack set operation.
",
- "CreateStackSetInput$ClientRequestToken": "A unique identifier for this CreateStackSet
request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to create another stack set with the same name. You might retry CreateStackSet
requests to ensure that CloudFormation successfully received them.
If you don't specify an operation ID, the SDK generates one automatically.
",
- "DeleteStackInput$ClientRequestToken": "A unique identifier for this DeleteStack
request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to delete a stack with the same name. You might retry DeleteStack
requests to ensure that CloudFormation successfully received them.
All events triggered by a given stack operation are assigned the same client request token, which you can use to track operations. For example, if you execute a CreateStack
operation with the token token1
, then all the StackEvents
generated by that operation will have ClientRequestToken
set as token1
.
In the console, stack operations display the client request token on the Events tab. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you easily identify the stack operation . For example, if you create a stack using the console, each stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
",
- "DeleteStackInstancesInput$OperationId": "The unique identifier for this stack set operation.
If you don't specify an operation ID, the SDK generates one automatically.
The operation ID also functions as an idempotency token, to ensure that CloudFormation performs the stack set operation only once, even if you retry the request multiple times. You can retry stack set operation requests to ensure that CloudFormation successfully received them.
Repeating this stack set operation with a new operation ID retries all stack instances whose status is OUTDATED
.
",
+ "CreateStackSetInput$ClientRequestToken": "A unique identifier for this CreateStackSet
request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to create another stack set with the same name. You might retry CreateStackSet
requests to ensure that CloudFormation successfully received them.
If you don't specify an operation ID, the SDK generates one automatically.
",
+ "DeleteStackInput$ClientRequestToken": "A unique identifier for this DeleteStack
request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to delete a stack with the same name. You might retry DeleteStack
requests to ensure that CloudFormation successfully received them.
All events triggered by a given stack operation are assigned the same client request token, which you can use to track operations. For example, if you execute a CreateStack
operation with the token token1
, then all the StackEvents
generated by that operation will have ClientRequestToken
set as token1
.
In the console, stack operations display the client request token on the Events tab. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you easily identify the stack operation . For example, if you create a stack using the console, each stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
",
+ "DeleteStackInstancesInput$OperationId": "The unique identifier for this stack set operation.
If you don't specify an operation ID, the SDK generates one automatically.
The operation ID also functions as an idempotency token, to ensure that CloudFormation performs the stack set operation only once, even if you retry the request multiple times. You can retry stack set operation requests to ensure that CloudFormation successfully received them.
Repeating this stack set operation with a new operation ID retries all stack instances whose status is OUTDATED
.
",
"DeleteStackInstancesOutput$OperationId": "The unique identifier for this stack set operation.
",
"DescribeStackSetOperationInput$OperationId": "The unique ID of the stack set operation.
",
"DetectStackSetDriftInput$OperationId": " The ID of the stack set operation.
",
@@ -410,11 +411,12 @@
"ImportStacksToStackSetOutput$OperationId": "The unique identifier for the stack set operation.
",
"ListStackSetOperationResultsInput$OperationId": "The ID of the stack set operation.
",
"RecordHandlerProgressInput$ClientRequestToken": "Reserved for use by the CloudFormation CLI.
",
+ "RollbackStackInput$ClientRequestToken": "A unique identifier for this RollbackStack
request.
",
"StackEvent$ClientRequestToken": "The token passed to the operation that generated this event.
All events triggered by a given stack operation are assigned the same client request token, which you can use to track operations. For example, if you execute a CreateStack
operation with the token token1
, then all the StackEvents
generated by that operation will have ClientRequestToken
set as token1
.
In the console, stack operations display the client request token on the Events tab. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you easily identify the stack operation . For example, if you create a stack using the console, each stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
",
"StackSetOperation$OperationId": "The unique ID of a stack set operation.
",
"StackSetOperationSummary$OperationId": "The unique ID of the stack set operation.
",
"StopStackSetOperationInput$OperationId": "The ID of the stack operation.
",
- "UpdateStackInput$ClientRequestToken": "A unique identifier for this UpdateStack
request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to update a stack with the same name. You might retry UpdateStack
requests to ensure that CloudFormation successfully received them.
All events triggered by a given stack operation are assigned the same client request token, which you can use to track operations. For example, if you execute a CreateStack
operation with the token token1
, then all the StackEvents
generated by that operation will have ClientRequestToken
set as token1
.
In the console, stack operations display the client request token on the Events tab. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you easily identify the stack operation . For example, if you create a stack using the console, each stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
",
+ "UpdateStackInput$ClientRequestToken": "A unique identifier for this UpdateStack
request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to update a stack with the same name. You might retry UpdateStack
requests to ensure that CloudFormation successfully received them.
All events triggered by a given stack operation are assigned the same client request token, which you can use to track operations. For example, if you execute a CreateStack
operation with the token token1
, then all the StackEvents
generated by that operation will have ClientRequestToken
set as token1
.
In the console, stack operations display the client request token on the Events tab. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you easily identify the stack operation . For example, if you create a stack using the console, each stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002
.
",
"UpdateStackInstancesInput$OperationId": "The unique identifier for this stack set operation.
The operation ID also functions as an idempotency token, to ensure that CloudFormation performs the stack set operation only once, even if you retry the request multiple times. You might retry stack set operation requests to ensure that CloudFormation successfully received them.
If you don't specify an operation ID, the SDK generates one automatically.
",
"UpdateStackInstancesOutput$OperationId": "The unique identifier for this stack set operation.
",
"UpdateStackSetInput$OperationId": "The unique ID for this stack set operation.
The operation ID also functions as an idempotency token, to ensure that CloudFormation performs the stack set operation only once, even if you retry the request multiple times. You might retry stack set operation requests to ensure that CloudFormation successfully received them.
If you don't specify an operation ID, CloudFormation generates one automatically.
Repeating this stack set operation with a new operation ID retries all stack instances whose status is OUTDATED
.
",
@@ -788,7 +790,9 @@
"base": null,
"refs": {
"CreateStackInput$DisableRollback": "Set to true
to disable rollback of the stack if stack creation failed. You can specify either DisableRollback
or OnFailure
, but not both.
Default: false
",
- "Stack$DisableRollback": "Boolean to enable or disable rollback on stack creation failures:
-
true
: disable rollback
-
false
: enable rollback
"
+ "ExecuteChangeSetInput$DisableRollback": "Preserves the state of previously provisioned resources when an operation fails.
Default: True
",
+ "Stack$DisableRollback": "Boolean to enable or disable rollback on stack creation failures:
-
true
: disable rollback
-
false
: enable rollback
",
+ "UpdateStackInput$DisableRollback": "Preserve the state of previously provisioned resources when an operation fails.
Default: False
"
}
},
"DriftedStackInstancesCount": {
@@ -800,7 +804,7 @@
"EnableTerminationProtection": {
"base": null,
"refs": {
- "CreateStackInput$EnableTerminationProtection": "Whether to enable termination protection on the specified stack. If a user attempts to delete a stack with termination protection enabled, the operation fails and the stack remains unchanged. For more information, see Protecting a Stack From Being Deleted in the CloudFormation User Guide. Termination protection is disabled on stacks by default.
For nested stacks, termination protection is set on the root stack and cannot be changed directly on the nested stack.
",
+ "CreateStackInput$EnableTerminationProtection": "Whether to enable termination protection on the specified stack. If a user attempts to delete a stack with termination protection enabled, the operation fails and the stack remains unchanged. For more information, see Protecting a Stack From Being Deleted in the CloudFormation User Guide. Termination protection is disabled on stacks by default.
For nested stacks, termination protection is set on the root stack and cannot be changed directly on the nested stack.
",
"Stack$EnableTerminationProtection": "Whether termination protection is enabled for the stack.
For nested stacks, termination protection is set on the root stack and cannot be changed directly on the nested stack. For more information, see Protecting a Stack From Being Deleted in the CloudFormation User Guide.
",
"UpdateTerminationProtectionInput$EnableTerminationProtection": "Whether to enable termination protection on the specified stack.
"
}
@@ -876,7 +880,7 @@
"base": null,
"refs": {
"Export$Name": "The name of exported output value. Use this name and the Fn::ImportValue
function to import the associated value into other stacks. The name is defined in the Export
field in the associated stack's Outputs
section.
",
- "ListImportsInput$ExportName": "The name of the exported output value. CloudFormation returns the stack names that are importing this value.
",
+ "ListImportsInput$ExportName": "The name of the exported output value. CloudFormation returns the stack names that are importing this value.
",
"Output$ExportName": "The name of the export associated with the output.
"
}
},
@@ -966,7 +970,7 @@
"Imports": {
"base": null,
"refs": {
- "ListImportsOutput$Imports": "A list of stack names that are importing the specified exported output value.
"
+ "ListImportsOutput$Imports": "A list of stack names that are importing the specified exported output value.
"
}
},
"InProgressStackInstancesCount": {
@@ -1299,7 +1303,7 @@
"ListChangeSetsOutput$NextToken": "If the output exceeds 1 MB, a string that identifies the next page of change sets. If there is no additional page, this value is null.
",
"ListExportsInput$NextToken": "A string (provided by the ListExports response output) that identifies the next page of exported output values that you asked to retrieve.
",
"ListExportsOutput$NextToken": "If the output exceeds 100 exported output values, a string that identifies the next page of exports. If there is no additional page, this value is null.
",
- "ListImportsInput$NextToken": "A string (provided by the ListImports response output) that identifies the next page of stacks that are importing the specified exported output value.
",
+ "ListImportsInput$NextToken": "A string (provided by the ListImports response output) that identifies the next page of stacks that are importing the specified exported output value.
",
"ListImportsOutput$NextToken": "A string that identifies the next page of exports. If there is no additional page, this value is null.
",
"ListStackInstancesInput$NextToken": "If the previous request didn't return all of the remaining results, the response's NextToken
parameter value is set to a token. To retrieve the next set of results, call ListStackInstances
again and assign that token to the request object's NextToken
parameter. If there are no remaining results, the previous response object's NextToken
parameter is set to null
.
",
"ListStackInstancesOutput$NextToken": "If the request doesn't return all of the remaining results, NextToken
is set to a token. To retrieve the next set of results, call ListStackInstances
again and assign that token to the request object's NextToken
parameter. If the request returns all results, NextToken
is set to null
.
",
@@ -1324,7 +1328,7 @@
"NoEcho": {
"base": null,
"refs": {
- "ParameterDeclaration$NoEcho": "Flag that indicates whether the parameter value is shown as plain text in logs and in the Management Console.
",
+ "ParameterDeclaration$NoEcho": "Flag that indicates whether the parameter value is shown as plain text in logs and in the Amazon Web Services Management Console.
",
"TemplateParameter$NoEcho": "Flag indicating whether the parameter should be displayed as plain text in logs and UIs.
"
}
},
@@ -1477,7 +1481,7 @@
"CreateChangeSetInput$Parameters": "A list of Parameter
structures that specify input parameters for the change set. For more information, see the Parameter data type.
",
"CreateStackInput$Parameters": "A list of Parameter
structures that specify input parameters for the stack. For more information, see the Parameter data type.
",
"CreateStackInstancesInput$ParameterOverrides": "A list of stack set parameters whose values you want to override in the selected stack instances.
Any overridden parameter values will be applied to all stack instances in the specified accounts and Regions. When specifying parameters and their values, be aware of how CloudFormation sets parameter values during stack instance operations:
-
To override the current value for a parameter, include the parameter and specify its value.
-
To leave an overridden parameter set to its present value, include the parameter and specify UsePreviousValue
as true
. (You cannot specify both a value and set UsePreviousValue
to true
.)
-
To set an overridden parameter back to the value specified in the stack set, specify a parameter list but do not include the parameter in the list.
-
To leave all parameters set to their present values, do not specify this property at all.
During stack set updates, any parameter values overridden for a stack instance are not updated, but retain their overridden value.
You can only override the parameter values that are specified in the stack set; to add or delete a parameter itself, use UpdateStackSet to update the stack set template.
",
- "CreateStackSetInput$Parameters": "The input parameters for the stack set template.
",
+ "CreateStackSetInput$Parameters": "The input parameters for the stack set template.
",
"DescribeChangeSetOutput$Parameters": "A list of Parameter
structures that describes the input parameters and their values used to create the change set. For more information, see the Parameter data type.
",
"EstimateTemplateCostInput$Parameters": "A list of Parameter
structures that specify input parameters.
",
"Stack$Parameters": "A list of Parameter
structures.
",
@@ -1655,9 +1659,9 @@
"DescribeStackInstanceInput$StackInstanceRegion": "The name of a Region that's associated with this stack instance.
",
"ListStackInstancesInput$StackInstanceRegion": "The name of the Region where you want to list stack instances.
",
"RegionList$member": null,
- "StackInstance$Region": "The name of the Region that the stack instance is associated with.
",
- "StackInstanceSummary$Region": "The name of the Region that the stack instance is associated with.
",
- "StackSetOperationResultSummary$Region": "The name of the Region for this operation result.
"
+ "StackInstance$Region": "The name of the Amazon Web Services Region that the stack instance is associated with.
",
+ "StackInstanceSummary$Region": "The name of the Amazon Web Services Region that the stack instance is associated with.
",
+ "StackSetOperationResultSummary$Region": "The name of the Amazon Web Services Region for this operation result.
"
}
},
"RegionConcurrencyType": {
@@ -1669,8 +1673,8 @@
"RegionList": {
"base": null,
"refs": {
- "CreateStackInstancesInput$Regions": "The names of one or more Regions where you want to create stack instances using the specified accounts.
",
- "DeleteStackInstancesInput$Regions": "The Regions where you want to delete stack set instances.
",
+ "CreateStackInstancesInput$Regions": "The names of one or more Regions where you want to create stack instances using the specified Amazon Web Services accounts.
",
+ "DeleteStackInstancesInput$Regions": "The Regions where you want to delete stack set instances.
",
"StackSetOperationPreferences$RegionOrder": "The order of the Regions in where you want to perform the stack operation.
",
"UpdateStackInstancesInput$Regions": "The names of one or more Regions in which you want to update parameter values for stack instances. The overridden parameter values will be applied to all stack instances in the specified accounts and Regions.
",
"UpdateStackSetInput$Regions": "The Regions in which to update associated stack instances. If you specify Regions, you must also specify accounts in which to update stack set instances.
To update all the stack instances associated with this stack set, do not specify the Accounts
or Regions
properties.
If the stack set update includes changes to the template (that is, if the TemplateBody
or TemplateURL
properties are specified), or the Parameters
property, CloudFormation marks all stack instances with a status of OUTDATED
prior to updating the stack instances in the specified accounts and Regions. If the stack set update does not include changes to the template or parameters, CloudFormation updates the stack instances in the specified accounts and Regions, while leaving all other stack instances with their existing stack instance status.
"
@@ -1809,7 +1813,7 @@
"ResourceIdentifierSummaries": {
"base": null,
"refs": {
- "GetTemplateSummaryOutput$ResourceIdentifierSummaries": "A list of resource identifier summaries that describe the target resources of an import operation and the properties you can provide during the import to identify the target resources. For example, BucketName
is a possible identifier property for an AWS::S3::Bucket
resource.
"
+ "GetTemplateSummaryOutput$ResourceIdentifierSummaries": "A list of resource identifier summaries that describe the target resources of an import operation and the properties you can provide during the import to identify the target resources. For example, BucketName
is a possible identifier property for an AWS::S3::Bucket
resource.
"
}
},
"ResourceIdentifierSummary": {
@@ -1916,7 +1920,7 @@
"ResourcesToSkip": {
"base": null,
"refs": {
- "ContinueUpdateRollbackInput$ResourcesToSkip": "A list of the logical IDs of the resources that CloudFormation skips during the continue update rollback operation. You can specify only resources that are in the UPDATE_FAILED
state because a rollback failed. You can't specify resources that are in the UPDATE_FAILED
state for other reasons, for example, because an update was cancelled. To check why a resource update failed, use the DescribeStackResources action, and view the resource status reason.
Specify this property to skip rolling back resources that CloudFormation can't successfully roll back. We recommend that you troubleshoot resources before skipping them. CloudFormation sets the status of the specified resources to UPDATE_COMPLETE
and continues to roll back the stack. After the rollback is complete, the state of the skipped resources will be inconsistent with the state of the resources in the stack template. Before performing another stack update, you must update the stack or resources to be consistent with each other. If you don't, subsequent stack updates might fail, and the stack will become unrecoverable.
Specify the minimum number of resources required to successfully roll back your stack. For example, a failed resource update might cause dependent resources to fail. In this case, it might not be necessary to skip the dependent resources.
To skip resources that are part of nested stacks, use the following format: NestedStackName.ResourceLogicalID
. If you want to specify the logical ID of a stack resource (Type: AWS::CloudFormation::Stack
) in the ResourcesToSkip
list, then its corresponding embedded stack must be in one of the following states: DELETE_IN_PROGRESS
, DELETE_COMPLETE
, or DELETE_FAILED
.
Don't confuse a child stack's name with its corresponding logical ID defined in the parent stack. For an example of a continue update rollback operation with nested stacks, see Using ResourcesToSkip to recover a nested stacks hierarchy.
"
+ "ContinueUpdateRollbackInput$ResourcesToSkip": "A list of the logical IDs of the resources that CloudFormation skips during the continue update rollback operation. You can specify only resources that are in the UPDATE_FAILED
state because a rollback failed. You can't specify resources that are in the UPDATE_FAILED
state for other reasons, for example, because an update was cancelled. To check why a resource update failed, use the DescribeStackResources action, and view the resource status reason.
Specify this property to skip rolling back resources that CloudFormation can't successfully roll back. We recommend that you troubleshoot resources before skipping them. CloudFormation sets the status of the specified resources to UPDATE_COMPLETE
and continues to roll back the stack. After the rollback is complete, the state of the skipped resources will be inconsistent with the state of the resources in the stack template. Before performing another stack update, you must update the stack or resources to be consistent with each other. If you don't, subsequent stack updates might fail, and the stack will become unrecoverable.
Specify the minimum number of resources required to successfully roll back your stack. For example, a failed resource update might cause dependent resources to fail. In this case, it might not be necessary to skip the dependent resources.
To skip resources that are part of nested stacks, use the following format: NestedStackName.ResourceLogicalID
. If you want to specify the logical ID of a stack resource (Type: AWS::CloudFormation::Stack
) in the ResourcesToSkip
list, then its corresponding embedded stack must be in one of the following states: DELETE_IN_PROGRESS
, DELETE_COMPLETE
, or DELETE_FAILED
.
Don't confuse a child stack's name with its corresponding logical ID defined in the parent stack. For an example of a continue update rollback operation with nested stacks, see Using ResourcesToSkip to recover a nested stacks hierarchy.
"
}
},
"RetainResources": {
@@ -1951,6 +1955,7 @@
"CreateStackInput$RoleARN": "The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) role that CloudFormation assumes to create the stack. CloudFormation uses the role's credentials to make calls on your behalf. CloudFormation always uses this role for all future operations on the stack. As long as users have permission to operate on the stack, CloudFormation uses this role even if the users don't have permission to pass it. Ensure that the role grants least privilege.
If you don't specify a value, CloudFormation uses the role that was previously associated with the stack. If no role is available, CloudFormation uses a temporary session that is generated from your user credentials.
",
"CreateStackSetInput$AdministrationRoleARN": "The Amazon Resource Number (ARN) of the IAM role to use to create this stack set.
Specify an IAM role only if you are using customized administrator roles to control which users or groups can manage specific stack sets within the same administrator account. For more information, see Prerequisites: Granting Permissions for Stack Set Operations in the CloudFormation User Guide.
",
"DeleteStackInput$RoleARN": "The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) role that CloudFormation assumes to delete the stack. CloudFormation uses the role's credentials to make calls on your behalf.
If you don't specify a value, CloudFormation uses the role that was previously associated with the stack. If no role is available, CloudFormation uses a temporary session that is generated from your user credentials.
",
+ "RollbackStackInput$RoleARN": "The Amazon Resource Name (ARN) of an Identity and Access Management role that CloudFormation assumes to rollback the stack.
",
"Stack$RoleARN": "The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) role that is associated with the stack. During a stack operation, CloudFormation uses this role's credentials to make calls on your behalf.
",
"StackSet$AdministrationRoleARN": "The Amazon Resource Number (ARN) of the IAM role used to create or update the stack set.
Use customized administrator roles to control which users or groups can manage specific stack sets within the same administrator account. For more information, see Prerequisites: Granting Permissions for Stack Set Operations in the CloudFormation User Guide.
",
"StackSetOperation$AdministrationRoleARN": "The Amazon Resource Number (ARN) of the IAM role used to perform this stack set operation.
Use customized administrator roles to control which users or groups can manage specific stack sets within the same administrator account. For more information, see Define Permissions for Multiple Administrators in the CloudFormation User Guide.
",
@@ -1977,6 +1982,16 @@
"UpdateStackInput$RollbackConfiguration": "The rollback triggers for CloudFormation to monitor during stack creation and updating operations, and for the specified monitoring period afterwards.
"
}
},
+ "RollbackStackInput": {
+ "base": null,
+ "refs": {
+ }
+ },
+ "RollbackStackOutput": {
+ "base": null,
+ "refs": {
+ }
+ },
"RollbackTrigger": {
"base": "A rollback trigger CloudFormation monitors during creation and updating of stacks. If any of the alarms you specify goes to ALARM state during the stack operation or within the specified monitoring period afterwards, CloudFormation rolls back the entire stack operation.
",
"refs": {
@@ -2046,9 +2061,9 @@
"StackDriftDetectionId": {
"base": null,
"refs": {
- "DescribeStackDriftDetectionStatusInput$StackDriftDetectionId": "The ID of the drift detection results of this operation.
CloudFormation generates new results, with a new drift detection ID, each time this operation is run. However, the number of drift results CloudFormation retains for any given stack, and for how long, may vary.
",
- "DescribeStackDriftDetectionStatusOutput$StackDriftDetectionId": "The ID of the drift detection results of this operation.
CloudFormation generates new results, with a new drift detection ID, each time this operation is run. However, the number of reports CloudFormation retains for any given stack, and for how long, may vary.
",
- "DetectStackDriftOutput$StackDriftDetectionId": "The ID of the drift detection results of this operation.
CloudFormation generates new results, with a new drift detection ID, each time this operation is run. However, the number of drift results CloudFormation retains for any given stack, and for how long, may vary.
"
+ "DescribeStackDriftDetectionStatusInput$StackDriftDetectionId": "The ID of the drift detection results of this operation.
CloudFormation generates new results, with a new drift detection ID, each time this operation is run. However, the number of drift results CloudFormation retains for any given stack, and for how long, may vary.
",
+ "DescribeStackDriftDetectionStatusOutput$StackDriftDetectionId": "The ID of the drift detection results of this operation.
CloudFormation generates new results, with a new drift detection ID, each time this operation is run. However, the number of reports CloudFormation retains for any given stack, and for how long, may vary.
",
+ "DetectStackDriftOutput$StackDriftDetectionId": "The ID of the drift detection results of this operation.
CloudFormation generates new results, with a new drift detection ID, each time this operation is run. However, the number of drift results CloudFormation retains for any given stack, and for how long, may vary.
"
}
},
"StackDriftDetectionStatus": {
@@ -2078,7 +2093,7 @@
"StackDriftStatus": {
"base": null,
"refs": {
- "DescribeStackDriftDetectionStatusOutput$StackDriftStatus": "Status of the stack's actual configuration compared to its expected configuration.
-
DRIFTED
: The stack differs from its expected template configuration. A stack is considered to have drifted if one or more of its resources have drifted.
-
NOT_CHECKED
: CloudFormation has not checked if the stack differs from its expected template configuration.
-
IN_SYNC
: The stack's actual configuration matches its expected template configuration.
-
UNKNOWN
: This value is reserved for future use.
",
+ "DescribeStackDriftDetectionStatusOutput$StackDriftStatus": "Status of the stack's actual configuration compared to its expected configuration.
-
DRIFTED
: The stack differs from its expected template configuration. A stack is considered to have drifted if one or more of its resources have drifted.
-
NOT_CHECKED
: CloudFormation has not checked if the stack differs from its expected template configuration.
-
IN_SYNC
: The stack's actual configuration matches its expected template configuration.
-
UNKNOWN
: This value is reserved for future use.
",
"StackDriftInformation$StackDriftStatus": "Status of the stack's actual configuration compared to its expected template configuration.
-
DRIFTED
: The stack differs from its expected template configuration. A stack is considered to have drifted if one or more of its resources have drifted.
-
NOT_CHECKED
: CloudFormation has not checked if the stack differs from its expected template configuration.
-
IN_SYNC
: The stack's actual configuration matches its expected template configuration.
-
UNKNOWN
: This value is reserved for future use.
",
"StackDriftInformationSummary$StackDriftStatus": "Status of the stack's actual configuration compared to its expected template configuration.
-
DRIFTED
: The stack differs from its expected template configuration. A stack is considered to have drifted if one or more of its resources have drifted.
-
NOT_CHECKED
: CloudFormation has not checked if the stack differs from its expected template configuration.
-
IN_SYNC
: The stack's actual configuration matches its expected template configuration.
-
UNKNOWN
: This value is reserved for future use.
",
"StackInstance$DriftStatus": "Status of the stack instance's actual configuration compared to the expected template and parameter configuration of the stack set to which it belongs.
-
DRIFTED
: The stack differs from the expected template and parameter configuration of the stack set to which it belongs. A stack instance is considered to have drifted if one or more of the resources in the associated stack have drifted.
-
NOT_CHECKED
: CloudFormation has not checked if the stack instance differs from its expected stack set configuration.
-
IN_SYNC
: The stack instance's actual configuration matches its expected stack set configuration.
-
UNKNOWN
: This value is reserved for future use.
",
@@ -2108,6 +2123,7 @@
"DescribeChangeSetOutput$StackId": "The ARN of the stack that is associated with the change set.
",
"DescribeStackDriftDetectionStatusOutput$StackId": "The ID of the stack.
",
"Export$ExportingStackId": "The stack that contains the exported output name and value.
",
+ "RollbackStackOutput$StackId": "Unique identifier of the stack.
",
"Stack$StackId": "Unique identifier of the stack.
",
"Stack$ParentId": "For nested stacks--stacks created as resources for another stack--the stack ID of the direct parent of this stack. For the first level of nested stacks, the root stack is also the parent stack.
For more information, see Working with Nested Stacks in the CloudFormation User Guide.
",
"Stack$RootId": "For nested stacks--stacks created as resources for another stack--the stack ID of the top-level stack to which the nested stack ultimately belongs.
For more information, see Working with Nested Stacks in the CloudFormation User Guide.
",
@@ -2203,7 +2219,7 @@
"refs": {
"CancelUpdateStackInput$StackName": "The name or the unique stack ID that is associated with the stack.
",
"ChangeSetSummary$StackName": "The name of the stack with which the change set is associated.
",
- "CreateStackInput$StackName": "The name that is associated with the stack. The name must be unique in the Region in which you are creating the stack.
A stack name can contain only alphanumeric characters (case sensitive) and hyphens. It must start with an alphabetic character and cannot be longer than 128 characters.
",
+ "CreateStackInput$StackName": "The name that is associated with the stack. The name must be unique in the Region in which you are creating the stack.
A stack name can contain only alphanumeric characters (case sensitive) and hyphens. It must start with an alphabetical character and cannot be longer than 128 characters.
",
"DeleteStackInput$StackName": "The name or the unique stack ID that is associated with the stack.
",
"DescribeChangeSetOutput$StackName": "The name of the stack that is associated with the change set.
",
"DescribeStackEventsInput$StackName": "The name or the unique stack ID that is associated with the stack, which are not always interchangeable:
Default: There is no default value.
",
@@ -2231,11 +2247,12 @@
"DeleteChangeSetInput$StackName": "If you specified the name of a change set to delete, specify the stack name or ID (ARN) that is associated with it.
",
"DescribeChangeSetInput$StackName": "If you specified the name of a change set, specify the stack name or ID (ARN) of the change set you want to describe.
",
"DescribeStackResourceDriftsInput$StackName": "The name of the stack for which you want drift information.
",
- "DetectStackDriftInput$StackName": "The name of the stack for which you want to detect drift.
",
+ "DetectStackDriftInput$StackName": "The name of the stack for which you want to detect drift.
",
"DetectStackResourceDriftInput$StackName": "The name of the stack to which the resource belongs.
",
"ExecuteChangeSetInput$StackName": "If you specified the name of a change set, specify the stack name or ID (ARN) that is associated with the change set you want to execute.
",
"GetTemplateSummaryInput$StackName": "The name or the stack ID that is associated with the stack, which are not always interchangeable. For running stacks, you can specify either the stack's name or its unique stack ID. For deleted stack, you must specify the unique stack ID.
Conditional: You must specify only one of the following parameters: StackName
, StackSetName
, TemplateBody
, or TemplateURL
.
",
"ListChangeSetsInput$StackName": "The name or the Amazon Resource Name (ARN) of the stack for which you want to list change sets.
",
+ "RollbackStackInput$StackName": "The name that is associated with the stack.
",
"SignalResourceInput$StackName": "The stack name or unique stack ID that includes the resource that you want to signal.
",
"UpdateTerminationProtectionInput$StackName": "The name or unique ID of the stack for which you want to set termination protection.
"
}
@@ -2346,7 +2363,7 @@
}
},
"StackSet": {
- "base": "A structure that contains information about a stack set. A stack set enables you to provision stacks into accounts and across Regions by using a single CloudFormation template. In the stack set, you specify the template to use, as well as any parameters and capabilities that the template requires.
",
+ "base": "A structure that contains information about a stack set. A stack set enables you to provision stacks into Amazon Web Services accounts and across Regions by using a single CloudFormation template. In the stack set, you specify the template to use, as well as any parameters and capabilities that the template requires.
",
"refs": {
"DescribeStackSetOutput$StackSet": "The specified stack set.
"
}
@@ -2652,7 +2669,7 @@
"TemplateStage": {
"base": null,
"refs": {
- "GetTemplateInput$TemplateStage": "For templates that include transforms, the stage of the template that CloudFormation returns. To get the user-submitted template, specify Original
. To get the template after CloudFormation has processed all transforms, specify Processed
.
If the template doesn't include transforms, Original
and Processed
return the same template. By default, CloudFormation specifies Processed
.
",
+ "GetTemplateInput$TemplateStage": "For templates that include transforms, the stage of the template that CloudFormation returns. To get the user-submitted template, specify Original
. To get the template after CloudFormation has processed all transforms, specify Processed
.
If the template doesn't include transforms, Original
and Processed
return the same template. By default, CloudFormation specifies Processed
.
",
"StageList$member": null
}
},
diff --git a/models/apis/codebuild/2016-10-06/docs-2.json b/models/apis/codebuild/2016-10-06/docs-2.json
index 3d9d4c24be1..d28ac764a3d 100644
--- a/models/apis/codebuild/2016-10-06/docs-2.json
+++ b/models/apis/codebuild/2016-10-06/docs-2.json
@@ -277,7 +277,7 @@
"BuildPhaseType": {
"base": null,
"refs": {
- "BuildPhase$phaseType": "The name of the build phase. Valid values include:
-
BUILD
: Core build activities typically occur in this build phase.
-
COMPLETED
: The build has been completed.
-
DOWNLOAD_SOURCE
: Source code is being downloaded in this build phase.
-
FINALIZING
: The build process is completing in this build phase.
-
INSTALL
: Installation activities typically occur in this build phase.
-
POST_BUILD
: Post-build activities typically occur in this build phase.
-
PRE_BUILD
: Pre-build activities typically occur in this build phase.
-
PROVISIONING
: The build environment is being set up.
-
QUEUED
: The build has been submitted and is queued behind other submitted builds.
-
SUBMITTED
: The build has been submitted.
-
UPLOAD_ARTIFACTS
: Build output artifacts are being uploaded to the output location.
"
+ "BuildPhase$phaseType": "The name of the build phase. Valid values include:
- BUILD
-
Core build activities typically occur in this build phase.
- COMPLETED
-
The build has been completed.
- DOWNLOAD_SOURCE
-
Source code is being downloaded in this build phase.
- FINALIZING
-
The build process is completing in this build phase.
- INSTALL
-
Installation activities typically occur in this build phase.
- POST_BUILD
-
Post-build activities typically occur in this build phase.
- PRE_BUILD
-
Pre-build activities typically occur in this build phase.
- PROVISIONING
-
The build environment is being set up.
- QUEUED
-
The build has been submitted and is queued behind other submitted builds.
- SUBMITTED
-
The build has been submitted.
- UPLOAD_ARTIFACTS
-
Build output artifacts are being uploaded to the output location.
"
}
},
"BuildPhases": {
@@ -1516,8 +1516,8 @@
"Build$buildStatus": "The current status of the build. Valid values include:
-
FAILED
: The build failed.
-
FAULT
: The build faulted.
-
IN_PROGRESS
: The build is still in progress.
-
STOPPED
: The build stopped.
-
SUCCEEDED
: The build succeeded.
-
TIMED_OUT
: The build timed out.
",
"BuildBatch$buildBatchStatus": "The status of the batch build.
",
"BuildBatchFilter$status": "The status of the batch builds to retrieve. Only batch builds that have this status will be retrieved.
",
- "BuildBatchPhase$phaseStatus": "The current status of the batch build phase. Valid values include:
- FAILED
-
The build phase failed.
- FAULT
-
The build phase faulted.
- IN_PROGRESS
-
The build phase is still in progress.
- QUEUED
-
The build has been submitted and is queued behind other submitted builds.
- STOPPED
-
The build phase stopped.
- SUCCEEDED
-
The build phase succeeded.
- TIMED_OUT
-
The build phase timed out.
",
- "BuildPhase$phaseStatus": "The current status of the build phase. Valid values include:
- FAILED
-
The build phase failed.
- FAULT
-
The build phase faulted.
- IN_PROGRESS
-
The build phase is still in progress.
- QUEUED
-
The build has been submitted and is queued behind other submitted builds.
- STOPPED
-
The build phase stopped.
- SUCCEEDED
-
The build phase succeeded.
- TIMED_OUT
-
The build phase timed out.
",
+ "BuildBatchPhase$phaseStatus": "The current status of the batch build phase. Valid values include:
- FAILED
-
The build phase failed.
- FAULT
-
The build phase faulted.
- IN_PROGRESS
-
The build phase is still in progress.
- STOPPED
-
The build phase stopped.
- SUCCEEDED
-
The build phase succeeded.
- TIMED_OUT
-
The build phase timed out.
",
+ "BuildPhase$phaseStatus": "The current status of the build phase. Valid values include:
- FAILED
-
The build phase failed.
- FAULT
-
The build phase faulted.
- IN_PROGRESS
-
The build phase is still in progress.
- STOPPED
-
The build phase stopped.
- SUCCEEDED
-
The build phase succeeded.
- TIMED_OUT
-
The build phase timed out.
",
"BuildSummary$buildStatus": "The status of the build group.
- FAILED
-
The build group failed.
- FAULT
-
The build group faulted.
- IN_PROGRESS
-
The build group is still in progress.
- STOPPED
-
The build group stopped.
- SUCCEEDED
-
The build group succeeded.
- TIMED_OUT
-
The build group timed out.
"
}
},
diff --git a/models/apis/firehose/2015-08-04/api-2.json b/models/apis/firehose/2015-08-04/api-2.json
index bd0cd6d4709..582c9189798 100644
--- a/models/apis/firehose/2015-08-04/api-2.json
+++ b/models/apis/firehose/2015-08-04/api-2.json
@@ -220,7 +220,7 @@
"type":"string",
"max":512,
"min":1,
- "pattern":"jdbc:(redshift|postgresql)://((?!-)[A-Za-z0-9-]{1,63}(?Describes the specified delivery stream and its status. For example, after your delivery stream is created, call DescribeDeliveryStream
to see whether the delivery stream is ACTIVE
and therefore ready for data to be sent to it. If the status of a delivery stream is CREATING_FAILED
, this status doesn't change, and you can't invoke CreateDeliveryStream again on it. However, you can invoke the DeleteDeliveryStream operation to delete it. If the status is DELETING_FAILED
, you can force deletion by invoking DeleteDeliveryStream again but with DeleteDeliveryStreamInput$AllowForceDelete set to true.
",
"ListDeliveryStreams": "Lists your delivery streams in alphabetical order of their names.
The number of delivery streams might be too large to return using a single call to ListDeliveryStreams
. You can limit the number of delivery streams returned, using the Limit
parameter. To determine whether there are more delivery streams to list, check the value of HasMoreDeliveryStreams
in the output. If there are more delivery streams to list, you can request them by calling this operation again and setting the ExclusiveStartDeliveryStreamName
parameter to the name of the last delivery stream returned in the last call.
",
"ListTagsForDeliveryStream": "Lists the tags for the specified delivery stream. This operation has a limit of five transactions per second per account.
",
- "PutRecord": "Writes a single data record into an Amazon Kinesis Data Firehose delivery stream. To write multiple data records into a delivery stream, use PutRecordBatch. Applications using these operations are referred to as producers.
By default, each delivery stream can take in up to 2,000 transactions per second, 5,000 records per second, or 5 MB per second. If you use PutRecord and PutRecordBatch, the limits are an aggregate across these two operations for each delivery stream. For more information about limits and how to request an increase, see Amazon Kinesis Data Firehose Limits.
You must specify the name of the delivery stream and the data record when using PutRecord. The data record consists of a data blob that can be up to 1,000 KB in size, and any kind of data. For example, it can be a segment from a log file, geographic location data, website clickstream data, and so on.
Kinesis Data Firehose buffers records before delivering them to the destination. To disambiguate the data blobs at the destination, a common solution is to use delimiters in the data, such as a newline (\\n
) or some other character unique within the data. This allows the consumer application to parse individual data items when reading the data from the destination.
The PutRecord
operation returns a RecordId
, which is a unique string assigned to each record. Producer applications can use this ID for purposes such as auditability and investigation.
If the PutRecord
operation throws a ServiceUnavailableException
, back off and retry. If the exception persists, it is possible that the throughput limits have been exceeded for the delivery stream.
Data records sent to Kinesis Data Firehose are stored for 24 hours from the time they are added to a delivery stream as it tries to send the records to the destination. If the destination is unreachable for more than 24 hours, the data is no longer available.
Don't concatenate two or more base64 strings to form the data fields of your records. Instead, concatenate the raw data, then perform base64 encoding.
",
- "PutRecordBatch": "Writes multiple data records into a delivery stream in a single call, which can achieve higher throughput per producer than when writing single records. To write single data records into a delivery stream, use PutRecord. Applications using these operations are referred to as producers.
For information about service quota, see Amazon Kinesis Data Firehose Quota.
Each PutRecordBatch request supports up to 500 records. Each record in the request can be as large as 1,000 KB (before 64-bit encoding), up to a limit of 4 MB for the entire request. These limits cannot be changed.
You must specify the name of the delivery stream and the data record when using PutRecord. The data record consists of a data blob that can be up to 1,000 KB in size, and any kind of data. For example, it could be a segment from a log file, geographic location data, website clickstream data, and so on.
Kinesis Data Firehose buffers records before delivering them to the destination. To disambiguate the data blobs at the destination, a common solution is to use delimiters in the data, such as a newline (\\n
) or some other character unique within the data. This allows the consumer application to parse individual data items when reading the data from the destination.
The PutRecordBatch response includes a count of failed records, FailedPutCount
, and an array of responses, RequestResponses
. Even if the PutRecordBatch call succeeds, the value of FailedPutCount
may be greater than 0, indicating that there are records for which the operation didn't succeed. Each entry in the RequestResponses
array provides additional information about the processed record. It directly correlates with a record in the request array using the same ordering, from the top to the bottom. The response array always includes the same number of records as the request array. RequestResponses
includes both successfully and unsuccessfully processed records. Kinesis Data Firehose tries to process all records in each PutRecordBatch request. A single record failure does not stop the processing of subsequent records.
A successfully processed record includes a RecordId
value, which is unique for the record. An unsuccessfully processed record includes ErrorCode
and ErrorMessage
values. ErrorCode
reflects the type of error, and is one of the following values: ServiceUnavailableException
or InternalFailure
. ErrorMessage
provides more detailed information about the error.
If there is an internal server error or a timeout, the write might have completed or it might have failed. If FailedPutCount
is greater than 0, retry the request, resending only those records that might have failed processing. This minimizes the possible duplicate records and also reduces the total bytes sent (and corresponding charges). We recommend that you handle any duplicates at the destination.
If PutRecordBatch throws ServiceUnavailableException
, back off and retry. If the exception persists, it is possible that the throughput limits have been exceeded for the delivery stream.
Data records sent to Kinesis Data Firehose are stored for 24 hours from the time they are added to a delivery stream as it attempts to send the records to the destination. If the destination is unreachable for more than 24 hours, the data is no longer available.
Don't concatenate two or more base64 strings to form the data fields of your records. Instead, concatenate the raw data, then perform base64 encoding.
",
+ "PutRecord": "Writes a single data record into an Amazon Kinesis Data Firehose delivery stream. To write multiple data records into a delivery stream, use PutRecordBatch. Applications using these operations are referred to as producers.
By default, each delivery stream can take in up to 2,000 transactions per second, 5,000 records per second, or 5 MB per second. If you use PutRecord and PutRecordBatch, the limits are an aggregate across these two operations for each delivery stream. For more information about limits and how to request an increase, see Amazon Kinesis Data Firehose Limits.
You must specify the name of the delivery stream and the data record when using PutRecord. The data record consists of a data blob that can be up to 1,000 KiB in size, and any kind of data. For example, it can be a segment from a log file, geographic location data, website clickstream data, and so on.
Kinesis Data Firehose buffers records before delivering them to the destination. To disambiguate the data blobs at the destination, a common solution is to use delimiters in the data, such as a newline (\\n
) or some other character unique within the data. This allows the consumer application to parse individual data items when reading the data from the destination.
The PutRecord
operation returns a RecordId
, which is a unique string assigned to each record. Producer applications can use this ID for purposes such as auditability and investigation.
If the PutRecord
operation throws a ServiceUnavailableException
, back off and retry. If the exception persists, it is possible that the throughput limits have been exceeded for the delivery stream.
Data records sent to Kinesis Data Firehose are stored for 24 hours from the time they are added to a delivery stream as it tries to send the records to the destination. If the destination is unreachable for more than 24 hours, the data is no longer available.
Don't concatenate two or more base64 strings to form the data fields of your records. Instead, concatenate the raw data, then perform base64 encoding.
",
+ "PutRecordBatch": "Writes multiple data records into a delivery stream in a single call, which can achieve higher throughput per producer than when writing single records. To write single data records into a delivery stream, use PutRecord. Applications using these operations are referred to as producers.
For information about service quota, see Amazon Kinesis Data Firehose Quota.
Each PutRecordBatch request supports up to 500 records. Each record in the request can be as large as 1,000 KB (before base64 encoding), up to a limit of 4 MB for the entire request. These limits cannot be changed.
You must specify the name of the delivery stream and the data record when using PutRecord. The data record consists of a data blob that can be up to 1,000 KB in size, and any kind of data. For example, it could be a segment from a log file, geographic location data, website clickstream data, and so on.
Kinesis Data Firehose buffers records before delivering them to the destination. To disambiguate the data blobs at the destination, a common solution is to use delimiters in the data, such as a newline (\\n
) or some other character unique within the data. This allows the consumer application to parse individual data items when reading the data from the destination.
The PutRecordBatch response includes a count of failed records, FailedPutCount
, and an array of responses, RequestResponses
. Even if the PutRecordBatch call succeeds, the value of FailedPutCount
may be greater than 0, indicating that there are records for which the operation didn't succeed. Each entry in the RequestResponses
array provides additional information about the processed record. It directly correlates with a record in the request array using the same ordering, from the top to the bottom. The response array always includes the same number of records as the request array. RequestResponses
includes both successfully and unsuccessfully processed records. Kinesis Data Firehose tries to process all records in each PutRecordBatch request. A single record failure does not stop the processing of subsequent records.
A successfully processed record includes a RecordId
value, which is unique for the record. An unsuccessfully processed record includes ErrorCode
and ErrorMessage
values. ErrorCode
reflects the type of error, and is one of the following values: ServiceUnavailableException
or InternalFailure
. ErrorMessage
provides more detailed information about the error.
If there is an internal server error or a timeout, the write might have completed or it might have failed. If FailedPutCount
is greater than 0, retry the request, resending only those records that might have failed processing. This minimizes the possible duplicate records and also reduces the total bytes sent (and corresponding charges). We recommend that you handle any duplicates at the destination.
If PutRecordBatch throws ServiceUnavailableException
, back off and retry. If the exception persists, it is possible that the throughput limits have been exceeded for the delivery stream.
Data records sent to Kinesis Data Firehose are stored for 24 hours from the time they are added to a delivery stream as it attempts to send the records to the destination. If the destination is unreachable for more than 24 hours, the data is no longer available.
Don't concatenate two or more base64 strings to form the data fields of your records. Instead, concatenate the raw data, then perform base64 encoding.
",
"StartDeliveryStreamEncryption": "Enables server-side encryption (SSE) for the delivery stream.
This operation is asynchronous. It returns immediately. When you invoke it, Kinesis Data Firehose first sets the encryption status of the stream to ENABLING
, and then to ENABLED
. The encryption status of a delivery stream is the Status
property in DeliveryStreamEncryptionConfiguration. If the operation fails, the encryption status changes to ENABLING_FAILED
. You can continue to read and write data to your delivery stream while the encryption status is ENABLING
, but the data is not encrypted. It can take up to 5 seconds after the encryption status changes to ENABLED
before all records written to the delivery stream are encrypted. To find out whether a record or a batch of records was encrypted, check the response elements PutRecordOutput$Encrypted and PutRecordBatchOutput$Encrypted, respectively.
To check the encryption status of a delivery stream, use DescribeDeliveryStream.
Even if encryption is currently enabled for a delivery stream, you can still invoke this operation on it to change the ARN of the CMK or both its type and ARN. If you invoke this method to change the CMK, and the old CMK is of type CUSTOMER_MANAGED_CMK
, Kinesis Data Firehose schedules the grant it had on the old CMK for retirement. If the new CMK is of type CUSTOMER_MANAGED_CMK
, Kinesis Data Firehose creates a grant that enables it to use the new CMK to encrypt and decrypt data and to manage the grant.
If a delivery stream already has encryption enabled and then you invoke this operation to change the ARN of the CMK or both its type and ARN and you get ENABLING_FAILED
, this only means that the attempt to change the CMK failed. In this case, encryption remains enabled with the old CMK.
If the encryption status of your delivery stream is ENABLING_FAILED
, you can invoke this operation again with a valid CMK. The CMK must be enabled and the key policy mustn't explicitly deny the permission for Kinesis Data Firehose to invoke KMS encrypt and decrypt operations.
You can enable SSE for a delivery stream only if it's a delivery stream that uses DirectPut
as its source.
The StartDeliveryStreamEncryption
and StopDeliveryStreamEncryption
operations have a combined limit of 25 calls per delivery stream per 24 hours. For example, you reach the limit if you call StartDeliveryStreamEncryption
13 times and StopDeliveryStreamEncryption
12 times for the same delivery stream in a 24-hour period.
",
"StopDeliveryStreamEncryption": "Disables server-side encryption (SSE) for the delivery stream.
This operation is asynchronous. It returns immediately. When you invoke it, Kinesis Data Firehose first sets the encryption status of the stream to DISABLING
, and then to DISABLED
. You can continue to read and write data to your stream while its status is DISABLING
. It can take up to 5 seconds after the encryption status changes to DISABLED
before all records written to the delivery stream are no longer subject to encryption. To find out whether a record or a batch of records was encrypted, check the response elements PutRecordOutput$Encrypted and PutRecordBatchOutput$Encrypted, respectively.
To check the encryption state of a delivery stream, use DescribeDeliveryStream.
If SSE is enabled using a customer managed CMK and then you invoke StopDeliveryStreamEncryption
, Kinesis Data Firehose schedules the related KMS grant for retirement and then retires it after it ensures that it is finished delivering records to the destination.
The StartDeliveryStreamEncryption
and StopDeliveryStreamEncryption
operations have a combined limit of 25 calls per delivery stream per 24 hours. For example, you reach the limit if you call StartDeliveryStreamEncryption
13 times and StopDeliveryStreamEncryption
12 times for the same delivery stream in a 24-hour period.
",
"TagDeliveryStream": "Adds or updates tags for the specified delivery stream. A tag is a key-value pair that you can define and assign to AWS resources. If you specify a tag that already exists, the tag value is replaced with the value that you specify in the request. Tags are metadata. For example, you can add friendly names and descriptions or other types of information that can help you distinguish the delivery stream. For more information about tags, see Using Cost Allocation Tags in the AWS Billing and Cost Management User Guide.
Each delivery stream can have up to 50 tags.
This operation has a limit of five transactions per second per account.
",
@@ -38,6 +38,7 @@
"DataFormatConversionConfiguration$Enabled": "Defaults to true
. Set it to false
if you want to disable format conversion while preserving the configuration details.
",
"DeleteDeliveryStreamInput$AllowForceDelete": "Set this to true if you want to delete the delivery stream even if Kinesis Data Firehose is unable to retire the grant for the CMK. Kinesis Data Firehose might be unable to retire the grant due to a customer error, such as when the CMK or the grant are in an invalid state. If you force deletion, you can then use the RevokeGrant operation to revoke the grant you gave to Kinesis Data Firehose. If a failure to retire the grant happens due to an AWS KMS issue, Kinesis Data Firehose keeps retrying the delete operation.
The default value is false.
",
"DeliveryStreamDescription$HasMoreDestinations": "Indicates whether there are more destinations available to list.
",
+ "DynamicPartitioningConfiguration$Enabled": "Specifies that the dynamic partitioning is enabled for this Kinesis Data Firehose delivery stream.
",
"ListDeliveryStreamsOutput$HasMoreDeliveryStreams": "Indicates whether there are more delivery streams available to list.
",
"ListTagsForDeliveryStreamOutput$HasMoreTags": "If this is true
in the response, more tags are available. To list the remaining tags, set ExclusiveStartTagKey
to the key of the last tag returned and call ListTagsForDeliveryStream
again.
",
"OpenXJsonSerDe$ConvertDotsInJsonKeysToUnderscores": "When set to true
, specifies that the names of the keys include dots and that you want Kinesis Data Firehose to replace them with underscores. This is useful because Apache Hive does not allow dots in column names. For example, if the JSON contains a key whose name is \"a.b\", you can define the column name to be \"a_b\" when using this option.
The default is false
.
",
@@ -322,6 +323,14 @@
"UpdateDestinationInput$DestinationId": "The ID of the destination.
"
}
},
+ "DynamicPartitioningConfiguration": {
+ "base": "The configuration of the dynamic partitioning mechanism that creates smaller data sets from the streaming data by partitioning it based on partition keys. Currently, dynamic partitioning is only supported for Amazon S3 destinations. For more information, see https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html
",
+ "refs": {
+ "ExtendedS3DestinationConfiguration$DynamicPartitioningConfiguration": "The configuration of the dynamic partitioning mechanism that creates smaller data sets from the streaming data by partitioning it based on partition keys. Currently, dynamic partitioning is only supported for Amazon S3 destinations. For more information, see https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html
",
+ "ExtendedS3DestinationDescription$DynamicPartitioningConfiguration": "The configuration of the dynamic partitioning mechanism that creates smaller data sets from the streaming data by partitioning it based on partition keys. Currently, dynamic partitioning is only supported for Amazon S3 destinations. For more information, see https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html
",
+ "ExtendedS3DestinationUpdate$DynamicPartitioningConfiguration": "The configuration of the dynamic partitioning mechanism that creates smaller data sets from the streaming data by partitioning it based on partition keys. Currently, dynamic partitioning is only supported for Amazon S3 destinations. For more information, see https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html
"
+ }
+ },
"ElasticsearchBufferingHints": {
"base": "Describes the buffering to perform before delivering data to the Amazon ES destination.
",
"refs": {
@@ -647,7 +656,7 @@
"HttpEndpointUrl": {
"base": null,
"refs": {
- "HttpEndpointConfiguration$Url": "The URL of the HTTP endpoint selected as the destination.
",
+ "HttpEndpointConfiguration$Url": "The URL of the HTTP endpoint selected as the destination.
If you choose an HTTP endpoint as your destination, review and follow the instructions in the Appendix - HTTP Endpoint Delivery Request and Response Specifications.
",
"HttpEndpointDescription$Url": "The URL of the HTTP endpoint selected as the destination.
"
}
},
@@ -791,10 +800,10 @@
"refs": {
"ColumnToJsonKeyMappings$key": null,
"ListOfNonEmptyStringsWithoutWhitespace$member": null,
- "SchemaConfiguration$RoleARN": "The role that Kinesis Data Firehose can use to access AWS Glue. This role must be in the same account you use for Kinesis Data Firehose. Cross-account roles aren't allowed.
",
+ "SchemaConfiguration$RoleARN": "The role that Kinesis Data Firehose can use to access AWS Glue. This role must be in the same account you use for Kinesis Data Firehose. Cross-account roles aren't allowed.
If the SchemaConfiguration
request parameter is used as part of invoking the CreateDeliveryStream
API, then the RoleARN
property is required and its value must be specified.
",
"SchemaConfiguration$CatalogId": "The ID of the AWS Glue Data Catalog. If you don't supply this, the AWS account ID is used by default.
",
- "SchemaConfiguration$DatabaseName": "Specifies the name of the AWS Glue database that contains the schema for the output data.
",
- "SchemaConfiguration$TableName": "Specifies the AWS Glue table that contains the column information that constitutes your data schema.
",
+ "SchemaConfiguration$DatabaseName": "Specifies the name of the AWS Glue database that contains the schema for the output data.
If the SchemaConfiguration
request parameter is used as part of invoking the CreateDeliveryStream
API, then the DatabaseName
property is required and its value must be specified.
",
+ "SchemaConfiguration$TableName": "Specifies the AWS Glue table that contains the column information that constitutes your data schema.
If the SchemaConfiguration
request parameter is used as part of invoking the CreateDeliveryStream
API, then the TableName
property is required and its value must be specified.
",
"SchemaConfiguration$Region": "If you don't specify an AWS Region, the default is the current Region.
",
"SchemaConfiguration$VersionId": "Specifies the table version for the output data schema. If you don't specify this version ID, or if you set it to LATEST
, Kinesis Data Firehose uses the most recent version. This means that any updates to the table are automatically picked up.
",
"SecurityGroupIdList$member": null,
@@ -1065,6 +1074,18 @@
"refs": {
}
},
+ "RetryDurationInSeconds": {
+ "base": null,
+ "refs": {
+ "RetryOptions$DurationInSeconds": "The period of time during which Kinesis Data Firehose retries to deliver data to the specified Amazon S3 prefix.
"
+ }
+ },
+ "RetryOptions": {
+ "base": " The retry behavior in case Kinesis Data Firehose is unable to deliver data to an Amazon S3 prefix.
",
+ "refs": {
+ "DynamicPartitioningConfiguration$RetryOptions": "The retry behavior in case Kinesis Data Firehose is unable to deliver data to an Amazon S3 prefix.
"
+ }
+ },
"RoleARN": {
"base": null,
"refs": {
diff --git a/models/apis/kms/2014-11-01/api-2.json b/models/apis/kms/2014-11-01/api-2.json
index 2d6df268a1f..3ce9f4e3276 100644
--- a/models/apis/kms/2014-11-01/api-2.json
+++ b/models/apis/kms/2014-11-01/api-2.json
@@ -1037,7 +1037,12 @@
"Policy":{"shape":"PolicyType"},
"Description":{"shape":"DescriptionType"},
"KeyUsage":{"shape":"KeyUsageType"},
- "CustomerMasterKeySpec":{"shape":"CustomerMasterKeySpec"},
+ "CustomerMasterKeySpec":{
+ "shape":"CustomerMasterKeySpec",
+ "deprecated":true,
+ "deprecatedMessage":"This parameter has been deprecated. Instead, use the KeySpec parameter."
+ },
+ "KeySpec":{"shape":"KeySpec"},
"Origin":{"shape":"OriginType"},
"CustomKeyStoreId":{"shape":"CustomKeyStoreIdType"},
"BypassPolicyLockoutSafetyCheck":{"shape":"BooleanType"},
@@ -1107,6 +1112,8 @@
},
"CustomerMasterKeySpec":{
"type":"string",
+ "deprecated":true,
+ "deprecatedMessage":"This enum has been deprecated. Instead, use the KeySpec enum.",
"enum":[
"RSA_2048",
"RSA_3072",
@@ -1490,7 +1497,12 @@
"members":{
"KeyId":{"shape":"KeyIdType"},
"PublicKey":{"shape":"PublicKeyType"},
- "CustomerMasterKeySpec":{"shape":"CustomerMasterKeySpec"},
+ "CustomerMasterKeySpec":{
+ "shape":"CustomerMasterKeySpec",
+ "deprecated":true,
+ "deprecatedMessage":"This field has been deprecated. Instead, use the KeySpec field."
+ },
+ "KeySpec":{"shape":"KeySpec"},
"KeyUsage":{"shape":"KeyUsageType"},
"EncryptionAlgorithms":{"shape":"EncryptionAlgorithmSpecList"},
"SigningAlgorithms":{"shape":"SigningAlgorithmSpecList"}
@@ -1727,7 +1739,12 @@
"CloudHsmClusterId":{"shape":"CloudHsmClusterIdType"},
"ExpirationModel":{"shape":"ExpirationModelType"},
"KeyManager":{"shape":"KeyManagerType"},
- "CustomerMasterKeySpec":{"shape":"CustomerMasterKeySpec"},
+ "CustomerMasterKeySpec":{
+ "shape":"CustomerMasterKeySpec",
+ "deprecated":true,
+ "deprecatedMessage":"This field has been deprecated. Instead, use the KeySpec field."
+ },
+ "KeySpec":{"shape":"KeySpec"},
"EncryptionAlgorithms":{"shape":"EncryptionAlgorithmSpecList"},
"SigningAlgorithms":{"shape":"SigningAlgorithmSpecList"},
"MultiRegion":{"shape":"NullableBooleanType"},
@@ -1735,6 +1752,19 @@
"PendingDeletionWindowInDays":{"shape":"PendingWindowInDaysType"}
}
},
+ "KeySpec":{
+ "type":"string",
+ "enum":[
+ "RSA_2048",
+ "RSA_3072",
+ "RSA_4096",
+ "ECC_NIST_P256",
+ "ECC_NIST_P384",
+ "ECC_NIST_P521",
+ "ECC_SECG_P256K1",
+ "SYMMETRIC_DEFAULT"
+ ]
+ },
"KeyState":{
"type":"string",
"enum":[
diff --git a/models/apis/kms/2014-11-01/docs-2.json b/models/apis/kms/2014-11-01/docs-2.json
index a952a4cebc4..dff2b324c13 100644
--- a/models/apis/kms/2014-11-01/docs-2.json
+++ b/models/apis/kms/2014-11-01/docs-2.json
@@ -1,67 +1,67 @@
{
"version": "2.0",
- "service": "AWS Key Management Service AWS Key Management Service (AWS KMS) is an encryption and key management web service. This guide describes the AWS KMS operations that you can call programmatically. For general information about AWS KMS, see the AWS Key Management Service Developer Guide .
AWS provides SDKs that consist of libraries and sample code for various programming languages and platforms (Java, Ruby, .Net, macOS, Android, etc.). The SDKs provide a convenient way to create programmatic access to AWS KMS and other AWS services. For example, the SDKs take care of tasks such as signing requests (see below), managing errors, and retrying requests automatically. For more information about the AWS SDKs, including how to download and install them, see Tools for Amazon Web Services.
We recommend that you use the AWS SDKs to make programmatic API calls to AWS KMS.
Clients must support TLS (Transport Layer Security) 1.0. We recommend TLS 1.2. Clients must also support cipher suites with Perfect Forward Secrecy (PFS) such as Ephemeral Diffie-Hellman (DHE) or Elliptic Curve Ephemeral Diffie-Hellman (ECDHE). Most modern systems such as Java 7 and later support these modes.
Signing Requests
Requests must be signed by using an access key ID and a secret access key. We strongly recommend that you do not use your AWS account (root) access key ID and secret key for everyday work with AWS KMS. Instead, use the access key ID and secret access key for an IAM user. You can also use the AWS Security Token Service to generate temporary security credentials that you can use to sign requests.
All AWS KMS operations require Signature Version 4.
Logging API Requests
AWS KMS supports AWS CloudTrail, a service that logs AWS API calls and related events for your AWS account and delivers them to an Amazon S3 bucket that you specify. By using the information collected by CloudTrail, you can determine what requests were made to AWS KMS, who made the request, when it was made, and so on. To learn more about CloudTrail, including how to turn it on and find your log files, see the AWS CloudTrail User Guide.
Additional Resources
For more information about credentials and request signing, see the following:
Commonly Used API Operations
Of the API operations discussed in this guide, the following will prove the most useful for most applications. You will likely perform operations other than these, such as creating keys and assigning policies, by using the console.
",
+ "service": "Key Management Service Key Management Service (KMS) is an encryption and key management web service. This guide describes the KMS operations that you can call programmatically. For general information about KMS, see the Key Management Service Developer Guide .
KMS is replacing the term customer master key (CMK) with KMS key and KMS key. The concept has not changed. To prevent breaking changes, KMS is keeping some variations of this term.
Amazon Web Services provides SDKs that consist of libraries and sample code for various programming languages and platforms (Java, Ruby, .Net, macOS, Android, etc.). The SDKs provide a convenient way to create programmatic access to KMS and other Amazon Web Services services. For example, the SDKs take care of tasks such as signing requests (see below), managing errors, and retrying requests automatically. For more information about the Amazon Web Services SDKs, including how to download and install them, see Tools for Amazon Web Services.
We recommend that you use the Amazon Web Services SDKs to make programmatic API calls to KMS.
Clients must support TLS (Transport Layer Security) 1.0. We recommend TLS 1.2. Clients must also support cipher suites with Perfect Forward Secrecy (PFS) such as Ephemeral Diffie-Hellman (DHE) or Elliptic Curve Ephemeral Diffie-Hellman (ECDHE). Most modern systems such as Java 7 and later support these modes.
Signing Requests
Requests must be signed by using an access key ID and a secret access key. We strongly recommend that you do not use your Amazon Web Services account (root) access key ID and secret key for everyday work with KMS. Instead, use the access key ID and secret access key for an IAM user. You can also use the Amazon Web Services Security Token Service to generate temporary security credentials that you can use to sign requests.
All KMS operations require Signature Version 4.
Logging API Requests
KMS supports CloudTrail, a service that logs Amazon Web Services API calls and related events for your Amazon Web Services account and delivers them to an Amazon S3 bucket that you specify. By using the information collected by CloudTrail, you can determine what requests were made to KMS, who made the request, when it was made, and so on. To learn more about CloudTrail, including how to turn it on and find your log files, see the CloudTrail User Guide.
Additional Resources
For more information about credentials and request signing, see the following:
Commonly Used API Operations
Of the API operations discussed in this guide, the following will prove the most useful for most applications. You will likely perform operations other than these, such as creating keys and assigning policies, by using the console.
",
"operations": {
- "CancelKeyDeletion": "Cancels the deletion of a customer master key (CMK). When this operation succeeds, the key state of the CMK is Disabled
. To enable the CMK, use EnableKey.
For more information about scheduling and canceling deletion of a CMK, see Deleting Customer Master Keys in the AWS Key Management Service Developer Guide.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:CancelKeyDeletion (key policy)
Related operations: ScheduleKeyDeletion
",
- "ConnectCustomKeyStore": "Connects or reconnects a custom key store to its associated AWS CloudHSM cluster.
The custom key store must be connected before you can create customer master keys (CMKs) in the key store or use the CMKs it contains. You can disconnect and reconnect a custom key store at any time.
To connect a custom key store, its associated AWS CloudHSM cluster must have at least one active HSM. To get the number of active HSMs in a cluster, use the DescribeClusters operation. To add HSMs to the cluster, use the CreateHsm operation. Also, the kmsuser
crypto user (CU) must not be logged into the cluster. This prevents AWS KMS from using this account to log in.
The connection process can take an extended amount of time to complete; up to 20 minutes. This operation starts the connection process, but it does not wait for it to complete. When it succeeds, this operation quickly returns an HTTP 200 response and a JSON object with no properties. However, this response does not indicate that the custom key store is connected. To get the connection state of the custom key store, use the DescribeCustomKeyStores operation.
During the connection process, AWS KMS finds the AWS CloudHSM cluster that is associated with the custom key store, creates the connection infrastructure, connects to the cluster, logs into the AWS CloudHSM client as the kmsuser
CU, and rotates its password.
The ConnectCustomKeyStore
operation might fail for various reasons. To find the reason, use the DescribeCustomKeyStores operation and see the ConnectionErrorCode
in the response. For help interpreting the ConnectionErrorCode
, see CustomKeyStoresListEntry.
To fix the failure, use the DisconnectCustomKeyStore operation to disconnect the custom key store, correct the error, use the UpdateCustomKeyStore operation if necessary, and then use ConnectCustomKeyStore
again.
If you are having trouble connecting or disconnecting a custom key store, see Troubleshooting a Custom Key Store in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a custom key store in a different AWS account.
Required permissions: kms:ConnectCustomKeyStore (IAM policy)
Related operations
",
- "CreateAlias": "Creates a friendly name for a customer master key (CMK).
Adding, deleting, or updating an alias can allow or deny permission to the CMK. For details, see Using ABAC in AWS KMS in the AWS Key Management Service Developer Guide.
You can use an alias to identify a CMK in the AWS KMS console, in the DescribeKey operation and in cryptographic operations, such as Encrypt and GenerateDataKey. You can also change the CMK that's associated with the alias (UpdateAlias) or delete the alias (DeleteAlias) at any time. These operations don't affect the underlying CMK.
You can associate the alias with any customer managed CMK in the same AWS Region. Each alias is associated with only one CMK at a time, but a CMK can have multiple aliases. A valid CMK is required. You can't create an alias without a CMK.
The alias must be unique in the account and Region, but you can have aliases with the same name in different Regions. For detailed information about aliases, see Using aliases in the AWS Key Management Service Developer Guide.
This operation does not return a response. To get the alias that you created, use the ListAliases operation.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on an alias in a different AWS account.
Required permissions
For details, see Controlling access to aliases in the AWS Key Management Service Developer Guide.
Related operations:
",
- "CreateCustomKeyStore": "Creates a custom key store that is associated with an AWS CloudHSM cluster that you own and manage.
This operation is part of the Custom Key Store feature feature in AWS KMS, which combines the convenience and extensive integration of AWS KMS with the isolation and control of a single-tenant key store.
Before you create the custom key store, you must assemble the required elements, including an AWS CloudHSM cluster that fulfills the requirements for a custom key store. For details about the required elements, see Assemble the Prerequisites in the AWS Key Management Service Developer Guide.
When the operation completes successfully, it returns the ID of the new custom key store. Before you can use your new custom key store, you need to use the ConnectCustomKeyStore operation to connect the new key store to its AWS CloudHSM cluster. Even if you are not going to use your custom key store immediately, you might want to connect it to verify that all settings are correct and then disconnect it until you are ready to use it.
For help with failures, see Troubleshooting a Custom Key Store in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a custom key store in a different AWS account.
Required permissions: kms:CreateCustomKeyStore (IAM policy).
Related operations:
",
- "CreateGrant": "Adds a grant to a customer master key (CMK).
A grant is a policy instrument that allows AWS principals to use AWS KMS customer master keys (CMKs) in cryptographic operations. It also can allow them to view a CMK (DescribeKey) and create and manage grants. When authorizing access to a CMK, grants are considered along with key policies and IAM policies. Grants are often used for temporary permissions because you can create one, use its permissions, and delete it without changing your key policies or IAM policies.
For detailed information about grants, including grant terminology, see Using grants in the AWS Key Management Service Developer Guide . For examples of working with grants in several programming languages, see Programming grants.
The CreateGrant
operation returns a GrantToken
and a GrantId
.
-
When you create, retire, or revoke a grant, there might be a brief delay, usually less than five minutes, until the grant is available throughout AWS KMS. This state is known as eventual consistency. Once the grant has achieved eventual consistency, the grantee principal can use the permissions in the grant without identifying the grant.
However, to use the permissions in the grant immediately, use the GrantToken
that CreateGrant
returns. For details, see Using a grant token in the AWS Key Management Service Developer Guide .
-
The CreateGrant
operation also returns a GrantId
. You can use the GrantId
and a key identifier to identify the grant in the RetireGrant and RevokeGrant operations. To find the grant ID, use the ListGrants or ListRetirableGrants operations.
For information about symmetric and asymmetric CMKs, see Using Symmetric and Asymmetric CMKs in the AWS Key Management Service Developer Guide. For more information about grants, see Grants in the AWS Key Management Service Developer Guide .
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation on a CMK in a different AWS account, specify the key ARN in the value of the KeyId
parameter.
Required permissions: kms:CreateGrant (key policy)
Related operations:
",
- "CreateKey": "Creates a unique customer managed customer master key (CMK) in your AWS account and Region.
You can use the CreateKey
operation to create symmetric or asymmetric CMKs.
-
Symmetric CMKs contain a 256-bit symmetric key that never leaves AWS KMS unencrypted. To use the CMK, you must call AWS KMS. You can use a symmetric CMK to encrypt and decrypt small amounts of data, but they are typically used to generate data keys and data keys pairs. For details, see GenerateDataKey and GenerateDataKeyPair.
-
Asymmetric CMKs can contain an RSA key pair or an Elliptic Curve (ECC) key pair. The private key in an asymmetric CMK never leaves AWS KMS unencrypted. However, you can use the GetPublicKey operation to download the public key so it can be used outside of AWS KMS. CMKs with RSA key pairs can be used to encrypt or decrypt data or sign and verify messages (but not both). CMKs with ECC key pairs can be used only to sign and verify messages.
For information about symmetric and asymmetric CMKs, see Using Symmetric and Asymmetric CMKs in the AWS Key Management Service Developer Guide.
To create different types of CMKs, use the following guidance:
- Asymmetric CMKs
-
To create an asymmetric CMK, use the CustomerMasterKeySpec
parameter to specify the type of key material in the CMK. Then, use the KeyUsage
parameter to determine whether the CMK will be used to encrypt and decrypt or sign and verify. You can't change these properties after the CMK is created.
- Symmetric CMKs
-
When creating a symmetric CMK, you don't need to specify the CustomerMasterKeySpec
or KeyUsage
parameters. The default value for CustomerMasterKeySpec
, SYMMETRIC_DEFAULT
, and the default value for KeyUsage
, ENCRYPT_DECRYPT
, are the only valid values for symmetric CMKs.
- Multi-Region primary keys
- Imported key material
-
To create a multi-Region primary key in the local AWS Region, use the MultiRegion
parameter with a value of True
. To create a multi-Region replica key, that is, a CMK with the same key ID and key material as a primary key, but in a different AWS Region, use the ReplicateKey operation. To change a replica key to a primary key, and its primary key to a replica key, use the UpdatePrimaryRegion operation.
This operation supports multi-Region keys, an AWS KMS feature that lets you create multiple interoperable CMKs in different AWS Regions. Because these CMKs have the same key ID, key material, and other metadata, you can use them to encrypt data in one AWS Region and decrypt it in a different AWS Region without making a cross-Region call or exposing the plaintext data. For more information about multi-Region keys, see Using multi-Region keys in the AWS Key Management Service Developer Guide.
You can create symmetric and asymmetric multi-Region keys and multi-Region keys with imported key material. You cannot create multi-Region keys in a custom key store.
-
To import your own key material, begin by creating a symmetric CMK with no key material. To do this, use the Origin
parameter of CreateKey
with a value of EXTERNAL
. Next, use GetParametersForImport operation to get a public key and import token, and use the public key to encrypt your key material. Then, use ImportKeyMaterial with your import token to import the key material. For step-by-step instructions, see Importing Key Material in the AWS Key Management Service Developer Guide . You cannot import the key material into an asymmetric CMK.
To create a multi-Region primary key with imported key material, use the Origin
parameter of CreateKey
with a value of EXTERNAL
and the MultiRegion
parameter with a value of True
. To create replicas of the multi-Region primary key, use the ReplicateKey operation. For more information about multi-Region keys, see Using multi-Region keys in the AWS Key Management Service Developer Guide.
- Custom key store
-
To create a symmetric CMK in a custom key store, use the CustomKeyStoreId
parameter to specify the custom key store. You must also use the Origin
parameter with a value of AWS_CLOUDHSM
. The AWS CloudHSM cluster that is associated with the custom key store must have at least two active HSMs in different Availability Zones in the AWS Region.
You cannot create an asymmetric CMK or a multi-Region CMK in a custom key store. For information about custom key stores in AWS KMS see Using Custom Key Stores in the AWS Key Management Service Developer Guide .
Cross-account use: No. You cannot use this operation to create a CMK in a different AWS account.
Required permissions: kms:CreateKey (IAM policy). To use the Tags
parameter, kms:TagResource (IAM policy). For examples and information about related permissions, see Allow a user to create CMKs in the AWS Key Management Service Developer Guide.
Related operations:
",
- "Decrypt": "Decrypts ciphertext that was encrypted by a AWS KMS customer master key (CMK) using any of the following operations:
You can use this operation to decrypt ciphertext that was encrypted under a symmetric or asymmetric CMK. When the CMK is asymmetric, you must specify the CMK and the encryption algorithm that was used to encrypt the ciphertext. For information about symmetric and asymmetric CMKs, see Using Symmetric and Asymmetric CMKs in the AWS Key Management Service Developer Guide.
The Decrypt operation also decrypts ciphertext that was encrypted outside of AWS KMS by the public key in an AWS KMS asymmetric CMK. However, it cannot decrypt ciphertext produced by other libraries, such as the AWS Encryption SDK or Amazon S3 client-side encryption. These libraries return a ciphertext format that is incompatible with AWS KMS.
If the ciphertext was encrypted under a symmetric CMK, the KeyId
parameter is optional. AWS KMS can get this information from metadata that it adds to the symmetric ciphertext blob. This feature adds durability to your implementation by ensuring that authorized users can decrypt ciphertext decades after it was encrypted, even if they've lost track of the CMK ID. However, specifying the CMK is always recommended as a best practice. When you use the KeyId
parameter to specify a CMK, AWS KMS only uses the CMK you specify. If the ciphertext was encrypted under a different CMK, the Decrypt
operation fails. This practice ensures that you use the CMK that you intend.
Whenever possible, use key policies to give users permission to call the Decrypt
operation on a particular CMK, instead of using IAM policies. Otherwise, you might create an IAM user policy that gives the user Decrypt
permission on all CMKs. This user could decrypt ciphertext that was encrypted by CMKs in other accounts if the key policy for the cross-account CMK permits it. If you must use an IAM policy for Decrypt
permissions, limit the user to particular CMKs or particular trusted accounts. For details, see Best practices for IAM policies in the AWS Key Management Service Developer Guide.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. You can decrypt a ciphertext using a CMK in a different AWS account.
Required permissions: kms:Decrypt (key policy)
Related operations:
",
- "DeleteAlias": "Deletes the specified alias.
Adding, deleting, or updating an alias can allow or deny permission to the CMK. For details, see Using ABAC in AWS KMS in the AWS Key Management Service Developer Guide.
Because an alias is not a property of a CMK, you can delete and change the aliases of a CMK without affecting the CMK. Also, aliases do not appear in the response from the DescribeKey operation. To get the aliases of all CMKs, use the ListAliases operation.
Each CMK can have multiple aliases. To change the alias of a CMK, use DeleteAlias to delete the current alias and CreateAlias to create a new alias. To associate an existing alias with a different customer master key (CMK), call UpdateAlias.
Cross-account use: No. You cannot perform this operation on an alias in a different AWS account.
Required permissions
For details, see Controlling access to aliases in the AWS Key Management Service Developer Guide.
Related operations:
",
- "DeleteCustomKeyStore": "Deletes a custom key store. This operation does not delete the AWS CloudHSM cluster that is associated with the custom key store, or affect any users or keys in the cluster.
The custom key store that you delete cannot contain any AWS KMS customer master keys (CMKs). Before deleting the key store, verify that you will never need to use any of the CMKs in the key store for any cryptographic operations. Then, use ScheduleKeyDeletion to delete the AWS KMS customer master keys (CMKs) from the key store. When the scheduled waiting period expires, the ScheduleKeyDeletion
operation deletes the CMKs. Then it makes a best effort to delete the key material from the associated cluster. However, you might need to manually delete the orphaned key material from the cluster and its backups.
After all CMKs are deleted from AWS KMS, use DisconnectCustomKeyStore to disconnect the key store from AWS KMS. Then, you can delete the custom key store.
Instead of deleting the custom key store, consider using DisconnectCustomKeyStore to disconnect it from AWS KMS. While the key store is disconnected, you cannot create or use the CMKs in the key store. But, you do not need to delete CMKs and you can reconnect a disconnected custom key store at any time.
If the operation succeeds, it returns a JSON object with no properties.
This operation is part of the Custom Key Store feature feature in AWS KMS, which combines the convenience and extensive integration of AWS KMS with the isolation and control of a single-tenant key store.
Cross-account use: No. You cannot perform this operation on a custom key store in a different AWS account.
Required permissions: kms:DeleteCustomKeyStore (IAM policy)
Related operations:
",
- "DeleteImportedKeyMaterial": "Deletes key material that you previously imported. This operation makes the specified customer master key (CMK) unusable. For more information about importing key material into AWS KMS, see Importing Key Material in the AWS Key Management Service Developer Guide.
When the specified CMK is in the PendingDeletion
state, this operation does not change the CMK's state. Otherwise, it changes the CMK's state to PendingImport
.
After you delete key material, you can use ImportKeyMaterial to reimport the same key material into the CMK.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:DeleteImportedKeyMaterial (key policy)
Related operations:
",
- "DescribeCustomKeyStores": "Gets information about custom key stores in the account and Region.
This operation is part of the Custom Key Store feature feature in AWS KMS, which combines the convenience and extensive integration of AWS KMS with the isolation and control of a single-tenant key store.
By default, this operation returns information about all custom key stores in the account and Region. To get only information about a particular custom key store, use either the CustomKeyStoreName
or CustomKeyStoreId
parameter (but not both).
To determine whether the custom key store is connected to its AWS CloudHSM cluster, use the ConnectionState
element in the response. If an attempt to connect the custom key store failed, the ConnectionState
value is FAILED
and the ConnectionErrorCode
element in the response indicates the cause of the failure. For help interpreting the ConnectionErrorCode
, see CustomKeyStoresListEntry.
Custom key stores have a DISCONNECTED
connection state if the key store has never been connected or you use the DisconnectCustomKeyStore operation to disconnect it. If your custom key store state is CONNECTED
but you are having trouble using it, make sure that its associated AWS CloudHSM cluster is active and contains the minimum number of HSMs required for the operation, if any.
For help repairing your custom key store, see the Troubleshooting Custom Key Stores topic in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a custom key store in a different AWS account.
Required permissions: kms:DescribeCustomKeyStores (IAM policy)
Related operations:
",
- "DescribeKey": "Provides detailed information about a customer master key (CMK). You can run DescribeKey
on a customer managed CMK or an AWS managed CMK.
This detailed information includes the key ARN, creation date (and deletion date, if applicable), the key state, and the origin and expiration date (if any) of the key material. For CMKs in custom key stores, it includes information about the custom key store, such as the key store ID and the AWS CloudHSM cluster ID. It includes fields, like KeySpec
, that help you distinguish symmetric from asymmetric CMKs. It also provides information that is particularly important to asymmetric CMKs, such as the key usage (encryption or signing) and the encryption algorithms or signing algorithms that the CMK supports.
DescribeKey
does not return the following information:
If you call the DescribeKey
operation on a predefined AWS alias, that is, an AWS alias with no key ID, AWS KMS creates an AWS managed CMK. Then, it associates the alias with the new CMK, and returns the KeyId
and Arn
of the new CMK in the response.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:DescribeKey (key policy)
Related operations:
",
- "DisableKey": "Sets the state of a customer master key (CMK) to disabled. This change temporarily prevents use of the CMK for cryptographic operations.
For more information about how key state affects the use of a CMK, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide .
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:DisableKey (key policy)
Related operations: EnableKey
",
- "DisableKeyRotation": "Disables automatic rotation of the key material for the specified symmetric customer master key (CMK).
You cannot enable automatic rotation of asymmetric CMKs, CMKs with imported key material, or CMKs in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:DisableKeyRotation (key policy)
Related operations:
",
- "DisconnectCustomKeyStore": "Disconnects the custom key store from its associated AWS CloudHSM cluster. While a custom key store is disconnected, you can manage the custom key store and its customer master keys (CMKs), but you cannot create or use CMKs in the custom key store. You can reconnect the custom key store at any time.
While a custom key store is disconnected, all attempts to create customer master keys (CMKs) in the custom key store or to use existing CMKs in cryptographic operations will fail. This action can prevent users from storing and accessing sensitive data.
To find the connection state of a custom key store, use the DescribeCustomKeyStores operation. To reconnect a custom key store, use the ConnectCustomKeyStore operation.
If the operation succeeds, it returns a JSON object with no properties.
This operation is part of the Custom Key Store feature feature in AWS KMS, which combines the convenience and extensive integration of AWS KMS with the isolation and control of a single-tenant key store.
Cross-account use: No. You cannot perform this operation on a custom key store in a different AWS account.
Required permissions: kms:DisconnectCustomKeyStore (IAM policy)
Related operations:
",
- "EnableKey": "Sets the key state of a customer master key (CMK) to enabled. This allows you to use the CMK for cryptographic operations.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:EnableKey (key policy)
Related operations: DisableKey
",
- "EnableKeyRotation": "Enables automatic rotation of the key material for the specified symmetric customer master key (CMK).
You cannot enable automatic rotation of asymmetric CMKs, CMKs with imported key material, or CMKs in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:EnableKeyRotation (key policy)
Related operations:
",
- "Encrypt": "Encrypts plaintext into ciphertext by using a customer master key (CMK). The Encrypt
operation has two primary use cases:
-
You can encrypt small amounts of arbitrary data, such as a personal identifier or database password, or other sensitive information.
-
You can use the Encrypt
operation to move encrypted data from one AWS Region to another. For example, in Region A, generate a data key and use the plaintext key to encrypt your data. Then, in Region A, use the Encrypt
operation to encrypt the plaintext data key under a CMK in Region B. Now, you can move the encrypted data and the encrypted data key to Region B. When necessary, you can decrypt the encrypted data key and the encrypted data entirely within in Region B.
You don't need to use the Encrypt
operation to encrypt a data key. The GenerateDataKey and GenerateDataKeyPair operations return a plaintext data key and an encrypted copy of that data key.
When you encrypt data, you must specify a symmetric or asymmetric CMK to use in the encryption operation. The CMK must have a KeyUsage
value of ENCRYPT_DECRYPT.
To find the KeyUsage
of a CMK, use the DescribeKey operation.
If you use a symmetric CMK, you can use an encryption context to add additional security to your encryption operation. If you specify an EncryptionContext
when encrypting data, you must specify the same encryption context (a case-sensitive exact match) when decrypting the data. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
If you specify an asymmetric CMK, you must also specify the encryption algorithm. The algorithm must be compatible with the CMK type.
When you use an asymmetric CMK to encrypt or reencrypt data, be sure to record the CMK and encryption algorithm that you choose. You will be required to provide the same CMK and encryption algorithm when you decrypt the data. If the CMK and algorithm do not match the values used to encrypt the data, the decrypt operation fails.
You are not required to supply the CMK ID and encryption algorithm when you decrypt with symmetric CMKs because AWS KMS stores this information in the ciphertext blob. AWS KMS cannot store metadata in ciphertext generated with asymmetric keys. The standard format for asymmetric key ciphertext does not include configurable fields.
The maximum size of the data that you can encrypt varies with the type of CMK and the encryption algorithm that you choose.
-
Symmetric CMKs
-
RSA_2048
-
RSA_3072
-
RSA_4096
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:Encrypt (key policy)
Related operations:
",
- "GenerateDataKey": "Generates a unique symmetric data key for client-side encryption. This operation returns a plaintext copy of the data key and a copy that is encrypted under a customer master key (CMK) that you specify. You can use the plaintext key to encrypt your data outside of AWS KMS and store the encrypted data key with the encrypted data.
GenerateDataKey
returns a unique data key for each request. The bytes in the plaintext key are not related to the caller or the CMK.
To generate a data key, specify the symmetric CMK that will be used to encrypt the data key. You cannot use an asymmetric CMK to generate data keys. To get the type of your CMK, use the DescribeKey operation. You must also specify the length of the data key. Use either the KeySpec
or NumberOfBytes
parameters (but not both). For 128-bit and 256-bit data keys, use the KeySpec
parameter.
To get only an encrypted copy of the data key, use GenerateDataKeyWithoutPlaintext. To generate an asymmetric data key pair, use the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext operation. To get a cryptographically secure random byte string, use GenerateRandom.
You can use the optional encryption context to add additional security to the encryption operation. If you specify an EncryptionContext
, you must specify the same encryption context (a case-sensitive exact match) when decrypting the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
How to use your data key
We recommend that you use the following pattern to encrypt data locally in your application. You can write your own code or use a client-side encryption library, such as the AWS Encryption SDK, the Amazon DynamoDB Encryption Client, or Amazon S3 client-side encryption to do these tasks for you.
To encrypt data outside of AWS KMS:
-
Use the GenerateDataKey
operation to get a data key.
-
Use the plaintext data key (in the Plaintext
field of the response) to encrypt your data outside of AWS KMS. Then erase the plaintext data key from memory.
-
Store the encrypted data key (in the CiphertextBlob
field of the response) with the encrypted data.
To decrypt data outside of AWS KMS:
-
Use the Decrypt operation to decrypt the encrypted data key. The operation returns a plaintext copy of the data key.
-
Use the plaintext data key to decrypt data outside of AWS KMS, then erase the plaintext data key from memory.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GenerateDataKey (key policy)
Related operations:
",
- "GenerateDataKeyPair": "Generates a unique asymmetric data key pair. The GenerateDataKeyPair
operation returns a plaintext public key, a plaintext private key, and a copy of the private key that is encrypted under the symmetric CMK you specify. You can use the data key pair to perform asymmetric cryptography outside of AWS KMS.
GenerateDataKeyPair
returns a unique data key pair for each request. The bytes in the keys are not related to the caller or the CMK that is used to encrypt the private key.
You can use the public key that GenerateDataKeyPair
returns to encrypt data or verify a signature outside of AWS KMS. Then, store the encrypted private key with the data. When you are ready to decrypt data or sign a message, you can use the Decrypt operation to decrypt the encrypted private key.
To generate a data key pair, you must specify a symmetric customer master key (CMK) to encrypt the private key in a data key pair. You cannot use an asymmetric CMK or a CMK in a custom key store. To get the type and origin of your CMK, use the DescribeKey operation.
If you are using the data key pair to encrypt data, or for any operation where you don't immediately need a private key, consider using the GenerateDataKeyPairWithoutPlaintext operation. GenerateDataKeyPairWithoutPlaintext
returns a plaintext public key and an encrypted private key, but omits the plaintext private key that you need only to decrypt ciphertext or sign a message. Later, when you need to decrypt the data or sign a message, use the Decrypt operation to decrypt the encrypted private key in the data key pair.
You can use the optional encryption context to add additional security to the encryption operation. If you specify an EncryptionContext
, you must specify the same encryption context (a case-sensitive exact match) when decrypting the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GenerateDataKeyPair (key policy)
Related operations:
",
- "GenerateDataKeyPairWithoutPlaintext": "Generates a unique asymmetric data key pair. The GenerateDataKeyPairWithoutPlaintext
operation returns a plaintext public key and a copy of the private key that is encrypted under the symmetric CMK you specify. Unlike GenerateDataKeyPair, this operation does not return a plaintext private key.
To generate a data key pair, you must specify a symmetric customer master key (CMK) to encrypt the private key in the data key pair. You cannot use an asymmetric CMK or a CMK in a custom key store. To get the type and origin of your CMK, use the KeySpec
field in the DescribeKey response.
You can use the public key that GenerateDataKeyPairWithoutPlaintext
returns to encrypt data or verify a signature outside of AWS KMS. Then, store the encrypted private key with the data. When you are ready to decrypt data or sign a message, you can use the Decrypt operation to decrypt the encrypted private key.
GenerateDataKeyPairWithoutPlaintext
returns a unique data key pair for each request. The bytes in the key are not related to the caller or CMK that is used to encrypt the private key.
You can use the optional encryption context to add additional security to the encryption operation. If you specify an EncryptionContext
, you must specify the same encryption context (a case-sensitive exact match) when decrypting the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GenerateDataKeyPairWithoutPlaintext (key policy)
Related operations:
",
- "GenerateDataKeyWithoutPlaintext": "Generates a unique symmetric data key. This operation returns a data key that is encrypted under a customer master key (CMK) that you specify. To request an asymmetric data key pair, use the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext operations.
GenerateDataKeyWithoutPlaintext
is identical to the GenerateDataKey operation except that returns only the encrypted copy of the data key. This operation is useful for systems that need to encrypt data at some point, but not immediately. When you need to encrypt the data, you call the Decrypt operation on the encrypted copy of the key.
It's also useful in distributed systems with different levels of trust. For example, you might store encrypted data in containers. One component of your system creates new containers and stores an encrypted data key with each container. Then, a different component puts the data into the containers. That component first decrypts the data key, uses the plaintext data key to encrypt data, puts the encrypted data into the container, and then destroys the plaintext data key. In this system, the component that creates the containers never sees the plaintext data key.
GenerateDataKeyWithoutPlaintext
returns a unique data key for each request. The bytes in the keys are not related to the caller or CMK that is used to encrypt the private key.
To generate a data key, you must specify the symmetric customer master key (CMK) that is used to encrypt the data key. You cannot use an asymmetric CMK to generate a data key. To get the type of your CMK, use the DescribeKey operation.
If the operation succeeds, you will find the encrypted copy of the data key in the CiphertextBlob
field.
You can use the optional encryption context to add additional security to the encryption operation. If you specify an EncryptionContext
, you must specify the same encryption context (a case-sensitive exact match) when decrypting the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GenerateDataKeyWithoutPlaintext (key policy)
Related operations:
",
- "GenerateRandom": "Returns a random byte string that is cryptographically secure.
By default, the random byte string is generated in AWS KMS. To generate the byte string in the AWS CloudHSM cluster that is associated with a custom key store, specify the custom key store ID.
For more information about entropy and random number generation, see AWS Key Management Service Cryptographic Details.
Required permissions: kms:GenerateRandom (IAM policy)
",
- "GetKeyPolicy": "Gets a key policy attached to the specified customer master key (CMK).
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:GetKeyPolicy (key policy)
Related operations: PutKeyPolicy
",
- "GetKeyRotationStatus": "Gets a Boolean value that indicates whether automatic rotation of the key material is enabled for the specified customer master key (CMK).
You cannot enable automatic rotation of asymmetric CMKs, CMKs with imported key material, or CMKs in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key. The key rotation status for these CMKs is always false
.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
-
Disabled: The key rotation status does not change when you disable a CMK. However, while the CMK is disabled, AWS KMS does not rotate the backing key.
-
Pending deletion: While a CMK is pending deletion, its key rotation status is false
and AWS KMS does not rotate the backing key. If you cancel the deletion, the original key rotation status is restored.
Cross-account use: Yes. To perform this operation on a CMK in a different AWS account, specify the key ARN in the value of the KeyId
parameter.
Required permissions: kms:GetKeyRotationStatus (key policy)
Related operations:
",
- "GetParametersForImport": "Returns the items you need to import key material into a symmetric, customer managed customer master key (CMK). For more information about importing key material into AWS KMS, see Importing Key Material in the AWS Key Management Service Developer Guide.
This operation returns a public key and an import token. Use the public key to encrypt the symmetric key material. Store the import token to send with a subsequent ImportKeyMaterial request.
You must specify the key ID of the symmetric CMK into which you will import key material. This CMK's Origin
must be EXTERNAL
. You must also specify the wrapping algorithm and type of wrapping key (public key) that you will use to encrypt the key material. You cannot perform this operation on an asymmetric CMK or on any CMK in a different AWS account.
To import key material, you must use the public key and import token from the same response. These items are valid for 24 hours. The expiration date and time appear in the GetParametersForImport
response. You cannot use an expired token in an ImportKeyMaterial request. If your key and token expire, send another GetParametersForImport
request.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:GetParametersForImport (key policy)
Related operations:
",
- "GetPublicKey": "Returns the public key of an asymmetric CMK. Unlike the private key of a asymmetric CMK, which never leaves AWS KMS unencrypted, callers with kms:GetPublicKey
permission can download the public key of an asymmetric CMK. You can share the public key to allow others to encrypt messages and verify signatures outside of AWS KMS. For information about symmetric and asymmetric CMKs, see Using Symmetric and Asymmetric CMKs in the AWS Key Management Service Developer Guide.
You do not need to download the public key. Instead, you can use the public key within AWS KMS by calling the Encrypt, ReEncrypt, or Verify operations with the identifier of an asymmetric CMK. When you use the public key within AWS KMS, you benefit from the authentication, authorization, and logging that are part of every AWS KMS operation. You also reduce of risk of encrypting data that cannot be decrypted. These features are not effective outside of AWS KMS. For details, see Special Considerations for Downloading Public Keys.
To help you use the public key safely outside of AWS KMS, GetPublicKey
returns important information about the public key in the response, including:
Although AWS KMS cannot enforce these restrictions on external operations, it is crucial that you use this information to prevent the public key from being used improperly. For example, you can prevent a public signing key from being used encrypt data, or prevent a public key from being used with an encryption algorithm that is not supported by AWS KMS. You can also avoid errors, such as using the wrong signing algorithm in a verification operation.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GetPublicKey (key policy)
Related operations: CreateKey
",
- "ImportKeyMaterial": "Imports key material into an existing symmetric AWS KMS customer master key (CMK) that was created without key material. After you successfully import key material into a CMK, you can reimport the same key material into that CMK, but you cannot import different key material.
You cannot perform this operation on an asymmetric CMK or on any CMK in a different AWS account. For more information about creating CMKs with no key material and then importing key material, see Importing Key Material in the AWS Key Management Service Developer Guide.
Before using this operation, call GetParametersForImport. Its response includes a public key and an import token. Use the public key to encrypt the key material. Then, submit the import token from the same GetParametersForImport
response.
When calling this operation, you must specify the following values:
-
The key ID or key ARN of a CMK with no key material. Its Origin
must be EXTERNAL
.
To create a CMK with no key material, call CreateKey and set the value of its Origin
parameter to EXTERNAL
. To get the Origin
of a CMK, call DescribeKey.)
-
The encrypted key material. To get the public key to encrypt the key material, call GetParametersForImport.
-
The import token that GetParametersForImport returned. You must use a public key and token from the same GetParametersForImport
response.
-
Whether the key material expires and if so, when. If you set an expiration date, AWS KMS deletes the key material from the CMK on the specified date, and the CMK becomes unusable. To use the CMK again, you must reimport the same key material. The only way to change an expiration date is by reimporting the same key material and specifying a new expiration date.
When this operation is successful, the key state of the CMK changes from PendingImport
to Enabled
, and you can use the CMK.
If this operation fails, use the exception to help determine the problem. If the error is related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the CMK and repeat the import procedure. For help, see How To Import Key Material in the AWS Key Management Service Developer Guide.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:ImportKeyMaterial (key policy)
Related operations:
",
- "ListAliases": "Gets a list of aliases in the caller's AWS account and region. For more information about aliases, see CreateAlias.
By default, the ListAliases
operation returns all aliases in the account and region. To get only the aliases associated with a particular customer master key (CMK), use the KeyId
parameter.
The ListAliases
response can include aliases that you created and associated with your customer managed CMKs, and aliases that AWS created and associated with AWS managed CMKs in your account. You can recognize AWS aliases because their names have the format aws/<service-name>
, such as aws/dynamodb
.
The response might also include aliases that have no TargetKeyId
field. These are predefined aliases that AWS has created but has not yet associated with a CMK. Aliases that AWS creates in your account, including predefined aliases, do not count against your AWS KMS aliases quota.
Cross-account use: No. ListAliases
does not return aliases in other AWS accounts.
Required permissions: kms:ListAliases (IAM policy)
For details, see Controlling access to aliases in the AWS Key Management Service Developer Guide.
Related operations:
",
- "ListGrants": "Gets a list of all grants for the specified customer master key (CMK).
You must specify the CMK in all requests. You can filter the grant list by grant ID or grantee principal.
The GranteePrincipal
field in the ListGrants
response usually contains the user or role designated as the grantee principal in the grant. However, when the grantee principal in the grant is an AWS service, the GranteePrincipal
field contains the service principal, which might represent several different grantee principals.
Cross-account use: Yes. To perform this operation on a CMK in a different AWS account, specify the key ARN in the value of the KeyId
parameter.
Required permissions: kms:ListGrants (key policy)
Related operations:
",
- "ListKeyPolicies": "Gets the names of the key policies that are attached to a customer master key (CMK). This operation is designed to get policy names that you can use in a GetKeyPolicy operation. However, the only valid policy name is default
.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:ListKeyPolicies (key policy)
Related operations:
",
- "ListKeys": "Gets a list of all customer master keys (CMKs) in the caller's AWS account and Region.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:ListKeys (IAM policy)
Related operations:
",
- "ListResourceTags": "Returns all tags on the specified customer master key (CMK).
For general information about tags, including the format and syntax, see Tagging AWS resources in the Amazon Web Services General Reference. For information about using tags in AWS KMS, see Tagging keys.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:ListResourceTags (key policy)
Related operations:
",
- "ListRetirableGrants": "Returns information about all grants in the AWS account and Region that have the specified retiring principal. For more information about grants, see Grants in the AWS Key Management Service Developer Guide .
You can specify any principal in your AWS account. The grants that are returned include grants for CMKs in your AWS account and other AWS accounts.
You might use this operation to determine which grants you may retire. To retire a grant, use the RetireGrant operation.
Cross-account use: You must specify a principal in your AWS account. However, this operation can return grants in any AWS account. You do not need kms:ListRetirableGrants
permission (or any other additional permission) in any AWS account other than your own.
Required permissions: kms:ListRetirableGrants (IAM policy) in your AWS account.
Related operations:
",
- "PutKeyPolicy": "Attaches a key policy to the specified customer master key (CMK).
For more information about key policies, see Key Policies in the AWS Key Management Service Developer Guide. For help writing and formatting a JSON policy document, see the IAM JSON Policy Reference in the IAM User Guide . For examples of adding a key policy in multiple programming languages, see Setting a key policy in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:PutKeyPolicy (key policy)
Related operations: GetKeyPolicy
",
- "ReEncrypt": "Decrypts ciphertext and then reencrypts it entirely within AWS KMS. You can use this operation to change the customer master key (CMK) under which data is encrypted, such as when you manually rotate a CMK or change the CMK that protects a ciphertext. You can also use it to reencrypt ciphertext under the same CMK, such as to change the encryption context of a ciphertext.
The ReEncrypt
operation can decrypt ciphertext that was encrypted by using an AWS KMS CMK in an AWS KMS operation, such as Encrypt or GenerateDataKey. It can also decrypt ciphertext that was encrypted by using the public key of an asymmetric CMK outside of AWS KMS. However, it cannot decrypt ciphertext produced by other libraries, such as the AWS Encryption SDK or Amazon S3 client-side encryption. These libraries return a ciphertext format that is incompatible with AWS KMS.
When you use the ReEncrypt
operation, you need to provide information for the decrypt operation and the subsequent encrypt operation.
-
If your ciphertext was encrypted under an asymmetric CMK, you must use the SourceKeyId
parameter to identify the CMK that encrypted the ciphertext. You must also supply the encryption algorithm that was used. This information is required to decrypt the data.
-
If your ciphertext was encrypted under a symmetric CMK, the SourceKeyId
parameter is optional. AWS KMS can get this information from metadata that it adds to the symmetric ciphertext blob. This feature adds durability to your implementation by ensuring that authorized users can decrypt ciphertext decades after it was encrypted, even if they've lost track of the CMK ID. However, specifying the source CMK is always recommended as a best practice. When you use the SourceKeyId
parameter to specify a CMK, AWS KMS uses only the CMK you specify. If the ciphertext was encrypted under a different CMK, the ReEncrypt
operation fails. This practice ensures that you use the CMK that you intend.
-
To reencrypt the data, you must use the DestinationKeyId
parameter specify the CMK that re-encrypts the data after it is decrypted. You can select a symmetric or asymmetric CMK. If the destination CMK is an asymmetric CMK, you must also provide the encryption algorithm. The algorithm that you choose must be compatible with the CMK.
When you use an asymmetric CMK to encrypt or reencrypt data, be sure to record the CMK and encryption algorithm that you choose. You will be required to provide the same CMK and encryption algorithm when you decrypt the data. If the CMK and algorithm do not match the values used to encrypt the data, the decrypt operation fails.
You are not required to supply the CMK ID and encryption algorithm when you decrypt with symmetric CMKs because AWS KMS stores this information in the ciphertext blob. AWS KMS cannot store metadata in ciphertext generated with asymmetric keys. The standard format for asymmetric key ciphertext does not include configurable fields.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. The source CMK and destination CMK can be in different AWS accounts. Either or both CMKs can be in a different account than the caller.
Required permissions:
To permit reencryption from or to a CMK, include the \"kms:ReEncrypt*\"
permission in your key policy. This permission is automatically included in the key policy when you use the console to create a CMK. But you must include it manually when you create a CMK programmatically or when you use the PutKeyPolicy operation to set a key policy.
Related operations:
",
- "ReplicateKey": "Replicates a multi-Region key into the specified Region. This operation creates a multi-Region replica key based on a multi-Region primary key in a different Region of the same AWS partition. You can create multiple replicas of a primary key, but each must be in a different Region. To create a multi-Region primary key, use the CreateKey operation.
This operation supports multi-Region keys, an AWS KMS feature that lets you create multiple interoperable CMKs in different AWS Regions. Because these CMKs have the same key ID, key material, and other metadata, you can use them to encrypt data in one AWS Region and decrypt it in a different AWS Region without making a cross-Region call or exposing the plaintext data. For more information about multi-Region keys, see Using multi-Region keys in the AWS Key Management Service Developer Guide.
A replica key is a fully-functional CMK that can be used independently of its primary and peer replica keys. A primary key and its replica keys share properties that make them interoperable. They have the same key ID and key material. They also have the same key spec, key usage, key material origin, and automatic key rotation status. AWS KMS automatically synchronizes these shared properties among related multi-Region keys. All other properties of a replica key can differ, including its key policy, tags, aliases, and key state. AWS KMS pricing and quotas for CMKs apply to each primary key and replica key.
When this operation completes, the new replica key has a transient key state of Creating
. This key state changes to Enabled
(or PendingImport
) after a few seconds when the process of creating the new replica key is complete. While the key state is Creating
, you can manage key, but you cannot yet use it in cryptographic operations. If you are creating and using the replica key programmatically, retry on KMSInvalidStateException
or call DescribeKey
to check its KeyState
value before using it. For details about the Creating
key state, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
The AWS CloudTrail log of a ReplicateKey
operation records a ReplicateKey
operation in the primary key's Region and a CreateKey operation in the replica key's Region.
If you replicate a multi-Region primary key with imported key material, the replica key is created with no key material. You must import the same key material that you imported into the primary key. For details, see Importing key material into multi-Region keys in the AWS Key Management Service Developer Guide.
To convert a replica key to a primary key, use the UpdatePrimaryRegion operation.
ReplicateKey
uses different default values for the KeyPolicy
and Tags
parameters than those used in the AWS KMS console. For details, see the parameter descriptions.
Cross-account use: No. You cannot use this operation to create a CMK in a different AWS account.
Required permissions:
-
kms:ReplicateKey
on the primary CMK (in the primary CMK's Region). Include this permission in the primary CMK's key policy.
-
kms:CreateKey
in an IAM policy in the replica Region.
-
To use the Tags
parameter, kms:TagResource
in an IAM policy in the replica Region.
Related operations
",
- "RetireGrant": "Deletes a grant. Typically, you retire a grant when you no longer need its permissions. To identify the grant to retire, use a grant token, or both the grant ID and a key identifier (key ID or key ARN) of the customer master key (CMK). The CreateGrant operation returns both values.
This operation can be called by the retiring principal for a grant, by the grantee principal if the grant allows the RetireGrant
operation, and by the AWS account (root user) in which the grant is created. It can also be called by principals to whom permission for retiring a grant is delegated. For details, see Retiring and revoking grants in the AWS Key Management Service Developer Guide.
For detailed information about grants, including grant terminology, see Using grants in the AWS Key Management Service Developer Guide . For examples of working with grants in several programming languages, see Programming grants.
Cross-account use: Yes. You can retire a grant on a CMK in a different AWS account.
Required permissions::Permission to retire a grant is determined primarily by the grant. For details, see Retiring and revoking grants in the AWS Key Management Service Developer Guide.
Related operations:
",
- "RevokeGrant": "Deletes the specified grant. You revoke a grant to terminate the permissions that the grant allows. For more information, see Retiring and revoking grants in the AWS Key Management Service Developer Guide .
When you create, retire, or revoke a grant, there might be a brief delay, usually less than five minutes, until the grant is available throughout AWS KMS. This state is known as eventual consistency. For details, see Eventual consistency in the AWS Key Management Service Developer Guide .
Cross-account use: Yes. To perform this operation on a CMK in a different AWS account, specify the key ARN in the value of the KeyId
parameter.
Required permissions: kms:RevokeGrant (key policy).
Related operations:
",
- "ScheduleKeyDeletion": "Schedules the deletion of a customer master key (CMK). By default, AWS KMS applies a waiting period of 30 days, but you can specify a waiting period of 7-30 days. When this operation is successful, the key state of the CMK changes to PendingDeletion
and the key can't be used in any cryptographic operations. It remains in this state for the duration of the waiting period. Before the waiting period ends, you can use CancelKeyDeletion to cancel the deletion of the CMK. After the waiting period ends, AWS KMS deletes the CMK, its key material, and all AWS KMS data associated with it, including all aliases that refer to it.
Deleting a CMK is a destructive and potentially dangerous operation. When a CMK is deleted, all data that was encrypted under the CMK is unrecoverable. (The only exception is a multi-Region replica key.) To prevent the use of a CMK without deleting it, use DisableKey.
If you schedule deletion of a CMK from a custom key store, when the waiting period expires, ScheduleKeyDeletion
deletes the CMK from AWS KMS. Then AWS KMS makes a best effort to delete the key material from the associated AWS CloudHSM cluster. However, you might need to manually delete the orphaned key material from the cluster and its backups.
You can schedule the deletion of a multi-Region primary key and its replica keys at any time. However, AWS KMS will not delete a multi-Region primary key with existing replica keys. If you schedule the deletion of a primary key with replicas, its key state changes to PendingReplicaDeletion
and it cannot be replicated or used in cryptographic operations. This status can continue indefinitely. When the last of its replicas keys is deleted (not just scheduled), the key state of the primary key changes to PendingDeletion
and its waiting period (PendingWindowInDays
) begins. For details, see Deleting multi-Region keys in the AWS Key Management Service Developer Guide.
For more information about scheduling a CMK for deletion, see Deleting Customer Master Keys in the AWS Key Management Service Developer Guide.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:ScheduleKeyDeletion (key policy)
Related operations
",
- "Sign": "Creates a digital signature for a message or message digest by using the private key in an asymmetric CMK. To verify the signature, use the Verify operation, or use the public key in the same asymmetric CMK outside of AWS KMS. For information about symmetric and asymmetric CMKs, see Using Symmetric and Asymmetric CMKs in the AWS Key Management Service Developer Guide.
Digital signatures are generated and verified by using asymmetric key pair, such as an RSA or ECC pair that is represented by an asymmetric customer master key (CMK). The key owner (or an authorized user) uses their private key to sign a message. Anyone with the public key can verify that the message was signed with that particular private key and that the message hasn't changed since it was signed.
To use the Sign
operation, provide the following information:
-
Use the KeyId
parameter to identify an asymmetric CMK with a KeyUsage
value of SIGN_VERIFY
. To get the KeyUsage
value of a CMK, use the DescribeKey operation. The caller must have kms:Sign
permission on the CMK.
-
Use the Message
parameter to specify the message or message digest to sign. You can submit messages of up to 4096 bytes. To sign a larger message, generate a hash digest of the message, and then provide the hash digest in the Message
parameter. To indicate whether the message is a full message or a digest, use the MessageType
parameter.
-
Choose a signing algorithm that is compatible with the CMK.
When signing a message, be sure to record the CMK and the signing algorithm. This information is required to verify the signature.
To verify the signature that this operation generates, use the Verify operation. Or use the GetPublicKey operation to download the public key and then use the public key to verify the signature outside of AWS KMS.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:Sign (key policy)
Related operations: Verify
",
- "TagResource": "Adds or edits tags on a customer managed CMK.
Tagging or untagging a CMK can allow or deny permission to the CMK. For details, see Using ABAC in AWS KMS in the AWS Key Management Service Developer Guide.
Each tag consists of a tag key and a tag value, both of which are case-sensitive strings. The tag value can be an empty (null) string. To add a tag, specify a new tag key and a tag value. To edit a tag, specify an existing tag key and a new tag value.
You can use this operation to tag a customer managed CMK, but you cannot tag an AWS managed CMK, an AWS owned CMK, a custom key store, or an alias.
You can also add tags to a CMK while creating it (CreateKey) or replicating it (ReplicateKey).
For information about using tags in AWS KMS, see Tagging keys. For general information about tags, including the format and syntax, see Tagging AWS resources in the Amazon Web Services General Reference.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:TagResource (key policy)
Related operations
",
- "UntagResource": "Deletes tags from a customer managed CMK. To delete a tag, specify the tag key and the CMK.
Tagging or untagging a CMK can allow or deny permission to the CMK. For details, see Using ABAC in AWS KMS in the AWS Key Management Service Developer Guide.
When it succeeds, the UntagResource
operation doesn't return any output. Also, if the specified tag key isn't found on the CMK, it doesn't throw an exception or return a response. To confirm that the operation worked, use the ListResourceTags operation.
For information about using tags in AWS KMS, see Tagging keys. For general information about tags, including the format and syntax, see Tagging AWS resources in the Amazon Web Services General Reference.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:UntagResource (key policy)
Related operations
",
- "UpdateAlias": "Associates an existing AWS KMS alias with a different customer master key (CMK). Each alias is associated with only one CMK at a time, although a CMK can have multiple aliases. The alias and the CMK must be in the same AWS account and Region.
Adding, deleting, or updating an alias can allow or deny permission to the CMK. For details, see Using ABAC in AWS KMS in the AWS Key Management Service Developer Guide.
The current and new CMK must be the same type (both symmetric or both asymmetric), and they must have the same key usage (ENCRYPT_DECRYPT
or SIGN_VERIFY
). This restriction prevents errors in code that uses aliases. If you must assign an alias to a different type of CMK, use DeleteAlias to delete the old alias and CreateAlias to create a new alias.
You cannot use UpdateAlias
to change an alias name. To change an alias name, use DeleteAlias to delete the old alias and CreateAlias to create a new alias.
Because an alias is not a property of a CMK, you can create, update, and delete the aliases of a CMK without affecting the CMK. Also, aliases do not appear in the response from the DescribeKey operation. To get the aliases of all CMKs in the account, use the ListAliases operation.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions
For details, see Controlling access to aliases in the AWS Key Management Service Developer Guide.
Related operations:
",
- "UpdateCustomKeyStore": "Changes the properties of a custom key store. Use the CustomKeyStoreId
parameter to identify the custom key store you want to edit. Use the remaining parameters to change the properties of the custom key store.
You can only update a custom key store that is disconnected. To disconnect the custom key store, use DisconnectCustomKeyStore. To reconnect the custom key store after the update completes, use ConnectCustomKeyStore. To find the connection state of a custom key store, use the DescribeCustomKeyStores operation.
Use the parameters of UpdateCustomKeyStore
to edit your keystore settings.
-
Use the NewCustomKeyStoreName parameter to change the friendly name of the custom key store to the value that you specify.
-
Use the KeyStorePassword parameter tell AWS KMS the current password of the kmsuser
crypto user (CU) in the associated AWS CloudHSM cluster. You can use this parameter to fix connection failures that occur when AWS KMS cannot log into the associated cluster because the kmsuser
password has changed. This value does not change the password in the AWS CloudHSM cluster.
-
Use the CloudHsmClusterId parameter to associate the custom key store with a different, but related, AWS CloudHSM cluster. You can use this parameter to repair a custom key store if its AWS CloudHSM cluster becomes corrupted or is deleted, or when you need to create or restore a cluster from a backup.
If the operation succeeds, it returns a JSON object with no properties.
This operation is part of the Custom Key Store feature feature in AWS KMS, which combines the convenience and extensive integration of AWS KMS with the isolation and control of a single-tenant key store.
Cross-account use: No. You cannot perform this operation on a custom key store in a different AWS account.
Required permissions: kms:UpdateCustomKeyStore (IAM policy)
Related operations:
",
- "UpdateKeyDescription": "Updates the description of a customer master key (CMK). To see the description of a CMK, use DescribeKey.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a CMK in a different AWS account.
Required permissions: kms:UpdateKeyDescription (key policy)
Related operations
",
- "UpdatePrimaryRegion": "Changes the primary key of a multi-Region key.
This operation changes the replica key in the specified Region to a primary key and changes the former primary key to a replica key. For example, suppose you have a primary key in us-east-1
and a replica key in eu-west-2
. If you run UpdatePrimaryRegion
with a PrimaryRegion
value of eu-west-2
, the primary key is now the key in eu-west-2
, and the key in us-east-1
becomes a replica key. For details, see
This operation supports multi-Region keys, an AWS KMS feature that lets you create multiple interoperable CMKs in different AWS Regions. Because these CMKs have the same key ID, key material, and other metadata, you can use them to encrypt data in one AWS Region and decrypt it in a different AWS Region without making a cross-Region call or exposing the plaintext data. For more information about multi-Region keys, see Using multi-Region keys in the AWS Key Management Service Developer Guide.
The primary key of a multi-Region key is the source for properties that are always shared by primary and replica keys, including the key material, key ID, key spec, key usage, key material origin, and automatic key rotation. It's the only key that can be replicated. You cannot delete the primary key until all replicas are deleted.
The key ID and primary Region that you specify uniquely identify the replica key that will become the primary key. The primary Region must already have a replica key. This operation does not create a CMK in the specified Region. To find the replica keys, use the DescribeKey operation on the primary key or any replica key. To create a replica key, use the ReplicateKey operation.
You can run this operation while using the affected multi-Region keys in cryptographic operations. This operation should not delay, interrupt, or cause failures in cryptographic operations.
Even after this operation completes, the process of updating the primary Region might still be in progress for a few more seconds. Operations such as DescribeKey
might display both the old and new primary keys as replicas. The old and new primary keys have a transient key state of Updating
. The original key state is restored when the update is complete. While the key state is Updating
, you can use the keys in cryptographic operations, but you cannot replicate the new primary key or perform certain management operations, such as enabling or disabling these keys. For details about the Updating
key state, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
This operation does not return any output. To verify that primary key is changed, use the DescribeKey operation.
Cross-account use: No. You cannot use this operation in a different AWS account.
Required permissions:
-
kms:UpdatePrimaryRegion
on the current primary CMK (in the primary CMK's Region). Include this permission primary CMK's key policy.
-
kms:UpdatePrimaryRegion
on the current replica CMK (in the replica CMK's Region). Include this permission in the replica CMK's key policy.
Related operations
",
- "Verify": "Verifies a digital signature that was generated by the Sign operation.
Verification confirms that an authorized user signed the message with the specified CMK and signing algorithm, and the message hasn't changed since it was signed. If the signature is verified, the value of the SignatureValid
field in the response is True
. If the signature verification fails, the Verify
operation fails with an KMSInvalidSignatureException
exception.
A digital signature is generated by using the private key in an asymmetric CMK. The signature is verified by using the public key in the same asymmetric CMK. For information about symmetric and asymmetric CMKs, see Using Symmetric and Asymmetric CMKs in the AWS Key Management Service Developer Guide.
To verify a digital signature, you can use the Verify
operation. Specify the same asymmetric CMK, message, and signing algorithm that were used to produce the signature.
You can also verify the digital signature by using the public key of the CMK outside of AWS KMS. Use the GetPublicKey operation to download the public key in the asymmetric CMK and then use the public key to verify the signature outside of AWS KMS. The advantage of using the Verify
operation is that it is performed within AWS KMS. As a result, it's easy to call, the operation is performed within the FIPS boundary, it is logged in AWS CloudTrail, and you can use key policy and IAM policy to determine who is authorized to use the CMK to verify signatures.
The CMK that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a CMK in a different AWS account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:Verify (key policy)
Related operations: Sign
"
+ "CancelKeyDeletion": "Cancels the deletion of a KMS key. When this operation succeeds, the key state of the KMS key is Disabled
. To enable the KMS key, use EnableKey.
For more information about scheduling and canceling deletion of a KMS key, see Deleting KMS keys in the Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:CancelKeyDeletion (key policy)
Related operations: ScheduleKeyDeletion
",
+ "ConnectCustomKeyStore": "Connects or reconnects a custom key store to its associated CloudHSM cluster.
The custom key store must be connected before you can create KMS keys in the key store or use the KMS keys it contains. You can disconnect and reconnect a custom key store at any time.
To connect a custom key store, its associated CloudHSM cluster must have at least one active HSM. To get the number of active HSMs in a cluster, use the DescribeClusters operation. To add HSMs to the cluster, use the CreateHsm operation. Also, the kmsuser
crypto user (CU) must not be logged into the cluster. This prevents KMS from using this account to log in.
The connection process can take an extended amount of time to complete; up to 20 minutes. This operation starts the connection process, but it does not wait for it to complete. When it succeeds, this operation quickly returns an HTTP 200 response and a JSON object with no properties. However, this response does not indicate that the custom key store is connected. To get the connection state of the custom key store, use the DescribeCustomKeyStores operation.
During the connection process, KMS finds the CloudHSM cluster that is associated with the custom key store, creates the connection infrastructure, connects to the cluster, logs into the CloudHSM client as the kmsuser
CU, and rotates its password.
The ConnectCustomKeyStore
operation might fail for various reasons. To find the reason, use the DescribeCustomKeyStores operation and see the ConnectionErrorCode
in the response. For help interpreting the ConnectionErrorCode
, see CustomKeyStoresListEntry.
To fix the failure, use the DisconnectCustomKeyStore operation to disconnect the custom key store, correct the error, use the UpdateCustomKeyStore operation if necessary, and then use ConnectCustomKeyStore
again.
If you are having trouble connecting or disconnecting a custom key store, see Troubleshooting a Custom Key Store in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account.
Required permissions: kms:ConnectCustomKeyStore (IAM policy)
Related operations
",
+ "CreateAlias": "Creates a friendly name for a KMS key.
Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see Using ABAC in KMS in the Key Management Service Developer Guide.
You can use an alias to identify a KMS key in the KMS console, in the DescribeKey operation and in cryptographic operations, such as Encrypt and GenerateDataKey. You can also change the KMS key that's associated with the alias (UpdateAlias) or delete the alias (DeleteAlias) at any time. These operations don't affect the underlying KMS key.
You can associate the alias with any customer managed key in the same Amazon Web Services Region. Each alias is associated with only one KMS key at a time, but a KMS key can have multiple aliases. A valid KMS key is required. You can't create an alias without a KMS key.
The alias must be unique in the account and Region, but you can have aliases with the same name in different Regions. For detailed information about aliases, see Using aliases in the Key Management Service Developer Guide.
This operation does not return a response. To get the alias that you created, use the ListAliases operation.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on an alias in a different Amazon Web Services account.
Required permissions
For details, see Controlling access to aliases in the Key Management Service Developer Guide.
Related operations:
",
+ "CreateCustomKeyStore": "Creates a custom key store that is associated with an CloudHSM cluster that you own and manage.
This operation is part of the Custom Key Store feature feature in KMS, which combines the convenience and extensive integration of KMS with the isolation and control of a single-tenant key store.
Before you create the custom key store, you must assemble the required elements, including an CloudHSM cluster that fulfills the requirements for a custom key store. For details about the required elements, see Assemble the Prerequisites in the Key Management Service Developer Guide.
When the operation completes successfully, it returns the ID of the new custom key store. Before you can use your new custom key store, you need to use the ConnectCustomKeyStore operation to connect the new key store to its CloudHSM cluster. Even if you are not going to use your custom key store immediately, you might want to connect it to verify that all settings are correct and then disconnect it until you are ready to use it.
For help with failures, see Troubleshooting a Custom Key Store in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account.
Required permissions: kms:CreateCustomKeyStore (IAM policy).
Related operations:
",
+ "CreateGrant": "Adds a grant to a KMS key.
A grant is a policy instrument that allows Amazon Web Services principals to use KMS keys in cryptographic operations. It also can allow them to view a KMS key (DescribeKey) and create and manage grants. When authorizing access to a KMS key, grants are considered along with key policies and IAM policies. Grants are often used for temporary permissions because you can create one, use its permissions, and delete it without changing your key policies or IAM policies.
For detailed information about grants, including grant terminology, see Using grants in the Key Management Service Developer Guide . For examples of working with grants in several programming languages, see Programming grants.
The CreateGrant
operation returns a GrantToken
and a GrantId
.
-
When you create, retire, or revoke a grant, there might be a brief delay, usually less than five minutes, until the grant is available throughout KMS. This state is known as eventual consistency. Once the grant has achieved eventual consistency, the grantee principal can use the permissions in the grant without identifying the grant.
However, to use the permissions in the grant immediately, use the GrantToken
that CreateGrant
returns. For details, see Using a grant token in the Key Management Service Developer Guide .
-
The CreateGrant
operation also returns a GrantId
. You can use the GrantId
and a key identifier to identify the grant in the RetireGrant and RevokeGrant operations. To find the grant ID, use the ListGrants or ListRetirableGrants operations.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key ARN in the value of the KeyId
parameter.
Required permissions: kms:CreateGrant (key policy)
Related operations:
",
+ "CreateKey": "Creates a unique customer managed KMS key in your Amazon Web Services account and Region.
KMS is replacing the term customer master key (CMK) with KMS key and KMS key. The concept has not changed. To prevent breaking changes, KMS is keeping some variations of this term.
You can use the CreateKey
operation to create symmetric or asymmetric KMS keys.
-
Symmetric KMS keys contain a 256-bit symmetric key that never leaves KMS unencrypted. To use the KMS key, you must call KMS. You can use a symmetric KMS key to encrypt and decrypt small amounts of data, but they are typically used to generate data keys and data keys pairs. For details, see GenerateDataKey and GenerateDataKeyPair.
-
Asymmetric KMS keys can contain an RSA key pair or an Elliptic Curve (ECC) key pair. The private key in an asymmetric KMS key never leaves KMS unencrypted. However, you can use the GetPublicKey operation to download the public key so it can be used outside of KMS. KMS keys with RSA key pairs can be used to encrypt or decrypt data or sign and verify messages (but not both). KMS keys with ECC key pairs can be used only to sign and verify messages.
For information about symmetric and asymmetric KMS keys, see Using Symmetric and Asymmetric KMS keys in the Key Management Service Developer Guide.
To create different types of KMS keys, use the following guidance:
- Asymmetric KMS keys
-
To create an asymmetric KMS key, use the KeySpec
parameter to specify the type of key material in the KMS key. Then, use the KeyUsage
parameter to determine whether the KMS key will be used to encrypt and decrypt or sign and verify. You can't change these properties after the KMS key is created.
- Symmetric KMS keys
-
When creating a symmetric KMS key, you don't need to specify the KeySpec
or KeyUsage
parameters. The default value for KeySpec
, SYMMETRIC_DEFAULT
, and the default value for KeyUsage
, ENCRYPT_DECRYPT
, are the only valid values for symmetric KMS keys.
- Multi-Region primary keys
- Imported key material
-
To create a multi-Region primary key in the local Amazon Web Services Region, use the MultiRegion
parameter with a value of True
. To create a multi-Region replica key, that is, a KMS key with the same key ID and key material as a primary key, but in a different Amazon Web Services Region, use the ReplicateKey operation. To change a replica key to a primary key, and its primary key to a replica key, use the UpdatePrimaryRegion operation.
This operation supports multi-Region keys, an KMS feature that lets you create multiple interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
You can create symmetric and asymmetric multi-Region keys and multi-Region keys with imported key material. You cannot create multi-Region keys in a custom key store.
-
To import your own key material, begin by creating a symmetric KMS key with no key material. To do this, use the Origin
parameter of CreateKey
with a value of EXTERNAL
. Next, use GetParametersForImport operation to get a public key and import token, and use the public key to encrypt your key material. Then, use ImportKeyMaterial with your import token to import the key material. For step-by-step instructions, see Importing Key Material in the Key Management Service Developer Guide . You cannot import the key material into an asymmetric KMS key.
To create a multi-Region primary key with imported key material, use the Origin
parameter of CreateKey
with a value of EXTERNAL
and the MultiRegion
parameter with a value of True
. To create replicas of the multi-Region primary key, use the ReplicateKey operation. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
- Custom key store
-
To create a symmetric KMS key in a custom key store, use the CustomKeyStoreId
parameter to specify the custom key store. You must also use the Origin
parameter with a value of AWS_CLOUDHSM
. The CloudHSM cluster that is associated with the custom key store must have at least two active HSMs in different Availability Zones in the Amazon Web Services Region.
You cannot create an asymmetric KMS key in a custom key store. For information about custom key stores in KMS see Using Custom Key Stores in the Key Management Service Developer Guide .
Cross-account use: No. You cannot use this operation to create a KMS key in a different Amazon Web Services account.
Required permissions: kms:CreateKey (IAM policy). To use the Tags
parameter, kms:TagResource (IAM policy). For examples and information about related permissions, see Allow a user to create KMS keys in the Key Management Service Developer Guide.
Related operations:
",
+ "Decrypt": "Decrypts ciphertext that was encrypted by a KMS key using any of the following operations:
You can use this operation to decrypt ciphertext that was encrypted under a symmetric or asymmetric KMS key. When the KMS key is asymmetric, you must specify the KMS key and the encryption algorithm that was used to encrypt the ciphertext. For information about symmetric and asymmetric KMS keys, see Using Symmetric and Asymmetric KMS keys in the Key Management Service Developer Guide.
The Decrypt operation also decrypts ciphertext that was encrypted outside of KMS by the public key in an KMS asymmetric KMS key. However, it cannot decrypt ciphertext produced by other libraries, such as the Amazon Web Services Encryption SDK or Amazon S3 client-side encryption. These libraries return a ciphertext format that is incompatible with KMS.
If the ciphertext was encrypted under a symmetric KMS key, the KeyId
parameter is optional. KMS can get this information from metadata that it adds to the symmetric ciphertext blob. This feature adds durability to your implementation by ensuring that authorized users can decrypt ciphertext decades after it was encrypted, even if they've lost track of the key ID. However, specifying the KMS key is always recommended as a best practice. When you use the KeyId
parameter to specify a KMS key, KMS only uses the KMS key you specify. If the ciphertext was encrypted under a different KMS key, the Decrypt
operation fails. This practice ensures that you use the KMS key that you intend.
Whenever possible, use key policies to give users permission to call the Decrypt
operation on a particular KMS key, instead of using IAM policies. Otherwise, you might create an IAM user policy that gives the user Decrypt
permission on all KMS keys. This user could decrypt ciphertext that was encrypted by KMS keys in other accounts if the key policy for the cross-account KMS key permits it. If you must use an IAM policy for Decrypt
permissions, limit the user to particular KMS keys or particular trusted accounts. For details, see Best practices for IAM policies in the Key Management Service Developer Guide.
Applications in Amazon Web Services Nitro Enclaves can call this operation by using the Amazon Web Services Nitro Enclaves Development Kit. For information about the supporting parameters, see How Amazon Web Services Nitro Enclaves use KMS in the Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:Decrypt (key policy)
Related operations:
",
+ "DeleteAlias": "Deletes the specified alias.
Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see Using ABAC in KMS in the Key Management Service Developer Guide.
Because an alias is not a property of a KMS key, you can delete and change the aliases of a KMS key without affecting the KMS key. Also, aliases do not appear in the response from the DescribeKey operation. To get the aliases of all KMS keys, use the ListAliases operation.
Each KMS key can have multiple aliases. To change the alias of a KMS key, use DeleteAlias to delete the current alias and CreateAlias to create a new alias. To associate an existing alias with a different KMS key, call UpdateAlias.
Cross-account use: No. You cannot perform this operation on an alias in a different Amazon Web Services account.
Required permissions
For details, see Controlling access to aliases in the Key Management Service Developer Guide.
Related operations:
",
+ "DeleteCustomKeyStore": "Deletes a custom key store. This operation does not delete the CloudHSM cluster that is associated with the custom key store, or affect any users or keys in the cluster.
The custom key store that you delete cannot contain any KMS KMS keys. Before deleting the key store, verify that you will never need to use any of the KMS keys in the key store for any cryptographic operations. Then, use ScheduleKeyDeletion to delete the KMS keys from the key store. When the scheduled waiting period expires, the ScheduleKeyDeletion
operation deletes the KMS keys. Then it makes a best effort to delete the key material from the associated cluster. However, you might need to manually delete the orphaned key material from the cluster and its backups.
After all KMS keys are deleted from KMS, use DisconnectCustomKeyStore to disconnect the key store from KMS. Then, you can delete the custom key store.
Instead of deleting the custom key store, consider using DisconnectCustomKeyStore to disconnect it from KMS. While the key store is disconnected, you cannot create or use the KMS keys in the key store. But, you do not need to delete KMS keys and you can reconnect a disconnected custom key store at any time.
If the operation succeeds, it returns a JSON object with no properties.
This operation is part of the Custom Key Store feature feature in KMS, which combines the convenience and extensive integration of KMS with the isolation and control of a single-tenant key store.
Cross-account use: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account.
Required permissions: kms:DeleteCustomKeyStore (IAM policy)
Related operations:
",
+ "DeleteImportedKeyMaterial": "Deletes key material that you previously imported. This operation makes the specified KMS key unusable. For more information about importing key material into KMS, see Importing Key Material in the Key Management Service Developer Guide.
When the specified KMS key is in the PendingDeletion
state, this operation does not change the KMS key's state. Otherwise, it changes the KMS key's state to PendingImport
.
After you delete key material, you can use ImportKeyMaterial to reimport the same key material into the KMS key.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:DeleteImportedKeyMaterial (key policy)
Related operations:
",
+ "DescribeCustomKeyStores": "Gets information about custom key stores in the account and Region.
This operation is part of the Custom Key Store feature feature in KMS, which combines the convenience and extensive integration of KMS with the isolation and control of a single-tenant key store.
By default, this operation returns information about all custom key stores in the account and Region. To get only information about a particular custom key store, use either the CustomKeyStoreName
or CustomKeyStoreId
parameter (but not both).
To determine whether the custom key store is connected to its CloudHSM cluster, use the ConnectionState
element in the response. If an attempt to connect the custom key store failed, the ConnectionState
value is FAILED
and the ConnectionErrorCode
element in the response indicates the cause of the failure. For help interpreting the ConnectionErrorCode
, see CustomKeyStoresListEntry.
Custom key stores have a DISCONNECTED
connection state if the key store has never been connected or you use the DisconnectCustomKeyStore operation to disconnect it. If your custom key store state is CONNECTED
but you are having trouble using it, make sure that its associated CloudHSM cluster is active and contains the minimum number of HSMs required for the operation, if any.
For help repairing your custom key store, see the Troubleshooting Custom Key Stores topic in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account.
Required permissions: kms:DescribeCustomKeyStores (IAM policy)
Related operations:
",
+ "DescribeKey": "Provides detailed information about a KMS key. You can run DescribeKey
on a customer managed key or an Amazon Web Services managed key.
This detailed information includes the key ARN, creation date (and deletion date, if applicable), the key state, and the origin and expiration date (if any) of the key material. It includes fields, like KeySpec
, that help you distinguish symmetric from asymmetric KMS keys. It also provides information that is particularly important to asymmetric keys, such as the key usage (encryption or signing) and the encryption algorithms or signing algorithms that the KMS key supports. For KMS keys in custom key stores, it includes information about the custom key store, such as the key store ID and the CloudHSM cluster ID. For multi-Region keys, it displays the primary key and all related replica keys.
DescribeKey
does not return the following information:
-
Aliases associated with the KMS key. To get this information, use ListAliases.
-
Whether automatic key rotation is enabled on the KMS key. To get this information, use GetKeyRotationStatus. Also, some key states prevent a KMS key from being automatically rotated. For details, see How Automatic Key Rotation Works in Key Management Service Developer Guide.
-
Tags on the KMS key. To get this information, use ListResourceTags.
-
Key policies and grants on the KMS key. To get this information, use GetKeyPolicy and ListGrants.
If you call the DescribeKey
operation on a predefined Amazon Web Services alias, that is, an Amazon Web Services alias with no key ID, KMS creates an Amazon Web Services managed key. Then, it associates the alias with the new KMS key, and returns the KeyId
and Arn
of the new KMS key in the response.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:DescribeKey (key policy)
Related operations:
",
+ "DisableKey": "Sets the state of a KMS key to disabled. This change temporarily prevents use of the KMS key for cryptographic operations.
For more information about how key state affects the use of a KMS key, see Key state: Effect on your KMS key in the Key Management Service Developer Guide .
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:DisableKey (key policy)
Related operations: EnableKey
",
+ "DisableKeyRotation": "Disables automatic rotation of the key material for the specified symmetric KMS key.
You cannot enable automatic rotation of asymmetric KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:DisableKeyRotation (key policy)
Related operations:
",
+ "DisconnectCustomKeyStore": "Disconnects the custom key store from its associated CloudHSM cluster. While a custom key store is disconnected, you can manage the custom key store and its KMS keys, but you cannot create or use KMS keys in the custom key store. You can reconnect the custom key store at any time.
While a custom key store is disconnected, all attempts to create KMS keys in the custom key store or to use existing KMS keys in cryptographic operations will fail. This action can prevent users from storing and accessing sensitive data.
To find the connection state of a custom key store, use the DescribeCustomKeyStores operation. To reconnect a custom key store, use the ConnectCustomKeyStore operation.
If the operation succeeds, it returns a JSON object with no properties.
This operation is part of the Custom Key Store feature feature in KMS, which combines the convenience and extensive integration of KMS with the isolation and control of a single-tenant key store.
Cross-account use: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account.
Required permissions: kms:DisconnectCustomKeyStore (IAM policy)
Related operations:
",
+ "EnableKey": "Sets the key state of a KMS key to enabled. This allows you to use the KMS key for cryptographic operations.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:EnableKey (key policy)
Related operations: DisableKey
",
+ "EnableKeyRotation": "Enables automatic rotation of the key material for the specified symmetric KMS key.
You cannot enable automatic rotation of asymmetric KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:EnableKeyRotation (key policy)
Related operations:
",
+ "Encrypt": "Encrypts plaintext into ciphertext by using a KMS key. The Encrypt
operation has two primary use cases:
-
You can encrypt small amounts of arbitrary data, such as a personal identifier or database password, or other sensitive information.
-
You can use the Encrypt
operation to move encrypted data from one Amazon Web Services Region to another. For example, in Region A, generate a data key and use the plaintext key to encrypt your data. Then, in Region A, use the Encrypt
operation to encrypt the plaintext data key under a KMS key in Region B. Now, you can move the encrypted data and the encrypted data key to Region B. When necessary, you can decrypt the encrypted data key and the encrypted data entirely within in Region B.
You don't need to use the Encrypt
operation to encrypt a data key. The GenerateDataKey and GenerateDataKeyPair operations return a plaintext data key and an encrypted copy of that data key.
When you encrypt data, you must specify a symmetric or asymmetric KMS key to use in the encryption operation. The KMS key must have a KeyUsage
value of ENCRYPT_DECRYPT.
To find the KeyUsage
of a KMS key, use the DescribeKey operation.
If you use a symmetric KMS key, you can use an encryption context to add additional security to your encryption operation. If you specify an EncryptionContext
when encrypting data, you must specify the same encryption context (a case-sensitive exact match) when decrypting the data. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the Key Management Service Developer Guide.
If you specify an asymmetric KMS key, you must also specify the encryption algorithm. The algorithm must be compatible with the KMS key type.
When you use an asymmetric KMS key to encrypt or reencrypt data, be sure to record the KMS key and encryption algorithm that you choose. You will be required to provide the same KMS key and encryption algorithm when you decrypt the data. If the KMS key and algorithm do not match the values used to encrypt the data, the decrypt operation fails.
You are not required to supply the key ID and encryption algorithm when you decrypt with symmetric KMS keys because KMS stores this information in the ciphertext blob. KMS cannot store metadata in ciphertext generated with asymmetric keys. The standard format for asymmetric key ciphertext does not include configurable fields.
The maximum size of the data that you can encrypt varies with the type of KMS key and the encryption algorithm that you choose.
-
Symmetric KMS keys
-
RSA_2048
-
RSA_3072
-
RSA_4096
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:Encrypt (key policy)
Related operations:
",
+ "GenerateDataKey": "Generates a unique symmetric data key for client-side encryption. This operation returns a plaintext copy of the data key and a copy that is encrypted under a KMS key that you specify. You can use the plaintext key to encrypt your data outside of KMS and store the encrypted data key with the encrypted data.
GenerateDataKey
returns a unique data key for each request. The bytes in the plaintext key are not related to the caller or the KMS key.
To generate a data key, specify the symmetric KMS key that will be used to encrypt the data key. You cannot use an asymmetric KMS key to generate data keys. To get the type of your KMS key, use the DescribeKey operation. You must also specify the length of the data key. Use either the KeySpec
or NumberOfBytes
parameters (but not both). For 128-bit and 256-bit data keys, use the KeySpec
parameter.
To get only an encrypted copy of the data key, use GenerateDataKeyWithoutPlaintext. To generate an asymmetric data key pair, use the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext operation. To get a cryptographically secure random byte string, use GenerateRandom.
You can use the optional encryption context to add additional security to the encryption operation. If you specify an EncryptionContext
, you must specify the same encryption context (a case-sensitive exact match) when decrypting the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the Key Management Service Developer Guide.
Applications in Amazon Web Services Nitro Enclaves can call this operation by using the Amazon Web Services Nitro Enclaves Development Kit. For information about the supporting parameters, see How Amazon Web Services Nitro Enclaves use KMS in the Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
How to use your data key
We recommend that you use the following pattern to encrypt data locally in your application. You can write your own code or use a client-side encryption library, such as the Amazon Web Services Encryption SDK, the Amazon DynamoDB Encryption Client, or Amazon S3 client-side encryption to do these tasks for you.
To encrypt data outside of KMS:
-
Use the GenerateDataKey
operation to get a data key.
-
Use the plaintext data key (in the Plaintext
field of the response) to encrypt your data outside of KMS. Then erase the plaintext data key from memory.
-
Store the encrypted data key (in the CiphertextBlob
field of the response) with the encrypted data.
To decrypt data outside of KMS:
-
Use the Decrypt operation to decrypt the encrypted data key. The operation returns a plaintext copy of the data key.
-
Use the plaintext data key to decrypt data outside of KMS, then erase the plaintext data key from memory.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GenerateDataKey (key policy)
Related operations:
",
+ "GenerateDataKeyPair": "Generates a unique asymmetric data key pair. The GenerateDataKeyPair
operation returns a plaintext public key, a plaintext private key, and a copy of the private key that is encrypted under the symmetric KMS key you specify. You can use the data key pair to perform asymmetric cryptography and implement digital signatures outside of KMS.
You can use the public key that GenerateDataKeyPair
returns to encrypt data or verify a signature outside of KMS. Then, store the encrypted private key with the data. When you are ready to decrypt data or sign a message, you can use the Decrypt operation to decrypt the encrypted private key.
To generate a data key pair, you must specify a symmetric KMS key to encrypt the private key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a custom key store. To get the type and origin of your KMS key, use the DescribeKey operation.
Use the KeyPairSpec
parameter to choose an RSA or Elliptic Curve (ECC) data key pair. KMS recommends that your use ECC key pairs for signing, and use RSA key pairs for either encryption or signing, but not both. However, KMS cannot enforce any restrictions on the use of data key pairs outside of KMS.
If you are using the data key pair to encrypt data, or for any operation where you don't immediately need a private key, consider using the GenerateDataKeyPairWithoutPlaintext operation. GenerateDataKeyPairWithoutPlaintext
returns a plaintext public key and an encrypted private key, but omits the plaintext private key that you need only to decrypt ciphertext or sign a message. Later, when you need to decrypt the data or sign a message, use the Decrypt operation to decrypt the encrypted private key in the data key pair.
GenerateDataKeyPair
returns a unique data key pair for each request. The bytes in the keys are not related to the caller or the KMS key that is used to encrypt the private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as specified in RFC 5280. The private key is a DER-encoded PKCS8 PrivateKeyInfo, as specified in RFC 5958.
You can use the optional encryption context to add additional security to the encryption operation. If you specify an EncryptionContext
, you must specify the same encryption context (a case-sensitive exact match) when decrypting the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GenerateDataKeyPair (key policy)
Related operations:
",
+ "GenerateDataKeyPairWithoutPlaintext": "Generates a unique asymmetric data key pair. The GenerateDataKeyPairWithoutPlaintext
operation returns a plaintext public key and a copy of the private key that is encrypted under the symmetric KMS key you specify. Unlike GenerateDataKeyPair, this operation does not return a plaintext private key.
You can use the public key that GenerateDataKeyPairWithoutPlaintext
returns to encrypt data or verify a signature outside of KMS. Then, store the encrypted private key with the data. When you are ready to decrypt data or sign a message, you can use the Decrypt operation to decrypt the encrypted private key.
To generate a data key pair, you must specify a symmetric KMS key to encrypt the private key in a data key pair. You cannot use an asymmetric KMS key or a KMS key in a custom key store. To get the type and origin of your KMS key, use the DescribeKey operation.
Use the KeyPairSpec
parameter to choose an RSA or Elliptic Curve (ECC) data key pair. KMS recommends that your use ECC key pairs for signing, and use RSA key pairs for either encryption or signing, but not both. However, KMS cannot enforce any restrictions on the use of data key pairs outside of KMS.
GenerateDataKeyPairWithoutPlaintext
returns a unique data key pair for each request. The bytes in the key are not related to the caller or KMS key that is used to encrypt the private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo, as specified in RFC 5280.
You can use the optional encryption context to add additional security to the encryption operation. If you specify an EncryptionContext
, you must specify the same encryption context (a case-sensitive exact match) when decrypting the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GenerateDataKeyPairWithoutPlaintext (key policy)
Related operations:
",
+ "GenerateDataKeyWithoutPlaintext": "Generates a unique symmetric data key. This operation returns a data key that is encrypted under a KMS key that you specify. To request an asymmetric data key pair, use the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext operations.
GenerateDataKeyWithoutPlaintext
is identical to the GenerateDataKey operation except that returns only the encrypted copy of the data key. This operation is useful for systems that need to encrypt data at some point, but not immediately. When you need to encrypt the data, you call the Decrypt operation on the encrypted copy of the key.
It's also useful in distributed systems with different levels of trust. For example, you might store encrypted data in containers. One component of your system creates new containers and stores an encrypted data key with each container. Then, a different component puts the data into the containers. That component first decrypts the data key, uses the plaintext data key to encrypt data, puts the encrypted data into the container, and then destroys the plaintext data key. In this system, the component that creates the containers never sees the plaintext data key.
GenerateDataKeyWithoutPlaintext
returns a unique data key for each request. The bytes in the keys are not related to the caller or KMS key that is used to encrypt the private key.
To generate a data key, you must specify the symmetric KMS key that is used to encrypt the data key. You cannot use an asymmetric KMS key to generate a data key. To get the type of your KMS key, use the DescribeKey operation.
If the operation succeeds, you will find the encrypted copy of the data key in the CiphertextBlob
field.
You can use the optional encryption context to add additional security to the encryption operation. If you specify an EncryptionContext
, you must specify the same encryption context (a case-sensitive exact match) when decrypting the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException
. For more information, see Encryption Context in the Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GenerateDataKeyWithoutPlaintext (key policy)
Related operations:
",
+ "GenerateRandom": "Returns a random byte string that is cryptographically secure.
By default, the random byte string is generated in KMS. To generate the byte string in the CloudHSM cluster that is associated with a custom key store, specify the custom key store ID.
Applications in Amazon Web Services Nitro Enclaves can call this operation by using the Amazon Web Services Nitro Enclaves Development Kit. For information about the supporting parameters, see How Amazon Web Services Nitro Enclaves use KMS in the Key Management Service Developer Guide.
For more information about entropy and random number generation, see Key Management Service Cryptographic Details.
Required permissions: kms:GenerateRandom (IAM policy)
",
+ "GetKeyPolicy": "Gets a key policy attached to the specified KMS key.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:GetKeyPolicy (key policy)
Related operations: PutKeyPolicy
",
+ "GetKeyRotationStatus": "Gets a Boolean value that indicates whether automatic rotation of the key material is enabled for the specified KMS key.
You cannot enable automatic rotation of asymmetric KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key. The key rotation status for these KMS keys is always false
.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
-
Disabled: The key rotation status does not change when you disable a KMS key. However, while the KMS key is disabled, KMS does not rotate the key material.
-
Pending deletion: While a KMS key is pending deletion, its key rotation status is false
and KMS does not rotate the key material. If you cancel the deletion, the original key rotation status is restored.
Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key ARN in the value of the KeyId
parameter.
Required permissions: kms:GetKeyRotationStatus (key policy)
Related operations:
",
+ "GetParametersForImport": "Returns the items you need to import key material into a symmetric, customer managed KMS key. For more information about importing key material into KMS, see Importing Key Material in the Key Management Service Developer Guide.
This operation returns a public key and an import token. Use the public key to encrypt the symmetric key material. Store the import token to send with a subsequent ImportKeyMaterial request.
You must specify the key ID of the symmetric KMS key into which you will import key material. This KMS key's Origin
must be EXTERNAL
. You must also specify the wrapping algorithm and type of wrapping key (public key) that you will use to encrypt the key material. You cannot perform this operation on an asymmetric KMS key or on any KMS key in a different Amazon Web Services account.
To import key material, you must use the public key and import token from the same response. These items are valid for 24 hours. The expiration date and time appear in the GetParametersForImport
response. You cannot use an expired token in an ImportKeyMaterial request. If your key and token expire, send another GetParametersForImport
request.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:GetParametersForImport (key policy)
Related operations:
",
+ "GetPublicKey": "Returns the public key of an asymmetric KMS key. Unlike the private key of a asymmetric KMS key, which never leaves KMS unencrypted, callers with kms:GetPublicKey
permission can download the public key of an asymmetric KMS key. You can share the public key to allow others to encrypt messages and verify signatures outside of KMS. For information about symmetric and asymmetric KMS keys, see Using Symmetric and Asymmetric KMS keys in the Key Management Service Developer Guide.
You do not need to download the public key. Instead, you can use the public key within KMS by calling the Encrypt, ReEncrypt, or Verify operations with the identifier of an asymmetric KMS key. When you use the public key within KMS, you benefit from the authentication, authorization, and logging that are part of every KMS operation. You also reduce of risk of encrypting data that cannot be decrypted. These features are not effective outside of KMS. For details, see Special Considerations for Downloading Public Keys.
To help you use the public key safely outside of KMS, GetPublicKey
returns important information about the public key in the response, including:
-
KeySpec: The type of key material in the public key, such as RSA_4096
or ECC_NIST_P521
.
-
KeyUsage: Whether the key is used for encryption or signing.
-
EncryptionAlgorithms or SigningAlgorithms: A list of the encryption algorithms or the signing algorithms for the key.
Although KMS cannot enforce these restrictions on external operations, it is crucial that you use this information to prevent the public key from being used improperly. For example, you can prevent a public signing key from being used encrypt data, or prevent a public key from being used with an encryption algorithm that is not supported by KMS. You can also avoid errors, such as using the wrong signing algorithm in a verification operation.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:GetPublicKey (key policy)
Related operations: CreateKey
",
+ "ImportKeyMaterial": "Imports key material into an existing symmetric KMS KMS key that was created without key material. After you successfully import key material into a KMS key, you can reimport the same key material into that KMS key, but you cannot import different key material.
You cannot perform this operation on an asymmetric KMS key or on any KMS key in a different Amazon Web Services account. For more information about creating KMS keys with no key material and then importing key material, see Importing Key Material in the Key Management Service Developer Guide.
Before using this operation, call GetParametersForImport. Its response includes a public key and an import token. Use the public key to encrypt the key material. Then, submit the import token from the same GetParametersForImport
response.
When calling this operation, you must specify the following values:
-
The key ID or key ARN of a KMS key with no key material. Its Origin
must be EXTERNAL
.
To create a KMS key with no key material, call CreateKey and set the value of its Origin
parameter to EXTERNAL
. To get the Origin
of a KMS key, call DescribeKey.)
-
The encrypted key material. To get the public key to encrypt the key material, call GetParametersForImport.
-
The import token that GetParametersForImport returned. You must use a public key and token from the same GetParametersForImport
response.
-
Whether the key material expires and if so, when. If you set an expiration date, KMS deletes the key material from the KMS key on the specified date, and the KMS key becomes unusable. To use the KMS key again, you must reimport the same key material. The only way to change an expiration date is by reimporting the same key material and specifying a new expiration date.
When this operation is successful, the key state of the KMS key changes from PendingImport
to Enabled
, and you can use the KMS key.
If this operation fails, use the exception to help determine the problem. If the error is related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key and repeat the import procedure. For help, see How To Import Key Material in the Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:ImportKeyMaterial (key policy)
Related operations:
",
+ "ListAliases": "Gets a list of aliases in the caller's Amazon Web Services account and region. For more information about aliases, see CreateAlias.
By default, the ListAliases
operation returns all aliases in the account and region. To get only the aliases associated with a particular KMS key, use the KeyId
parameter.
The ListAliases
response can include aliases that you created and associated with your customer managed keys, and aliases that Amazon Web Services created and associated with Amazon Web Services managed keys in your account. You can recognize Amazon Web Services aliases because their names have the format aws/<service-name>
, such as aws/dynamodb
.
The response might also include aliases that have no TargetKeyId
field. These are predefined aliases that Amazon Web Services has created but has not yet associated with a KMS key. Aliases that Amazon Web Services creates in your account, including predefined aliases, do not count against your KMS aliases quota.
Cross-account use: No. ListAliases
does not return aliases in other Amazon Web Services accounts.
Required permissions: kms:ListAliases (IAM policy)
For details, see Controlling access to aliases in the Key Management Service Developer Guide.
Related operations:
",
+ "ListGrants": "Gets a list of all grants for the specified KMS key.
You must specify the KMS key in all requests. You can filter the grant list by grant ID or grantee principal.
For detailed information about grants, including grant terminology, see Using grants in the Key Management Service Developer Guide . For examples of working with grants in several programming languages, see Programming grants.
The GranteePrincipal
field in the ListGrants
response usually contains the user or role designated as the grantee principal in the grant. However, when the grantee principal in the grant is an Amazon Web Services service, the GranteePrincipal
field contains the service principal, which might represent several different grantee principals.
Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key ARN in the value of the KeyId
parameter.
Required permissions: kms:ListGrants (key policy)
Related operations:
",
+ "ListKeyPolicies": "Gets the names of the key policies that are attached to a KMS key. This operation is designed to get policy names that you can use in a GetKeyPolicy operation. However, the only valid policy name is default
.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:ListKeyPolicies (key policy)
Related operations:
",
+ "ListKeys": "Gets a list of all KMS keys in the caller's Amazon Web Services account and Region.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:ListKeys (IAM policy)
Related operations:
",
+ "ListResourceTags": "Returns all tags on the specified KMS key.
For general information about tags, including the format and syntax, see Tagging Amazon Web Services resources in the Amazon Web Services General Reference. For information about using tags in KMS, see Tagging keys.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:ListResourceTags (key policy)
Related operations:
",
+ "ListRetirableGrants": "Returns information about all grants in the Amazon Web Services account and Region that have the specified retiring principal.
You can specify any principal in your Amazon Web Services account. The grants that are returned include grants for KMS keys in your Amazon Web Services account and other Amazon Web Services accounts. You might use this operation to determine which grants you may retire. To retire a grant, use the RetireGrant operation.
For detailed information about grants, including grant terminology, see Using grants in the Key Management Service Developer Guide . For examples of working with grants in several programming languages, see Programming grants.
Cross-account use: You must specify a principal in your Amazon Web Services account. However, this operation can return grants in any Amazon Web Services account. You do not need kms:ListRetirableGrants
permission (or any other additional permission) in any Amazon Web Services account other than your own.
Required permissions: kms:ListRetirableGrants (IAM policy) in your Amazon Web Services account.
Related operations:
",
+ "PutKeyPolicy": "Attaches a key policy to the specified KMS key.
For more information about key policies, see Key Policies in the Key Management Service Developer Guide. For help writing and formatting a JSON policy document, see the IAM JSON Policy Reference in the Identity and Access Management User Guide . For examples of adding a key policy in multiple programming languages, see Setting a key policy in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:PutKeyPolicy (key policy)
Related operations: GetKeyPolicy
",
+ "ReEncrypt": "Decrypts ciphertext and then reencrypts it entirely within KMS. You can use this operation to change the KMS key under which data is encrypted, such as when you manually rotate a KMS key or change the KMS key that protects a ciphertext. You can also use it to reencrypt ciphertext under the same KMS key, such as to change the encryption context of a ciphertext.
The ReEncrypt
operation can decrypt ciphertext that was encrypted by using an KMS KMS key in an KMS operation, such as Encrypt or GenerateDataKey. It can also decrypt ciphertext that was encrypted by using the public key of an asymmetric KMS key outside of KMS. However, it cannot decrypt ciphertext produced by other libraries, such as the Amazon Web Services Encryption SDK or Amazon S3 client-side encryption. These libraries return a ciphertext format that is incompatible with KMS.
When you use the ReEncrypt
operation, you need to provide information for the decrypt operation and the subsequent encrypt operation.
-
If your ciphertext was encrypted under an asymmetric KMS key, you must use the SourceKeyId
parameter to identify the KMS key that encrypted the ciphertext. You must also supply the encryption algorithm that was used. This information is required to decrypt the data.
-
If your ciphertext was encrypted under a symmetric KMS key, the SourceKeyId
parameter is optional. KMS can get this information from metadata that it adds to the symmetric ciphertext blob. This feature adds durability to your implementation by ensuring that authorized users can decrypt ciphertext decades after it was encrypted, even if they've lost track of the key ID. However, specifying the source KMS key is always recommended as a best practice. When you use the SourceKeyId
parameter to specify a KMS key, KMS uses only the KMS key you specify. If the ciphertext was encrypted under a different KMS key, the ReEncrypt
operation fails. This practice ensures that you use the KMS key that you intend.
-
To reencrypt the data, you must use the DestinationKeyId
parameter specify the KMS key that re-encrypts the data after it is decrypted. You can select a symmetric or asymmetric KMS key. If the destination KMS key is an asymmetric KMS key, you must also provide the encryption algorithm. The algorithm that you choose must be compatible with the KMS key.
When you use an asymmetric KMS key to encrypt or reencrypt data, be sure to record the KMS key and encryption algorithm that you choose. You will be required to provide the same KMS key and encryption algorithm when you decrypt the data. If the KMS key and algorithm do not match the values used to encrypt the data, the decrypt operation fails.
You are not required to supply the key ID and encryption algorithm when you decrypt with symmetric KMS keys because KMS stores this information in the ciphertext blob. KMS cannot store metadata in ciphertext generated with asymmetric keys. The standard format for asymmetric key ciphertext does not include configurable fields.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. The source KMS key and destination KMS key can be in different Amazon Web Services accounts. Either or both KMS keys can be in a different account than the caller. To specify a KMS key in a different account, you must use its key ARN or alias ARN.
Required permissions:
To permit reencryption from or to a KMS key, include the \"kms:ReEncrypt*\"
permission in your key policy. This permission is automatically included in the key policy when you use the console to create a KMS key. But you must include it manually when you create a KMS key programmatically or when you use the PutKeyPolicy operation to set a key policy.
Related operations:
",
+ "ReplicateKey": "Replicates a multi-Region key into the specified Region. This operation creates a multi-Region replica key based on a multi-Region primary key in a different Region of the same Amazon Web Services partition. You can create multiple replicas of a primary key, but each must be in a different Region. To create a multi-Region primary key, use the CreateKey operation.
This operation supports multi-Region keys, an KMS feature that lets you create multiple interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
A replica key is a fully-functional KMS key that can be used independently of its primary and peer replica keys. A primary key and its replica keys share properties that make them interoperable. They have the same key ID and key material. They also have the same key spec, key usage, key material origin, and automatic key rotation status. KMS automatically synchronizes these shared properties among related multi-Region keys. All other properties of a replica key can differ, including its key policy, tags, aliases, and key state. KMS pricing and quotas for KMS keys apply to each primary key and replica key.
When this operation completes, the new replica key has a transient key state of Creating
. This key state changes to Enabled
(or PendingImport
) after a few seconds when the process of creating the new replica key is complete. While the key state is Creating
, you can manage key, but you cannot yet use it in cryptographic operations. If you are creating and using the replica key programmatically, retry on KMSInvalidStateException
or call DescribeKey
to check its KeyState
value before using it. For details about the Creating
key state, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
The CloudTrail log of a ReplicateKey
operation records a ReplicateKey
operation in the primary key's Region and a CreateKey operation in the replica key's Region.
If you replicate a multi-Region primary key with imported key material, the replica key is created with no key material. You must import the same key material that you imported into the primary key. For details, see Importing key material into multi-Region keys in the Key Management Service Developer Guide.
To convert a replica key to a primary key, use the UpdatePrimaryRegion operation.
ReplicateKey
uses different default values for the KeyPolicy
and Tags
parameters than those used in the KMS console. For details, see the parameter descriptions.
Cross-account use: No. You cannot use this operation to create a replica key in a different Amazon Web Services account.
Required permissions:
-
kms:ReplicateKey
on the primary key (in the primary key's Region). Include this permission in the primary key's key policy.
-
kms:CreateKey
in an IAM policy in the replica Region.
-
To use the Tags
parameter, kms:TagResource
in an IAM policy in the replica Region.
Related operations
",
+ "RetireGrant": "Deletes a grant. Typically, you retire a grant when you no longer need its permissions. To identify the grant to retire, use a grant token, or both the grant ID and a key identifier (key ID or key ARN) of the KMS key. The CreateGrant operation returns both values.
This operation can be called by the retiring principal for a grant, by the grantee principal if the grant allows the RetireGrant
operation, and by the Amazon Web Services account (root user) in which the grant is created. It can also be called by principals to whom permission for retiring a grant is delegated. For details, see Retiring and revoking grants in the Key Management Service Developer Guide.
For detailed information about grants, including grant terminology, see Using grants in the Key Management Service Developer Guide . For examples of working with grants in several programming languages, see Programming grants.
Cross-account use: Yes. You can retire a grant on a KMS key in a different Amazon Web Services account.
Required permissions::Permission to retire a grant is determined primarily by the grant. For details, see Retiring and revoking grants in the Key Management Service Developer Guide.
Related operations:
",
+ "RevokeGrant": "Deletes the specified grant. You revoke a grant to terminate the permissions that the grant allows. For more information, see Retiring and revoking grants in the Key Management Service Developer Guide .
When you create, retire, or revoke a grant, there might be a brief delay, usually less than five minutes, until the grant is available throughout KMS. This state is known as eventual consistency. For details, see Eventual consistency in the Key Management Service Developer Guide .
For detailed information about grants, including grant terminology, see Using grants in the Key Management Service Developer Guide . For examples of working with grants in several programming languages, see Programming grants.
Cross-account use: Yes. To perform this operation on a KMS key in a different Amazon Web Services account, specify the key ARN in the value of the KeyId
parameter.
Required permissions: kms:RevokeGrant (key policy).
Related operations:
",
+ "ScheduleKeyDeletion": "Schedules the deletion of a KMS key. By default, KMS applies a waiting period of 30 days, but you can specify a waiting period of 7-30 days. When this operation is successful, the key state of the KMS key changes to PendingDeletion
and the key can't be used in any cryptographic operations. It remains in this state for the duration of the waiting period. Before the waiting period ends, you can use CancelKeyDeletion to cancel the deletion of the KMS key. After the waiting period ends, KMS deletes the KMS key, its key material, and all KMS data associated with it, including all aliases that refer to it.
Deleting a KMS key is a destructive and potentially dangerous operation. When a KMS key is deleted, all data that was encrypted under the KMS key is unrecoverable. (The only exception is a multi-Region replica key.) To prevent the use of a KMS key without deleting it, use DisableKey.
If you schedule deletion of a KMS key from a custom key store, when the waiting period expires, ScheduleKeyDeletion
deletes the KMS key from KMS. Then KMS makes a best effort to delete the key material from the associated CloudHSM cluster. However, you might need to manually delete the orphaned key material from the cluster and its backups.
You can schedule the deletion of a multi-Region primary key and its replica keys at any time. However, KMS will not delete a multi-Region primary key with existing replica keys. If you schedule the deletion of a primary key with replicas, its key state changes to PendingReplicaDeletion
and it cannot be replicated or used in cryptographic operations. This status can continue indefinitely. When the last of its replicas keys is deleted (not just scheduled), the key state of the primary key changes to PendingDeletion
and its waiting period (PendingWindowInDays
) begins. For details, see Deleting multi-Region keys in the Key Management Service Developer Guide.
For more information about scheduling a KMS key for deletion, see Deleting KMS keys in the Key Management Service Developer Guide.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:ScheduleKeyDeletion (key policy)
Related operations
",
+ "Sign": "Creates a digital signature for a message or message digest by using the private key in an asymmetric KMS key. To verify the signature, use the Verify operation, or use the public key in the same asymmetric KMS key outside of KMS. For information about symmetric and asymmetric KMS keys, see Using Symmetric and Asymmetric KMS keys in the Key Management Service Developer Guide.
Digital signatures are generated and verified by using asymmetric key pair, such as an RSA or ECC pair that is represented by an asymmetric KMS key. The key owner (or an authorized user) uses their private key to sign a message. Anyone with the public key can verify that the message was signed with that particular private key and that the message hasn't changed since it was signed.
To use the Sign
operation, provide the following information:
-
Use the KeyId
parameter to identify an asymmetric KMS key with a KeyUsage
value of SIGN_VERIFY
. To get the KeyUsage
value of a KMS key, use the DescribeKey operation. The caller must have kms:Sign
permission on the KMS key.
-
Use the Message
parameter to specify the message or message digest to sign. You can submit messages of up to 4096 bytes. To sign a larger message, generate a hash digest of the message, and then provide the hash digest in the Message
parameter. To indicate whether the message is a full message or a digest, use the MessageType
parameter.
-
Choose a signing algorithm that is compatible with the KMS key.
When signing a message, be sure to record the KMS key and the signing algorithm. This information is required to verify the signature.
To verify the signature that this operation generates, use the Verify operation. Or use the GetPublicKey operation to download the public key and then use the public key to verify the signature outside of KMS.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:Sign (key policy)
Related operations: Verify
",
+ "TagResource": "Adds or edits tags on a customer managed key.
Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see Using ABAC in KMS in the Key Management Service Developer Guide.
Each tag consists of a tag key and a tag value, both of which are case-sensitive strings. The tag value can be an empty (null) string. To add a tag, specify a new tag key and a tag value. To edit a tag, specify an existing tag key and a new tag value.
You can use this operation to tag a customer managed key, but you cannot tag an Amazon Web Services managed key, an Amazon Web Services owned key, a custom key store, or an alias.
You can also add tags to a KMS key while creating it (CreateKey) or replicating it (ReplicateKey).
For information about using tags in KMS, see Tagging keys. For general information about tags, including the format and syntax, see Tagging Amazon Web Services resources in the Amazon Web Services General Reference.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:TagResource (key policy)
Related operations
",
+ "UntagResource": "Deletes tags from a customer managed key. To delete a tag, specify the tag key and the KMS key.
Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see Using ABAC in KMS in the Key Management Service Developer Guide.
When it succeeds, the UntagResource
operation doesn't return any output. Also, if the specified tag key isn't found on the KMS key, it doesn't throw an exception or return a response. To confirm that the operation worked, use the ListResourceTags operation.
For information about using tags in KMS, see Tagging keys. For general information about tags, including the format and syntax, see Tagging Amazon Web Services resources in the Amazon Web Services General Reference.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:UntagResource (key policy)
Related operations
",
+ "UpdateAlias": "Associates an existing KMS alias with a different KMS key. Each alias is associated with only one KMS key at a time, although a KMS key can have multiple aliases. The alias and the KMS key must be in the same Amazon Web Services account and Region.
Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see Using ABAC in KMS in the Key Management Service Developer Guide.
The current and new KMS key must be the same type (both symmetric or both asymmetric), and they must have the same key usage (ENCRYPT_DECRYPT
or SIGN_VERIFY
). This restriction prevents errors in code that uses aliases. If you must assign an alias to a different type of KMS key, use DeleteAlias to delete the old alias and CreateAlias to create a new alias.
You cannot use UpdateAlias
to change an alias name. To change an alias name, use DeleteAlias to delete the old alias and CreateAlias to create a new alias.
Because an alias is not a property of a KMS key, you can create, update, and delete the aliases of a KMS key without affecting the KMS key. Also, aliases do not appear in the response from the DescribeKey operation. To get the aliases of all KMS keys in the account, use the ListAliases operation.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions
For details, see Controlling access to aliases in the Key Management Service Developer Guide.
Related operations:
",
+ "UpdateCustomKeyStore": "Changes the properties of a custom key store. Use the CustomKeyStoreId
parameter to identify the custom key store you want to edit. Use the remaining parameters to change the properties of the custom key store.
You can only update a custom key store that is disconnected. To disconnect the custom key store, use DisconnectCustomKeyStore. To reconnect the custom key store after the update completes, use ConnectCustomKeyStore. To find the connection state of a custom key store, use the DescribeCustomKeyStores operation.
Use the parameters of UpdateCustomKeyStore
to edit your keystore settings.
-
Use the NewCustomKeyStoreName parameter to change the friendly name of the custom key store to the value that you specify.
-
Use the KeyStorePassword parameter tell KMS the current password of the kmsuser
crypto user (CU) in the associated CloudHSM cluster. You can use this parameter to fix connection failures that occur when KMS cannot log into the associated cluster because the kmsuser
password has changed. This value does not change the password in the CloudHSM cluster.
-
Use the CloudHsmClusterId parameter to associate the custom key store with a different, but related, CloudHSM cluster. You can use this parameter to repair a custom key store if its CloudHSM cluster becomes corrupted or is deleted, or when you need to create or restore a cluster from a backup.
If the operation succeeds, it returns a JSON object with no properties.
This operation is part of the Custom Key Store feature feature in KMS, which combines the convenience and extensive integration of KMS with the isolation and control of a single-tenant key store.
Cross-account use: No. You cannot perform this operation on a custom key store in a different Amazon Web Services account.
Required permissions: kms:UpdateCustomKeyStore (IAM policy)
Related operations:
",
+ "UpdateKeyDescription": "Updates the description of a KMS key. To see the description of a KMS key, use DescribeKey.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account.
Required permissions: kms:UpdateKeyDescription (key policy)
Related operations
",
+ "UpdatePrimaryRegion": "Changes the primary key of a multi-Region key.
This operation changes the replica key in the specified Region to a primary key and changes the former primary key to a replica key. For example, suppose you have a primary key in us-east-1
and a replica key in eu-west-2
. If you run UpdatePrimaryRegion
with a PrimaryRegion
value of eu-west-2
, the primary key is now the key in eu-west-2
, and the key in us-east-1
becomes a replica key. For details, see Updating the primary Region in the Key Management Service Developer Guide.
This operation supports multi-Region keys, an KMS feature that lets you create multiple interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
The primary key of a multi-Region key is the source for properties that are always shared by primary and replica keys, including the key material, key ID, key spec, key usage, key material origin, and automatic key rotation. It's the only key that can be replicated. You cannot delete the primary key until all replica keys are deleted.
The key ID and primary Region that you specify uniquely identify the replica key that will become the primary key. The primary Region must already have a replica key. This operation does not create a KMS key in the specified Region. To find the replica keys, use the DescribeKey operation on the primary key or any replica key. To create a replica key, use the ReplicateKey operation.
You can run this operation while using the affected multi-Region keys in cryptographic operations. This operation should not delay, interrupt, or cause failures in cryptographic operations.
Even after this operation completes, the process of updating the primary Region might still be in progress for a few more seconds. Operations such as DescribeKey
might display both the old and new primary keys as replicas. The old and new primary keys have a transient key state of Updating
. The original key state is restored when the update is complete. While the key state is Updating
, you can use the keys in cryptographic operations, but you cannot replicate the new primary key or perform certain management operations, such as enabling or disabling these keys. For details about the Updating
key state, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
This operation does not return any output. To verify that primary key is changed, use the DescribeKey operation.
Cross-account use: No. You cannot use this operation in a different Amazon Web Services account.
Required permissions:
-
kms:UpdatePrimaryRegion
on the current primary key (in the primary key's Region). Include this permission primary key's key policy.
-
kms:UpdatePrimaryRegion
on the current replica key (in the replica key's Region). Include this permission in the replica key's key policy.
Related operations
",
+ "Verify": "Verifies a digital signature that was generated by the Sign operation.
Verification confirms that an authorized user signed the message with the specified KMS key and signing algorithm, and the message hasn't changed since it was signed. If the signature is verified, the value of the SignatureValid
field in the response is True
. If the signature verification fails, the Verify
operation fails with an KMSInvalidSignatureException
exception.
A digital signature is generated by using the private key in an asymmetric KMS key. The signature is verified by using the public key in the same asymmetric KMS key. For information about symmetric and asymmetric KMS keys, see Using Symmetric and Asymmetric KMS keys in the Key Management Service Developer Guide.
To verify a digital signature, you can use the Verify
operation. Specify the same asymmetric KMS key, message, and signing algorithm that were used to produce the signature.
You can also verify the digital signature by using the public key of the KMS key outside of KMS. Use the GetPublicKey operation to download the public key in the asymmetric KMS key and then use the public key to verify the signature outside of KMS. The advantage of using the Verify
operation is that it is performed within KMS. As a result, it's easy to call, the operation is performed within the FIPS boundary, it is logged in CloudTrail, and you can use key policy and IAM policy to determine who is authorized to use the KMS key to verify signatures.
The KMS key that you use for this operation must be in a compatible key state. For details, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
Cross-account use: Yes. To perform this operation with a KMS key in a different Amazon Web Services account, specify the key ARN or alias ARN in the value of the KeyId
parameter.
Required permissions: kms:Verify (key policy)
Related operations: Sign
"
},
"shapes": {
"AWSAccountIdType": {
"base": null,
"refs": {
- "KeyMetadata$AWSAccountId": "The twelve-digit account ID of the AWS account that owns the CMK.
"
+ "KeyMetadata$AWSAccountId": "The twelve-digit account ID of the Amazon Web Services account that owns the KMS key.
"
}
},
"AlgorithmSpec": {
"base": null,
"refs": {
- "GetParametersForImportRequest$WrappingAlgorithm": "The algorithm you will use to encrypt the key material before importing it with ImportKeyMaterial. For more information, see Encrypt the Key Material in the AWS Key Management Service Developer Guide.
"
+ "GetParametersForImportRequest$WrappingAlgorithm": "The algorithm you will use to encrypt the key material before importing it with ImportKeyMaterial. For more information, see Encrypt the Key Material in the Key Management Service Developer Guide.
"
}
},
"AliasList": {
@@ -80,9 +80,9 @@
"base": null,
"refs": {
"AliasListEntry$AliasName": "String that contains the alias. This value begins with alias/
.
",
- "CreateAliasRequest$AliasName": "Specifies the alias name. This value must begin with alias/
followed by a name, such as alias/ExampleAlias
.
The AliasName
value must be string of 1-256 characters. It can contain only alphanumeric characters, forward slashes (/), underscores (_), and dashes (-). The alias name cannot begin with alias/aws/
. The alias/aws/
prefix is reserved for AWS managed CMKs.
",
+ "CreateAliasRequest$AliasName": "Specifies the alias name. This value must begin with alias/
followed by a name, such as alias/ExampleAlias
.
The AliasName
value must be string of 1-256 characters. It can contain only alphanumeric characters, forward slashes (/), underscores (_), and dashes (-). The alias name cannot begin with alias/aws/
. The alias/aws/
prefix is reserved for Amazon Web Services managed keys.
",
"DeleteAliasRequest$AliasName": "The alias to be deleted. The alias name must begin with alias/
followed by the alias name, such as alias/ExampleAlias
.
",
- "UpdateAliasRequest$AliasName": "Identifies the alias that is changing its CMK. This value must begin with alias/
followed by the alias name, such as alias/ExampleAlias
. You cannot use UpdateAlias to change the alias name.
"
+ "UpdateAliasRequest$AliasName": "Identifies the alias that is changing its KMS key. This value must begin with alias/
followed by the alias name, such as alias/ExampleAlias
. You cannot use UpdateAlias to change the alias name.
"
}
},
"AlreadyExistsException": {
@@ -95,24 +95,24 @@
"refs": {
"AliasListEntry$AliasArn": "String that contains the key ARN.
",
"KeyListEntry$KeyArn": "ARN of the key.
",
- "KeyMetadata$Arn": "The Amazon Resource Name (ARN) of the CMK. For examples, see AWS Key Management Service (AWS KMS) in the Example ARNs section of the AWS General Reference.
",
+ "KeyMetadata$Arn": "The Amazon Resource Name (ARN) of the KMS key. For examples, see Key Management Service (KMS) in the Example ARNs section of the Amazon Web Services General Reference.
",
"MultiRegionKey$Arn": "Displays the key ARN of a primary or replica key of a multi-Region key.
"
}
},
"BooleanType": {
"base": null,
"refs": {
- "CreateKeyRequest$BypassPolicyLockoutSafetyCheck": "A flag to indicate whether to bypass the key policy lockout safety check.
Setting this value to true increases the risk that the CMK becomes unmanageable. Do not set this value to true indiscriminately.
For more information, refer to the scenario in the Default Key Policy section in the AWS Key Management Service Developer Guide .
Use this parameter only when you include a policy in the request and you intend to prevent the principal that is making the request from making a subsequent PutKeyPolicy request on the CMK.
The default value is false.
",
+ "CreateKeyRequest$BypassPolicyLockoutSafetyCheck": "A flag to indicate whether to bypass the key policy lockout safety check.
Setting this value to true increases the risk that the KMS key becomes unmanageable. Do not set this value to true indiscriminately.
For more information, refer to the scenario in the Default Key Policy section in the Key Management Service Developer Guide .
Use this parameter only when you include a policy in the request and you intend to prevent the principal that is making the request from making a subsequent PutKeyPolicy request on the KMS key.
The default value is false.
",
"DescribeCustomKeyStoresResponse$Truncated": "A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker
element in thisresponse to the Marker
parameter in a subsequent request.
",
"GetKeyRotationStatusResponse$KeyRotationEnabled": "A Boolean value that specifies whether key rotation is enabled.
",
- "KeyMetadata$Enabled": "Specifies whether the CMK is enabled. When KeyState
is Enabled
this value is true, otherwise it is false.
",
+ "KeyMetadata$Enabled": "Specifies whether the KMS key is enabled. When KeyState
is Enabled
this value is true, otherwise it is false.
",
"ListAliasesResponse$Truncated": "A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker
element in thisresponse to the Marker
parameter in a subsequent request.
",
"ListGrantsResponse$Truncated": "A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker
element in thisresponse to the Marker
parameter in a subsequent request.
",
"ListKeyPoliciesResponse$Truncated": "A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker
element in thisresponse to the Marker
parameter in a subsequent request.
",
"ListKeysResponse$Truncated": "A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker
element in thisresponse to the Marker
parameter in a subsequent request.
",
"ListResourceTagsResponse$Truncated": "A flag that indicates whether there are more items in the list. When this value is true, the list in this response is truncated. To get more items, pass the value of the NextMarker
element in thisresponse to the Marker
parameter in a subsequent request.
",
- "PutKeyPolicyRequest$BypassPolicyLockoutSafetyCheck": "A flag to indicate whether to bypass the key policy lockout safety check.
Setting this value to true increases the risk that the CMK becomes unmanageable. Do not set this value to true indiscriminately.
For more information, refer to the scenario in the Default Key Policy section in the AWS Key Management Service Developer Guide.
Use this parameter only when you intend to prevent the principal that is making the request from making a subsequent PutKeyPolicy
request on the CMK.
The default value is false.
",
- "ReplicateKeyRequest$BypassPolicyLockoutSafetyCheck": "A flag to indicate whether to bypass the key policy lockout safety check.
Setting this value to true increases the risk that the CMK becomes unmanageable. Do not set this value to true indiscriminately.
For more information, refer to the scenario in the Default Key Policy section in the AWS Key Management Service Developer Guide.
Use this parameter only when you intend to prevent the principal that is making the request from making a subsequent PutKeyPolicy
request on the CMK.
The default value is false.
",
+ "PutKeyPolicyRequest$BypassPolicyLockoutSafetyCheck": "A flag to indicate whether to bypass the key policy lockout safety check.
Setting this value to true increases the risk that the KMS key becomes unmanageable. Do not set this value to true indiscriminately.
For more information, refer to the scenario in the Default Key Policy section in the Key Management Service Developer Guide.
Use this parameter only when you intend to prevent the principal that is making the request from making a subsequent PutKeyPolicy
request on the KMS key.
The default value is false.
",
+ "ReplicateKeyRequest$BypassPolicyLockoutSafetyCheck": "A flag to indicate whether to bypass the key policy lockout safety check.
Setting this value to true increases the risk that the KMS key becomes unmanageable. Do not set this value to true indiscriminately.
For more information, refer to the scenario in the Default Key Policy section in the Key Management Service Developer Guide.
Use this parameter only when you intend to prevent the principal that is making the request from making a subsequent PutKeyPolicy
request on the KMS key.
The default value is false.
",
"VerifyResponse$SignatureValid": "A Boolean value that indicates whether the signature was verified. A value of True
indicates that the Signature
was produced by signing the Message
with the specified KeyID
and SigningAlgorithm.
If the signature is not verified, the Verify
operation fails with a KMSInvalidSignatureException
exception.
"
}
},
@@ -130,51 +130,51 @@
"base": null,
"refs": {
"DecryptRequest$CiphertextBlob": "Ciphertext to be decrypted. The blob includes metadata.
",
- "EncryptResponse$CiphertextBlob": "The encrypted plaintext. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
- "GenerateDataKeyPairResponse$PrivateKeyCiphertextBlob": "The encrypted copy of the private key. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
- "GenerateDataKeyPairWithoutPlaintextResponse$PrivateKeyCiphertextBlob": "The encrypted copy of the private key. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
- "GenerateDataKeyResponse$CiphertextBlob": "The encrypted copy of the data key. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
- "GenerateDataKeyWithoutPlaintextResponse$CiphertextBlob": "The encrypted data key. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "EncryptResponse$CiphertextBlob": "The encrypted plaintext. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "GenerateDataKeyPairResponse$PrivateKeyCiphertextBlob": "The encrypted copy of the private key. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "GenerateDataKeyPairWithoutPlaintextResponse$PrivateKeyCiphertextBlob": "The encrypted copy of the private key. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "GenerateDataKeyResponse$CiphertextBlob": "The encrypted copy of the data key. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "GenerateDataKeyWithoutPlaintextResponse$CiphertextBlob": "The encrypted data key. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
"GetParametersForImportResponse$ImportToken": "The import token to send in a subsequent ImportKeyMaterial request.
",
"ImportKeyMaterialRequest$ImportToken": "The import token that you received in the response to a previous GetParametersForImport request. It must be from the same response that contained the public key that you used to encrypt the key material.
",
"ImportKeyMaterialRequest$EncryptedKeyMaterial": "The encrypted key material to import. The key material must be encrypted with the public wrapping key that GetParametersForImport returned, using the wrapping algorithm that you specified in the same GetParametersForImport
request.
",
"ReEncryptRequest$CiphertextBlob": "Ciphertext of the data to reencrypt.
",
- "ReEncryptResponse$CiphertextBlob": "The reencrypted data. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
- "SignResponse$Signature": "The cryptographic signature that was generated for the message.
-
When used with the supported RSA signing algorithms, the encoding of this value is defined by PKCS #1 in RFC 8017.
-
When used with the ECDSA_SHA_256
, ECDSA_SHA_384
, or ECDSA_SHA_512
signing algorithms, this value is a DER-encoded object as defined by ANS X9.62–2005 and RFC 3279 Section 2.2.3. This is the most commonly used signature format and is appropriate for most uses.
When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "ReEncryptResponse$CiphertextBlob": "The reencrypted data. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "SignResponse$Signature": "The cryptographic signature that was generated for the message.
-
When used with the supported RSA signing algorithms, the encoding of this value is defined by PKCS #1 in RFC 8017.
-
When used with the ECDSA_SHA_256
, ECDSA_SHA_384
, or ECDSA_SHA_512
signing algorithms, this value is a DER-encoded object as defined by ANS X9.62–2005 and RFC 3279 Section 2.2.3. This is the most commonly used signature format and is appropriate for most uses.
When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
"VerifyRequest$Signature": "The signature that the Sign
operation generated.
"
}
},
"CloudHsmClusterIdType": {
"base": null,
"refs": {
- "CreateCustomKeyStoreRequest$CloudHsmClusterId": "Identifies the AWS CloudHSM cluster for the custom key store. Enter the cluster ID of any active AWS CloudHSM cluster that is not already associated with a custom key store. To find the cluster ID, use the DescribeClusters operation.
",
- "CustomKeyStoresListEntry$CloudHsmClusterId": "A unique identifier for the AWS CloudHSM cluster that is associated with the custom key store.
",
- "KeyMetadata$CloudHsmClusterId": "The cluster ID of the AWS CloudHSM cluster that contains the key material for the CMK. When you create a CMK in a custom key store, AWS KMS creates the key material for the CMK in the associated AWS CloudHSM cluster. This value is present only when the CMK is created in a custom key store.
",
- "UpdateCustomKeyStoreRequest$CloudHsmClusterId": "Associates the custom key store with a related AWS CloudHSM cluster.
Enter the cluster ID of the cluster that you used to create the custom key store or a cluster that shares a backup history and has the same cluster certificate as the original cluster. You cannot use this parameter to associate a custom key store with an unrelated cluster. In addition, the replacement cluster must fulfill the requirements for a cluster associated with a custom key store. To view the cluster certificate of a cluster, use the DescribeClusters operation.
"
+ "CreateCustomKeyStoreRequest$CloudHsmClusterId": "Identifies the CloudHSM cluster for the custom key store. Enter the cluster ID of any active CloudHSM cluster that is not already associated with a custom key store. To find the cluster ID, use the DescribeClusters operation.
",
+ "CustomKeyStoresListEntry$CloudHsmClusterId": "A unique identifier for the CloudHSM cluster that is associated with the custom key store.
",
+ "KeyMetadata$CloudHsmClusterId": "The cluster ID of the CloudHSM cluster that contains the key material for the KMS key. When you create a KMS key in a custom key store, KMS creates the key material for the KMS key in the associated CloudHSM cluster. This value is present only when the KMS key is created in a custom key store.
",
+ "UpdateCustomKeyStoreRequest$CloudHsmClusterId": "Associates the custom key store with a related CloudHSM cluster.
Enter the cluster ID of the cluster that you used to create the custom key store or a cluster that shares a backup history and has the same cluster certificate as the original cluster. You cannot use this parameter to associate a custom key store with an unrelated cluster. In addition, the replacement cluster must fulfill the requirements for a cluster associated with a custom key store. To view the cluster certificate of a cluster, use the DescribeClusters operation.
"
}
},
"CloudHsmClusterInUseException": {
- "base": "The request was rejected because the specified AWS CloudHSM cluster is already associated with a custom key store or it shares a backup history with a cluster that is associated with a custom key store. Each custom key store must be associated with a different AWS CloudHSM cluster.
Clusters that share a backup history have the same cluster certificate. To view the cluster certificate of a cluster, use the DescribeClusters operation.
",
+ "base": "The request was rejected because the specified CloudHSM cluster is already associated with a custom key store or it shares a backup history with a cluster that is associated with a custom key store. Each custom key store must be associated with a different CloudHSM cluster.
Clusters that share a backup history have the same cluster certificate. To view the cluster certificate of a cluster, use the DescribeClusters operation.
",
"refs": {
}
},
"CloudHsmClusterInvalidConfigurationException": {
- "base": "The request was rejected because the associated AWS CloudHSM cluster did not meet the configuration requirements for a custom key store.
-
The cluster must be configured with private subnets in at least two different Availability Zones in the Region.
-
The security group for the cluster (cloudhsm-cluster-<cluster-id>-sg) must include inbound rules and outbound rules that allow TCP traffic on ports 2223-2225. The Source in the inbound rules and the Destination in the outbound rules must match the security group ID. These rules are set by default when you create the cluster. Do not delete or change them. To get information about a particular security group, use the DescribeSecurityGroups operation.
-
The cluster must contain at least as many HSMs as the operation requires. To add HSMs, use the AWS CloudHSM CreateHsm operation.
For the CreateCustomKeyStore, UpdateCustomKeyStore, and CreateKey operations, the AWS CloudHSM cluster must have at least two active HSMs, each in a different Availability Zone. For the ConnectCustomKeyStore operation, the AWS CloudHSM must contain at least one active HSM.
For information about the requirements for an AWS CloudHSM cluster that is associated with a custom key store, see Assemble the Prerequisites in the AWS Key Management Service Developer Guide. For information about creating a private subnet for an AWS CloudHSM cluster, see Create a Private Subnet in the AWS CloudHSM User Guide. For information about cluster security groups, see Configure a Default Security Group in the AWS CloudHSM User Guide .
",
+ "base": "The request was rejected because the associated CloudHSM cluster did not meet the configuration requirements for a custom key store.
-
The cluster must be configured with private subnets in at least two different Availability Zones in the Region.
-
The security group for the cluster (cloudhsm-cluster-<cluster-id>-sg) must include inbound rules and outbound rules that allow TCP traffic on ports 2223-2225. The Source in the inbound rules and the Destination in the outbound rules must match the security group ID. These rules are set by default when you create the cluster. Do not delete or change them. To get information about a particular security group, use the DescribeSecurityGroups operation.
-
The cluster must contain at least as many HSMs as the operation requires. To add HSMs, use the CloudHSM CreateHsm operation.
For the CreateCustomKeyStore, UpdateCustomKeyStore, and CreateKey operations, the CloudHSM cluster must have at least two active HSMs, each in a different Availability Zone. For the ConnectCustomKeyStore operation, the CloudHSM must contain at least one active HSM.
For information about the requirements for an CloudHSM cluster that is associated with a custom key store, see Assemble the Prerequisites in the Key Management Service Developer Guide. For information about creating a private subnet for an CloudHSM cluster, see Create a Private Subnet in the CloudHSM User Guide. For information about cluster security groups, see Configure a Default Security Group in the CloudHSM User Guide .
",
"refs": {
}
},
"CloudHsmClusterNotActiveException": {
- "base": "The request was rejected because the AWS CloudHSM cluster that is associated with the custom key store is not active. Initialize and activate the cluster and try the command again. For detailed instructions, see Getting Started in the AWS CloudHSM User Guide.
",
+ "base": "The request was rejected because the CloudHSM cluster that is associated with the custom key store is not active. Initialize and activate the cluster and try the command again. For detailed instructions, see Getting Started in the CloudHSM User Guide.
",
"refs": {
}
},
"CloudHsmClusterNotFoundException": {
- "base": "The request was rejected because AWS KMS cannot find the AWS CloudHSM cluster with the specified cluster ID. Retry the request with a different cluster ID.
",
+ "base": "The request was rejected because KMS cannot find the CloudHSM cluster with the specified cluster ID. Retry the request with a different cluster ID.
",
"refs": {
}
},
"CloudHsmClusterNotRelatedException": {
- "base": "The request was rejected because the specified AWS CloudHSM cluster has a different cluster certificate than the original cluster. You cannot use the operation to specify an unrelated cluster.
Specify a cluster that shares a backup history with the original cluster. This includes clusters that were created from a backup of the current cluster, and clusters that were created from the same backup that produced the current cluster.
Clusters that share a backup history have the same cluster certificate. To view the cluster certificate of a cluster, use the DescribeClusters operation.
",
+ "base": "The request was rejected because the specified CloudHSM cluster has a different cluster certificate than the original cluster. You cannot use the operation to specify an unrelated cluster.
Specify a cluster that shares a backup history with the original cluster. This includes clusters that were created from a backup of the current cluster, and clusters that were created from the same backup that produced the current cluster.
Clusters that share a backup history have the same cluster certificate. To view the cluster certificate of a cluster, use the DescribeClusters operation.
",
"refs": {
}
},
@@ -191,13 +191,13 @@
"ConnectionErrorCodeType": {
"base": null,
"refs": {
- "CustomKeyStoresListEntry$ConnectionErrorCode": "Describes the connection error. This field appears in the response only when the ConnectionState
is FAILED
. For help resolving these errors, see How to Fix a Connection Failure in AWS Key Management Service Developer Guide.
Valid values are:
-
CLUSTER_NOT_FOUND
- AWS KMS cannot find the AWS CloudHSM cluster with the specified cluster ID.
-
INSUFFICIENT_CLOUDHSM_HSMS
- The associated AWS CloudHSM cluster does not contain any active HSMs. To connect a custom key store to its AWS CloudHSM cluster, the cluster must contain at least one active HSM.
-
INTERNAL_ERROR
- AWS KMS could not complete the request due to an internal error. Retry the request. For ConnectCustomKeyStore
requests, disconnect the custom key store before trying to connect again.
-
INVALID_CREDENTIALS
- AWS KMS does not have the correct password for the kmsuser
crypto user in the AWS CloudHSM cluster. Before you can connect your custom key store to its AWS CloudHSM cluster, you must change the kmsuser
account password and update the key store password value for the custom key store.
-
NETWORK_ERRORS
- Network errors are preventing AWS KMS from connecting to the custom key store.
-
SUBNET_NOT_FOUND
- A subnet in the AWS CloudHSM cluster configuration was deleted. If AWS KMS cannot find all of the subnets in the cluster configuration, attempts to connect the custom key store to the AWS CloudHSM cluster fail. To fix this error, create a cluster from a recent backup and associate it with your custom key store. (This process creates a new cluster configuration with a VPC and private subnets.) For details, see How to Fix a Connection Failure in the AWS Key Management Service Developer Guide.
-
USER_LOCKED_OUT
- The kmsuser
CU account is locked out of the associated AWS CloudHSM cluster due to too many failed password attempts. Before you can connect your custom key store to its AWS CloudHSM cluster, you must change the kmsuser
account password and update the key store password value for the custom key store.
-
USER_LOGGED_IN
- The kmsuser
CU account is logged into the the associated AWS CloudHSM cluster. This prevents AWS KMS from rotating the kmsuser
account password and logging into the cluster. Before you can connect your custom key store to its AWS CloudHSM cluster, you must log the kmsuser
CU out of the cluster. If you changed the kmsuser
password to log into the cluster, you must also and update the key store password value for the custom key store. For help, see How to Log Out and Reconnect in the AWS Key Management Service Developer Guide.
-
USER_NOT_FOUND
- AWS KMS cannot find a kmsuser
CU account in the associated AWS CloudHSM cluster. Before you can connect your custom key store to its AWS CloudHSM cluster, you must create a kmsuser
CU account in the cluster, and then update the key store password value for the custom key store.
"
+ "CustomKeyStoresListEntry$ConnectionErrorCode": "Describes the connection error. This field appears in the response only when the ConnectionState
is FAILED
. For help resolving these errors, see How to Fix a Connection Failure in Key Management Service Developer Guide.
Valid values are:
-
CLUSTER_NOT_FOUND
- KMS cannot find the CloudHSM cluster with the specified cluster ID.
-
INSUFFICIENT_CLOUDHSM_HSMS
- The associated CloudHSM cluster does not contain any active HSMs. To connect a custom key store to its CloudHSM cluster, the cluster must contain at least one active HSM.
-
INTERNAL_ERROR
- KMS could not complete the request due to an internal error. Retry the request. For ConnectCustomKeyStore
requests, disconnect the custom key store before trying to connect again.
-
INVALID_CREDENTIALS
- KMS does not have the correct password for the kmsuser
crypto user in the CloudHSM cluster. Before you can connect your custom key store to its CloudHSM cluster, you must change the kmsuser
account password and update the key store password value for the custom key store.
-
NETWORK_ERRORS
- Network errors are preventing KMS from connecting to the custom key store.
-
SUBNET_NOT_FOUND
- A subnet in the CloudHSM cluster configuration was deleted. If KMS cannot find all of the subnets in the cluster configuration, attempts to connect the custom key store to the CloudHSM cluster fail. To fix this error, create a cluster from a recent backup and associate it with your custom key store. (This process creates a new cluster configuration with a VPC and private subnets.) For details, see How to Fix a Connection Failure in the Key Management Service Developer Guide.
-
USER_LOCKED_OUT
- The kmsuser
CU account is locked out of the associated CloudHSM cluster due to too many failed password attempts. Before you can connect your custom key store to its CloudHSM cluster, you must change the kmsuser
account password and update the key store password value for the custom key store.
-
USER_LOGGED_IN
- The kmsuser
CU account is logged into the the associated CloudHSM cluster. This prevents KMS from rotating the kmsuser
account password and logging into the cluster. Before you can connect your custom key store to its CloudHSM cluster, you must log the kmsuser
CU out of the cluster. If you changed the kmsuser
password to log into the cluster, you must also and update the key store password value for the custom key store. For help, see How to Log Out and Reconnect in the Key Management Service Developer Guide.
-
USER_NOT_FOUND
- KMS cannot find a kmsuser
CU account in the associated CloudHSM cluster. Before you can connect your custom key store to its CloudHSM cluster, you must create a kmsuser
CU account in the cluster, and then update the key store password value for the custom key store.
"
}
},
"ConnectionStateType": {
"base": null,
"refs": {
- "CustomKeyStoresListEntry$ConnectionState": "Indicates whether the custom key store is connected to its AWS CloudHSM cluster.
You can create and use CMKs in your custom key stores only when its connection state is CONNECTED
.
The value is DISCONNECTED
if the key store has never been connected or you use the DisconnectCustomKeyStore operation to disconnect it. If the value is CONNECTED
but you are having trouble using the custom key store, make sure that its associated AWS CloudHSM cluster is active and contains at least one active HSM.
A value of FAILED
indicates that an attempt to connect was unsuccessful. The ConnectionErrorCode
field in the response indicates the cause of the failure. For help resolving a connection failure, see Troubleshooting a Custom Key Store in the AWS Key Management Service Developer Guide.
"
+ "CustomKeyStoresListEntry$ConnectionState": "Indicates whether the custom key store is connected to its CloudHSM cluster.
You can create and use KMS keys in your custom key stores only when its connection state is CONNECTED
.
The value is DISCONNECTED
if the key store has never been connected or you use the DisconnectCustomKeyStore operation to disconnect it. If the value is CONNECTED
but you are having trouble using the custom key store, make sure that its associated CloudHSM cluster is active and contains at least one active HSM.
A value of FAILED
indicates that an attempt to connect was unsuccessful. The ConnectionErrorCode
field in the response indicates the cause of the failure. For help resolving a connection failure, see Troubleshooting a Custom Key Store in the Key Management Service Developer Guide.
"
}
},
"CreateAliasRequest": {
@@ -236,7 +236,7 @@
}
},
"CustomKeyStoreHasCMKsException": {
- "base": "The request was rejected because the custom key store contains AWS KMS customer master keys (CMKs). After verifying that you do not need to use the CMKs, use the ScheduleKeyDeletion operation to delete the CMKs. After they are deleted, you can delete the custom key store.
",
+ "base": "The request was rejected because the custom key store contains KMS keys. After verifying that you do not need to use the KMS keys, use the ScheduleKeyDeletion operation to delete the KMS keys. After they are deleted, you can delete the custom key store.
",
"refs": {
}
},
@@ -245,13 +245,13 @@
"refs": {
"ConnectCustomKeyStoreRequest$CustomKeyStoreId": "Enter the key store ID of the custom key store that you want to connect. To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
",
"CreateCustomKeyStoreResponse$CustomKeyStoreId": "A unique identifier for the new custom key store.
",
- "CreateKeyRequest$CustomKeyStoreId": "Creates the CMK in the specified custom key store and the key material in its associated AWS CloudHSM cluster. To create a CMK in a custom key store, you must also specify the Origin
parameter with a value of AWS_CLOUDHSM
. The AWS CloudHSM cluster that is associated with the custom key store must have at least two active HSMs, each in a different Availability Zone in the Region.
This parameter is valid only for symmetric CMKs and regional CMKs. You cannot create an asymmetric CMK or a multi-Region CMK in a custom key store.
To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
The response includes the custom key store ID and the ID of the AWS CloudHSM cluster.
This operation is part of the Custom Key Store feature feature in AWS KMS, which combines the convenience and extensive integration of AWS KMS with the isolation and control of a single-tenant key store.
",
+ "CreateKeyRequest$CustomKeyStoreId": "Creates the KMS key in the specified custom key store and the key material in its associated CloudHSM cluster. To create a KMS key in a custom key store, you must also specify the Origin
parameter with a value of AWS_CLOUDHSM
. The CloudHSM cluster that is associated with the custom key store must have at least two active HSMs, each in a different Availability Zone in the Region.
This parameter is valid only for symmetric KMS keys and regional KMS keys. You cannot create an asymmetric KMS key or a multi-Region key in a custom key store.
To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
The response includes the custom key store ID and the ID of the CloudHSM cluster.
This operation is part of the Custom Key Store feature feature in KMS, which combines the convenience and extensive integration of KMS with the isolation and control of a single-tenant key store.
",
"CustomKeyStoresListEntry$CustomKeyStoreId": "A unique identifier for the custom key store.
",
"DeleteCustomKeyStoreRequest$CustomKeyStoreId": "Enter the ID of the custom key store you want to delete. To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
",
"DescribeCustomKeyStoresRequest$CustomKeyStoreId": "Gets only information about the specified custom key store. Enter the key store ID.
By default, this operation gets information about all custom key stores in the account and Region. To limit the output to a particular custom key store, you can use either the CustomKeyStoreId
or CustomKeyStoreName
parameter, but not both.
",
"DisconnectCustomKeyStoreRequest$CustomKeyStoreId": "Enter the ID of the custom key store you want to disconnect. To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
",
- "GenerateRandomRequest$CustomKeyStoreId": "Generates the random byte string in the AWS CloudHSM cluster that is associated with the specified custom key store. To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
",
- "KeyMetadata$CustomKeyStoreId": "A unique identifier for the custom key store that contains the CMK. This value is present only when the CMK is created in a custom key store.
",
+ "GenerateRandomRequest$CustomKeyStoreId": "Generates the random byte string in the CloudHSM cluster that is associated with the specified custom key store. To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
",
+ "KeyMetadata$CustomKeyStoreId": "A unique identifier for the custom key store that contains the KMS key. This value is present only when the KMS key is created in a custom key store.
",
"UpdateCustomKeyStoreRequest$CustomKeyStoreId": "Identifies the custom key store that you want to update. Enter the ID of the custom key store. To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
"
}
},
@@ -268,14 +268,14 @@
"CustomKeyStoreNameType": {
"base": null,
"refs": {
- "CreateCustomKeyStoreRequest$CustomKeyStoreName": "Specifies a friendly name for the custom key store. The name must be unique in your AWS account.
",
+ "CreateCustomKeyStoreRequest$CustomKeyStoreName": "Specifies a friendly name for the custom key store. The name must be unique in your Amazon Web Services account.
",
"CustomKeyStoresListEntry$CustomKeyStoreName": "The user-specified friendly name for the custom key store.
",
"DescribeCustomKeyStoresRequest$CustomKeyStoreName": "Gets only information about the specified custom key store. Enter the friendly name of the custom key store.
By default, this operation gets information about all custom key stores in the account and Region. To limit the output to a particular custom key store, you can use either the CustomKeyStoreId
or CustomKeyStoreName
parameter, but not both.
",
- "UpdateCustomKeyStoreRequest$NewCustomKeyStoreName": "Changes the friendly name of the custom key store to the value that you specify. The custom key store name must be unique in the AWS account.
"
+ "UpdateCustomKeyStoreRequest$NewCustomKeyStoreName": "Changes the friendly name of the custom key store to the value that you specify. The custom key store name must be unique in the Amazon Web Services account.
"
}
},
"CustomKeyStoreNotFoundException": {
- "base": "The request was rejected because AWS KMS cannot find a custom key store with the specified key store name or ID.
",
+ "base": "The request was rejected because KMS cannot find a custom key store with the specified key store name or ID.
",
"refs": {
}
},
@@ -294,17 +294,17 @@
"CustomerMasterKeySpec": {
"base": null,
"refs": {
- "CreateKeyRequest$CustomerMasterKeySpec": "Specifies the type of CMK to create. The default value, SYMMETRIC_DEFAULT
, creates a CMK with a 256-bit symmetric key for encryption and decryption. For help choosing a key spec for your CMK, see How to Choose Your CMK Configuration in the AWS Key Management Service Developer Guide.
The CustomerMasterKeySpec
determines whether the CMK contains a symmetric key or an asymmetric key pair. It also determines the encryption algorithms or signing algorithms that the CMK supports. You can't change the CustomerMasterKeySpec
after the CMK is created. To further restrict the algorithms that can be used with the CMK, use a condition key in its key policy or IAM policy. For more information, see kms:EncryptionAlgorithm or kms:Signing Algorithm in the AWS Key Management Service Developer Guide.
AWS services that are integrated with AWS KMS use symmetric CMKs to protect your data. These services do not support asymmetric CMKs. For help determining whether a CMK is symmetric or asymmetric, see Identifying Symmetric and Asymmetric CMKs in the AWS Key Management Service Developer Guide.
AWS KMS supports the following key specs for CMKs:
",
- "GetPublicKeyResponse$CustomerMasterKeySpec": "The type of the of the public key that was downloaded.
",
- "KeyMetadata$CustomerMasterKeySpec": "Describes the type of key material in the CMK.
"
+ "CreateKeyRequest$CustomerMasterKeySpec": "Instead, use the KeySpec
parameter.
The KeySpec
and CustomerMasterKeySpec
parameters work the same way. Only the names differ. We recommend that you use KeySpec
parameter in your code. However, to avoid breaking changes, KMS will support both parameters.
",
+ "GetPublicKeyResponse$CustomerMasterKeySpec": "Instead, use the KeySpec
field in the GetPublicKey
response.
The KeySpec
and CustomerMasterKeySpec
fields have the same value. We recommend that you use the KeySpec
field in your code. However, to avoid breaking changes, KMS will support both fields.
",
+ "KeyMetadata$CustomerMasterKeySpec": "Instead, use the KeySpec
field.
The KeySpec
and CustomerMasterKeySpec
fields have the same value. We recommend that you use the KeySpec
field in your code. However, to avoid breaking changes, KMS will support both fields.
"
}
},
"DataKeyPairSpec": {
"base": null,
"refs": {
- "GenerateDataKeyPairRequest$KeyPairSpec": "Determines the type of data key pair that is generated.
The AWS KMS rule that restricts the use of asymmetric RSA CMKs to encrypt and decrypt or to sign and verify (but not both), and the rule that permits you to use ECC CMKs only to sign and verify, are not effective outside of AWS KMS.
",
+ "GenerateDataKeyPairRequest$KeyPairSpec": "Determines the type of data key pair that is generated.
The KMS rule that restricts the use of asymmetric RSA KMS keys to encrypt and decrypt or to sign and verify (but not both), and the rule that permits you to use ECC KMS keys only to sign and verify, are not effective on data key pairs, which are used outside of KMS.
",
"GenerateDataKeyPairResponse$KeyPairSpec": "The type of data key pair that was generated.
",
- "GenerateDataKeyPairWithoutPlaintextRequest$KeyPairSpec": "Determines the type of data key pair that is generated.
The AWS KMS rule that restricts the use of asymmetric RSA CMKs to encrypt and decrypt or to sign and verify (but not both), and the rule that permits you to use ECC CMKs only to sign and verify, are not effective outside of AWS KMS.
",
+ "GenerateDataKeyPairWithoutPlaintextRequest$KeyPairSpec": "Determines the type of data key pair that is generated.
The KMS rule that restricts the use of asymmetric RSA KMS keys to encrypt and decrypt or to sign and verify (but not both), and the rule that permits you to use ECC KMS keys only to sign and verify, are not effective on data key pairs, which are used outside of KMS.
",
"GenerateDataKeyPairWithoutPlaintextResponse$KeyPairSpec": "The type of data key pair that was generated.
"
}
},
@@ -319,15 +319,15 @@
"base": null,
"refs": {
"AliasListEntry$CreationDate": "Date and time that the alias was most recently created in the account and Region. Formatted as Unix time.
",
- "AliasListEntry$LastUpdatedDate": "Date and time that the alias was most recently associated with a CMK in the account and Region. Formatted as Unix time.
",
+ "AliasListEntry$LastUpdatedDate": "Date and time that the alias was most recently associated with a KMS key in the account and Region. Formatted as Unix time.
",
"CustomKeyStoresListEntry$CreationDate": "The date and time when the custom key store was created.
",
"GetParametersForImportResponse$ParametersValidTo": "The time at which the import token and public key are no longer valid. After this time, you cannot use them to make an ImportKeyMaterial request and you must send another GetParametersForImport
request to get new ones.
",
"GrantListEntry$CreationDate": "The date and time when the grant was created.
",
- "ImportKeyMaterialRequest$ValidTo": "The time at which the imported key material expires. When the key material expires, AWS KMS deletes the key material and the CMK becomes unusable. You must omit this parameter when the ExpirationModel
parameter is set to KEY_MATERIAL_DOES_NOT_EXPIRE
. Otherwise it is required.
",
- "KeyMetadata$CreationDate": "The date and time when the CMK was created.
",
- "KeyMetadata$DeletionDate": "The date and time after which AWS KMS deletes this CMK. This value is present only when the CMK is scheduled for deletion, that is, when its KeyState
is PendingDeletion
.
When the primary key in a multi-Region key is scheduled for deletion but still has replica keys, its key state is PendingReplicaDeletion
and the length of its waiting period is displayed in the PendingDeletionWindowInDays
field.
",
- "KeyMetadata$ValidTo": "The time at which the imported key material expires. When the key material expires, AWS KMS deletes the key material and the CMK becomes unusable. This value is present only for CMKs whose Origin
is EXTERNAL
and whose ExpirationModel
is KEY_MATERIAL_EXPIRES
, otherwise this value is omitted.
",
- "ScheduleKeyDeletionResponse$DeletionDate": "The date and time after which AWS KMS deletes the customer master key (CMK).
If the CMK is a multi-Region primary key with replica keys, this field does not appear. The deletion date for the primary key isn't known until its last replica key is deleted.
"
+ "ImportKeyMaterialRequest$ValidTo": "The time at which the imported key material expires. When the key material expires, KMS deletes the key material and the KMS key becomes unusable. You must omit this parameter when the ExpirationModel
parameter is set to KEY_MATERIAL_DOES_NOT_EXPIRE
. Otherwise it is required.
",
+ "KeyMetadata$CreationDate": "The date and time when the KMS key was created.
",
+ "KeyMetadata$DeletionDate": "The date and time after which KMS deletes this KMS key. This value is present only when the KMS key is scheduled for deletion, that is, when its KeyState
is PendingDeletion
.
When the primary key in a multi-Region key is scheduled for deletion but still has replica keys, its key state is PendingReplicaDeletion
and the length of its waiting period is displayed in the PendingDeletionWindowInDays
field.
",
+ "KeyMetadata$ValidTo": "The time at which the imported key material expires. When the key material expires, KMS deletes the key material and the KMS key becomes unusable. This value is present only for KMS keys whose Origin
is EXTERNAL
and whose ExpirationModel
is KEY_MATERIAL_EXPIRES
, otherwise this value is omitted.
",
+ "ScheduleKeyDeletionResponse$DeletionDate": "The date and time after which KMS deletes the KMS key.
If the KMS key is a multi-Region primary key with replica keys, this field does not appear. The deletion date for the primary key isn't known until its last replica key is deleted.
"
}
},
"DecryptRequest": {
@@ -388,10 +388,10 @@
"DescriptionType": {
"base": null,
"refs": {
- "CreateKeyRequest$Description": "A description of the CMK.
Use a description that helps you decide whether the CMK is appropriate for a task. The default value is an empty string (no description).
",
- "KeyMetadata$Description": "The description of the CMK.
",
- "ReplicateKeyRequest$Description": "A description of the CMK. Use a description that helps you decide whether the CMK is appropriate for a task. The default value is an empty string (no description).
The description is not a shared property of multi-Region keys. You can specify the same description or a different description for each key in a set of related multi-Region keys. AWS KMS does not synchronize this property.
",
- "UpdateKeyDescriptionRequest$Description": "New description for the CMK.
"
+ "CreateKeyRequest$Description": "A description of the KMS key.
Use a description that helps you decide whether the KMS key is appropriate for a task. The default value is an empty string (no description).
To set or change the description after the key is created, use UpdateKeyDescription.
",
+ "KeyMetadata$Description": "The description of the KMS key.
",
+ "ReplicateKeyRequest$Description": "A description of the KMS key. The default value is an empty string (no description).
The description is not a shared property of multi-Region keys. You can specify the same description or a different description for each key in a set of related multi-Region keys. KMS does not synchronize this property.
",
+ "UpdateKeyDescriptionRequest$Description": "New description for the KMS key.
"
}
},
"DisableKeyRequest": {
@@ -405,7 +405,7 @@
}
},
"DisabledException": {
- "base": "The request was rejected because the specified CMK is not enabled.
",
+ "base": "The request was rejected because the specified KMS key is not enabled.
",
"refs": {
}
},
@@ -442,13 +442,13 @@
"EncryptionAlgorithmSpec": {
"base": null,
"refs": {
- "DecryptRequest$EncryptionAlgorithm": "Specifies the encryption algorithm that will be used to decrypt the ciphertext. Specify the same algorithm that was used to encrypt the data. If you specify a different algorithm, the Decrypt
operation fails.
This parameter is required only when the ciphertext was encrypted under an asymmetric CMK. The default value, SYMMETRIC_DEFAULT
, represents the only supported algorithm that is valid for symmetric CMKs.
",
+ "DecryptRequest$EncryptionAlgorithm": "Specifies the encryption algorithm that will be used to decrypt the ciphertext. Specify the same algorithm that was used to encrypt the data. If you specify a different algorithm, the Decrypt
operation fails.
This parameter is required only when the ciphertext was encrypted under an asymmetric KMS key. The default value, SYMMETRIC_DEFAULT
, represents the only supported algorithm that is valid for symmetric KMS keys.
",
"DecryptResponse$EncryptionAlgorithm": "The encryption algorithm that was used to decrypt the ciphertext.
",
- "EncryptRequest$EncryptionAlgorithm": "Specifies the encryption algorithm that AWS KMS will use to encrypt the plaintext message. The algorithm must be compatible with the CMK that you specify.
This parameter is required only for asymmetric CMKs. The default value, SYMMETRIC_DEFAULT
, is the algorithm used for symmetric CMKs. If you are using an asymmetric CMK, we recommend RSAES_OAEP_SHA_256.
",
+ "EncryptRequest$EncryptionAlgorithm": "Specifies the encryption algorithm that KMS will use to encrypt the plaintext message. The algorithm must be compatible with the KMS key that you specify.
This parameter is required only for asymmetric KMS keys. The default value, SYMMETRIC_DEFAULT
, is the algorithm used for symmetric KMS keys. If you are using an asymmetric KMS key, we recommend RSAES_OAEP_SHA_256.
",
"EncryptResponse$EncryptionAlgorithm": "The encryption algorithm that was used to encrypt the plaintext.
",
"EncryptionAlgorithmSpecList$member": null,
- "ReEncryptRequest$SourceEncryptionAlgorithm": "Specifies the encryption algorithm that AWS KMS will use to decrypt the ciphertext before it is reencrypted. The default value, SYMMETRIC_DEFAULT
, represents the algorithm used for symmetric CMKs.
Specify the same algorithm that was used to encrypt the ciphertext. If you specify a different algorithm, the decrypt attempt fails.
This parameter is required only when the ciphertext was encrypted under an asymmetric CMK.
",
- "ReEncryptRequest$DestinationEncryptionAlgorithm": "Specifies the encryption algorithm that AWS KMS will use to reecrypt the data after it has decrypted it. The default value, SYMMETRIC_DEFAULT
, represents the encryption algorithm used for symmetric CMKs.
This parameter is required only when the destination CMK is an asymmetric CMK.
",
+ "ReEncryptRequest$SourceEncryptionAlgorithm": "Specifies the encryption algorithm that KMS will use to decrypt the ciphertext before it is reencrypted. The default value, SYMMETRIC_DEFAULT
, represents the algorithm used for symmetric KMS keys.
Specify the same algorithm that was used to encrypt the ciphertext. If you specify a different algorithm, the decrypt attempt fails.
This parameter is required only when the ciphertext was encrypted under an asymmetric KMS key.
",
+ "ReEncryptRequest$DestinationEncryptionAlgorithm": "Specifies the encryption algorithm that KMS will use to reecrypt the data after it has decrypted it. The default value, SYMMETRIC_DEFAULT
, represents the encryption algorithm used for symmetric KMS keys.
This parameter is required only when the destination KMS key is an asymmetric KMS key.
",
"ReEncryptResponse$SourceEncryptionAlgorithm": "The encryption algorithm that was used to decrypt the ciphertext before it was reencrypted.
",
"ReEncryptResponse$DestinationEncryptionAlgorithm": "The encryption algorithm that was used to reencrypt the data.
"
}
@@ -456,8 +456,8 @@
"EncryptionAlgorithmSpecList": {
"base": null,
"refs": {
- "GetPublicKeyResponse$EncryptionAlgorithms": "The encryption algorithms that AWS KMS supports for this key.
This information is critical. If a public key encrypts data outside of AWS KMS by using an unsupported encryption algorithm, the ciphertext cannot be decrypted.
This field appears in the response only when the KeyUsage
of the public key is ENCRYPT_DECRYPT
.
",
- "KeyMetadata$EncryptionAlgorithms": "The encryption algorithms that the CMK supports. You cannot use the CMK with other encryption algorithms within AWS KMS.
This value is present only when the KeyUsage
of the CMK is ENCRYPT_DECRYPT
.
"
+ "GetPublicKeyResponse$EncryptionAlgorithms": "The encryption algorithms that KMS supports for this key.
This information is critical. If a public key encrypts data outside of KMS by using an unsupported encryption algorithm, the ciphertext cannot be decrypted.
This field appears in the response only when the KeyUsage
of the public key is ENCRYPT_DECRYPT
.
",
+ "KeyMetadata$EncryptionAlgorithms": "The encryption algorithms that the KMS key supports. You cannot use the KMS key with other encryption algorithms within KMS.
This value is present only when the KeyUsage
of the KMS key is ENCRYPT_DECRYPT
.
"
}
},
"EncryptionContextKey": {
@@ -469,16 +469,16 @@
"EncryptionContextType": {
"base": null,
"refs": {
- "DecryptRequest$EncryptionContext": "Specifies the encryption context to use when decrypting the data. An encryption context is valid only for cryptographic operations with a symmetric CMK. The standard asymmetric encryption algorithms that AWS KMS uses do not support an encryption context.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.
For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
",
- "EncryptRequest$EncryptionContext": "Specifies the encryption context that will be used to encrypt the data. An encryption context is valid only for cryptographic operations with a symmetric CMK. The standard asymmetric encryption algorithms that AWS KMS uses do not support an encryption context.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.
For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
",
- "GenerateDataKeyPairRequest$EncryptionContext": "Specifies the encryption context that will be used when encrypting the private key in the data key pair.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.
For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
",
- "GenerateDataKeyPairWithoutPlaintextRequest$EncryptionContext": "Specifies the encryption context that will be used when encrypting the private key in the data key pair.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.
For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
",
- "GenerateDataKeyRequest$EncryptionContext": "Specifies the encryption context that will be used when encrypting the data key.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.
For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
",
- "GenerateDataKeyWithoutPlaintextRequest$EncryptionContext": "Specifies the encryption context that will be used when encrypting the data key.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.
For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
",
+ "DecryptRequest$EncryptionContext": "Specifies the encryption context to use when decrypting the data. An encryption context is valid only for cryptographic operations with a symmetric KMS key. The standard asymmetric encryption algorithms that KMS uses do not support an encryption context.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric KMS key, but it is highly recommended.
For more information, see Encryption Context in the Key Management Service Developer Guide.
",
+ "EncryptRequest$EncryptionContext": "Specifies the encryption context that will be used to encrypt the data. An encryption context is valid only for cryptographic operations with a symmetric KMS key. The standard asymmetric encryption algorithms that KMS uses do not support an encryption context.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric KMS key, but it is highly recommended.
For more information, see Encryption Context in the Key Management Service Developer Guide.
",
+ "GenerateDataKeyPairRequest$EncryptionContext": "Specifies the encryption context that will be used when encrypting the private key in the data key pair.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric KMS key, but it is highly recommended.
For more information, see Encryption Context in the Key Management Service Developer Guide.
",
+ "GenerateDataKeyPairWithoutPlaintextRequest$EncryptionContext": "Specifies the encryption context that will be used when encrypting the private key in the data key pair.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric KMS key, but it is highly recommended.
For more information, see Encryption Context in the Key Management Service Developer Guide.
",
+ "GenerateDataKeyRequest$EncryptionContext": "Specifies the encryption context that will be used when encrypting the data key.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric KMS key, but it is highly recommended.
For more information, see Encryption Context in the Key Management Service Developer Guide.
",
+ "GenerateDataKeyWithoutPlaintextRequest$EncryptionContext": "Specifies the encryption context that will be used when encrypting the data key.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric KMS key, but it is highly recommended.
For more information, see Encryption Context in the Key Management Service Developer Guide.
",
"GrantConstraints$EncryptionContextSubset": "A list of key-value pairs that must be included in the encryption context of the cryptographic operation request. The grant allows the cryptographic operation only when the encryption context in the request includes the key-value pairs specified in this constraint, although it can include additional key-value pairs.
",
"GrantConstraints$EncryptionContextEquals": "A list of key-value pairs that must match the encryption context in the cryptographic operation request. The grant allows the operation only when the encryption context in the request is the same as the encryption context specified in this constraint.
",
- "ReEncryptRequest$SourceEncryptionContext": "Specifies the encryption context to use to decrypt the ciphertext. Enter the same encryption context that was used to encrypt the ciphertext.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.
For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
",
- "ReEncryptRequest$DestinationEncryptionContext": "Specifies that encryption context to use when the reencrypting the data.
A destination encryption context is valid only when the destination CMK is a symmetric CMK. The standard ciphertext format for asymmetric CMKs does not include fields for metadata.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric CMK, but it is highly recommended.
For more information, see Encryption Context in the AWS Key Management Service Developer Guide.
"
+ "ReEncryptRequest$SourceEncryptionContext": "Specifies the encryption context to use to decrypt the ciphertext. Enter the same encryption context that was used to encrypt the ciphertext.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric KMS key, but it is highly recommended.
For more information, see Encryption Context in the Key Management Service Developer Guide.
",
+ "ReEncryptRequest$DestinationEncryptionContext": "Specifies that encryption context to use when the reencrypting the data.
A destination encryption context is valid only when the destination KMS key is a symmetric KMS key. The standard ciphertext format for asymmetric KMS keys does not include fields for metadata.
An encryption context is a collection of non-secret key-value pairs that represents additional authenticated data. When you use an encryption context to encrypt data, you must specify the same (an exact case-sensitive match) encryption context to decrypt the data. An encryption context is optional when encrypting with a symmetric KMS key, but it is highly recommended.
For more information, see Encryption Context in the Key Management Service Developer Guide.
"
}
},
"EncryptionContextValue": {
@@ -529,7 +529,7 @@
"base": null,
"refs": {
"ImportKeyMaterialRequest$ExpirationModel": "Specifies whether the key material expires. The default is KEY_MATERIAL_EXPIRES
, in which case you must include the ValidTo
parameter. When this parameter is set to KEY_MATERIAL_DOES_NOT_EXPIRE
, you must omit the ValidTo
parameter.
",
- "KeyMetadata$ExpirationModel": "Specifies whether the CMK's key material expires. This value is present only when Origin
is EXTERNAL
, otherwise this value is omitted.
"
+ "KeyMetadata$ExpirationModel": "Specifies whether the KMS key's key material expires. This value is present only when Origin
is EXTERNAL
, otherwise this value is omitted.
"
}
},
"ExpiredImportTokenException": {
@@ -628,9 +628,9 @@
}
},
"GrantConstraints": {
- "base": "Use this structure to allow cryptographic operations in the grant only when the operation request includes the specified encryption context.
AWS KMS applies the grant constraints only to cryptographic operations that support an encryption context, that is, all cryptographic operations with a symmetric CMK. Grant constraints are not applied to operations that do not support an encryption context, such as cryptographic operations with asymmetric CMKs and management operations, such as DescribeKey or RetireGrant.
In a cryptographic operation, the encryption context in the decryption operation must be an exact, case-sensitive match for the keys and values in the encryption context of the encryption operation. Only the order of the pairs can vary.
However, in a grant constraint, the key in each key-value pair is not case sensitive, but the value is case sensitive.
To avoid confusion, do not use multiple encryption context pairs that differ only by case. To require a fully case-sensitive encryption context, use the kms:EncryptionContext:
and kms:EncryptionContextKeys
conditions in an IAM or key policy. For details, see kms:EncryptionContext: in the AWS Key Management Service Developer Guide .
",
+ "base": "Use this structure to allow cryptographic operations in the grant only when the operation request includes the specified encryption context.
KMS applies the grant constraints only to cryptographic operations that support an encryption context, that is, all cryptographic operations with a symmetric KMS key. Grant constraints are not applied to operations that do not support an encryption context, such as cryptographic operations with asymmetric KMS keys and management operations, such as DescribeKey or RetireGrant.
In a cryptographic operation, the encryption context in the decryption operation must be an exact, case-sensitive match for the keys and values in the encryption context of the encryption operation. Only the order of the pairs can vary.
However, in a grant constraint, the key in each key-value pair is not case sensitive, but the value is case sensitive.
To avoid confusion, do not use multiple encryption context pairs that differ only by case. To require a fully case-sensitive encryption context, use the kms:EncryptionContext:
and kms:EncryptionContextKeys
conditions in an IAM or key policy. For details, see kms:EncryptionContext: in the Key Management Service Developer Guide .
",
"refs": {
- "CreateGrantRequest$Constraints": "Specifies a grant constraint.
AWS KMS supports the EncryptionContextEquals
and EncryptionContextSubset
grant constraints. Each constraint value can include up to 8 encryption context pairs. The encryption context value in each constraint cannot exceed 384 characters.
These grant constraints allow a cryptographic operation only when the encryption context in the request matches (EncryptionContextEquals
) or includes (EncryptionContextSubset
) the encryption context specified in this structure. For more information about encryption context, see Encryption Context in the AWS Key Management Service Developer Guide . For information about grant constraints, see Using grant constraints in the AWS Key Management Service Developer Guide.
The encryption context grant constraints are supported only on operations that include an encryption context. You cannot use an encryption context grant constraint for cryptographic operations with asymmetric CMKs or for management operations, such as DescribeKey or RetireGrant.
",
+ "CreateGrantRequest$Constraints": "Specifies a grant constraint.
KMS supports the EncryptionContextEquals
and EncryptionContextSubset
grant constraints. Each constraint value can include up to 8 encryption context pairs. The encryption context value in each constraint cannot exceed 384 characters.
These grant constraints allow the permissions in the grant only when the encryption context in the request matches (EncryptionContextEquals
) or includes (EncryptionContextSubset
) the encryption context specified in this structure. For information about grant constraints, see Using grant constraints in the Key Management Service Developer Guide. For more information about encryption context, see Encryption Context in the Key Management Service Developer Guide .
The encryption context grant constraints are supported only on operations that include an encryption context. You cannot use an encryption context grant constraint for cryptographic operations with asymmetric KMS keys or for management operations, such as DescribeKey or RetireGrant.
",
"GrantListEntry$Constraints": "A list of key-value pairs that must be present in the encryption context of certain subsequent operations that the grant allows.
"
}
},
@@ -672,33 +672,33 @@
"GrantOperationList": {
"base": null,
"refs": {
- "CreateGrantRequest$Operations": "A list of operations that the grant permits.
The operation must be supported on the CMK. For example, you cannot create a grant for a symmetric CMK that allows the Sign operation, or a grant for an asymmetric CMK that allows the GenerateDataKey operation. If you try, AWS KMS returns a ValidationError
exception. For details, see Grant operations in the AWS Key Management Service Developer Guide.
",
+ "CreateGrantRequest$Operations": "A list of operations that the grant permits.
The operation must be supported on the KMS key. For example, you cannot create a grant for a symmetric KMS key that allows the Sign operation, or a grant for an asymmetric KMS key that allows the GenerateDataKey operation. If you try, KMS returns a ValidationError
exception. For details, see Grant operations in the Key Management Service Developer Guide.
",
"GrantListEntry$Operations": "The list of operations permitted by the grant.
"
}
},
"GrantTokenList": {
"base": null,
"refs": {
- "CreateGrantRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "DecryptRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a newly created grant that has not yet achieved eventual consistency. Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "DescribeKeyRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "EncryptRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "GenerateDataKeyPairRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "GenerateDataKeyPairWithoutPlaintextRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "GenerateDataKeyRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "GenerateDataKeyWithoutPlaintextRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "GetPublicKeyRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "ReEncryptRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "SignRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
- "VerifyRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
"
+ "CreateGrantRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "DecryptRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "DescribeKeyRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "EncryptRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "GenerateDataKeyPairRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "GenerateDataKeyPairWithoutPlaintextRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "GenerateDataKeyRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "GenerateDataKeyWithoutPlaintextRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "GetPublicKeyRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "ReEncryptRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "SignRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
+ "VerifyRequest$GrantTokens": "A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
"
}
},
"GrantTokenType": {
"base": null,
"refs": {
- "CreateGrantResponse$GrantToken": "The grant token.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token in the AWS Key Management Service Developer Guide.
",
+ "CreateGrantResponse$GrantToken": "The grant token.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
",
"GrantTokenList$member": null,
- "RetireGrantRequest$GrantToken": "Identifies the grant to be retired. You can use a grant token to identify a new grant even before it has achieved eventual consistency.
Only the CreateGrant operation returns a grant token. For details, see Grant token and Eventual consistency in the AWS Key Management Service Developer Guide.
"
+ "RetireGrantRequest$GrantToken": "Identifies the grant to be retired. You can use a grant token to identify a new grant even before it has achieved eventual consistency.
Only the CreateGrant operation returns a grant token. For details, see Grant token and Eventual consistency in the Key Management Service Developer Guide.
"
}
},
"ImportKeyMaterialRequest": {
@@ -712,17 +712,17 @@
}
},
"IncorrectKeyException": {
- "base": "The request was rejected because the specified CMK cannot decrypt the data. The KeyId
in a Decrypt request and the SourceKeyId
in a ReEncrypt request must identify the same CMK that was used to encrypt the ciphertext.
",
+ "base": "The request was rejected because the specified KMS key cannot decrypt the data. The KeyId
in a Decrypt request and the SourceKeyId
in a ReEncrypt request must identify the same KMS key that was used to encrypt the ciphertext.
",
"refs": {
}
},
"IncorrectKeyMaterialException": {
- "base": "The request was rejected because the key material in the request is, expired, invalid, or is not the same key material that was previously imported into this customer master key (CMK).
",
+ "base": "The request was rejected because the key material in the request is, expired, invalid, or is not the same key material that was previously imported into this KMS key.
",
"refs": {
}
},
"IncorrectTrustAnchorException": {
- "base": "The request was rejected because the trust anchor certificate in the request is not the trust anchor certificate for the specified AWS CloudHSM cluster.
When you initialize the cluster, you create the trust anchor certificate and save it in the customerCA.crt
file.
",
+ "base": "The request was rejected because the trust anchor certificate in the request is not the trust anchor certificate for the specified CloudHSM cluster.
When you initialize the cluster, you create the trust anchor certificate and save it in the customerCA.crt
file.
",
"refs": {
}
},
@@ -737,7 +737,7 @@
}
},
"InvalidCiphertextException": {
- "base": "From the Decrypt or ReEncrypt operation, the request was rejected because the specified ciphertext, or additional authenticated data incorporated into the ciphertext, such as the encryption context, is corrupted, missing, or otherwise invalid.
From the ImportKeyMaterial operation, the request was rejected because AWS KMS could not decrypt the encrypted (wrapped) key material.
",
+ "base": "From the Decrypt or ReEncrypt operation, the request was rejected because the specified ciphertext, or additional authenticated data incorporated into the ciphertext, such as the encryption context, is corrupted, missing, or otherwise invalid.
From the ImportKeyMaterial operation, the request was rejected because KMS could not decrypt the encrypted (wrapped) key material.
",
"refs": {
}
},
@@ -752,12 +752,12 @@
}
},
"InvalidImportTokenException": {
- "base": "The request was rejected because the provided import token is invalid or is associated with a different customer master key (CMK).
",
+ "base": "The request was rejected because the provided import token is invalid or is associated with a different KMS key.
",
"refs": {
}
},
"InvalidKeyUsageException": {
- "base": "The request was rejected for one of the following reasons:
-
The KeyUsage
value of the CMK is incompatible with the API operation.
-
The encryption algorithm or signing algorithm specified for the operation is incompatible with the type of key material in the CMK (CustomerMasterKeySpec
).
For encrypting, decrypting, re-encrypting, and generating data keys, the KeyUsage
must be ENCRYPT_DECRYPT
. For signing and verifying, the KeyUsage
must be SIGN_VERIFY
. To find the KeyUsage
of a CMK, use the DescribeKey operation.
To find the encryption or signing algorithms supported for a particular CMK, use the DescribeKey operation.
",
+ "base": "The request was rejected for one of the following reasons:
-
The KeyUsage
value of the KMS key is incompatible with the API operation.
-
The encryption algorithm or signing algorithm specified for the operation is incompatible with the type of key material in the KMS key (KeySpec
).
For encrypting, decrypting, re-encrypting, and generating data keys, the KeyUsage
must be ENCRYPT_DECRYPT
. For signing and verifying, the KeyUsage
must be SIGN_VERIFY
. To find the KeyUsage
of a KMS key, use the DescribeKey operation.
To find the encryption or signing algorithms supported for a particular KMS key, use the DescribeKey operation.
",
"refs": {
}
},
@@ -772,80 +772,80 @@
}
},
"KMSInvalidSignatureException": {
- "base": "The request was rejected because the signature verification failed. Signature verification fails when it cannot confirm that signature was produced by signing the specified message with the specified CMK and signing algorithm.
",
+ "base": "The request was rejected because the signature verification failed. Signature verification fails when it cannot confirm that signature was produced by signing the specified message with the specified KMS key and signing algorithm.
",
"refs": {
}
},
"KMSInvalidStateException": {
- "base": "The request was rejected because the state of the specified resource is not valid for this request.
For more information about how key state affects the use of a CMK, see How Key State Affects Use of a Customer Master Key in the AWS Key Management Service Developer Guide .
",
+ "base": "The request was rejected because the state of the specified resource is not valid for this request.
For more information about how key state affects the use of a KMS key, see Key state: Effect on your KMS key in the Key Management Service Developer Guide .
",
"refs": {
}
},
"KeyIdType": {
"base": null,
"refs": {
- "AliasListEntry$TargetKeyId": "String that contains the key identifier of the CMK associated with the alias.
",
- "CancelKeyDeletionRequest$KeyId": "Identifies the customer master key (CMK) whose deletion is being canceled.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "CancelKeyDeletionResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK whose deletion is canceled.
",
- "CreateAliasRequest$TargetKeyId": "Associates the alias with the specified customer managed CMK. The CMK must be in the same AWS Region.
A valid CMK ID is required. If you supply a null or empty string value, this operation returns an error.
For help finding the key ID and ARN, see Finding the Key ID and ARN in the AWS Key Management Service Developer Guide.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "CreateGrantRequest$KeyId": "Identifies the customer master key (CMK) for the grant. The grant gives principals permission to use this CMK.
Specify the key ID or key ARN of the CMK. To specify a CMK in a different AWS account, you must use the key ARN.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "DecryptRequest$KeyId": "Specifies the customer master key (CMK) that AWS KMS uses to decrypt the ciphertext. Enter a key ID of the CMK that was used to encrypt the ciphertext.
This parameter is required only when the ciphertext was encrypted under an asymmetric CMK. If you used a symmetric CMK, AWS KMS can get the CMK from metadata that it adds to the symmetric ciphertext blob. However, it is always recommended as a best practice. This practice ensures that you use the CMK that you intend.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "DecryptResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK that was used to decrypt the ciphertext.
",
- "DeleteImportedKeyMaterialRequest$KeyId": "Identifies the CMK from which you are deleting imported key material. The Origin
of the CMK must be EXTERNAL
.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "DescribeKeyRequest$KeyId": "Describes the specified customer master key (CMK).
If you specify a predefined AWS alias (an AWS alias with no key ID), KMS associates the alias with an AWS managed CMK and returns its KeyId
and Arn
in the response.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "DisableKeyRequest$KeyId": "Identifies the customer master key (CMK) to disable.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "DisableKeyRotationRequest$KeyId": "Identifies a symmetric customer master key (CMK). You cannot enable or disable automatic rotation of asymmetric CMKs, CMKs with imported key material, or CMKs in a custom key store.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "EnableKeyRequest$KeyId": "Identifies the customer master key (CMK) to enable.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "EnableKeyRotationRequest$KeyId": "Identifies a symmetric customer master key (CMK). You cannot enable automatic rotation of asymmetric CMKs, CMKs with imported key material, or CMKs in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "EncryptRequest$KeyId": "Identifies the customer master key (CMK) to use in the encryption operation.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "EncryptResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK that was used to encrypt the plaintext.
",
- "GenerateDataKeyPairRequest$KeyId": "Specifies the symmetric CMK that encrypts the private key in the data key pair. You cannot specify an asymmetric CMK or a CMK in a custom key store. To get the type and origin of your CMK, use the DescribeKey operation.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "GenerateDataKeyPairResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK that encrypted the private key.
",
- "GenerateDataKeyPairWithoutPlaintextRequest$KeyId": "Specifies the CMK that encrypts the private key in the data key pair. You must specify a symmetric CMK. You cannot use an asymmetric CMK or a CMK in a custom key store. To get the type and origin of your CMK, use the DescribeKey operation.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "GenerateDataKeyPairWithoutPlaintextResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK that encrypted the private key.
",
- "GenerateDataKeyRequest$KeyId": "Identifies the symmetric CMK that encrypts the data key.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "GenerateDataKeyResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK that encrypted the data key.
",
- "GenerateDataKeyWithoutPlaintextRequest$KeyId": "The identifier of the symmetric customer master key (CMK) that encrypts the data key.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "GenerateDataKeyWithoutPlaintextResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK that encrypted the data key.
",
- "GetKeyPolicyRequest$KeyId": "Gets the key policy for the specified customer master key (CMK).
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "GetKeyRotationStatusRequest$KeyId": "Gets the rotation status for the specified customer master key (CMK).
Specify the key ID or key ARN of the CMK. To specify a CMK in a different AWS account, you must use the key ARN.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "GetParametersForImportRequest$KeyId": "The identifier of the symmetric CMK into which you will import key material. The Origin
of the CMK must be EXTERNAL
.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "GetParametersForImportResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK to use in a subsequent ImportKeyMaterial request. This is the same CMK specified in the GetParametersForImport
request.
",
- "GetPublicKeyRequest$KeyId": "Identifies the asymmetric CMK that includes the public key.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "GetPublicKeyResponse$KeyId": "The Amazon Resource Name (key ARN) of the asymmetric CMK from which the public key was downloaded.
",
- "GrantListEntry$KeyId": "The unique identifier for the customer master key (CMK) to which the grant applies.
",
- "ImportKeyMaterialRequest$KeyId": "The identifier of the symmetric CMK that receives the imported key material. The CMK's Origin
must be EXTERNAL
. This must be the same CMK specified in the KeyID
parameter of the corresponding GetParametersForImport request.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
+ "AliasListEntry$TargetKeyId": "String that contains the key identifier of the KMS key associated with the alias.
",
+ "CancelKeyDeletionRequest$KeyId": "Identifies the KMS key whose deletion is being canceled.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "CancelKeyDeletionResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key whose deletion is canceled.
",
+ "CreateAliasRequest$TargetKeyId": "Associates the alias with the specified customer managed key. The KMS key must be in the same Amazon Web Services Region.
A valid key ID is required. If you supply a null or empty string value, this operation returns an error.
For help finding the key ID and ARN, see Finding the Key ID and ARN in the Key Management Service Developer Guide .
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "CreateGrantRequest$KeyId": "Identifies the KMS key for the grant. The grant gives principals permission to use this KMS key.
Specify the key ID or key ARN of the KMS key. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "DecryptRequest$KeyId": "Specifies the KMS key that KMS uses to decrypt the ciphertext. Enter a key ID of the KMS key that was used to encrypt the ciphertext.
This parameter is required only when the ciphertext was encrypted under an asymmetric KMS key. If you used a symmetric KMS key, KMS can get the KMS key from metadata that it adds to the symmetric ciphertext blob. However, it is always recommended as a best practice. This practice ensures that you use the KMS key that you intend.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "DecryptResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key that was used to decrypt the ciphertext.
",
+ "DeleteImportedKeyMaterialRequest$KeyId": "Identifies the KMS key from which you are deleting imported key material. The Origin
of the KMS key must be EXTERNAL
.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "DescribeKeyRequest$KeyId": "Describes the specified KMS key.
If you specify a predefined Amazon Web Services alias (an Amazon Web Services alias with no key ID), KMS associates the alias with an Amazon Web Services managed key and returns its KeyId
and Arn
in the response.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "DisableKeyRequest$KeyId": "Identifies the KMS key to disable.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "DisableKeyRotationRequest$KeyId": "Identifies a symmetric KMS key. You cannot enable or disable automatic rotation of asymmetric KMS keys, KMS keys with imported key material, or KMS keys in a custom key store.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "EnableKeyRequest$KeyId": "Identifies the KMS key to enable.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "EnableKeyRotationRequest$KeyId": "Identifies a symmetric KMS key. You cannot enable automatic rotation of asymmetric KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To enable or disable automatic rotation of a set of related multi-Region keys, set the property on the primary key.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "EncryptRequest$KeyId": "Identifies the KMS key to use in the encryption operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "EncryptResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key that was used to encrypt the plaintext.
",
+ "GenerateDataKeyPairRequest$KeyId": "Specifies the symmetric KMS key that encrypts the private key in the data key pair. You cannot specify an asymmetric KMS key or a KMS key in a custom key store. To get the type and origin of your KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "GenerateDataKeyPairResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key that encrypted the private key.
",
+ "GenerateDataKeyPairWithoutPlaintextRequest$KeyId": "Specifies the KMS key that encrypts the private key in the data key pair. You must specify a symmetric KMS key. You cannot use an asymmetric KMS key or a KMS key in a custom key store. To get the type and origin of your KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "GenerateDataKeyPairWithoutPlaintextResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key that encrypted the private key.
",
+ "GenerateDataKeyRequest$KeyId": "Identifies the symmetric KMS key that encrypts the data key.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "GenerateDataKeyResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key that encrypted the data key.
",
+ "GenerateDataKeyWithoutPlaintextRequest$KeyId": "The identifier of the symmetric KMS key that encrypts the data key.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "GenerateDataKeyWithoutPlaintextResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key that encrypted the data key.
",
+ "GetKeyPolicyRequest$KeyId": "Gets the key policy for the specified KMS key.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "GetKeyRotationStatusRequest$KeyId": "Gets the rotation status for the specified KMS key.
Specify the key ID or key ARN of the KMS key. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "GetParametersForImportRequest$KeyId": "The identifier of the symmetric KMS key into which you will import key material. The Origin
of the KMS key must be EXTERNAL
.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "GetParametersForImportResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key to use in a subsequent ImportKeyMaterial request. This is the same KMS key specified in the GetParametersForImport
request.
",
+ "GetPublicKeyRequest$KeyId": "Identifies the asymmetric KMS key that includes the public key.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "GetPublicKeyResponse$KeyId": "The Amazon Resource Name (key ARN) of the asymmetric KMS key from which the public key was downloaded.
",
+ "GrantListEntry$KeyId": "The unique identifier for the KMS key to which the grant applies.
",
+ "ImportKeyMaterialRequest$KeyId": "The identifier of the symmetric KMS key that receives the imported key material. The KMS key's Origin
must be EXTERNAL
. This must be the same KMS key specified in the KeyID
parameter of the corresponding GetParametersForImport request.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
"KeyListEntry$KeyId": "Unique identifier of the key.
",
- "KeyMetadata$KeyId": "The globally unique identifier for the CMK.
",
- "ListAliasesRequest$KeyId": "Lists only aliases that are associated with the specified CMK. Enter a CMK in your AWS account.
This parameter is optional. If you omit it, ListAliases
returns all aliases in the account and Region.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "ListGrantsRequest$KeyId": "Returns only grants for the specified customer master key (CMK). This parameter is required.
Specify the key ID or key ARN of the CMK. To specify a CMK in a different AWS account, you must use the key ARN.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "ListKeyPoliciesRequest$KeyId": "Gets the names of key policies for the specified customer master key (CMK).
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "ListResourceTagsRequest$KeyId": "Gets tags on the specified customer master key (CMK).
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "PutKeyPolicyRequest$KeyId": "Sets the key policy on the specified customer master key (CMK).
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "ReEncryptRequest$SourceKeyId": "Specifies the customer master key (CMK) that AWS KMS will use to decrypt the ciphertext before it is re-encrypted. Enter a key ID of the CMK that was used to encrypt the ciphertext.
This parameter is required only when the ciphertext was encrypted under an asymmetric CMK. If you used a symmetric CMK, AWS KMS can get the CMK from metadata that it adds to the symmetric ciphertext blob. However, it is always recommended as a best practice. This practice ensures that you use the CMK that you intend.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "ReEncryptRequest$DestinationKeyId": "A unique identifier for the CMK that is used to reencrypt the data. Specify a symmetric or asymmetric CMK with a KeyUsage
value of ENCRYPT_DECRYPT
. To find the KeyUsage
value of a CMK, use the DescribeKey operation.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "ReEncryptResponse$SourceKeyId": "Unique identifier of the CMK used to originally encrypt the data.
",
- "ReEncryptResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK that was used to reencrypt the data.
",
- "ReplicateKeyRequest$KeyId": "Identifies the multi-Region primary key that is being replicated. To determine whether a CMK is a multi-Region primary key, use the DescribeKey operation to check the value of the MultiRegionKeyType
property.
Specify the key ID or key ARN of a multi-Region primary key.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "RetireGrantRequest$KeyId": "The key ARN CMK associated with the grant. To find the key ARN, use the ListKeys operation.
For example: arn:aws:kms:us-east-2:444455556666:key/1234abcd-12ab-34cd-56ef-1234567890ab
",
- "RevokeGrantRequest$KeyId": "A unique identifier for the customer master key (CMK) associated with the grant. To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
Specify the key ID or key ARN of the CMK. To specify a CMK in a different AWS account, you must use the key ARN.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "ScheduleKeyDeletionRequest$KeyId": "The unique identifier of the customer master key (CMK) to delete.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "ScheduleKeyDeletionResponse$KeyId": "The Amazon Resource Name (key ARN) of the CMK whose deletion is scheduled.
",
- "SignRequest$KeyId": "Identifies an asymmetric CMK. AWS KMS uses the private key in the asymmetric CMK to sign the message. The KeyUsage
type of the CMK must be SIGN_VERIFY
. To find the KeyUsage
of a CMK, use the DescribeKey operation.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "SignResponse$KeyId": "The Amazon Resource Name (key ARN) of the asymmetric CMK that was used to sign the message.
",
- "TagResourceRequest$KeyId": "Identifies a customer managed CMK in the account and Region.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "UntagResourceRequest$KeyId": "Identifies the CMK from which you are removing tags.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "UpdateAliasRequest$TargetKeyId": "Identifies the customer managed CMK to associate with the alias. You don't have permission to associate an alias with an AWS managed CMK.
The CMK must be in the same AWS account and Region as the alias. Also, the new target CMK must be the same type as the current target CMK (both symmetric or both asymmetric) and they must have the same key usage.
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
To verify that the alias is mapped to the correct CMK, use ListAliases.
",
- "UpdateKeyDescriptionRequest$KeyId": "Updates the description of the specified customer master key (CMK).
Specify the key ID or key ARN of the CMK.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "UpdatePrimaryRegionRequest$KeyId": "Identifies the current primary key. When the operation completes, this CMK will be a replica key.
Specify the key ID or key ARN of a multi-Region primary key.
For example:
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
",
- "VerifyRequest$KeyId": "Identifies the asymmetric CMK that will be used to verify the signature. This must be the same CMK that was used to generate the signature. If you specify a different CMK, the signature verification fails.
To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a CMK in a different AWS account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
- "VerifyResponse$KeyId": "The Amazon Resource Name (key ARN) of the asymmetric CMK that was used to verify the signature.
"
+ "KeyMetadata$KeyId": "The globally unique identifier for the KMS key.
",
+ "ListAliasesRequest$KeyId": "Lists only aliases that are associated with the specified KMS key. Enter a KMS key in your Amazon Web Services account.
This parameter is optional. If you omit it, ListAliases
returns all aliases in the account and Region.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "ListGrantsRequest$KeyId": "Returns only grants for the specified KMS key. This parameter is required.
Specify the key ID or key ARN of the KMS key. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "ListKeyPoliciesRequest$KeyId": "Gets the names of key policies for the specified KMS key.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "ListResourceTagsRequest$KeyId": "Gets tags on the specified KMS key.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "PutKeyPolicyRequest$KeyId": "Sets the key policy on the specified KMS key.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "ReEncryptRequest$SourceKeyId": "Specifies the KMS key that KMS will use to decrypt the ciphertext before it is re-encrypted. Enter a key ID of the KMS key that was used to encrypt the ciphertext.
This parameter is required only when the ciphertext was encrypted under an asymmetric KMS key. If you used a symmetric KMS key, KMS can get the KMS key from metadata that it adds to the symmetric ciphertext blob. However, it is always recommended as a best practice. This practice ensures that you use the KMS key that you intend.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "ReEncryptRequest$DestinationKeyId": "A unique identifier for the KMS key that is used to reencrypt the data. Specify a symmetric or asymmetric KMS key with a KeyUsage
value of ENCRYPT_DECRYPT
. To find the KeyUsage
value of a KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "ReEncryptResponse$SourceKeyId": "Unique identifier of the KMS key used to originally encrypt the data.
",
+ "ReEncryptResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key that was used to reencrypt the data.
",
+ "ReplicateKeyRequest$KeyId": "Identifies the multi-Region primary key that is being replicated. To determine whether a KMS key is a multi-Region primary key, use the DescribeKey operation to check the value of the MultiRegionKeyType
property.
Specify the key ID or key ARN of a multi-Region primary key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "RetireGrantRequest$KeyId": "The key ARN KMS key associated with the grant. To find the key ARN, use the ListKeys operation.
For example: arn:aws:kms:us-east-2:444455556666:key/1234abcd-12ab-34cd-56ef-1234567890ab
",
+ "RevokeGrantRequest$KeyId": "A unique identifier for the KMS key associated with the grant. To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
Specify the key ID or key ARN of the KMS key. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "ScheduleKeyDeletionRequest$KeyId": "The unique identifier of the KMS key to delete.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "ScheduleKeyDeletionResponse$KeyId": "The Amazon Resource Name (key ARN) of the KMS key whose deletion is scheduled.
",
+ "SignRequest$KeyId": "Identifies an asymmetric KMS key. KMS uses the private key in the asymmetric KMS key to sign the message. The KeyUsage
type of the KMS key must be SIGN_VERIFY
. To find the KeyUsage
of a KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "SignResponse$KeyId": "The Amazon Resource Name (key ARN) of the asymmetric KMS key that was used to sign the message.
",
+ "TagResourceRequest$KeyId": "Identifies a customer managed key in the account and Region.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "UntagResourceRequest$KeyId": "Identifies the KMS key from which you are removing tags.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "UpdateAliasRequest$TargetKeyId": "Identifies the customer managed key to associate with the alias. You don't have permission to associate an alias with an Amazon Web Services managed key.
The KMS key must be in the same Amazon Web Services account and Region as the alias. Also, the new target KMS key must be the same type as the current target KMS key (both symmetric or both asymmetric) and they must have the same key usage.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
To verify that the alias is mapped to the correct KMS key, use ListAliases.
",
+ "UpdateKeyDescriptionRequest$KeyId": "Updates the description of the specified KMS key.
Specify the key ID or key ARN of the KMS key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "UpdatePrimaryRegionRequest$KeyId": "Identifies the current primary key. When the operation completes, this KMS key will be a replica key.
Specify the key ID or key ARN of a multi-Region primary key.
For example:
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
",
+ "VerifyRequest$KeyId": "Identifies the asymmetric KMS key that will be used to verify the signature. This must be the same KMS key that was used to generate the signature. If you specify a different KMS key, the signature verification fails.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with \"alias/\"
. To specify a KMS key in a different Amazon Web Services account, you must use the key ARN or alias ARN.
For example:
-
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
-
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
-
Alias name: alias/ExampleAlias
-
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
",
+ "VerifyResponse$KeyId": "The Amazon Resource Name (key ARN) of the asymmetric KMS key that was used to verify the signature.
"
}
},
"KeyList": {
"base": null,
"refs": {
- "ListKeysResponse$Keys": "A list of customer master keys (CMKs).
"
+ "ListKeysResponse$Keys": "A list of KMS keys.
"
}
},
"KeyListEntry": {
@@ -857,59 +857,67 @@
"KeyManagerType": {
"base": null,
"refs": {
- "KeyMetadata$KeyManager": "The manager of the CMK. CMKs in your AWS account are either customer managed or AWS managed. For more information about the difference, see Customer Master Keys in the AWS Key Management Service Developer Guide.
"
+ "KeyMetadata$KeyManager": "The manager of the KMS key. KMS keys in your Amazon Web Services account are either customer managed or Amazon Web Services managed. For more information about the difference, see KMS keys in the Key Management Service Developer Guide.
"
}
},
"KeyMetadata": {
- "base": "Contains metadata about a customer master key (CMK).
This data type is used as a response element for the CreateKey and DescribeKey operations.
",
+ "base": "Contains metadata about a KMS key.
This data type is used as a response element for the CreateKey and DescribeKey operations.
",
"refs": {
- "CreateKeyResponse$KeyMetadata": "Metadata associated with the CMK.
",
+ "CreateKeyResponse$KeyMetadata": "Metadata associated with the KMS key.
",
"DescribeKeyResponse$KeyMetadata": "Metadata associated with the key.
",
- "ReplicateKeyResponse$ReplicaKeyMetadata": "Displays details about the new replica CMK, including its Amazon Resource Name (key ARN) and key state. It also includes the ARN and AWS Region of its primary key and other replica keys.
"
+ "ReplicateKeyResponse$ReplicaKeyMetadata": "Displays details about the new replica key, including its Amazon Resource Name (key ARN) and key state. It also includes the ARN and Amazon Web Services Region of its primary key and other replica keys.
"
+ }
+ },
+ "KeySpec": {
+ "base": null,
+ "refs": {
+ "CreateKeyRequest$KeySpec": "Specifies the type of KMS key to create. The default value, SYMMETRIC_DEFAULT
, creates a KMS key with a 256-bit symmetric key for encryption and decryption. For help choosing a key spec for your KMS key, see How to Choose Your KMS key Configuration in the Key Management Service Developer Guide .
The KeySpec
determines whether the KMS key contains a symmetric key or an asymmetric key pair. It also determines the encryption algorithms or signing algorithms that the KMS key supports. You can't change the KeySpec
after the KMS key is created. To further restrict the algorithms that can be used with the KMS key, use a condition key in its key policy or IAM policy. For more information, see kms:EncryptionAlgorithm or kms:Signing Algorithm in the Key Management Service Developer Guide .
Amazon Web Services services that are integrated with KMS use symmetric KMS keys to protect your data. These services do not support asymmetric KMS keys. For help determining whether a KMS key is symmetric or asymmetric, see Identifying Symmetric and Asymmetric KMS keys in the Key Management Service Developer Guide.
KMS supports the following key specs for KMS keys:
",
+ "GetPublicKeyResponse$KeySpec": "The type of the of the public key that was downloaded.
",
+ "KeyMetadata$KeySpec": "Describes the type of key material in the KMS key.
"
}
},
"KeyState": {
"base": null,
"refs": {
- "KeyMetadata$KeyState": "The current status of the CMK.
For more information about how key state affects the use of a CMK, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
",
- "ScheduleKeyDeletionResponse$KeyState": "The current status of the CMK.
For more information about how key state affects the use of a CMK, see Key state: Effect on your CMK in the AWS Key Management Service Developer Guide.
"
+ "KeyMetadata$KeyState": "The current status of the KMS key.
For more information about how key state affects the use of a KMS key, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
",
+ "ScheduleKeyDeletionResponse$KeyState": "The current status of the KMS key.
For more information about how key state affects the use of a KMS key, see Key state: Effect on your KMS key in the Key Management Service Developer Guide.
"
}
},
"KeyStorePasswordType": {
"base": null,
"refs": {
- "CreateCustomKeyStoreRequest$KeyStorePassword": "Enter the password of the kmsuser
crypto user (CU) account in the specified AWS CloudHSM cluster. AWS KMS logs into the cluster as this user to manage key material on your behalf.
The password must be a string of 7 to 32 characters. Its value is case sensitive.
This parameter tells AWS KMS the kmsuser
account password; it does not change the password in the AWS CloudHSM cluster.
",
- "UpdateCustomKeyStoreRequest$KeyStorePassword": "Enter the current password of the kmsuser
crypto user (CU) in the AWS CloudHSM cluster that is associated with the custom key store.
This parameter tells AWS KMS the current password of the kmsuser
crypto user (CU). It does not set or change the password of any users in the AWS CloudHSM cluster.
"
+ "CreateCustomKeyStoreRequest$KeyStorePassword": "Enter the password of the kmsuser
crypto user (CU) account in the specified CloudHSM cluster. KMS logs into the cluster as this user to manage key material on your behalf.
The password must be a string of 7 to 32 characters. Its value is case sensitive.
This parameter tells KMS the kmsuser
account password; it does not change the password in the CloudHSM cluster.
",
+ "UpdateCustomKeyStoreRequest$KeyStorePassword": "Enter the current password of the kmsuser
crypto user (CU) in the CloudHSM cluster that is associated with the custom key store.
This parameter tells KMS the current password of the kmsuser
crypto user (CU). It does not set or change the password of any users in the CloudHSM cluster.
"
}
},
"KeyUnavailableException": {
- "base": "The request was rejected because the specified CMK was not available. You can retry the request.
",
+ "base": "The request was rejected because the specified KMS key was not available. You can retry the request.
",
"refs": {
}
},
"KeyUsageType": {
"base": null,
"refs": {
- "CreateKeyRequest$KeyUsage": "Determines the cryptographic operations for which you can use the CMK. The default value is ENCRYPT_DECRYPT
. This parameter is required only for asymmetric CMKs. You can't change the KeyUsage
value after the CMK is created.
Select only one valid value.
-
For symmetric CMKs, omit the parameter or specify ENCRYPT_DECRYPT
.
-
For asymmetric CMKs with RSA key material, specify ENCRYPT_DECRYPT
or SIGN_VERIFY
.
-
For asymmetric CMKs with ECC key material, specify SIGN_VERIFY
.
",
- "GetPublicKeyResponse$KeyUsage": "The permitted use of the public key. Valid values are ENCRYPT_DECRYPT
or SIGN_VERIFY
.
This information is critical. If a public key with SIGN_VERIFY
key usage encrypts data outside of AWS KMS, the ciphertext cannot be decrypted.
",
- "KeyMetadata$KeyUsage": "The cryptographic operations for which you can use the CMK.
"
+ "CreateKeyRequest$KeyUsage": "Determines the cryptographic operations for which you can use the KMS key. The default value is ENCRYPT_DECRYPT
. This parameter is required only for asymmetric KMS keys. You can't change the KeyUsage
value after the KMS key is created.
Select only one valid value.
-
For symmetric KMS keys, omit the parameter or specify ENCRYPT_DECRYPT
.
-
For asymmetric KMS keys with RSA key material, specify ENCRYPT_DECRYPT
or SIGN_VERIFY
.
-
For asymmetric KMS keys with ECC key material, specify SIGN_VERIFY
.
",
+ "GetPublicKeyResponse$KeyUsage": "The permitted use of the public key. Valid values are ENCRYPT_DECRYPT
or SIGN_VERIFY
.
This information is critical. If a public key with SIGN_VERIFY
key usage encrypts data outside of KMS, the ciphertext cannot be decrypted.
",
+ "KeyMetadata$KeyUsage": "The cryptographic operations for which you can use the KMS key.
"
}
},
"LimitExceededException": {
- "base": "The request was rejected because a quota was exceeded. For more information, see Quotas in the AWS Key Management Service Developer Guide.
",
+ "base": "The request was rejected because a quota was exceeded. For more information, see Quotas in the Key Management Service Developer Guide.
",
"refs": {
}
},
"LimitType": {
"base": null,
"refs": {
- "DescribeCustomKeyStoresRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, AWS KMS does not return more than the specified number of items, but it might return fewer.
",
- "ListAliasesRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, AWS KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.
",
- "ListGrantsRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, AWS KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.
",
- "ListKeyPoliciesRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, AWS KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 1000, inclusive. If you do not include a value, it defaults to 100.
Only one policy can be attached to a key.
",
- "ListKeysRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, AWS KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 1000, inclusive. If you do not include a value, it defaults to 100.
",
- "ListResourceTagsRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, AWS KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 50, inclusive. If you do not include a value, it defaults to 50.
",
- "ListRetirableGrantsRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, AWS KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.
"
+ "DescribeCustomKeyStoresRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, KMS does not return more than the specified number of items, but it might return fewer.
",
+ "ListAliasesRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.
",
+ "ListGrantsRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.
",
+ "ListKeyPoliciesRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 1000, inclusive. If you do not include a value, it defaults to 100.
Only one policy can be attached to a key.
",
+ "ListKeysRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 1000, inclusive. If you do not include a value, it defaults to 100.
",
+ "ListResourceTagsRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 50, inclusive. If you do not include a value, it defaults to 50.
",
+ "ListRetirableGrantsRequest$Limit": "Use this parameter to specify the maximum number of items to return. When this value is present, KMS does not return more than the specified number of items, but it might return fewer.
This value is optional. If you include a value, it must be between 1 and 100, inclusive. If you do not include a value, it defaults to 50.
"
}
},
"ListAliasesRequest": {
@@ -993,33 +1001,33 @@
"MessageType": {
"base": null,
"refs": {
- "SignRequest$MessageType": "Tells AWS KMS whether the value of the Message
parameter is a message or message digest. The default value, RAW, indicates a message. To indicate a message digest, enter DIGEST
.
",
- "VerifyRequest$MessageType": "Tells AWS KMS whether the value of the Message
parameter is a message or message digest. The default value, RAW, indicates a message. To indicate a message digest, enter DIGEST
.
Use the DIGEST
value only when the value of the Message
parameter is a message digest. If you use the DIGEST
value with a raw message, the security of the verification operation can be compromised.
"
+ "SignRequest$MessageType": "Tells KMS whether the value of the Message
parameter is a message or message digest. The default value, RAW, indicates a message. To indicate a message digest, enter DIGEST
.
",
+ "VerifyRequest$MessageType": "Tells KMS whether the value of the Message
parameter is a message or message digest. The default value, RAW, indicates a message. To indicate a message digest, enter DIGEST
.
Use the DIGEST
value only when the value of the Message
parameter is a message digest. If you use the DIGEST
value with a raw message, the security of the verification operation can be compromised.
"
}
},
"MultiRegionConfiguration": {
- "base": "Describes the configuration of this multi-Region CMK. This field appears only when the CMK is a primary or replica of a multi-Region CMK.
For more information about any listed CMK, use the DescribeKey operation.
",
+ "base": "Describes the configuration of this multi-Region key. This field appears only when the KMS key is a primary or replica of a multi-Region key.
For more information about any listed KMS key, use the DescribeKey operation.
",
"refs": {
- "KeyMetadata$MultiRegionConfiguration": "Lists the primary and replica CMKs in same multi-Region CMK. This field is present only when the value of the MultiRegion
field is True
.
For more information about any listed CMK, use the DescribeKey operation.
-
MultiRegionKeyType
indicates whether the CMK is a PRIMARY
or REPLICA
key.
-
PrimaryKey
displays the key ARN and Region of the primary key. This field displays the current CMK if it is the primary key.
-
ReplicaKeys
displays the key ARNs and Regions of all replica keys. This field includes the current CMK if it is a replica key.
"
+ "KeyMetadata$MultiRegionConfiguration": "Lists the primary and replica keys in same multi-Region key. This field is present only when the value of the MultiRegion
field is True
.
For more information about any listed KMS key, use the DescribeKey operation.
-
MultiRegionKeyType
indicates whether the KMS key is a PRIMARY
or REPLICA
key.
-
PrimaryKey
displays the key ARN and Region of the primary key. This field displays the current KMS key if it is the primary key.
-
ReplicaKeys
displays the key ARNs and Regions of all replica keys. This field includes the current KMS key if it is a replica key.
"
}
},
"MultiRegionKey": {
"base": "Describes the primary or replica key in a multi-Region key.
",
"refs": {
- "MultiRegionConfiguration$PrimaryKey": "Displays the key ARN and Region of the primary key. This field includes the current CMK if it is the primary key.
",
+ "MultiRegionConfiguration$PrimaryKey": "Displays the key ARN and Region of the primary key. This field includes the current KMS key if it is the primary key.
",
"MultiRegionKeyList$member": null
}
},
"MultiRegionKeyList": {
"base": null,
"refs": {
- "MultiRegionConfiguration$ReplicaKeys": "displays the key ARNs and Regions of all replica keys. This field includes the current CMK if it is a replica key.
"
+ "MultiRegionConfiguration$ReplicaKeys": "displays the key ARNs and Regions of all replica keys. This field includes the current KMS key if it is a replica key.
"
}
},
"MultiRegionKeyType": {
"base": null,
"refs": {
- "MultiRegionConfiguration$MultiRegionKeyType": "Indicates whether the CMK is a PRIMARY
or REPLICA
key.
"
+ "MultiRegionConfiguration$MultiRegionKeyType": "Indicates whether the KMS key is a PRIMARY
or REPLICA
key.
"
}
},
"NotFoundException": {
@@ -1030,8 +1038,8 @@
"NullableBooleanType": {
"base": null,
"refs": {
- "CreateKeyRequest$MultiRegion": "Creates a multi-Region primary key that you can replicate into other AWS Regions. You cannot change this value after you create the CMK.
For a multi-Region key, set this parameter to True
. For a single-Region CMK, omit this parameter or set it to False
. The default value is False
.
This operation supports multi-Region keys, an AWS KMS feature that lets you create multiple interoperable CMKs in different AWS Regions. Because these CMKs have the same key ID, key material, and other metadata, you can use them to encrypt data in one AWS Region and decrypt it in a different AWS Region without making a cross-Region call or exposing the plaintext data. For more information about multi-Region keys, see Using multi-Region keys in the AWS Key Management Service Developer Guide.
This value creates a primary key, not a replica. To create a replica key, use the ReplicateKey operation.
You can create a symmetric or asymmetric multi-Region CMK, and you can create a multi-Region CMK with imported key material. However, you cannot create a multi-Region CMK in a custom key store.
",
- "KeyMetadata$MultiRegion": "Indicates whether the CMK is a multi-Region (True
) or regional (False
) key. This value is True
for multi-Region primary and replica CMKs and False
for regional CMKs.
For more information about multi-Region keys, see Using multi-Region keys in the AWS Key Management Service Developer Guide.
"
+ "CreateKeyRequest$MultiRegion": "Creates a multi-Region primary key that you can replicate into other Amazon Web Services Regions. You cannot change this value after you create the KMS key.
For a multi-Region key, set this parameter to True
. For a single-Region KMS key, omit this parameter or set it to False
. The default value is False
.
This operation supports multi-Region keys, an KMS feature that lets you create multiple interoperable KMS keys in different Amazon Web Services Regions. Because these KMS keys have the same key ID, key material, and other metadata, you can use them interchangeably to encrypt data in one Amazon Web Services Region and decrypt it in a different Amazon Web Services Region without re-encrypting the data or making a cross-Region call. For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
This value creates a primary key, not a replica. To create a replica key, use the ReplicateKey operation.
You can create a symmetric or asymmetric multi-Region key, and you can create a multi-Region key with imported key material. However, you cannot create a multi-Region key in a custom key store.
",
+ "KeyMetadata$MultiRegion": "Indicates whether the KMS key is a multi-Region (True
) or regional (False
) key. This value is True
for multi-Region primary and replica keys and False
for regional KMS keys.
For more information about multi-Region keys, see Using multi-Region keys in the Key Management Service Developer Guide.
"
}
},
"NumberOfBytesType": {
@@ -1045,28 +1053,28 @@
"OriginType": {
"base": null,
"refs": {
- "CreateKeyRequest$Origin": "The source of the key material for the CMK. You cannot change the origin after you create the CMK. The default is AWS_KMS
, which means that AWS KMS creates the key material.
To create a CMK with no key material (for imported key material), set the value to EXTERNAL
. For more information about importing key material into AWS KMS, see Importing Key Material in the AWS Key Management Service Developer Guide. This value is valid only for symmetric CMKs.
To create a CMK in an AWS KMS custom key store and create its key material in the associated AWS CloudHSM cluster, set this value to AWS_CLOUDHSM
. You must also use the CustomKeyStoreId
parameter to identify the custom key store. This value is valid only for symmetric CMKs.
",
- "KeyMetadata$Origin": "The source of the CMK's key material. When this value is AWS_KMS
, AWS KMS created the key material. When this value is EXTERNAL
, the key material was imported from your existing key management infrastructure or the CMK lacks key material. When this value is AWS_CLOUDHSM
, the key material was created in the AWS CloudHSM cluster associated with a custom key store.
"
+ "CreateKeyRequest$Origin": "The source of the key material for the KMS key. You cannot change the origin after you create the KMS key. The default is AWS_KMS
, which means that KMS creates the key material.
To create a KMS key with no key material (for imported key material), set the value to EXTERNAL
. For more information about importing key material into KMS, see Importing Key Material in the Key Management Service Developer Guide. This value is valid only for symmetric KMS keys.
To create a KMS key in an KMS custom key store and create its key material in the associated CloudHSM cluster, set this value to AWS_CLOUDHSM
. You must also use the CustomKeyStoreId
parameter to identify the custom key store. This value is valid only for symmetric KMS keys.
",
+ "KeyMetadata$Origin": "The source of the key material for the KMS key. When this value is AWS_KMS
, KMS created the key material. When this value is EXTERNAL
, the key material was imported or the KMS key doesn't have any key material. When this value is AWS_CLOUDHSM
, the key material was created in the CloudHSM cluster associated with a custom key store.
"
}
},
"PendingWindowInDaysType": {
"base": null,
"refs": {
- "KeyMetadata$PendingDeletionWindowInDays": "The waiting period before the primary key in a multi-Region key is deleted. This waiting period begins when the last of its replica keys is deleted. This value is present only when the KeyState
of the CMK is PendingReplicaDeletion
. That indicates that the CMK is the primary key in a multi-Region key, it is scheduled for deletion, and it still has existing replica keys.
When a regional CMK or a replica key in a multi-Region key is scheduled for deletion, its deletion date is displayed in the DeletionDate
field. However, when the primary key in a multi-Region key is scheduled for deletion, its waiting period doesn't begin until all of its replica keys are deleted. This value displays that waiting period. When the last replica key in the multi-Region key is deleted, the KeyState
of the scheduled primary key changes from PendingReplicaDeletion
to PendingDeletion
and the deletion date appears in the DeletionDate
field.
",
- "ScheduleKeyDeletionRequest$PendingWindowInDays": "The waiting period, specified in number of days. After the waiting period ends, AWS KMS deletes the customer master key (CMK).
If the CMK is a multi-Region primary key with replicas, the waiting period begins when the last of its replica keys is deleted. Otherwise, the waiting period begins immediately.
This value is optional. If you include a value, it must be between 7 and 30, inclusive. If you do not include a value, it defaults to 30.
",
- "ScheduleKeyDeletionResponse$PendingWindowInDays": "The waiting period before the CMK is deleted.
If the CMK is a multi-Region primary key with replicas, the waiting period begins when the last of its replica keys is deleted. Otherwise, the waiting period begins immediately.
"
+ "KeyMetadata$PendingDeletionWindowInDays": "The waiting period before the primary key in a multi-Region key is deleted. This waiting period begins when the last of its replica keys is deleted. This value is present only when the KeyState
of the KMS key is PendingReplicaDeletion
. That indicates that the KMS key is the primary key in a multi-Region key, it is scheduled for deletion, and it still has existing replica keys.
When a single-Region KMS key or a multi-Region replica key is scheduled for deletion, its deletion date is displayed in the DeletionDate
field. However, when the primary key in a multi-Region key is scheduled for deletion, its waiting period doesn't begin until all of its replica keys are deleted. This value displays that waiting period. When the last replica key in the multi-Region key is deleted, the KeyState
of the scheduled primary key changes from PendingReplicaDeletion
to PendingDeletion
and the deletion date appears in the DeletionDate
field.
",
+ "ScheduleKeyDeletionRequest$PendingWindowInDays": "The waiting period, specified in number of days. After the waiting period ends, KMS deletes the KMS key.
If the KMS key is a multi-Region primary key with replicas, the waiting period begins when the last of its replica keys is deleted. Otherwise, the waiting period begins immediately.
This value is optional. If you include a value, it must be between 7 and 30, inclusive. If you do not include a value, it defaults to 30.
",
+ "ScheduleKeyDeletionResponse$PendingWindowInDays": "The waiting period before the KMS key is deleted.
If the KMS key is a multi-Region primary key with replicas, the waiting period begins when the last of its replica keys is deleted. Otherwise, the waiting period begins immediately.
"
}
},
"PlaintextType": {
"base": null,
"refs": {
- "DecryptResponse$Plaintext": "Decrypted plaintext data. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "DecryptResponse$Plaintext": "Decrypted plaintext data. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
"EncryptRequest$Plaintext": "Data to be encrypted.
",
- "GenerateDataKeyPairResponse$PrivateKeyPlaintext": "The plaintext copy of the private key. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
- "GenerateDataKeyResponse$Plaintext": "The plaintext data key. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded. Use this data key to encrypt your data outside of KMS. Then, remove it from memory as soon as possible.
",
- "GenerateRandomResponse$Plaintext": "The random byte string. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "GenerateDataKeyPairResponse$PrivateKeyPlaintext": "The plaintext copy of the private key. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
+ "GenerateDataKeyResponse$Plaintext": "The plaintext data key. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded. Use this data key to encrypt your data outside of KMS. Then, remove it from memory as soon as possible.
",
+ "GenerateRandomResponse$Plaintext": "The random byte string. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
",
"GetParametersForImportResponse$PublicKey": "The public key to use to encrypt the key material before importing it with ImportKeyMaterial.
",
- "SignRequest$Message": "Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message, provide the message digest.
If you provide a message, AWS KMS generates a hash digest of the message and then signs it.
",
+ "SignRequest$Message": "Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message, provide the message digest.
If you provide a message, KMS generates a hash digest of the message and then signs it.
",
"VerifyRequest$Message": "Specifies the message that was signed. You can submit a raw message of up to 4096 bytes, or a hash digest of the message. If you submit a digest, use the MessageType
parameter with a value of DIGEST
.
If the message specified here is different from the message that was signed, the signature verification fails. A message and its hash digest are considered to be the same message.
"
}
},
@@ -1087,23 +1095,23 @@
"PolicyType": {
"base": null,
"refs": {
- "CreateKeyRequest$Policy": "The key policy to attach to the CMK.
If you provide a key policy, it must meet the following criteria:
-
If you don't set BypassPolicyLockoutSafetyCheck
to true, the key policy must allow the principal that is making the CreateKey
request to make a subsequent PutKeyPolicy request on the CMK. This reduces the risk that the CMK becomes unmanageable. For more information, refer to the scenario in the Default Key Policy section of the AWS Key Management Service Developer Guide .
-
Each statement in the key policy must contain one or more principals. The principals in the key policy must exist and be visible to AWS KMS. When you create a new AWS principal (for example, an IAM user or role), you might need to enforce a delay before including the new principal in a key policy because the new principal might not be immediately visible to AWS KMS. For more information, see Changes that I make are not always immediately visible in the AWS Identity and Access Management User Guide.
If you do not provide a key policy, AWS KMS attaches a default key policy to the CMK. For more information, see Default Key Policy in the AWS Key Management Service Developer Guide.
The key policy size quota is 32 kilobytes (32768 bytes).
For help writing and formatting a JSON policy document, see the IAM JSON Policy Reference in the IAM User Guide .
",
+ "CreateKeyRequest$Policy": "The key policy to attach to the KMS key.
If you provide a key policy, it must meet the following criteria:
-
If you don't set BypassPolicyLockoutSafetyCheck
to true, the key policy must allow the principal that is making the CreateKey
request to make a subsequent PutKeyPolicy request on the KMS key. This reduces the risk that the KMS key becomes unmanageable. For more information, refer to the scenario in the Default Key Policy section of the Key Management Service Developer Guide .
-
Each statement in the key policy must contain one or more principals. The principals in the key policy must exist and be visible to KMS. When you create a new Amazon Web Services principal (for example, an IAM user or role), you might need to enforce a delay before including the new principal in a key policy because the new principal might not be immediately visible to KMS. For more information, see Changes that I make are not always immediately visible in the Amazon Web Services Identity and Access Management User Guide.
If you do not provide a key policy, KMS attaches a default key policy to the KMS key. For more information, see Default Key Policy in the Key Management Service Developer Guide.
The key policy size quota is 32 kilobytes (32768 bytes).
For help writing and formatting a JSON policy document, see the IAM JSON Policy Reference in the Identity and Access Management User Guide .
",
"GetKeyPolicyResponse$Policy": "A key policy document in JSON format.
",
- "PutKeyPolicyRequest$Policy": "The key policy to attach to the CMK.
The key policy must meet the following criteria:
-
If you don't set BypassPolicyLockoutSafetyCheck
to true, the key policy must allow the principal that is making the PutKeyPolicy
request to make a subsequent PutKeyPolicy
request on the CMK. This reduces the risk that the CMK becomes unmanageable. For more information, refer to the scenario in the Default Key Policy section of the AWS Key Management Service Developer Guide.
-
Each statement in the key policy must contain one or more principals. The principals in the key policy must exist and be visible to AWS KMS. When you create a new AWS principal (for example, an IAM user or role), you might need to enforce a delay before including the new principal in a key policy because the new principal might not be immediately visible to AWS KMS. For more information, see Changes that I make are not always immediately visible in the AWS Identity and Access Management User Guide.
The key policy cannot exceed 32 kilobytes (32768 bytes). For more information, see Resource Quotas in the AWS Key Management Service Developer Guide.
",
- "ReplicateKeyRequest$Policy": "The key policy to attach to the CMK. This parameter is optional. If you do not provide a key policy, AWS KMS attaches the default key policy to the CMK.
The key policy is not a shared property of multi-Region keys. You can specify the same key policy or a different key policy for each key in a set of related multi-Region keys. AWS KMS does not synchronize this property.
If you provide a key policy, it must meet the following criteria:
-
If you don't set BypassPolicyLockoutSafetyCheck
to true, the key policy must give the caller kms:PutKeyPolicy
permission on the replica CMK. This reduces the risk that the CMK becomes unmanageable. For more information, refer to the scenario in the Default Key Policy section of the AWS Key Management Service Developer Guide .
-
Each statement in the key policy must contain one or more principals. The principals in the key policy must exist and be visible to AWS KMS. When you create a new AWS principal (for example, an IAM user or role), you might need to enforce a delay before including the new principal in a key policy because the new principal might not be immediately visible to AWS KMS. For more information, see Changes that I make are not always immediately visible in the AWS Identity and Access Management User Guide.
-
The key policy size quota is 32 kilobytes (32768 bytes).
",
+ "PutKeyPolicyRequest$Policy": "The key policy to attach to the KMS key.
The key policy must meet the following criteria:
-
If you don't set BypassPolicyLockoutSafetyCheck
to true, the key policy must allow the principal that is making the PutKeyPolicy
request to make a subsequent PutKeyPolicy
request on the KMS key. This reduces the risk that the KMS key becomes unmanageable. For more information, refer to the scenario in the Default Key Policy section of the Key Management Service Developer Guide.
-
Each statement in the key policy must contain one or more principals. The principals in the key policy must exist and be visible to KMS. When you create a new Amazon Web Services principal (for example, an IAM user or role), you might need to enforce a delay before including the new principal in a key policy because the new principal might not be immediately visible to KMS. For more information, see Changes that I make are not always immediately visible in the Amazon Web Services Identity and Access Management User Guide.
The key policy cannot exceed 32 kilobytes (32768 bytes). For more information, see Resource Quotas in the Key Management Service Developer Guide.
",
+ "ReplicateKeyRequest$Policy": "The key policy to attach to the KMS key. This parameter is optional. If you do not provide a key policy, KMS attaches the default key policy to the KMS key.
The key policy is not a shared property of multi-Region keys. You can specify the same key policy or a different key policy for each key in a set of related multi-Region keys. KMS does not synchronize this property.
If you provide a key policy, it must meet the following criteria:
-
If you don't set BypassPolicyLockoutSafetyCheck
to true, the key policy must give the caller kms:PutKeyPolicy
permission on the replica key. This reduces the risk that the KMS key becomes unmanageable. For more information, refer to the scenario in the Default Key Policy section of the Key Management Service Developer Guide .
-
Each statement in the key policy must contain one or more principals. The principals in the key policy must exist and be visible to KMS. When you create a new Amazon Web Services principal (for example, an IAM user or role), you might need to enforce a delay before including the new principal in a key policy because the new principal might not be immediately visible to KMS. For more information, see Changes that I make are not always immediately visible in the Identity and Access Management User Guide .
-
The key policy size quota is 32 kilobytes (32768 bytes).
",
"ReplicateKeyResponse$ReplicaPolicy": "The key policy of the new replica key. The value is a key policy document in JSON format.
"
}
},
"PrincipalIdType": {
"base": null,
"refs": {
- "CreateGrantRequest$GranteePrincipal": "The identity that gets the permissions specified in the grant.
To specify the principal, use the Amazon Resource Name (ARN) of an AWS principal. Valid AWS principals include AWS accounts (root), IAM users, IAM roles, federated users, and assumed role users. For examples of the ARN syntax to use for specifying a principal, see AWS Identity and Access Management (IAM) in the Example ARNs section of the AWS General Reference.
",
- "CreateGrantRequest$RetiringPrincipal": "The principal that is given permission to retire the grant by using RetireGrant operation.
To specify the principal, use the Amazon Resource Name (ARN) of an AWS principal. Valid AWS principals include AWS accounts (root), IAM users, federated users, and assumed role users. For examples of the ARN syntax to use for specifying a principal, see AWS Identity and Access Management (IAM) in the Example ARNs section of the AWS General Reference.
",
- "GrantListEntry$GranteePrincipal": "The identity that gets the permissions in the grant.
The GranteePrincipal
field in the ListGrants
response usually contains the user or role designated as the grantee principal in the grant. However, when the grantee principal in the grant is an AWS service, the GranteePrincipal
field contains the service principal, which might represent several different grantee principals.
",
+ "CreateGrantRequest$GranteePrincipal": "The identity that gets the permissions specified in the grant.
To specify the principal, use the Amazon Resource Name (ARN) of an Amazon Web Services principal. Valid Amazon Web Services principals include Amazon Web Services accounts (root), IAM users, IAM roles, federated users, and assumed role users. For examples of the ARN syntax to use for specifying a principal, see Amazon Web Services Identity and Access Management (IAM) in the Example ARNs section of the Amazon Web Services General Reference.
",
+ "CreateGrantRequest$RetiringPrincipal": "The principal that has permission to use the RetireGrant operation to retire the grant.
To specify the principal, use the Amazon Resource Name (ARN) of an Amazon Web Services principal. Valid Amazon Web Services principals include Amazon Web Services accounts (root), IAM users, federated users, and assumed role users. For examples of the ARN syntax to use for specifying a principal, see Amazon Web Services Identity and Access Management (IAM) in the Example ARNs section of the Amazon Web Services General Reference.
The grant determines the retiring principal. Other principals might have permission to retire the grant or revoke the grant. For details, see RevokeGrant and Retiring and revoking grants in the Key Management Service Developer Guide.
",
+ "GrantListEntry$GranteePrincipal": "The identity that gets the permissions in the grant.
The GranteePrincipal
field in the ListGrants
response usually contains the user or role designated as the grantee principal in the grant. However, when the grantee principal in the grant is an Amazon Web Services service, the GranteePrincipal
field contains the service principal, which might represent several different grantee principals.
",
"GrantListEntry$RetiringPrincipal": "The principal that can retire the grant.
",
- "GrantListEntry$IssuingAccount": "The AWS account under which the grant was issued.
",
+ "GrantListEntry$IssuingAccount": "The Amazon Web Services account under which the grant was issued.
",
"ListGrantsRequest$GranteePrincipal": "Returns only grants where the specified principal is the grantee principal for the grant.
",
- "ListRetirableGrantsRequest$RetiringPrincipal": "The retiring principal for which to list grants. Enter a principal in your AWS account.
To specify the retiring principal, use the Amazon Resource Name (ARN) of an AWS principal. Valid AWS principals include AWS accounts (root), IAM users, federated users, and assumed role users. For examples of the ARN syntax for specifying a principal, see AWS Identity and Access Management (IAM) in the Example ARNs section of the Amazon Web Services General Reference.
"
+ "ListRetirableGrantsRequest$RetiringPrincipal": "The retiring principal for which to list grants. Enter a principal in your Amazon Web Services account.
To specify the retiring principal, use the Amazon Resource Name (ARN) of an Amazon Web Services principal. Valid Amazon Web Services principals include Amazon Web Services accounts (root), IAM users, federated users, and assumed role users. For examples of the ARN syntax for specifying a principal, see Amazon Web Services Identity and Access Management (IAM) in the Example ARNs section of the Amazon Web Services General Reference.
"
}
},
"PublicKeyType": {
@@ -1111,7 +1119,7 @@
"refs": {
"GenerateDataKeyPairResponse$PublicKey": "The public key (in plaintext).
",
"GenerateDataKeyPairWithoutPlaintextResponse$PublicKey": "The public key (in plaintext).
",
- "GetPublicKeyResponse$PublicKey": "The exported public key.
The value is a DER-encoded X.509 public key, also known as SubjectPublicKeyInfo
(SPKI), as defined in RFC 5280. When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
"
+ "GetPublicKeyResponse$PublicKey": "The exported public key.
The value is a DER-encoded X.509 public key, also known as SubjectPublicKeyInfo
(SPKI), as defined in RFC 5280. When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
"
}
},
"PutKeyPolicyRequest": {
@@ -1132,9 +1140,9 @@
"RegionType": {
"base": null,
"refs": {
- "MultiRegionKey$Region": "Displays the AWS Region of a primary or replica key in a multi-Region key.
",
- "ReplicateKeyRequest$ReplicaRegion": "The Region ID of the AWS Region for this replica key.
Enter the Region ID, such as us-east-1
or ap-southeast-2
. For a list of AWS Regions in which AWS KMS is supported, see AWS KMS service endpoints in the Amazon Web Services General Reference.
The replica must be in a different AWS Region than its primary key and other replicas of that primary key, but in the same AWS partition. AWS KMS must be available in the replica Region. If the Region is not enabled by default, the AWS account must be enabled in the Region.
For information about AWS partitions, see Amazon Resource Names (ARNs) in the Amazon Web Services General Reference. For information about enabling and disabling Regions, see Enabling a Region and Disabling a Region in the Amazon Web Services General Reference.
",
- "UpdatePrimaryRegionRequest$PrimaryRegion": "The AWS Region of the new primary key. Enter the Region ID, such as us-east-1
or ap-southeast-2
. There must be an existing replica key in this Region.
When the operation completes, the multi-Region key in this Region will be the primary key.
"
+ "MultiRegionKey$Region": "Displays the Amazon Web Services Region of a primary or replica key in a multi-Region key.
",
+ "ReplicateKeyRequest$ReplicaRegion": "The Region ID of the Amazon Web Services Region for this replica key.
Enter the Region ID, such as us-east-1
or ap-southeast-2
. For a list of Amazon Web Services Regions in which KMS is supported, see KMS service endpoints in the Amazon Web Services General Reference.
The replica must be in a different Amazon Web Services Region than its primary key and other replicas of that primary key, but in the same Amazon Web Services partition. KMS must be available in the replica Region. If the Region is not enabled by default, the Amazon Web Services account must be enabled in the Region.
For information about Amazon Web Services partitions, see Amazon Resource Names (ARNs) in the Amazon Web Services General Reference. For information about enabling and disabling Regions, see Enabling a Region and Disabling a Region in the Amazon Web Services General Reference.
",
+ "UpdatePrimaryRegionRequest$PrimaryRegion": "The Amazon Web Services Region of the new primary key. Enter the Region ID, such as us-east-1
or ap-southeast-2
. There must be an existing replica key in this Region.
When the operation completes, the multi-Region key in this Region will be the primary key.
"
}
},
"ReplicateKeyRequest": {
@@ -1180,7 +1188,7 @@
"SigningAlgorithmSpec": {
"base": null,
"refs": {
- "SignRequest$SigningAlgorithm": "Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric CMK.
",
+ "SignRequest$SigningAlgorithm": "Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key.
",
"SignResponse$SigningAlgorithm": "The signing algorithm that was used to sign the message.
",
"SigningAlgorithmSpecList$member": null,
"VerifyRequest$SigningAlgorithm": "The signing algorithm that was used to sign the message. If you submit a different algorithm, the signature verification fails.
",
@@ -1190,12 +1198,12 @@
"SigningAlgorithmSpecList": {
"base": null,
"refs": {
- "GetPublicKeyResponse$SigningAlgorithms": "The signing algorithms that AWS KMS supports for this key.
This field appears in the response only when the KeyUsage
of the public key is SIGN_VERIFY
.
",
- "KeyMetadata$SigningAlgorithms": "The signing algorithms that the CMK supports. You cannot use the CMK with other signing algorithms within AWS KMS.
This field appears only when the KeyUsage
of the CMK is SIGN_VERIFY
.
"
+ "GetPublicKeyResponse$SigningAlgorithms": "The signing algorithms that KMS supports for this key.
This field appears in the response only when the KeyUsage
of the public key is SIGN_VERIFY
.
",
+ "KeyMetadata$SigningAlgorithms": "The signing algorithms that the KMS key supports. You cannot use the KMS key with other signing algorithms within KMS.
This field appears only when the KeyUsage
of the KMS key is SIGN_VERIFY
.
"
}
},
"Tag": {
- "base": "A key-value pair. A tag consists of a tag key and a tag value. Tag keys and tag values are both required, but tag values can be empty (null) strings.
For information about the rules that apply to tag keys and tag values, see User-Defined Tag Restrictions in the AWS Billing and Cost Management User Guide.
",
+ "base": "A key-value pair. A tag consists of a tag key and a tag value. Tag keys and tag values are both required, but tag values can be empty (null) strings.
For information about the rules that apply to tag keys and tag values, see User-Defined Tag Restrictions in the Amazon Web Services Billing and Cost Management User Guide.
",
"refs": {
"TagList$member": null
}
@@ -1221,11 +1229,11 @@
"TagList": {
"base": null,
"refs": {
- "CreateKeyRequest$Tags": "Assigns one or more tags to the CMK. Use this parameter to tag the CMK when it is created. To tag an existing CMK, use the TagResource operation.
Tagging or untagging a CMK can allow or deny permission to the CMK. For details, see Using ABAC in AWS KMS in the AWS Key Management Service Developer Guide.
To use this parameter, you must have kms:TagResource permission in an IAM policy.
Each tag consists of a tag key and a tag value. Both the tag key and the tag value are required, but the tag value can be an empty (null) string. You cannot have more than one tag on a CMK with the same tag key. If you specify an existing tag key with a different tag value, AWS KMS replaces the current tag value with the specified one.
When you assign tags to an AWS resource, AWS generates a cost allocation report with usage and costs aggregated by tags. Tags can also be used to control access to a CMK. For details, see Tagging Keys.
",
- "ListResourceTagsResponse$Tags": "A list of tags. Each tag consists of a tag key and a tag value.
Tagging or untagging a CMK can allow or deny permission to the CMK. For details, see Using ABAC in AWS KMS in the AWS Key Management Service Developer Guide.
",
- "ReplicateKeyRequest$Tags": "Assigns one or more tags to the replica key. Use this parameter to tag the CMK when it is created. To tag an existing CMK, use the TagResource operation.
Tagging or untagging a CMK can allow or deny permission to the CMK. For details, see Using ABAC in AWS KMS in the AWS Key Management Service Developer Guide.
To use this parameter, you must have kms:TagResource permission in an IAM policy.
Tags are not a shared property of multi-Region keys. You can specify the same tags or different tags for each key in a set of related multi-Region keys. AWS KMS does not synchronize this property.
Each tag consists of a tag key and a tag value. Both the tag key and the tag value are required, but the tag value can be an empty (null) string. You cannot have more than one tag on a CMK with the same tag key. If you specify an existing tag key with a different tag value, AWS KMS replaces the current tag value with the specified one.
When you assign tags to an AWS resource, AWS generates a cost allocation report with usage and costs aggregated by tags. Tags can also be used to control access to a CMK. For details, see Tagging Keys.
",
+ "CreateKeyRequest$Tags": "Assigns one or more tags to the KMS key. Use this parameter to tag the KMS key when it is created. To tag an existing KMS key, use the TagResource operation.
Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see Using ABAC in KMS in the Key Management Service Developer Guide.
To use this parameter, you must have kms:TagResource permission in an IAM policy.
Each tag consists of a tag key and a tag value. Both the tag key and the tag value are required, but the tag value can be an empty (null) string. You cannot have more than one tag on a KMS key with the same tag key. If you specify an existing tag key with a different tag value, KMS replaces the current tag value with the specified one.
When you add tags to an Amazon Web Services resource, Amazon Web Services generates a cost allocation report with usage and costs aggregated by tags. Tags can also be used to control access to a KMS key. For details, see Tagging Keys.
",
+ "ListResourceTagsResponse$Tags": "A list of tags. Each tag consists of a tag key and a tag value.
Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see Using ABAC in KMS in the Key Management Service Developer Guide.
",
+ "ReplicateKeyRequest$Tags": "Assigns one or more tags to the replica key. Use this parameter to tag the KMS key when it is created. To tag an existing KMS key, use the TagResource operation.
Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see Using ABAC in KMS in the Key Management Service Developer Guide.
To use this parameter, you must have kms:TagResource permission in an IAM policy.
Tags are not a shared property of multi-Region keys. You can specify the same tags or different tags for each key in a set of related multi-Region keys. KMS does not synchronize this property.
Each tag consists of a tag key and a tag value. Both the tag key and the tag value are required, but the tag value can be an empty (null) string. You cannot have more than one tag on a KMS key with the same tag key. If you specify an existing tag key with a different tag value, KMS replaces the current tag value with the specified one.
When you add tags to an Amazon Web Services resource, Amazon Web Services generates a cost allocation report with usage and costs aggregated by tags. Tags can also be used to control access to a KMS key. For details, see Tagging Keys.
",
"ReplicateKeyResponse$ReplicaTags": "The tags on the new replica key. The value is a list of tag key and tag value pairs.
",
- "TagResourceRequest$Tags": "One or more tags.
Each tag consists of a tag key and a tag value. The tag value can be an empty (null) string.
You cannot have more than one tag on a CMK with the same tag key. If you specify an existing tag key with a different tag value, AWS KMS replaces the current tag value with the specified one.
"
+ "TagResourceRequest$Tags": "One or more tags.
Each tag consists of a tag key and a tag value. The tag value can be an empty (null) string.
You cannot have more than one tag on a KMS key with the same tag key. If you specify an existing tag key with a different tag value, KMS replaces the current tag value with the specified one.
"
}
},
"TagResourceRequest": {
@@ -1243,7 +1251,7 @@
"base": null,
"refs": {
"CreateCustomKeyStoreRequest$TrustAnchorCertificate": "Enter the content of the trust anchor certificate for the cluster. This is the content of the customerCA.crt
file that you created when you initialized the cluster.
",
- "CustomKeyStoresListEntry$TrustAnchorCertificate": "The trust anchor certificate of the associated AWS CloudHSM cluster. When you initialize the cluster, you create this certificate and save it in the customerCA.crt
file.
"
+ "CustomKeyStoresListEntry$TrustAnchorCertificate": "The trust anchor certificate of the associated CloudHSM cluster. When you initialize the cluster, you create this certificate and save it in the customerCA.crt
file.
"
}
},
"UnsupportedOperationException": {
diff --git a/models/apis/kms/2014-11-01/examples-1.json b/models/apis/kms/2014-11-01/examples-1.json
index bc9d6a008e8..411bcc54774 100644
--- a/models/apis/kms/2014-11-01/examples-1.json
+++ b/models/apis/kms/2014-11-01/examples-1.json
@@ -11,15 +11,15 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose deletion you are canceling. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose deletion you are canceling. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
},
"output": {
- "KeyId": "The ARN of the CMK whose deletion you canceled."
+ "KeyId": "The ARN of the KMS key whose deletion you canceled."
}
},
- "description": "The following example cancels deletion of the specified CMK.",
+ "description": "The following example cancels deletion of the specified KMS key.",
"id": "to-cancel-deletion-of-a-cmk-1477428535102",
- "title": "To cancel deletion of a customer master key (CMK)"
+ "title": "To cancel deletion of a KMS key"
}
],
"CreateAlias": [
@@ -31,10 +31,10 @@
"comments": {
"input": {
"AliasName": "The alias to create. Aliases must begin with 'alias/'. Do not use aliases that begin with 'alias/aws' because they are reserved for use by AWS.",
- "TargetKeyId": "The identifier of the CMK whose alias you are creating. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "TargetKeyId": "The identifier of the KMS key whose alias you are creating. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example creates an alias for the specified customer master key (CMK).",
+ "description": "The following example creates an alias for the specified KMS key.",
"id": "to-create-an-alias-1477505685119",
"title": "To create an alias"
}
@@ -56,7 +56,7 @@
"comments": {
"input": {
"GranteePrincipal": "The identity that is given permission to perform the operations specified in the grant.",
- "KeyId": "The identifier of the CMK to which the grant applies. You can use the key ID or the Amazon Resource Name (ARN) of the CMK.",
+ "KeyId": "The identifier of the KMS key to which the grant applies. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key.",
"Operations": "A list of operations that the grant allows."
},
"output": {
@@ -64,7 +64,7 @@
"GrantToken": "The grant token."
}
},
- "description": "The following example creates a grant that allows the specified IAM role to encrypt data with the specified customer master key (CMK).",
+ "description": "The following example creates a grant that allows the specified IAM role to encrypt data with the specified KMS key.",
"id": "to-create-a-grant-1477972226782",
"title": "To create a grant"
}
@@ -84,10 +84,15 @@
"AWSAccountId": "111122223333",
"Arn": "arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab",
"CreationDate": "2017-07-05T14:04:55-07:00",
+ "CustomerMasterKeySpec": "SYMMETRIC_DEFAULT",
"Description": "",
"Enabled": true,
+ "EncryptionAlgorithms": [
+ "SYMMETRIC_DEFAULT"
+ ],
"KeyId": "1234abcd-12ab-34cd-56ef-1234567890ab",
"KeyManager": "CUSTOMER",
+ "KeySpec": "SYMMETRIC_DEFAULT",
"KeyState": "Enabled",
"KeyUsage": "ENCRYPT_DECRYPT",
"Origin": "AWS_KMS"
@@ -98,12 +103,12 @@
"Tags": "One or more tags. Each tag consists of a tag key and a tag value."
},
"output": {
- "KeyMetadata": "An object that contains information about the CMK created by this operation."
+ "KeyMetadata": "An object that contains information about the KMS key created by this operation."
}
},
- "description": "The following example creates a CMK.",
+ "description": "The following example creates a KMS key.",
"id": "to-create-a-cmk-1478028992966",
- "title": "To create a customer master key (CMK)"
+ "title": "To create a KMS key"
}
],
"Decrypt": [
@@ -119,14 +124,14 @@
"comments": {
"input": {
"CiphertextBlob": "The encrypted data (ciphertext).",
- "KeyId": "A key identifier for the CMK to use to decrypt the data."
+ "KeyId": "A key identifier for the KMS key to use to decrypt the data."
},
"output": {
- "KeyId": "The Amazon Resource Name (ARN) of the CMK that was used to decrypt the data.",
+ "KeyId": "The Amazon Resource Name (ARN) of the KMS key that was used to decrypt the data.",
"Plaintext": "The decrypted (plaintext) data."
}
},
- "description": "The following example decrypts data that was encrypted with a customer master key (CMK) in AWS KMS.",
+ "description": "The following example decrypts data that was encrypted with a KMS key.",
"id": "to-decrypt-data-1478281622886",
"title": "To decrypt data"
}
@@ -153,10 +158,10 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose imported key material you are deleting. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose imported key material you are deleting. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example deletes the imported key material from the specified customer master key (CMK).",
+ "description": "The following example deletes the imported key material from the specified KMS key.",
"id": "to-delete-imported-key-material-1478561674507",
"title": "To delete imported key material"
}
@@ -179,6 +184,7 @@
],
"KeyId": "1234abcd-12ab-34cd-56ef-1234567890ab",
"KeyManager": "CUSTOMER",
+ "KeySpec": "SYMMETRIC_DEFAULT",
"KeyState": "Enabled",
"KeyUsage": "ENCRYPT_DECRYPT",
"MultiRegion": false,
@@ -187,15 +193,15 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK that you want information about. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key that you want information about. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
},
"output": {
- "KeyMetadata": "An object that contains information about the specified CMK."
+ "KeyMetadata": "An object that contains information about the specified KMS key."
}
},
- "description": "The following example gets metadata about a symmetric CMK.",
+ "description": "The following example gets metadata about a symmetric KMS key.",
"id": "get-key-details-1478565820907",
- "title": "To get details about a customer master key (CMK)"
+ "title": "To get details about a KMS key"
}
],
"DisableKey": [
@@ -205,12 +211,12 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK to disable. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key to disable. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example disables the specified CMK.",
+ "description": "The following example disables the specified KMS key.",
"id": "to-disable-a-cmk-1478566583659",
- "title": "To disable a customer master key (CMK)"
+ "title": "To disable a KMS key"
}
],
"DisableKeyRotation": [
@@ -220,10 +226,10 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose key material will no longer be rotated. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose key material will no longer be rotated. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example disables automatic annual rotation of the key material for the specified CMK.",
+ "description": "The following example disables automatic annual rotation of the key material for the specified KMS key.",
"id": "to-disable-automatic-rotation-of-key-material-1478624396092",
"title": "To disable automatic rotation of key material"
}
@@ -235,12 +241,12 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK to enable. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key to enable. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example enables the specified CMK.",
+ "description": "The following example enables the specified KMS key.",
"id": "to-enable-a-cmk-1478627501129",
- "title": "To enable a customer master key (CMK)"
+ "title": "To enable a KMS key"
}
],
"EnableKeyRotation": [
@@ -250,10 +256,10 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose key material will be rotated annually. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose key material will be rotated annually. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example enables automatic annual rotation of the key material for the specified CMK.",
+ "description": "The following example enables automatic annual rotation of the key material for the specified KMS key.",
"id": "to-enable-automatic-rotation-of-key-material-1478629109677",
"title": "To enable automatic rotation of key material"
}
@@ -270,15 +276,15 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK to use for encryption. You can use the key ID or Amazon Resource Name (ARN) of the CMK, or the name or ARN of an alias that refers to the CMK.",
+ "KeyId": "The identifier of the KMS key to use for encryption. You can use the key ID or Amazon Resource Name (ARN) of the KMS key, or the name or ARN of an alias that refers to the KMS key.",
"Plaintext": "The data to encrypt."
},
"output": {
"CiphertextBlob": "The encrypted data (ciphertext).",
- "KeyId": "The ARN of the CMK that was used to encrypt the data."
+ "KeyId": "The ARN of the KMS key that was used to encrypt the data."
}
},
- "description": "The following example encrypts data with the specified customer master key (CMK).",
+ "description": "The following example encrypts data with the specified KMS key.",
"id": "to-encrypt-data-1478906026012",
"title": "To encrypt data"
}
@@ -296,16 +302,16 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK to use to encrypt the data key. You can use the key ID or Amazon Resource Name (ARN) of the CMK, or the name or ARN of an alias that refers to the CMK.",
+ "KeyId": "The identifier of the KMS key to use to encrypt the data key. You can use the key ID or Amazon Resource Name (ARN) of the KMS key, or the name or ARN of an alias that refers to the KMS key.",
"KeySpec": "Specifies the type of data key to return."
},
"output": {
"CiphertextBlob": "The encrypted data key.",
- "KeyId": "The ARN of the CMK that was used to encrypt the data key.",
+ "KeyId": "The ARN of the KMS key that was used to encrypt the data key.",
"Plaintext": "The unencrypted (plaintext) data key."
}
},
- "description": "The following example generates a 256-bit symmetric data encryption key (data key) in two formats. One is the unencrypted (plainext) data key, and the other is the data key encrypted with the specified customer master key (CMK).",
+ "description": "The following example generates a 256-bit symmetric data encryption key (data key) in two formats. One is the unencrypted (plainext) data key, and the other is the data key encrypted with the specified KMS key.",
"id": "to-generate-a-data-key-1478912956062",
"title": "To generate a data key"
}
@@ -322,15 +328,15 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK to use to encrypt the data key. You can use the key ID or Amazon Resource Name (ARN) of the CMK, or the name or ARN of an alias that refers to the CMK.",
+ "KeyId": "The identifier of the KMS key to use to encrypt the data key. You can use the key ID or Amazon Resource Name (ARN) of the KMS key, or the name or ARN of an alias that refers to the KMS key.",
"KeySpec": "Specifies the type of data key to return."
},
"output": {
"CiphertextBlob": "The encrypted data key.",
- "KeyId": "The ARN of the CMK that was used to encrypt the data key."
+ "KeyId": "The ARN of the KMS key that was used to encrypt the data key."
}
},
- "description": "The following example generates an encrypted copy of a 256-bit symmetric data encryption key (data key). The data key is encrypted with the specified customer master key (CMK).",
+ "description": "The following example generates an encrypted copy of a 256-bit symmetric data encryption key (data key). The data key is encrypted with the specified KMS key.",
"id": "to-generate-an-encrypted-data-key-1478914121134",
"title": "To generate an encrypted data key"
}
@@ -351,7 +357,7 @@
"Plaintext": "The random data."
}
},
- "description": "The following example uses AWS KMS to generate 32 bytes of random data.",
+ "description": "The following example generates 32 bytes of random data.",
"id": "to-generate-random-data-1479163645600",
"title": "To generate random data"
}
@@ -367,14 +373,14 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose key policy you want to retrieve. You can use the key ID or the Amazon Resource Name (ARN) of the CMK.",
+ "KeyId": "The identifier of the KMS key whose key policy you want to retrieve. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key.",
"PolicyName": "The name of the key policy to retrieve."
},
"output": {
"Policy": "The key policy document."
}
},
- "description": "The following example retrieves the key policy for the specified customer master key (CMK).",
+ "description": "The following example retrieves the key policy for the specified KMS key.",
"id": "to-retrieve-a-key-policy-1479170128325",
"title": "To retrieve a key policy"
}
@@ -389,15 +395,15 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose key material rotation status you want to retrieve. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose key material rotation status you want to retrieve. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
},
"output": {
"KeyRotationEnabled": "A boolean that indicates the key material rotation status. Returns true when automatic annual rotation of the key material is enabled, or false when it is not."
}
},
- "description": "The following example retrieves the status of automatic annual rotation of the key material for the specified CMK.",
+ "description": "The following example retrieves the status of automatic annual rotation of the key material for the specified KMS key.",
"id": "to-retrieve-the-rotation-status-for-a-cmk-1479172287408",
- "title": "To retrieve the rotation status for a customer master key (CMK)"
+ "title": "To retrieve the rotation status for a KMS key"
}
],
"GetParametersForImport": [
@@ -415,20 +421,20 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK for which to retrieve the public key and import token. You can use the key ID or the Amazon Resource Name (ARN) of the CMK.",
+ "KeyId": "The identifier of the KMS key for which to retrieve the public key and import token. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key.",
"WrappingAlgorithm": "The algorithm that you will use to encrypt the key material before importing it.",
"WrappingKeySpec": "The type of wrapping key (public key) to return in the response."
},
"output": {
"ImportToken": "The import token to send with a subsequent ImportKeyMaterial request.",
- "KeyId": "The ARN of the CMK for which you are retrieving the public key and import token. This is the same CMK specified in the request.",
+ "KeyId": "The ARN of the KMS key for which you are retrieving the public key and import token. This is the same KMS key specified in the request.",
"ParametersValidTo": "The time at which the import token and public key are no longer valid.",
"PublicKey": "The public key to use to encrypt the key material before importing it."
}
},
- "description": "The following example retrieves the public key and import token for the specified CMK.",
+ "description": "The following example retrieves the public key and import token for the specified KMS key.",
"id": "to-retrieve-the-public-key-and-import-token-for-a-cmk-1480626483211",
- "title": "To retrieve the public key and import token for a customer master key (CMK)"
+ "title": "To retrieve the public key and import token for a KMS key"
}
],
"ImportKeyMaterial": [
@@ -444,12 +450,12 @@
"EncryptedKeyMaterial": "The encrypted key material to import.",
"ExpirationModel": "A value that specifies whether the key material expires.",
"ImportToken": "The import token that you received in the response to a previous GetParametersForImport request.",
- "KeyId": "The identifier of the CMK to import the key material into. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key to import the key material into. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example imports key material into the specified CMK.",
+ "description": "The following example imports key material into the specified KMS key.",
"id": "to-import-key-material-into-a-cmk-1480630551969",
- "title": "To import key material into a customer master key (CMK)"
+ "title": "To import key material into a KMS key"
}
],
"ListAliases": [
@@ -501,7 +507,7 @@
},
"comments": {
"output": {
- "Aliases": "A list of aliases, including the key ID of the customer master key (CMK) that each alias refers to.",
+ "Aliases": "A list of aliases, including the key ID of the KMS key that each alias refers to.",
"Truncated": "A boolean that indicates whether there are more items in the list. Returns true when there are more items, or false when there are not."
}
},
@@ -573,16 +579,16 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose grants you want to list. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose grants you want to list. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
},
"output": {
"Grants": "A list of grants.",
"Truncated": "A boolean that indicates whether there are more items in the list. Returns true when there are more items, or false when there are not."
}
},
- "description": "The following example lists grants for the specified CMK.",
+ "description": "The following example lists grants for the specified KMS key.",
"id": "to-list-grants-for-a-cmk-1481067365389",
- "title": "To list grants for a customer master key (CMK)"
+ "title": "To list grants for a KMS key"
}
],
"ListKeyPolicies": [
@@ -598,16 +604,16 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose key policies you want to list. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose key policies you want to list. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
},
"output": {
"PolicyNames": "A list of key policy names.",
"Truncated": "A boolean that indicates whether there are more items in the list. Returns true when there are more items, or false when there are not."
}
},
- "description": "The following example lists key policies for the specified CMK.",
+ "description": "The following example lists key policies for the specified KMS key.",
"id": "to-list-key-policies-for-a-cmk-1481069780998",
- "title": "To list key policies for a customer master key (CMK)"
+ "title": "To list key policies for a KMS key"
}
],
"ListKeys": [
@@ -647,13 +653,13 @@
},
"comments": {
"output": {
- "Keys": "A list of CMKs, including the key ID and Amazon Resource Name (ARN) of each one.",
+ "Keys": "A list of KMS keys, including the key ID and Amazon Resource Name (ARN) of each one.",
"Truncated": "A boolean that indicates whether there are more items in the list. Returns true when there are more items, or false when there are not."
}
},
- "description": "The following example lists CMKs.",
+ "description": "The following example lists KMS keys.",
"id": "to-list-cmks-1481071643069",
- "title": "To list customer master keys (CMKs)"
+ "title": "To list KMS keys"
}
],
"ListResourceTags": [
@@ -680,16 +686,16 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose tags you are listing. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose tags you are listing. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
},
"output": {
"Tags": "A list of tags.",
"Truncated": "A boolean that indicates whether there are more items in the list. Returns true when there are more items, or false when there are not."
}
},
- "description": "The following example lists tags for a CMK.",
+ "description": "The following example lists tags for a KMS key.",
"id": "to-list-tags-for-a-cmk-1483996855796",
- "title": "To list tags for a customer master key (CMK)"
+ "title": "To list tags for a KMS key"
}
],
"ListRetirableGrants": [
@@ -716,7 +722,7 @@
},
"comments": {
"input": {
- "RetiringPrincipal": "The retiring principal whose grants you want to list. Use the Amazon Resource Name (ARN) of an AWS principal such as an AWS account (root), IAM user, federated user, or assumed role user."
+ "RetiringPrincipal": "The retiring principal whose grants you want to list. Use the Amazon Resource Name (ARN) of a principal such as an AWS account (root), IAM user, federated user, or assumed role user."
},
"output": {
"Grants": "A list of grants that the specified principal can retire.",
@@ -737,14 +743,14 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK to attach the key policy to. You can use the key ID or the Amazon Resource Name (ARN) of the CMK.",
+ "KeyId": "The identifier of the KMS key to attach the key policy to. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key.",
"Policy": "The key policy document.",
"PolicyName": "The name of the key policy."
}
},
- "description": "The following example attaches a key policy to the specified CMK.",
+ "description": "The following example attaches a key policy to the specified KMS key.",
"id": "to-attach-a-key-policy-to-a-cmk-1481147345018",
- "title": "To attach a key policy to a customer master key (CMK)"
+ "title": "To attach a key policy to a KMS key"
}
],
"ReEncrypt": [
@@ -761,16 +767,16 @@
"comments": {
"input": {
"CiphertextBlob": "The data to reencrypt.",
- "DestinationKeyId": "The identifier of the CMK to use to reencrypt the data. You can use any valid key identifier.",
- "SourceKeyId": "The identifier of the CMK to use to decrypt the data. You can use any valid key identifier."
+ "DestinationKeyId": "The identifier of the KMS key to use to reencrypt the data. You can use any valid key identifier.",
+ "SourceKeyId": "The identifier of the KMS key to use to decrypt the data. You can use any valid key identifier."
},
"output": {
"CiphertextBlob": "The reencrypted data.",
- "KeyId": "The ARN of the CMK that was used to reencrypt the data.",
- "SourceKeyId": "The ARN of the CMK that was originally used to encrypt the data."
+ "KeyId": "The ARN of the KMS key that was used to reencrypt the data.",
+ "SourceKeyId": "The ARN of the KMS key that was originally used to encrypt the data."
}
},
- "description": "The following example reencrypts data with the specified CMK.",
+ "description": "The following example reencrypts data with the specified KMS key.",
"id": "to-reencrypt-data-1481230358001",
"title": "To reencrypt data"
}
@@ -784,7 +790,7 @@
"comments": {
"input": {
"GrantId": "The identifier of the grant to retire.",
- "KeyId": "The Amazon Resource Name (ARN) of the customer master key (CMK) associated with the grant."
+ "KeyId": "The Amazon Resource Name (ARN) of the KMS key associated with the grant."
}
},
"description": "The following example retires a grant.",
@@ -801,7 +807,7 @@
"comments": {
"input": {
"GrantId": "The identifier of the grant to revoke.",
- "KeyId": "The identifier of the customer master key (CMK) associated with the grant. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key associated with the grant. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
"description": "The following example revokes a grant.",
@@ -821,17 +827,17 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK to schedule for deletion. You can use the key ID or the Amazon Resource Name (ARN) of the CMK.",
- "PendingWindowInDays": "The waiting period, specified in number of days. After the waiting period ends, AWS KMS deletes the CMK."
+ "KeyId": "The identifier of the KMS key to schedule for deletion. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key.",
+ "PendingWindowInDays": "The waiting period, specified in number of days. After the waiting period ends, KMS deletes the KMS key."
},
"output": {
- "DeletionDate": "The date and time after which AWS KMS deletes the CMK.",
- "KeyId": "The ARN of the CMK that is scheduled for deletion."
+ "DeletionDate": "The date and time after which KMS deletes the KMS key.",
+ "KeyId": "The ARN of the KMS key that is scheduled for deletion."
}
},
- "description": "The following example schedules the specified CMK for deletion.",
+ "description": "The following example schedules the specified KMS key for deletion.",
"id": "to-schedule-a-cmk-for-deletion-1481331111094",
- "title": "To schedule a customer master key (CMK) for deletion"
+ "title": "To schedule a KMS key for deletion"
}
],
"TagResource": [
@@ -847,13 +853,13 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK you are tagging. You can use the key ID or the Amazon Resource Name (ARN) of the CMK.",
+ "KeyId": "The identifier of the KMS key you are tagging. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key.",
"Tags": "A list of tags."
}
},
- "description": "The following example tags a CMK.",
+ "description": "The following example tags a KMS key.",
"id": "to-tag-a-cmk-1483997246518",
- "title": "To tag a customer master key (CMK)"
+ "title": "To tag a KMS key"
}
],
"UntagResource": [
@@ -867,13 +873,13 @@
},
"comments": {
"input": {
- "KeyId": "The identifier of the CMK whose tags you are removing.",
+ "KeyId": "The identifier of the KMS key whose tags you are removing.",
"TagKeys": "A list of tag keys. Provide only the tag keys, not the tag values."
}
},
- "description": "The following example removes tags from a CMK.",
+ "description": "The following example removes tags from a KMS key.",
"id": "to-remove-tags-from-a-cmk-1483997590962",
- "title": "To remove tags from a customer master key (CMK)"
+ "title": "To remove tags from a KMS key"
}
],
"UpdateAlias": [
@@ -885,10 +891,10 @@
"comments": {
"input": {
"AliasName": "The alias to update.",
- "TargetKeyId": "The identifier of the CMK that the alias will refer to after this operation succeeds. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "TargetKeyId": "The identifier of the KMS key that the alias will refer to after this operation succeeds. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example updates the specified alias to refer to the specified customer master key (CMK).",
+ "description": "The following example updates the specified alias to refer to the specified KMS key.",
"id": "to-update-an-alias-1481572726920",
"title": "To update an alias"
}
@@ -896,18 +902,18 @@
"UpdateKeyDescription": [
{
"input": {
- "Description": "Example description that indicates the intended use of this CMK.",
+ "Description": "Example description that indicates the intended use of this KMS key.",
"KeyId": "1234abcd-12ab-34cd-56ef-1234567890ab"
},
"comments": {
"input": {
"Description": "The updated description.",
- "KeyId": "The identifier of the CMK whose description you are updating. You can use the key ID or the Amazon Resource Name (ARN) of the CMK."
+ "KeyId": "The identifier of the KMS key whose description you are updating. You can use the key ID or the Amazon Resource Name (ARN) of the KMS key."
}
},
- "description": "The following example updates the description of the specified CMK.",
+ "description": "The following example updates the description of the specified KMS key.",
"id": "to-update-the-description-of-a-cmk-1481574808619",
- "title": "To update the description of a customer master key (CMK)"
+ "title": "To update the description of a KMS key"
}
]
}
diff --git a/service/cloudformation/api.go b/service/cloudformation/api.go
index d0142d095ab..6e6174b5758 100644
--- a/service/cloudformation/api.go
+++ b/service/cloudformation/api.go
@@ -1879,7 +1879,7 @@ func (c *CloudFormation) DescribeStackInstanceRequest(input *DescribeStackInstan
// DescribeStackInstance API operation for AWS CloudFormation.
//
// Returns the stack instance that's associated with the specified stack set,
-// account, and Region.
+// Amazon Web Services account, and Region.
//
// For a list of stack instances that are associated with a specific stack set,
// use ListStackInstances.
@@ -4006,7 +4006,8 @@ func (c *CloudFormation) ListStackInstancesRequest(input *ListStackInstancesInpu
//
// Returns summary information about stack instances that are associated with
// the specified stack set. You can filter for stack instances that are associated
-// with a specific account name or Region, or that have a specific status.
+// with a specific Amazon Web Services account name or Region, or that have
+// a specific status.
//
// Returns awserr.Error for service API and SDK errors. Use runtime type assertions
// with awserr.Error's Code and Message methods to get detailed information about
@@ -4559,8 +4560,8 @@ func (c *CloudFormation) ListStackSetsRequest(input *ListStackSetsInput) (req *r
// user.
//
// * [Self-managed permissions] If you set the CallAs parameter to SELF while
-// signed in to your account, ListStackSets returns all self-managed stack
-// sets in your account.
+// signed in to your Amazon Web Services account, ListStackSets returns all
+// self-managed stack sets in your Amazon Web Services account.
//
// * [Service-managed permissions] If you set the CallAs parameter to SELF
// while signed in to the organization's management account, ListStackSets
@@ -5421,7 +5422,7 @@ func (c *CloudFormation) RegisterPublisherRequest(input *RegisterPublisherInput)
//
// Registers your account as a publisher of public extensions in the CloudFormation
// registry. Public extensions are available for use by all CloudFormation users.
-// This publisher ID applies to your account in all Regions.
+// This publisher ID applies to your account in all Amazon Web Services Regions.
//
// For information on requirements for registering as a public extension publisher,
// see Registering your account to publish CloudFormation extensions (https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/publish-extension.html#publish-extension-prereqs)
@@ -5505,8 +5506,8 @@ func (c *CloudFormation) RegisterTypeRequest(input *RegisterTypeInput) (req *req
// RegisterType API operation for AWS CloudFormation.
//
// Registers an extension with the CloudFormation service. Registering an extension
-// makes it available for use in CloudFormation templates in your account, and
-// includes:
+// makes it available for use in CloudFormation templates in your Amazon Web
+// Services account, and includes:
//
// * Validating the extension schema
//
@@ -5565,6 +5566,104 @@ func (c *CloudFormation) RegisterTypeWithContext(ctx aws.Context, input *Registe
return out, req.Send()
}
+const opRollbackStack = "RollbackStack"
+
+// RollbackStackRequest generates a "aws/request.Request" representing the
+// client's request for the RollbackStack operation. The "output" return
+// value will be populated with the request's response once the request completes
+// successfully.
+//
+// Use "Send" method on the returned Request to send the API call to the service.
+// the "output" return value is not valid until after Send returns without error.
+//
+// See RollbackStack for more information on using the RollbackStack
+// API call, and error handling.
+//
+// This method is useful when you want to inject custom logic or configuration
+// into the SDK's request lifecycle. Such as custom headers, or retry logic.
+//
+//
+// // Example sending a request using the RollbackStackRequest method.
+// req, resp := client.RollbackStackRequest(params)
+//
+// err := req.Send()
+// if err == nil { // resp is now filled
+// fmt.Println(resp)
+// }
+//
+// See also, https://docs.aws.amazon.com/goto/WebAPI/cloudformation-2010-05-15/RollbackStack
+func (c *CloudFormation) RollbackStackRequest(input *RollbackStackInput) (req *request.Request, output *RollbackStackOutput) {
+ op := &request.Operation{
+ Name: opRollbackStack,
+ HTTPMethod: "POST",
+ HTTPPath: "/",
+ }
+
+ if input == nil {
+ input = &RollbackStackInput{}
+ }
+
+ output = &RollbackStackOutput{}
+ req = c.newRequest(op, input, output)
+ return
+}
+
+// RollbackStack API operation for AWS CloudFormation.
+//
+// When specifying RollbackStack, you preserve the state of previously provisioned
+// resources when an operation fails. You can check the status of the stack
+// through the DescribeStacks API.
+//
+// Rolls back the specified stack to the last known stable state from CREATE_FAILED
+// or UPDATE_FAILED stack statuses.
+//
+// This operation will delete a stack if it doesn't contain a last known stable
+// state. A last known stable state includes any status in a *_COMPLETE. This
+// includes the following stack statuses.
+//
+// * CREATE_COMPLETE
+//
+// * UPDATE_COMPLETE
+//
+// * UPDATE_ROLLBACK_COMPLETE
+//
+// * IMPORT_COMPLETE
+//
+// * IMPORT_ROLLBACK_COMPLETE
+//
+// Returns awserr.Error for service API and SDK errors. Use runtime type assertions
+// with awserr.Error's Code and Message methods to get detailed information about
+// the error.
+//
+// See the AWS API reference guide for AWS CloudFormation's
+// API operation RollbackStack for usage and error information.
+//
+// Returned Error Codes:
+// * ErrCodeTokenAlreadyExistsException "TokenAlreadyExistsException"
+// A client request token already exists.
+//
+// See also, https://docs.aws.amazon.com/goto/WebAPI/cloudformation-2010-05-15/RollbackStack
+func (c *CloudFormation) RollbackStack(input *RollbackStackInput) (*RollbackStackOutput, error) {
+ req, out := c.RollbackStackRequest(input)
+ return out, req.Send()
+}
+
+// RollbackStackWithContext is the same as RollbackStack with the addition of
+// the ability to pass a context and additional request options.
+//
+// See RollbackStack for details on how to use this API operation.
+//
+// The context must be non-nil and will be used for request cancellation. If
+// the context is nil a panic will occur. In the future the SDK may create
+// sub-contexts for http.Requests. See https://golang.org/pkg/context/
+// for more information on using Contexts.
+func (c *CloudFormation) RollbackStackWithContext(ctx aws.Context, input *RollbackStackInput, opts ...request.Option) (*RollbackStackOutput, error) {
+ req, out := c.RollbackStackRequest(input)
+ req.SetContext(ctx)
+ req.ApplyOptions(opts...)
+ return out, req.Send()
+}
+
const opSetStackPolicy = "SetStackPolicy"
// SetStackPolicyRequest generates a "aws/request.Request" representing the
@@ -7420,14 +7519,14 @@ type CreateChangeSetInput struct {
// certain capabilities in order for CloudFormation to create the stack.
//
// * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some stack templates might include
- // resources that can affect permissions in your account; for example, by
- // creating new Identity and Access Management (IAM) users. For those stacks,
- // you must explicitly acknowledge this by specifying one of these capabilities.
- // The following IAM resources require you to specify either the CAPABILITY_IAM
- // or CAPABILITY_NAMED_IAM capability. If you have IAM resources, you can
- // specify either capability. If you have IAM resources with custom names,
- // you must specify CAPABILITY_NAMED_IAM. If you don't specify either of
- // these capabilities, CloudFormation returns an InsufficientCapabilities
+ // resources that can affect permissions in your Amazon Web Services account;
+ // for example, by creating new Identity and Access Management (IAM) users.
+ // For those stacks, you must explicitly acknowledge this by specifying one
+ // of these capabilities. The following IAM resources require you to specify
+ // either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability. If you have
+ // IAM resources, you can specify either capability. If you have IAM resources
+ // with custom names, you must specify CAPABILITY_NAMED_IAM. If you don't
+ // specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
// error. If your stack template contains these resources, we recommend that
// you review all permissions associated with them and edit their permissions
// if necessary. AWS::IAM::AccessKey (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
@@ -7787,14 +7886,14 @@ type CreateStackInput struct {
// certain capabilities in order for CloudFormation to create the stack.
//
// * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some stack templates might include
- // resources that can affect permissions in your account; for example, by
- // creating new Identity and Access Management (IAM) users. For those stacks,
- // you must explicitly acknowledge this by specifying one of these capabilities.
- // The following IAM resources require you to specify either the CAPABILITY_IAM
- // or CAPABILITY_NAMED_IAM capability. If you have IAM resources, you can
- // specify either capability. If you have IAM resources with custom names,
- // you must specify CAPABILITY_NAMED_IAM. If you don't specify either of
- // these capabilities, CloudFormation returns an InsufficientCapabilities
+ // resources that can affect permissions in your Amazon Web Services account;
+ // for example, by creating new Identity and Access Management (IAM) users.
+ // For those stacks, you must explicitly acknowledge this by specifying one
+ // of these capabilities. The following IAM resources require you to specify
+ // either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability. If you have
+ // IAM resources, you can specify either capability. If you have IAM resources
+ // with custom names, you must specify CAPABILITY_NAMED_IAM. If you don't
+ // specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
// error. If your stack template contains these resources, we recommend that
// you review all permissions associated with them and edit their permissions
// if necessary. AWS::IAM::AccessKey (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
@@ -7916,7 +8015,7 @@ type CreateStackInput struct {
// Region in which you are creating the stack.
//
// A stack name can contain only alphanumeric characters (case sensitive) and
- // hyphens. It must start with an alphabetic character and cannot be longer
+ // hyphens. It must start with an alphabetical character and cannot be longer
// than 128 characters.
//
// StackName is a required field
@@ -8127,8 +8226,8 @@ func (s *CreateStackInput) SetTimeoutInMinutes(v int64) *CreateStackInput {
type CreateStackInstancesInput struct {
_ struct{} `type:"structure"`
- // [Self-managed permissions] The names of one or more accounts that you want
- // to create stack instances in the specified Region(s) for.
+ // [Self-managed permissions] The names of one or more Amazon Web Services accounts
+ // that you want to create stack instances in the specified Region(s) for.
//
// You can specify Accounts or DeploymentTargets, but not both.
Accounts []*string `type:"list"`
@@ -8143,9 +8242,9 @@ type CreateStackInstancesInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -8202,7 +8301,7 @@ type CreateStackInstancesInput struct {
ParameterOverrides []*Parameter `type:"list"`
// The names of one or more Regions where you want to create stack instances
- // using the specified accounts.
+ // using the specified Amazon Web Services accounts.
//
// Regions is a required field
Regions []*string `type:"list" required:"true"`
@@ -8378,8 +8477,9 @@ type CreateStackSetInput struct {
//
// * To create a stack set with service-managed permissions while signed
// in to a delegated administrator account, specify DELEGATED_ADMIN. Your
- // account must be registered as a delegated admin in the management account.
- // For more information, see Register a delegated administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Amazon Web Services account must be registered as a delegated admin in
+ // the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
//
// Stack sets with service-managed permissions are created in the management
@@ -8391,17 +8491,17 @@ type CreateStackSetInput struct {
// set and related stack instances.
//
// * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some stack templates might include
- // resources that can affect permissions in your account; for example, by
- // creating new Identity and Access Management (IAM) users. For those stack
- // sets, you must explicitly acknowledge this by specifying one of these
- // capabilities. The following IAM resources require you to specify either
- // the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability. If you have IAM
- // resources, you can specify either capability. If you have IAM resources
- // with custom names, you must specify CAPABILITY_NAMED_IAM. If you don't
- // specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
- // error. If your stack template contains these resources, we recommend that
- // you review all permissions associated with them and edit their permissions
- // if necessary. AWS::IAM::AccessKey (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
+ // resources that can affect permissions in your Amazon Web Services account;
+ // for example, by creating new Identity and Access Management (IAM) users.
+ // For those stack sets, you must explicitly acknowledge this by specifying
+ // one of these capabilities. The following IAM resources require you to
+ // specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability.
+ // If you have IAM resources, you can specify either capability. If you have
+ // IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM.
+ // If you don't specify either of these capabilities, CloudFormation returns
+ // an InsufficientCapabilities error. If your stack template contains these
+ // resources, we recommend that you review all permissions associated with
+ // them and edit their permissions if necessary. AWS::IAM::AccessKey (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
// AWS::IAM::Group (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-group.html)
// AWS::IAM::InstanceProfile (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-instanceprofile.html)
// AWS::IAM::Policy (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-policy.html)
@@ -8908,8 +9008,8 @@ func (s *DeleteStackInput) SetStackName(v string) *DeleteStackInput {
type DeleteStackInstancesInput struct {
_ struct{} `type:"structure"`
- // [Self-managed permissions] The names of the accounts that you want to delete
- // stack instances for.
+ // [Self-managed permissions] The names of the Amazon Web Services accounts
+ // that you want to delete stack instances for.
//
// You can specify Accounts or DeploymentTargets, but not both.
Accounts []*string `type:"list"`
@@ -8924,9 +9024,9 @@ type DeleteStackInstancesInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -9113,9 +9213,9 @@ type DeleteStackSetInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -9185,8 +9285,8 @@ func (s DeleteStackSetOutput) GoString() string {
type DeploymentTargets struct {
_ struct{} `type:"structure"`
- // The names of one or more accounts for which you want to deploy stack set
- // updates.
+ // The names of one or more Amazon Web Services accounts for which you want
+ // to deploy stack set updates.
Accounts []*string `type:"list"`
// Returns the value of the AccountsUrl property.
@@ -10025,13 +10125,14 @@ type DescribeStackInstanceInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
- // The ID of an account that's associated with this stack instance.
+ // The ID of an Amazon Web Services account that's associated with this stack
+ // instance.
//
// StackInstanceAccount is a required field
StackInstanceAccount *string `type:"string" required:"true"`
@@ -10452,9 +10553,9 @@ type DescribeStackSetInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -10512,9 +10613,9 @@ type DescribeStackSetOperationInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -11475,9 +11576,9 @@ type DetectStackSetDriftInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -11690,6 +11791,12 @@ type ExecuteChangeSetInput struct {
// received them.
ClientRequestToken *string `min:"1" type:"string"`
+ // Preserves the state of previously provisioned resources when an operation
+ // fails.
+ //
+ // Default: True
+ DisableRollback *bool `type:"boolean"`
+
// If you specified the name of a change set, specify the stack name or ID (ARN)
// that is associated with the change set you want to execute.
StackName *string `min:"1" type:"string"`
@@ -11739,6 +11846,12 @@ func (s *ExecuteChangeSetInput) SetClientRequestToken(v string) *ExecuteChangeSe
return s
}
+// SetDisableRollback sets the DisableRollback field's value.
+func (s *ExecuteChangeSetInput) SetDisableRollback(v bool) *ExecuteChangeSetInput {
+ s.DisableRollback = &v
+ return s
+}
+
// SetStackName sets the StackName field's value.
func (s *ExecuteChangeSetInput) SetStackName(v string) *ExecuteChangeSetInput {
s.StackName = &v
@@ -11996,9 +12109,9 @@ type GetTemplateSummaryInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -12586,9 +12699,9 @@ type ListStackInstancesInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -12608,7 +12721,8 @@ type ListStackInstancesInput struct {
// response object's NextToken parameter is set to null.
NextToken *string `min:"1" type:"string"`
- // The name of the account that you want to list stack instances for.
+ // The name of the Amazon Web Services account that you want to list stack instances
+ // for.
StackInstanceAccount *string `type:"string"`
// The name of the Region where you want to list stack instances.
@@ -12845,9 +12959,9 @@ type ListStackSetOperationResultsInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -12991,9 +13105,9 @@ type ListStackSetOperationsInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -13119,9 +13233,9 @@ type ListStackSetsInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -14057,7 +14171,7 @@ type ParameterDeclaration struct {
Description *string `min:"1" type:"string"`
// Flag that indicates whether the parameter value is shown as plain text in
- // logs and in the Management Console.
+ // logs and in the Amazon Web Services Management Console.
NoEcho *bool `type:"boolean"`
// The criteria that CloudFormation uses to validate parameter values.
@@ -15262,6 +15376,95 @@ func (s *RollbackConfiguration) SetRollbackTriggers(v []*RollbackTrigger) *Rollb
return s
}
+type RollbackStackInput struct {
+ _ struct{} `type:"structure"`
+
+ // A unique identifier for this RollbackStack request.
+ ClientRequestToken *string `min:"1" type:"string"`
+
+ // The Amazon Resource Name (ARN) of an Identity and Access Management role
+ // that CloudFormation assumes to rollback the stack.
+ RoleARN *string `min:"20" type:"string"`
+
+ // The name that is associated with the stack.
+ //
+ // StackName is a required field
+ StackName *string `min:"1" type:"string" required:"true"`
+}
+
+// String returns the string representation
+func (s RollbackStackInput) String() string {
+ return awsutil.Prettify(s)
+}
+
+// GoString returns the string representation
+func (s RollbackStackInput) GoString() string {
+ return s.String()
+}
+
+// Validate inspects the fields of the type to determine if they are valid.
+func (s *RollbackStackInput) Validate() error {
+ invalidParams := request.ErrInvalidParams{Context: "RollbackStackInput"}
+ if s.ClientRequestToken != nil && len(*s.ClientRequestToken) < 1 {
+ invalidParams.Add(request.NewErrParamMinLen("ClientRequestToken", 1))
+ }
+ if s.RoleARN != nil && len(*s.RoleARN) < 20 {
+ invalidParams.Add(request.NewErrParamMinLen("RoleARN", 20))
+ }
+ if s.StackName == nil {
+ invalidParams.Add(request.NewErrParamRequired("StackName"))
+ }
+ if s.StackName != nil && len(*s.StackName) < 1 {
+ invalidParams.Add(request.NewErrParamMinLen("StackName", 1))
+ }
+
+ if invalidParams.Len() > 0 {
+ return invalidParams
+ }
+ return nil
+}
+
+// SetClientRequestToken sets the ClientRequestToken field's value.
+func (s *RollbackStackInput) SetClientRequestToken(v string) *RollbackStackInput {
+ s.ClientRequestToken = &v
+ return s
+}
+
+// SetRoleARN sets the RoleARN field's value.
+func (s *RollbackStackInput) SetRoleARN(v string) *RollbackStackInput {
+ s.RoleARN = &v
+ return s
+}
+
+// SetStackName sets the StackName field's value.
+func (s *RollbackStackInput) SetStackName(v string) *RollbackStackInput {
+ s.StackName = &v
+ return s
+}
+
+type RollbackStackOutput struct {
+ _ struct{} `type:"structure"`
+
+ // Unique identifier of the stack.
+ StackId *string `type:"string"`
+}
+
+// String returns the string representation
+func (s RollbackStackOutput) String() string {
+ return awsutil.Prettify(s)
+}
+
+// GoString returns the string representation
+func (s RollbackStackOutput) GoString() string {
+ return s.String()
+}
+
+// SetStackId sets the StackId field's value.
+func (s *RollbackStackOutput) SetStackId(v string) *RollbackStackOutput {
+ s.StackId = &v
+ return s
+}
+
// A rollback trigger CloudFormation monitors during creation and updating of
// stacks. If any of the alarms you specify goes to ALARM state during the stack
// operation or within the specified monitoring period afterwards, CloudFormation
@@ -16229,8 +16432,8 @@ func (s *StackEvent) SetTimestamp(v time.Time) *StackEvent {
type StackInstance struct {
_ struct{} `type:"structure"`
- // [Self-managed permissions] The name of the account that the stack instance
- // is associated with.
+ // [Self-managed permissions] The name of the Amazon Web Services account that
+ // the stack instance is associated with.
Account *string `type:"string"`
// Status of the stack instance's actual configuration compared to the expected
@@ -16263,7 +16466,8 @@ type StackInstance struct {
// in this stack instance.
ParameterOverrides []*Parameter `type:"list"`
- // The name of the Region that the stack instance is associated with.
+ // The name of the Amazon Web Services Region that the stack instance is associated
+ // with.
Region *string `type:"string"`
// The ID of the stack instance.
@@ -16469,8 +16673,8 @@ func (s *StackInstanceFilter) SetValues(v string) *StackInstanceFilter {
type StackInstanceSummary struct {
_ struct{} `type:"structure"`
- // [Self-managed permissions] The name of the account that the stack instance
- // is associated with.
+ // [Self-managed permissions] The name of the Amazon Web Services account that
+ // the stack instance is associated with.
Account *string `type:"string"`
// Status of the stack instance's actual configuration compared to the expected
@@ -16499,7 +16703,8 @@ type StackInstanceSummary struct {
// unit (OU) IDs that you specified for DeploymentTargets (https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_DeploymentTargets.html).
OrganizationalUnitId *string `type:"string"`
- // The name of the Region that the stack instance is associated with.
+ // The name of the Amazon Web Services Region that the stack instance is associated
+ // with.
Region *string `type:"string"`
// The ID of the stack instance.
@@ -17241,9 +17446,10 @@ func (s *StackResourceSummary) SetResourceType(v string) *StackResourceSummary {
}
// A structure that contains information about a stack set. A stack set enables
-// you to provision stacks into accounts and across Regions by using a single
-// CloudFormation template. In the stack set, you specify the template to use,
-// as well as any parameters and capabilities that the template requires.
+// you to provision stacks into Amazon Web Services accounts and across Regions
+// by using a single CloudFormation template. In the stack set, you specify
+// the template to use, as well as any parameters and capabilities that the
+// template requires.
type StackSet struct {
_ struct{} `type:"structure"`
@@ -17262,10 +17468,10 @@ type StackSet struct {
AutoDeployment *AutoDeployment `type:"structure"`
// The capabilities that are allowed in the stack set. Some stack set templates
- // might include resources that can affect permissions in your account—for
- // example, by creating new Identity and Access Management (IAM) users. For
- // more information, see Acknowledging IAM Resources in CloudFormation Templates.
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html#capabilities)
+ // might include resources that can affect permissions in your Amazon Web Services
+ // account—for example, by creating new Identity and Access Management (IAM)
+ // users. For more information, see Acknowledging IAM Resources in CloudFormation
+ // Templates. (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html#capabilities)
Capabilities []*string `type:"list"`
// A description of the stack set that you specify when the stack set is created
@@ -17878,7 +18084,8 @@ func (s *StackSetOperationPreferences) SetRegionOrder(v []*string) *StackSetOper
type StackSetOperationResultSummary struct {
_ struct{} `type:"structure"`
- // [Self-managed permissions] The name of the account for this operation result.
+ // [Self-managed permissions] The name of the Amazon Web Services account for
+ // this operation result.
Account *string `type:"string"`
// The results of the account gate function CloudFormation invokes, if present,
@@ -17889,7 +18096,7 @@ type StackSetOperationResultSummary struct {
// unit (OU) IDs that you specified for DeploymentTargets (https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_DeploymentTargets.html).
OrganizationalUnitId *string `type:"string"`
- // The name of the Region for this operation result.
+ // The name of the Amazon Web Services Region for this operation result.
Region *string `type:"string"`
// The result status of the stack set operation for the given account in the
@@ -18316,9 +18523,9 @@ type StopStackSetOperationInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -19187,14 +19394,14 @@ type UpdateStackInput struct {
// certain capabilities in order for CloudFormation to update the stack.
//
// * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some stack templates might include
- // resources that can affect permissions in your account; for example, by
- // creating new Identity and Access Management (IAM) users. For those stacks,
- // you must explicitly acknowledge this by specifying one of these capabilities.
- // The following IAM resources require you to specify either the CAPABILITY_IAM
- // or CAPABILITY_NAMED_IAM capability. If you have IAM resources, you can
- // specify either capability. If you have IAM resources with custom names,
- // you must specify CAPABILITY_NAMED_IAM. If you don't specify either of
- // these capabilities, CloudFormation returns an InsufficientCapabilities
+ // resources that can affect permissions in your Amazon Web Services account;
+ // for example, by creating new Identity and Access Management (IAM) users.
+ // For those stacks, you must explicitly acknowledge this by specifying one
+ // of these capabilities. The following IAM resources require you to specify
+ // either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability. If you have
+ // IAM resources, you can specify either capability. If you have IAM resources
+ // with custom names, you must specify CAPABILITY_NAMED_IAM. If you don't
+ // specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
// error. If your stack template contains these resources, we recommend that
// you review all permissions associated with them and edit their permissions
// if necessary. AWS::IAM::AccessKey (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
@@ -19245,6 +19452,12 @@ type UpdateStackInput struct {
// stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002.
ClientRequestToken *string `min:"1" type:"string"`
+ // Preserve the state of previously provisioned resources when an operation
+ // fails.
+ //
+ // Default: False
+ DisableRollback *bool `type:"boolean"`
+
// Amazon Simple Notification Service topic Amazon Resource Names (ARNs) that
// CloudFormation associates with the stack. Specify an empty list to remove
// all notification topics.
@@ -19433,6 +19646,12 @@ func (s *UpdateStackInput) SetClientRequestToken(v string) *UpdateStackInput {
return s
}
+// SetDisableRollback sets the DisableRollback field's value.
+func (s *UpdateStackInput) SetDisableRollback(v bool) *UpdateStackInput {
+ s.DisableRollback = &v
+ return s
+}
+
// SetNotificationARNs sets the NotificationARNs field's value.
func (s *UpdateStackInput) SetNotificationARNs(v []*string) *UpdateStackInput {
s.NotificationARNs = v
@@ -19520,10 +19739,10 @@ func (s *UpdateStackInput) SetUsePreviousTemplate(v bool) *UpdateStackInput {
type UpdateStackInstancesInput struct {
_ struct{} `type:"structure"`
- // [Self-managed permissions] The names of one or more accounts for which you
- // want to update parameter values for stack instances. The overridden parameter
- // values will be applied to all stack instances in the specified accounts and
- // Regions.
+ // [Self-managed permissions] The names of one or more Amazon Web Services accounts
+ // for which you want to update parameter values for stack instances. The overridden
+ // parameter values will be applied to all stack instances in the specified
+ // accounts and Regions.
//
// You can specify Accounts or DeploymentTargets, but not both.
Accounts []*string `type:"list"`
@@ -19538,9 +19757,9 @@ type UpdateStackInstancesInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -19799,9 +20018,9 @@ type UpdateStackSetInput struct {
// * If you are signed in to the management account, specify SELF.
//
// * If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN.
- // Your account must be registered as a delegated administrator in the management
- // account. For more information, see Register a delegated administrator
- // (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
+ // Your Amazon Web Services account must be registered as a delegated administrator
+ // in the management account. For more information, see Register a delegated
+ // administrator (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-orgs-delegated-admin.html)
// in the CloudFormation User Guide.
CallAs *string `type:"string" enum:"CallAs"`
@@ -19810,17 +20029,17 @@ type UpdateStackSetInput struct {
// and its associated stack instances.
//
// * CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some stack templates might include
- // resources that can affect permissions in your account; for example, by
- // creating new Identity and Access Management (IAM) users. For those stacks
- // sets, you must explicitly acknowledge this by specifying one of these
- // capabilities. The following IAM resources require you to specify either
- // the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability. If you have IAM
- // resources, you can specify either capability. If you have IAM resources
- // with custom names, you must specify CAPABILITY_NAMED_IAM. If you don't
- // specify either of these capabilities, CloudFormation returns an InsufficientCapabilities
- // error. If your stack template contains these resources, we recommend that
- // you review all permissions associated with them and edit their permissions
- // if necessary. AWS::IAM::AccessKey (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
+ // resources that can affect permissions in your Amazon Web Services account;
+ // for example, by creating new Identity and Access Management (IAM) users.
+ // For those stacks sets, you must explicitly acknowledge this by specifying
+ // one of these capabilities. The following IAM resources require you to
+ // specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability.
+ // If you have IAM resources, you can specify either capability. If you have
+ // IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM.
+ // If you don't specify either of these capabilities, CloudFormation returns
+ // an InsufficientCapabilities error. If your stack template contains these
+ // resources, we recommend that you review all permissions associated with
+ // them and edit their permissions if necessary. AWS::IAM::AccessKey (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-accesskey.html)
// AWS::IAM::Group (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-group.html)
// AWS::IAM::InstanceProfile (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iam-instanceprofile.html)
// AWS::IAM::Policy (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-iam-policy.html)
@@ -21048,6 +21267,24 @@ const (
// ResourceStatusImportRollbackComplete is a ResourceStatus enum value
ResourceStatusImportRollbackComplete = "IMPORT_ROLLBACK_COMPLETE"
+
+ // ResourceStatusUpdateRollbackInProgress is a ResourceStatus enum value
+ ResourceStatusUpdateRollbackInProgress = "UPDATE_ROLLBACK_IN_PROGRESS"
+
+ // ResourceStatusUpdateRollbackComplete is a ResourceStatus enum value
+ ResourceStatusUpdateRollbackComplete = "UPDATE_ROLLBACK_COMPLETE"
+
+ // ResourceStatusUpdateRollbackFailed is a ResourceStatus enum value
+ ResourceStatusUpdateRollbackFailed = "UPDATE_ROLLBACK_FAILED"
+
+ // ResourceStatusRollbackInProgress is a ResourceStatus enum value
+ ResourceStatusRollbackInProgress = "ROLLBACK_IN_PROGRESS"
+
+ // ResourceStatusRollbackComplete is a ResourceStatus enum value
+ ResourceStatusRollbackComplete = "ROLLBACK_COMPLETE"
+
+ // ResourceStatusRollbackFailed is a ResourceStatus enum value
+ ResourceStatusRollbackFailed = "ROLLBACK_FAILED"
)
// ResourceStatus_Values returns all elements of the ResourceStatus enum
@@ -21069,6 +21306,12 @@ func ResourceStatus_Values() []string {
ResourceStatusImportRollbackInProgress,
ResourceStatusImportRollbackFailed,
ResourceStatusImportRollbackComplete,
+ ResourceStatusUpdateRollbackInProgress,
+ ResourceStatusUpdateRollbackComplete,
+ ResourceStatusUpdateRollbackFailed,
+ ResourceStatusRollbackInProgress,
+ ResourceStatusRollbackComplete,
+ ResourceStatusRollbackFailed,
}
}
@@ -21389,6 +21632,9 @@ const (
// StackStatusUpdateComplete is a StackStatus enum value
StackStatusUpdateComplete = "UPDATE_COMPLETE"
+ // StackStatusUpdateFailed is a StackStatus enum value
+ StackStatusUpdateFailed = "UPDATE_FAILED"
+
// StackStatusUpdateRollbackInProgress is a StackStatus enum value
StackStatusUpdateRollbackInProgress = "UPDATE_ROLLBACK_IN_PROGRESS"
@@ -21435,6 +21681,7 @@ func StackStatus_Values() []string {
StackStatusUpdateInProgress,
StackStatusUpdateCompleteCleanupInProgress,
StackStatusUpdateComplete,
+ StackStatusUpdateFailed,
StackStatusUpdateRollbackInProgress,
StackStatusUpdateRollbackFailed,
StackStatusUpdateRollbackCompleteCleanupInProgress,
diff --git a/service/cloudformation/cloudformationiface/interface.go b/service/cloudformation/cloudformationiface/interface.go
index 02b022eb313..20f76853c7c 100644
--- a/service/cloudformation/cloudformationiface/interface.go
+++ b/service/cloudformation/cloudformationiface/interface.go
@@ -320,6 +320,10 @@ type CloudFormationAPI interface {
RegisterTypeWithContext(aws.Context, *cloudformation.RegisterTypeInput, ...request.Option) (*cloudformation.RegisterTypeOutput, error)
RegisterTypeRequest(*cloudformation.RegisterTypeInput) (*request.Request, *cloudformation.RegisterTypeOutput)
+ RollbackStack(*cloudformation.RollbackStackInput) (*cloudformation.RollbackStackOutput, error)
+ RollbackStackWithContext(aws.Context, *cloudformation.RollbackStackInput, ...request.Option) (*cloudformation.RollbackStackOutput, error)
+ RollbackStackRequest(*cloudformation.RollbackStackInput) (*request.Request, *cloudformation.RollbackStackOutput)
+
SetStackPolicy(*cloudformation.SetStackPolicyInput) (*cloudformation.SetStackPolicyOutput, error)
SetStackPolicyWithContext(aws.Context, *cloudformation.SetStackPolicyInput, ...request.Option) (*cloudformation.SetStackPolicyOutput, error)
SetStackPolicyRequest(*cloudformation.SetStackPolicyInput) (*request.Request, *cloudformation.SetStackPolicyOutput)
diff --git a/service/codebuild/api.go b/service/codebuild/api.go
index 15be53fd7d0..b64bf5e7269 100644
--- a/service/codebuild/api.go
+++ b/service/codebuild/api.go
@@ -5844,10 +5844,6 @@ type BuildBatchPhase struct {
//
// The build phase is still in progress.
//
- // QUEUED
- //
- // The build has been submitted and is queued behind other submitted builds.
- //
// STOPPED
//
// The build phase stopped.
@@ -6068,10 +6064,6 @@ type BuildPhase struct {
//
// The build phase is still in progress.
//
- // QUEUED
- //
- // The build has been submitted and is queued behind other submitted builds.
- //
// STOPPED
//
// The build phase stopped.
@@ -6087,29 +6079,49 @@ type BuildPhase struct {
// The name of the build phase. Valid values include:
//
- // * BUILD: Core build activities typically occur in this build phase.
+ // BUILD
+ //
+ // Core build activities typically occur in this build phase.
+ //
+ // COMPLETED
+ //
+ // The build has been completed.
//
- // * COMPLETED: The build has been completed.
+ // DOWNLOAD_SOURCE
//
- // * DOWNLOAD_SOURCE: Source code is being downloaded in this build phase.
+ // Source code is being downloaded in this build phase.
//
- // * FINALIZING: The build process is completing in this build phase.
+ // FINALIZING
//
- // * INSTALL: Installation activities typically occur in this build phase.
+ // The build process is completing in this build phase.
//
- // * POST_BUILD: Post-build activities typically occur in this build phase.
+ // INSTALL
//
- // * PRE_BUILD: Pre-build activities typically occur in this build phase.
+ // Installation activities typically occur in this build phase.
//
- // * PROVISIONING: The build environment is being set up.
+ // POST_BUILD
+ //
+ // Post-build activities typically occur in this build phase.
+ //
+ // PRE_BUILD
+ //
+ // Pre-build activities typically occur in this build phase.
+ //
+ // PROVISIONING
+ //
+ // The build environment is being set up.
+ //
+ // QUEUED
+ //
+ // The build has been submitted and is queued behind other submitted builds.
+ //
+ // SUBMITTED
//
- // * QUEUED: The build has been submitted and is queued behind other submitted
- // builds.
+ // The build has been submitted.
//
- // * SUBMITTED: The build has been submitted.
+ // UPLOAD_ARTIFACTS
//
- // * UPLOAD_ARTIFACTS: Build output artifacts are being uploaded to the output
- // location.
+ // Build output artifacts are being uploaded to the output location.
PhaseType *string `locationName:"phaseType" type:"string" enum:"BuildPhaseType"`
// When the build phase started, expressed in Unix time format.
diff --git a/service/firehose/api.go b/service/firehose/api.go
index 3db7c5a87b2..4bf52a6b2dc 100644
--- a/service/firehose/api.go
+++ b/service/firehose/api.go
@@ -573,7 +573,7 @@ func (c *Firehose) PutRecordRequest(input *PutRecordInput) (req *request.Request
//
// You must specify the name of the delivery stream and the data record when
// using PutRecord. The data record consists of a data blob that can be up to
-// 1,000 KB in size, and any kind of data. For example, it can be a segment
+// 1,000 KiB in size, and any kind of data. For example, it can be a segment
// from a log file, geographic location data, website clickstream data, and
// so on.
//
@@ -700,7 +700,7 @@ func (c *Firehose) PutRecordBatchRequest(input *PutRecordBatchInput) (req *reque
// (https://docs.aws.amazon.com/firehose/latest/dev/limits.html).
//
// Each PutRecordBatch request supports up to 500 records. Each record in the
-// request can be as large as 1,000 KB (before 64-bit encoding), up to a limit
+// request can be as large as 1,000 KB (before base64 encoding), up to a limit
// of 4 MB for the entire request. These limits cannot be changed.
//
// You must specify the name of the delivery stream and the data record when
@@ -2495,6 +2495,45 @@ func (s *DestinationDescription) SetSplunkDestinationDescription(v *SplunkDestin
return s
}
+// The configuration of the dynamic partitioning mechanism that creates smaller
+// data sets from the streaming data by partitioning it based on partition keys.
+// Currently, dynamic partitioning is only supported for Amazon S3 destinations.
+// For more information, see https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html
+// (https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html)
+type DynamicPartitioningConfiguration struct {
+ _ struct{} `type:"structure"`
+
+ // Specifies that the dynamic partitioning is enabled for this Kinesis Data
+ // Firehose delivery stream.
+ Enabled *bool `type:"boolean"`
+
+ // The retry behavior in case Kinesis Data Firehose is unable to deliver data
+ // to an Amazon S3 prefix.
+ RetryOptions *RetryOptions `type:"structure"`
+}
+
+// String returns the string representation
+func (s DynamicPartitioningConfiguration) String() string {
+ return awsutil.Prettify(s)
+}
+
+// GoString returns the string representation
+func (s DynamicPartitioningConfiguration) GoString() string {
+ return s.String()
+}
+
+// SetEnabled sets the Enabled field's value.
+func (s *DynamicPartitioningConfiguration) SetEnabled(v bool) *DynamicPartitioningConfiguration {
+ s.Enabled = &v
+ return s
+}
+
+// SetRetryOptions sets the RetryOptions field's value.
+func (s *DynamicPartitioningConfiguration) SetRetryOptions(v *RetryOptions) *DynamicPartitioningConfiguration {
+ s.RetryOptions = v
+ return s
+}
+
// Describes the buffering to perform before delivering data to the Amazon ES
// destination.
type ElasticsearchBufferingHints struct {
@@ -3183,6 +3222,13 @@ type ExtendedS3DestinationConfiguration struct {
// format to the Parquet or ORC format before writing it to Amazon S3.
DataFormatConversionConfiguration *DataFormatConversionConfiguration `type:"structure"`
+ // The configuration of the dynamic partitioning mechanism that creates smaller
+ // data sets from the streaming data by partitioning it based on partition keys.
+ // Currently, dynamic partitioning is only supported for Amazon S3 destinations.
+ // For more information, see https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html
+ // (https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html)
+ DynamicPartitioningConfiguration *DynamicPartitioningConfiguration `type:"structure"`
+
// The encryption configuration. If no value is specified, the default is no
// encryption.
EncryptionConfiguration *EncryptionConfiguration `type:"structure"`
@@ -3303,6 +3349,12 @@ func (s *ExtendedS3DestinationConfiguration) SetDataFormatConversionConfiguratio
return s
}
+// SetDynamicPartitioningConfiguration sets the DynamicPartitioningConfiguration field's value.
+func (s *ExtendedS3DestinationConfiguration) SetDynamicPartitioningConfiguration(v *DynamicPartitioningConfiguration) *ExtendedS3DestinationConfiguration {
+ s.DynamicPartitioningConfiguration = v
+ return s
+}
+
// SetEncryptionConfiguration sets the EncryptionConfiguration field's value.
func (s *ExtendedS3DestinationConfiguration) SetEncryptionConfiguration(v *EncryptionConfiguration) *ExtendedS3DestinationConfiguration {
s.EncryptionConfiguration = v
@@ -3372,6 +3424,13 @@ type ExtendedS3DestinationDescription struct {
// format to the Parquet or ORC format before writing it to Amazon S3.
DataFormatConversionConfiguration *DataFormatConversionConfiguration `type:"structure"`
+ // The configuration of the dynamic partitioning mechanism that creates smaller
+ // data sets from the streaming data by partitioning it based on partition keys.
+ // Currently, dynamic partitioning is only supported for Amazon S3 destinations.
+ // For more information, see https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html
+ // (https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html)
+ DynamicPartitioningConfiguration *DynamicPartitioningConfiguration `type:"structure"`
+
// The encryption configuration. If no value is specified, the default is no
// encryption.
//
@@ -3445,6 +3504,12 @@ func (s *ExtendedS3DestinationDescription) SetDataFormatConversionConfiguration(
return s
}
+// SetDynamicPartitioningConfiguration sets the DynamicPartitioningConfiguration field's value.
+func (s *ExtendedS3DestinationDescription) SetDynamicPartitioningConfiguration(v *DynamicPartitioningConfiguration) *ExtendedS3DestinationDescription {
+ s.DynamicPartitioningConfiguration = v
+ return s
+}
+
// SetEncryptionConfiguration sets the EncryptionConfiguration field's value.
func (s *ExtendedS3DestinationDescription) SetEncryptionConfiguration(v *EncryptionConfiguration) *ExtendedS3DestinationDescription {
s.EncryptionConfiguration = v
@@ -3508,6 +3573,13 @@ type ExtendedS3DestinationUpdate struct {
// format to the Parquet or ORC format before writing it to Amazon S3.
DataFormatConversionConfiguration *DataFormatConversionConfiguration `type:"structure"`
+ // The configuration of the dynamic partitioning mechanism that creates smaller
+ // data sets from the streaming data by partitioning it based on partition keys.
+ // Currently, dynamic partitioning is only supported for Amazon S3 destinations.
+ // For more information, see https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html
+ // (https://docs.aws.amazon.com/firehose/latest/dev/dynamic-partitioning.html)
+ DynamicPartitioningConfiguration *DynamicPartitioningConfiguration `type:"structure"`
+
// The encryption configuration. If no value is specified, the default is no
// encryption.
EncryptionConfiguration *EncryptionConfiguration `type:"structure"`
@@ -3619,6 +3691,12 @@ func (s *ExtendedS3DestinationUpdate) SetDataFormatConversionConfiguration(v *Da
return s
}
+// SetDynamicPartitioningConfiguration sets the DynamicPartitioningConfiguration field's value.
+func (s *ExtendedS3DestinationUpdate) SetDynamicPartitioningConfiguration(v *DynamicPartitioningConfiguration) *ExtendedS3DestinationUpdate {
+ s.DynamicPartitioningConfiguration = v
+ return s
+}
+
// SetEncryptionConfiguration sets the EncryptionConfiguration field's value.
func (s *ExtendedS3DestinationUpdate) SetEncryptionConfiguration(v *EncryptionConfiguration) *ExtendedS3DestinationUpdate {
s.EncryptionConfiguration = v
@@ -3863,6 +3941,10 @@ type HttpEndpointConfiguration struct {
// The URL of the HTTP endpoint selected as the destination.
//
+ // If you choose an HTTP endpoint as your destination, review and follow the
+ // instructions in the Appendix - HTTP Endpoint Delivery Request and Response
+ // Specifications (https://docs.aws.amazon.com/firehose/latest/dev/httpdeliveryrequestresponse.html).
+ //
// Url is a required field
Url *string `min:"1" type:"string" required:"true" sensitive:"true"`
}
@@ -6431,6 +6513,32 @@ func (s *ResourceNotFoundException) RequestID() string {
return s.RespMetadata.RequestID
}
+// The retry behavior in case Kinesis Data Firehose is unable to deliver data
+// to an Amazon S3 prefix.
+type RetryOptions struct {
+ _ struct{} `type:"structure"`
+
+ // The period of time during which Kinesis Data Firehose retries to deliver
+ // data to the specified Amazon S3 prefix.
+ DurationInSeconds *int64 `type:"integer"`
+}
+
+// String returns the string representation
+func (s RetryOptions) String() string {
+ return awsutil.Prettify(s)
+}
+
+// GoString returns the string representation
+func (s RetryOptions) GoString() string {
+ return s.String()
+}
+
+// SetDurationInSeconds sets the DurationInSeconds field's value.
+func (s *RetryOptions) SetDurationInSeconds(v int64) *RetryOptions {
+ s.DurationInSeconds = &v
+ return s
+}
+
// Describes the configuration of a destination in Amazon S3.
type S3DestinationConfiguration struct {
_ struct{} `type:"structure"`
@@ -6811,6 +6919,10 @@ type SchemaConfiguration struct {
// Specifies the name of the AWS Glue database that contains the schema for
// the output data.
+ //
+ // If the SchemaConfiguration request parameter is used as part of invoking
+ // the CreateDeliveryStream API, then the DatabaseName property is required
+ // and its value must be specified.
DatabaseName *string `min:"1" type:"string"`
// If you don't specify an AWS Region, the default is the current Region.
@@ -6819,10 +6931,18 @@ type SchemaConfiguration struct {
// The role that Kinesis Data Firehose can use to access AWS Glue. This role
// must be in the same account you use for Kinesis Data Firehose. Cross-account
// roles aren't allowed.
+ //
+ // If the SchemaConfiguration request parameter is used as part of invoking
+ // the CreateDeliveryStream API, then the RoleARN property is required and its
+ // value must be specified.
RoleARN *string `min:"1" type:"string"`
// Specifies the AWS Glue table that contains the column information that constitutes
// your data schema.
+ //
+ // If the SchemaConfiguration request parameter is used as part of invoking
+ // the CreateDeliveryStream API, then the TableName property is required and
+ // its value must be specified.
TableName *string `min:"1" type:"string"`
// Specifies the table version for the output data schema. If you don't specify
@@ -8584,6 +8704,12 @@ const (
// ProcessorParameterNameNumberOfRetries is a ProcessorParameterName enum value
ProcessorParameterNameNumberOfRetries = "NumberOfRetries"
+ // ProcessorParameterNameMetadataExtractionQuery is a ProcessorParameterName enum value
+ ProcessorParameterNameMetadataExtractionQuery = "MetadataExtractionQuery"
+
+ // ProcessorParameterNameJsonParsingEngine is a ProcessorParameterName enum value
+ ProcessorParameterNameJsonParsingEngine = "JsonParsingEngine"
+
// ProcessorParameterNameRoleArn is a ProcessorParameterName enum value
ProcessorParameterNameRoleArn = "RoleArn"
@@ -8592,6 +8718,12 @@ const (
// ProcessorParameterNameBufferIntervalInSeconds is a ProcessorParameterName enum value
ProcessorParameterNameBufferIntervalInSeconds = "BufferIntervalInSeconds"
+
+ // ProcessorParameterNameSubRecordType is a ProcessorParameterName enum value
+ ProcessorParameterNameSubRecordType = "SubRecordType"
+
+ // ProcessorParameterNameDelimiter is a ProcessorParameterName enum value
+ ProcessorParameterNameDelimiter = "Delimiter"
)
// ProcessorParameterName_Values returns all elements of the ProcessorParameterName enum
@@ -8599,21 +8731,37 @@ func ProcessorParameterName_Values() []string {
return []string{
ProcessorParameterNameLambdaArn,
ProcessorParameterNameNumberOfRetries,
+ ProcessorParameterNameMetadataExtractionQuery,
+ ProcessorParameterNameJsonParsingEngine,
ProcessorParameterNameRoleArn,
ProcessorParameterNameBufferSizeInMbs,
ProcessorParameterNameBufferIntervalInSeconds,
+ ProcessorParameterNameSubRecordType,
+ ProcessorParameterNameDelimiter,
}
}
const (
+ // ProcessorTypeRecordDeAggregation is a ProcessorType enum value
+ ProcessorTypeRecordDeAggregation = "RecordDeAggregation"
+
// ProcessorTypeLambda is a ProcessorType enum value
ProcessorTypeLambda = "Lambda"
+
+ // ProcessorTypeMetadataExtraction is a ProcessorType enum value
+ ProcessorTypeMetadataExtraction = "MetadataExtraction"
+
+ // ProcessorTypeAppendDelimiterToRecord is a ProcessorType enum value
+ ProcessorTypeAppendDelimiterToRecord = "AppendDelimiterToRecord"
)
// ProcessorType_Values returns all elements of the ProcessorType enum
func ProcessorType_Values() []string {
return []string{
+ ProcessorTypeRecordDeAggregation,
ProcessorTypeLambda,
+ ProcessorTypeMetadataExtraction,
+ ProcessorTypeAppendDelimiterToRecord,
}
}
diff --git a/service/kms/api.go b/service/kms/api.go
index 1f3b5eae7bf..1d827662daf 100644
--- a/service/kms/api.go
+++ b/service/kms/api.go
@@ -57,19 +57,19 @@ func (c *KMS) CancelKeyDeletionRequest(input *CancelKeyDeletionInput) (req *requ
// CancelKeyDeletion API operation for AWS Key Management Service.
//
-// Cancels the deletion of a customer master key (CMK). When this operation
-// succeeds, the key state of the CMK is Disabled. To enable the CMK, use EnableKey.
+// Cancels the deletion of a KMS key. When this operation succeeds, the key
+// state of the KMS key is Disabled. To enable the KMS key, use EnableKey.
//
-// For more information about scheduling and canceling deletion of a CMK, see
-// Deleting Customer Master Keys (https://docs.aws.amazon.com/kms/latest/developerguide/deleting-keys.html)
-// in the AWS Key Management Service Developer Guide.
+// For more information about scheduling and canceling deletion of a KMS key,
+// see Deleting KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/deleting-keys.html)
+// in the Key Management Service Developer Guide.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:CancelKeyDeletion (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -104,9 +104,9 @@ func (c *KMS) CancelKeyDeletionRequest(input *CancelKeyDeletionInput) (req *requ
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/CancelKeyDeletion
func (c *KMS) CancelKeyDeletion(input *CancelKeyDeletionInput) (*CancelKeyDeletionOutput, error) {
@@ -176,19 +176,19 @@ func (c *KMS) ConnectCustomKeyStoreRequest(input *ConnectCustomKeyStoreInput) (r
// ConnectCustomKeyStore API operation for AWS Key Management Service.
//
// Connects or reconnects a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// to its associated AWS CloudHSM cluster.
+// to its associated CloudHSM cluster.
//
-// The custom key store must be connected before you can create customer master
-// keys (CMKs) in the key store or use the CMKs it contains. You can disconnect
-// and reconnect a custom key store at any time.
+// The custom key store must be connected before you can create KMS keys in
+// the key store or use the KMS keys it contains. You can disconnect and reconnect
+// a custom key store at any time.
//
-// To connect a custom key store, its associated AWS CloudHSM cluster must have
+// To connect a custom key store, its associated CloudHSM cluster must have
// at least one active HSM. To get the number of active HSMs in a cluster, use
// the DescribeClusters (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_DescribeClusters.html)
// operation. To add HSMs to the cluster, use the CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
// operation. Also, the kmsuser crypto user (https://docs.aws.amazon.com/kms/latest/developerguide/key-store-concepts.html#concept-kmsuser)
-// (CU) must not be logged into the cluster. This prevents AWS KMS from using
-// this account to log in.
+// (CU) must not be logged into the cluster. This prevents KMS from using this
+// account to log in.
//
// The connection process can take an extended amount of time to complete; up
// to 20 minutes. This operation starts the connection process, but it does
@@ -198,10 +198,10 @@ func (c *KMS) ConnectCustomKeyStoreRequest(input *ConnectCustomKeyStoreInput) (r
// the connection state of the custom key store, use the DescribeCustomKeyStores
// operation.
//
-// During the connection process, AWS KMS finds the AWS CloudHSM cluster that
-// is associated with the custom key store, creates the connection infrastructure,
-// connects to the cluster, logs into the AWS CloudHSM client as the kmsuser
-// CU, and rotates its password.
+// During the connection process, KMS finds the CloudHSM cluster that is associated
+// with the custom key store, creates the connection infrastructure, connects
+// to the cluster, logs into the CloudHSM client as the kmsuser CU, and rotates
+// its password.
//
// The ConnectCustomKeyStore operation might fail for various reasons. To find
// the reason, use the DescribeCustomKeyStores operation and see the ConnectionErrorCode
@@ -213,10 +213,10 @@ func (c *KMS) ConnectCustomKeyStoreRequest(input *ConnectCustomKeyStoreInput) (r
//
// If you are having trouble connecting or disconnecting a custom key store,
// see Troubleshooting a Custom Key Store (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// Cross-account use: No. You cannot perform this operation on a custom key
-// store in a different AWS account.
+// store in a different Amazon Web Services account.
//
// Required permissions: kms:ConnectCustomKeyStore (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy)
@@ -242,11 +242,11 @@ func (c *KMS) ConnectCustomKeyStoreRequest(input *ConnectCustomKeyStoreInput) (r
//
// Returned Error Types:
// * CloudHsmClusterNotActiveException
-// The request was rejected because the AWS CloudHSM cluster that is associated
+// The request was rejected because the CloudHSM cluster that is associated
// with the custom key store is not active. Initialize and activate the cluster
// and try the command again. For detailed instructions, see Getting Started
// (https://docs.aws.amazon.com/cloudhsm/latest/userguide/getting-started.html)
-// in the AWS CloudHSM User Guide.
+// in the CloudHSM User Guide.
//
// * CustomKeyStoreInvalidStateException
// The request was rejected because of the ConnectionState of the custom key
@@ -268,7 +268,7 @@ func (c *KMS) ConnectCustomKeyStoreRequest(input *ConnectCustomKeyStoreInput) (r
// for all other ConnectionState values.
//
// * CustomKeyStoreNotFoundException
-// The request was rejected because AWS KMS cannot find a custom key store with
+// The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
//
// * InternalException
@@ -276,8 +276,8 @@ func (c *KMS) ConnectCustomKeyStoreRequest(input *ConnectCustomKeyStoreInput) (r
// can be retried.
//
// * CloudHsmClusterInvalidConfigurationException
-// The request was rejected because the associated AWS CloudHSM cluster did
-// not meet the configuration requirements for a custom key store.
+// The request was rejected because the associated CloudHSM cluster did not
+// meet the configuration requirements for a custom key store.
//
// * The cluster must be configured with private subnets in at least two
// different Availability Zones in the Region.
@@ -292,20 +292,19 @@ func (c *KMS) ConnectCustomKeyStoreRequest(input *ConnectCustomKeyStoreInput) (r
// operation.
//
// * The cluster must contain at least as many HSMs as the operation requires.
-// To add HSMs, use the AWS CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
+// To add HSMs, use the CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
// operation. For the CreateCustomKeyStore, UpdateCustomKeyStore, and CreateKey
-// operations, the AWS CloudHSM cluster must have at least two active HSMs,
-// each in a different Availability Zone. For the ConnectCustomKeyStore operation,
-// the AWS CloudHSM must contain at least one active HSM.
-//
-// For information about the requirements for an AWS CloudHSM cluster that is
-// associated with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
-// in the AWS Key Management Service Developer Guide. For information about
-// creating a private subnet for an AWS CloudHSM cluster, see Create a Private
-// Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
-// in the AWS CloudHSM User Guide. For information about cluster security groups,
+// operations, the CloudHSM cluster must have at least two active HSMs, each
+// in a different Availability Zone. For the ConnectCustomKeyStore operation,
+// the CloudHSM must contain at least one active HSM.
+//
+// For information about the requirements for an CloudHSM cluster that is associated
+// with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
+// in the Key Management Service Developer Guide. For information about creating
+// a private subnet for an CloudHSM cluster, see Create a Private Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
+// in the CloudHSM User Guide. For information about cluster security groups,
// see Configure a Default Security Group (https://docs.aws.amazon.com/cloudhsm/latest/userguide/configure-sg.html)
-// in the AWS CloudHSM User Guide .
+// in the CloudHSM User Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/ConnectCustomKeyStore
func (c *KMS) ConnectCustomKeyStore(input *ConnectCustomKeyStoreInput) (*ConnectCustomKeyStoreOutput, error) {
@@ -374,37 +373,37 @@ func (c *KMS) CreateAliasRequest(input *CreateAliasInput) (req *request.Request,
// CreateAlias API operation for AWS Key Management Service.
//
-// Creates a friendly name for a customer master key (CMK).
+// Creates a friendly name for a KMS key.
//
// Adding, deleting, or updating an alias can allow or deny permission to the
-// CMK. For details, see Using ABAC in AWS KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
-// in the AWS Key Management Service Developer Guide.
+// KMS key. For details, see Using ABAC in KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
+// in the Key Management Service Developer Guide.
//
-// You can use an alias to identify a CMK in the AWS KMS console, in the DescribeKey
+// You can use an alias to identify a KMS key in the KMS console, in the DescribeKey
// operation and in cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations),
-// such as Encrypt and GenerateDataKey. You can also change the CMK that's associated
-// with the alias (UpdateAlias) or delete the alias (DeleteAlias) at any time.
-// These operations don't affect the underlying CMK.
+// such as Encrypt and GenerateDataKey. You can also change the KMS key that's
+// associated with the alias (UpdateAlias) or delete the alias (DeleteAlias)
+// at any time. These operations don't affect the underlying KMS key.
//
-// You can associate the alias with any customer managed CMK in the same AWS
-// Region. Each alias is associated with only one CMK at a time, but a CMK can
-// have multiple aliases. A valid CMK is required. You can't create an alias
-// without a CMK.
+// You can associate the alias with any customer managed key in the same Amazon
+// Web Services Region. Each alias is associated with only one KMS key at a
+// time, but a KMS key can have multiple aliases. A valid KMS key is required.
+// You can't create an alias without a KMS key.
//
// The alias must be unique in the account and Region, but you can have aliases
// with the same name in different Regions. For detailed information about aliases,
// see Using aliases (https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// This operation does not return a response. To get the alias that you created,
// use the ListAliases operation.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
// Cross-account use: No. You cannot perform this operation on an alias in a
-// different AWS account.
+// different Amazon Web Services account.
//
// Required permissions
//
@@ -412,10 +411,10 @@ func (c *KMS) CreateAliasRequest(input *CreateAliasInput) (req *request.Request,
// on the alias (IAM policy).
//
// * kms:CreateAlias (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
-// on the CMK (key policy).
+// on the KMS key (key policy).
//
// For details, see Controlling access to aliases (https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html#alias-access)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// Related operations:
//
@@ -455,15 +454,15 @@ func (c *KMS) CreateAliasRequest(input *CreateAliasInput) (req *request.Request,
// * LimitExceededException
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// * InvalidStateException
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/CreateAlias
func (c *KMS) CreateAlias(input *CreateAliasInput) (*CreateAliasOutput, error) {
@@ -532,31 +531,31 @@ func (c *KMS) CreateCustomKeyStoreRequest(input *CreateCustomKeyStoreInput) (req
// CreateCustomKeyStore API operation for AWS Key Management Service.
//
// Creates a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// that is associated with an AWS CloudHSM cluster (https://docs.aws.amazon.com/cloudhsm/latest/userguide/clusters.html)
+// that is associated with an CloudHSM cluster (https://docs.aws.amazon.com/cloudhsm/latest/userguide/clusters.html)
// that you own and manage.
//
// This operation is part of the Custom Key Store feature (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// feature in AWS KMS, which combines the convenience and extensive integration
-// of AWS KMS with the isolation and control of a single-tenant key store.
+// feature in KMS, which combines the convenience and extensive integration
+// of KMS with the isolation and control of a single-tenant key store.
//
// Before you create the custom key store, you must assemble the required elements,
-// including an AWS CloudHSM cluster that fulfills the requirements for a custom
+// including an CloudHSM cluster that fulfills the requirements for a custom
// key store. For details about the required elements, see Assemble the Prerequisites
// (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// When the operation completes successfully, it returns the ID of the new custom
// key store. Before you can use your new custom key store, you need to use
-// the ConnectCustomKeyStore operation to connect the new key store to its AWS
-// CloudHSM cluster. Even if you are not going to use your custom key store
-// immediately, you might want to connect it to verify that all settings are
-// correct and then disconnect it until you are ready to use it.
+// the ConnectCustomKeyStore operation to connect the new key store to its CloudHSM
+// cluster. Even if you are not going to use your custom key store immediately,
+// you might want to connect it to verify that all settings are correct and
+// then disconnect it until you are ready to use it.
//
// For help with failures, see Troubleshooting a Custom Key Store (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// Cross-account use: No. You cannot perform this operation on a custom key
-// store in a different AWS account.
+// store in a different Amazon Web Services account.
//
// Required permissions: kms:CreateCustomKeyStore (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy).
@@ -582,10 +581,10 @@ func (c *KMS) CreateCustomKeyStoreRequest(input *CreateCustomKeyStoreInput) (req
//
// Returned Error Types:
// * CloudHsmClusterInUseException
-// The request was rejected because the specified AWS CloudHSM cluster is already
+// The request was rejected because the specified CloudHSM cluster is already
// associated with a custom key store or it shares a backup history with a cluster
// that is associated with a custom key store. Each custom key store must be
-// associated with a different AWS CloudHSM cluster.
+// associated with a different CloudHSM cluster.
//
// Clusters that share a backup history have the same cluster certificate. To
// view the cluster certificate of a cluster, use the DescribeClusters (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_DescribeClusters.html)
@@ -597,32 +596,31 @@ func (c *KMS) CreateCustomKeyStoreRequest(input *CreateCustomKeyStoreInput) (req
// key store name that is unique in the account.
//
// * CloudHsmClusterNotFoundException
-// The request was rejected because AWS KMS cannot find the AWS CloudHSM cluster
-// with the specified cluster ID. Retry the request with a different cluster
-// ID.
+// The request was rejected because KMS cannot find the CloudHSM cluster with
+// the specified cluster ID. Retry the request with a different cluster ID.
//
// * InternalException
// The request was rejected because an internal exception occurred. The request
// can be retried.
//
// * CloudHsmClusterNotActiveException
-// The request was rejected because the AWS CloudHSM cluster that is associated
+// The request was rejected because the CloudHSM cluster that is associated
// with the custom key store is not active. Initialize and activate the cluster
// and try the command again. For detailed instructions, see Getting Started
// (https://docs.aws.amazon.com/cloudhsm/latest/userguide/getting-started.html)
-// in the AWS CloudHSM User Guide.
+// in the CloudHSM User Guide.
//
// * IncorrectTrustAnchorException
// The request was rejected because the trust anchor certificate in the request
-// is not the trust anchor certificate for the specified AWS CloudHSM cluster.
+// is not the trust anchor certificate for the specified CloudHSM cluster.
//
// When you initialize the cluster (https://docs.aws.amazon.com/cloudhsm/latest/userguide/initialize-cluster.html#sign-csr),
// you create the trust anchor certificate and save it in the customerCA.crt
// file.
//
// * CloudHsmClusterInvalidConfigurationException
-// The request was rejected because the associated AWS CloudHSM cluster did
-// not meet the configuration requirements for a custom key store.
+// The request was rejected because the associated CloudHSM cluster did not
+// meet the configuration requirements for a custom key store.
//
// * The cluster must be configured with private subnets in at least two
// different Availability Zones in the Region.
@@ -637,20 +635,19 @@ func (c *KMS) CreateCustomKeyStoreRequest(input *CreateCustomKeyStoreInput) (req
// operation.
//
// * The cluster must contain at least as many HSMs as the operation requires.
-// To add HSMs, use the AWS CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
+// To add HSMs, use the CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
// operation. For the CreateCustomKeyStore, UpdateCustomKeyStore, and CreateKey
-// operations, the AWS CloudHSM cluster must have at least two active HSMs,
-// each in a different Availability Zone. For the ConnectCustomKeyStore operation,
-// the AWS CloudHSM must contain at least one active HSM.
-//
-// For information about the requirements for an AWS CloudHSM cluster that is
-// associated with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
-// in the AWS Key Management Service Developer Guide. For information about
-// creating a private subnet for an AWS CloudHSM cluster, see Create a Private
-// Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
-// in the AWS CloudHSM User Guide. For information about cluster security groups,
+// operations, the CloudHSM cluster must have at least two active HSMs, each
+// in a different Availability Zone. For the ConnectCustomKeyStore operation,
+// the CloudHSM must contain at least one active HSM.
+//
+// For information about the requirements for an CloudHSM cluster that is associated
+// with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
+// in the Key Management Service Developer Guide. For information about creating
+// a private subnet for an CloudHSM cluster, see Create a Private Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
+// in the CloudHSM User Guide. For information about cluster security groups,
// see Configure a Default Security Group (https://docs.aws.amazon.com/cloudhsm/latest/userguide/configure-sg.html)
-// in the AWS CloudHSM User Guide .
+// in the CloudHSM User Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/CreateCustomKeyStore
func (c *KMS) CreateCustomKeyStore(input *CreateCustomKeyStoreInput) (*CreateCustomKeyStoreOutput, error) {
@@ -718,49 +715,44 @@ func (c *KMS) CreateGrantRequest(input *CreateGrantInput) (req *request.Request,
// CreateGrant API operation for AWS Key Management Service.
//
-// Adds a grant to a customer master key (CMK).
+// Adds a grant to a KMS key.
//
-// A grant is a policy instrument that allows AWS principals to use AWS KMS
-// customer master keys (CMKs) in cryptographic operations. It also can allow
-// them to view a CMK (DescribeKey) and create and manage grants. When authorizing
-// access to a CMK, grants are considered along with key policies and IAM policies.
+// A grant is a policy instrument that allows Amazon Web Services principals
+// to use KMS keys in cryptographic operations. It also can allow them to view
+// a KMS key (DescribeKey) and create and manage grants. When authorizing access
+// to a KMS key, grants are considered along with key policies and IAM policies.
// Grants are often used for temporary permissions because you can create one,
// use its permissions, and delete it without changing your key policies or
// IAM policies.
//
// For detailed information about grants, including grant terminology, see Using
// grants (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html)
-// in the AWS Key Management Service Developer Guide . For examples of working
-// with grants in several programming languages, see Programming grants (https://docs.aws.amazon.com/kms/latest/developerguide/programming-grants.html).
+// in the Key Management Service Developer Guide . For examples of working with
+// grants in several programming languages, see Programming grants (https://docs.aws.amazon.com/kms/latest/developerguide/programming-grants.html).
//
// The CreateGrant operation returns a GrantToken and a GrantId.
//
// * When you create, retire, or revoke a grant, there might be a brief delay,
// usually less than five minutes, until the grant is available throughout
-// AWS KMS. This state is known as eventual consistency. Once the grant has
-// achieved eventual consistency, the grantee principal can use the permissions
-// in the grant without identifying the grant. However, to use the permissions
+// KMS. This state is known as eventual consistency. Once the grant has achieved
+// eventual consistency, the grantee principal can use the permissions in
+// the grant without identifying the grant. However, to use the permissions
// in the grant immediately, use the GrantToken that CreateGrant returns.
-// For details, see Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/using-grant-token.html)
-// in the AWS Key Management Service Developer Guide .
+// For details, see Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+// in the Key Management Service Developer Guide .
//
// * The CreateGrant operation also returns a GrantId. You can use the GrantId
// and a key identifier to identify the grant in the RetireGrant and RevokeGrant
// operations. To find the grant ID, use the ListGrants or ListRetirableGrants
// operations.
//
-// For information about symmetric and asymmetric CMKs, see Using Symmetric
-// and Asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
-// in the AWS Key Management Service Developer Guide. For more information about
-// grants, see Grants (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html)
-// in the AWS Key Management Service Developer Guide .
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
-//
-// Cross-account use: Yes. To perform this operation on a CMK in a different
-// AWS account, specify the key ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation on a KMS key in a different
+// Amazon Web Services account, specify the key ARN in the value of the KeyId
+// parameter.
//
// Required permissions: kms:CreateGrant (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -788,7 +780,7 @@ func (c *KMS) CreateGrantRequest(input *CreateGrantInput) (req *request.Request,
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -808,15 +800,15 @@ func (c *KMS) CreateGrantRequest(input *CreateGrantInput) (req *request.Request,
// * LimitExceededException
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// * InvalidStateException
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/CreateGrant
func (c *KMS) CreateGrant(input *CreateGrantInput) (*CreateGrantOutput, error) {
@@ -884,106 +876,111 @@ func (c *KMS) CreateKeyRequest(input *CreateKeyInput) (req *request.Request, out
// CreateKey API operation for AWS Key Management Service.
//
-// Creates a unique customer managed customer master key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#master-keys)
-// (CMK) in your AWS account and Region.
+// Creates a unique customer managed KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms-keys)
+// in your Amazon Web Services account and Region.
+//
+// KMS is replacing the term customer master key (CMK) with KMS key and KMS
+// key. The concept has not changed. To prevent breaking changes, KMS is keeping
+// some variations of this term.
//
-// You can use the CreateKey operation to create symmetric or asymmetric CMKs.
+// You can use the CreateKey operation to create symmetric or asymmetric KMS
+// keys.
//
-// * Symmetric CMKs contain a 256-bit symmetric key that never leaves AWS
-// KMS unencrypted. To use the CMK, you must call AWS KMS. You can use a
-// symmetric CMK to encrypt and decrypt small amounts of data, but they are
-// typically used to generate data keys (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#data-keys)
+// * Symmetric KMS keys contain a 256-bit symmetric key that never leaves
+// KMS unencrypted. To use the KMS key, you must call KMS. You can use a
+// symmetric KMS key to encrypt and decrypt small amounts of data, but they
+// are typically used to generate data keys (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#data-keys)
// and data keys pairs (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#data-key-pairs).
// For details, see GenerateDataKey and GenerateDataKeyPair.
//
-// * Asymmetric CMKs can contain an RSA key pair or an Elliptic Curve (ECC)
-// key pair. The private key in an asymmetric CMK never leaves AWS KMS unencrypted.
-// However, you can use the GetPublicKey operation to download the public
-// key so it can be used outside of AWS KMS. CMKs with RSA key pairs can
-// be used to encrypt or decrypt data or sign and verify messages (but not
-// both). CMKs with ECC key pairs can be used only to sign and verify messages.
+// * Asymmetric KMS keys can contain an RSA key pair or an Elliptic Curve
+// (ECC) key pair. The private key in an asymmetric KMS key never leaves
+// KMS unencrypted. However, you can use the GetPublicKey operation to download
+// the public key so it can be used outside of KMS. KMS keys with RSA key
+// pairs can be used to encrypt or decrypt data or sign and verify messages
+// (but not both). KMS keys with ECC key pairs can be used only to sign and
+// verify messages.
//
-// For information about symmetric and asymmetric CMKs, see Using Symmetric
-// and Asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
-// in the AWS Key Management Service Developer Guide.
+// For information about symmetric and asymmetric KMS keys, see Using Symmetric
+// and Asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
+// in the Key Management Service Developer Guide.
//
-// To create different types of CMKs, use the following guidance:
+// To create different types of KMS keys, use the following guidance:
//
-// Asymmetric CMKs
+// Asymmetric KMS keys
//
-// To create an asymmetric CMK, use the CustomerMasterKeySpec parameter to specify
-// the type of key material in the CMK. Then, use the KeyUsage parameter to
-// determine whether the CMK will be used to encrypt and decrypt or sign and
-// verify. You can't change these properties after the CMK is created.
+// To create an asymmetric KMS key, use the KeySpec parameter to specify the
+// type of key material in the KMS key. Then, use the KeyUsage parameter to
+// determine whether the KMS key will be used to encrypt and decrypt or sign
+// and verify. You can't change these properties after the KMS key is created.
//
-// Symmetric CMKs
+// Symmetric KMS keys
//
-// When creating a symmetric CMK, you don't need to specify the CustomerMasterKeySpec
-// or KeyUsage parameters. The default value for CustomerMasterKeySpec, SYMMETRIC_DEFAULT,
+// When creating a symmetric KMS key, you don't need to specify the KeySpec
+// or KeyUsage parameters. The default value for KeySpec, SYMMETRIC_DEFAULT,
// and the default value for KeyUsage, ENCRYPT_DECRYPT, are the only valid values
-// for symmetric CMKs.
+// for symmetric KMS keys.
//
// Multi-Region primary keys
//
// Imported key material
//
-// To create a multi-Region primary key in the local AWS Region, use the MultiRegion
-// parameter with a value of True. To create a multi-Region replica key, that
-// is, a CMK with the same key ID and key material as a primary key, but in
-// a different AWS Region, use the ReplicateKey operation. To change a replica
-// key to a primary key, and its primary key to a replica key, use the UpdatePrimaryRegion
-// operation.
-//
-// This operation supports multi-Region keys, an AWS KMS feature that lets you
-// create multiple interoperable CMKs in different AWS Regions. Because these
-// CMKs have the same key ID, key material, and other metadata, you can use
-// them to encrypt data in one AWS Region and decrypt it in a different AWS
-// Region without making a cross-Region call or exposing the plaintext data.
-// For more information about multi-Region keys, see Using multi-Region keys
-// (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
-// in the AWS Key Management Service Developer Guide.
+// To create a multi-Region primary key in the local Amazon Web Services Region,
+// use the MultiRegion parameter with a value of True. To create a multi-Region
+// replica key, that is, a KMS key with the same key ID and key material as
+// a primary key, but in a different Amazon Web Services Region, use the ReplicateKey
+// operation. To change a replica key to a primary key, and its primary key
+// to a replica key, use the UpdatePrimaryRegion operation.
+//
+// This operation supports multi-Region keys, an KMS feature that lets you create
+// multiple interoperable KMS keys in different Amazon Web Services Regions.
+// Because these KMS keys have the same key ID, key material, and other metadata,
+// you can use them interchangeably to encrypt data in one Amazon Web Services
+// Region and decrypt it in a different Amazon Web Services Region without re-encrypting
+// the data or making a cross-Region call. For more information about multi-Region
+// keys, see Using multi-Region keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
+// in the Key Management Service Developer Guide.
//
// You can create symmetric and asymmetric multi-Region keys and multi-Region
// keys with imported key material. You cannot create multi-Region keys in a
// custom key store.
//
-// To import your own key material, begin by creating a symmetric CMK with no
-// key material. To do this, use the Origin parameter of CreateKey with a value
-// of EXTERNAL. Next, use GetParametersForImport operation to get a public key
-// and import token, and use the public key to encrypt your key material. Then,
-// use ImportKeyMaterial with your import token to import the key material.
+// To import your own key material, begin by creating a symmetric KMS key with
+// no key material. To do this, use the Origin parameter of CreateKey with a
+// value of EXTERNAL. Next, use GetParametersForImport operation to get a public
+// key and import token, and use the public key to encrypt your key material.
+// Then, use ImportKeyMaterial with your import token to import the key material.
// For step-by-step instructions, see Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
-// in the AWS Key Management Service Developer Guide . You cannot import the
-// key material into an asymmetric CMK.
+// in the Key Management Service Developer Guide . You cannot import the key
+// material into an asymmetric KMS key.
//
// To create a multi-Region primary key with imported key material, use the
// Origin parameter of CreateKey with a value of EXTERNAL and the MultiRegion
// parameter with a value of True. To create replicas of the multi-Region primary
// key, use the ReplicateKey operation. For more information about multi-Region
// keys, see Using multi-Region keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// Custom key store
//
-// To create a symmetric CMK in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html),
+// To create a symmetric KMS key in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html),
// use the CustomKeyStoreId parameter to specify the custom key store. You must
-// also use the Origin parameter with a value of AWS_CLOUDHSM. The AWS CloudHSM
+// also use the Origin parameter with a value of AWS_CLOUDHSM. The CloudHSM
// cluster that is associated with the custom key store must have at least two
-// active HSMs in different Availability Zones in the AWS Region.
+// active HSMs in different Availability Zones in the Amazon Web Services Region.
//
-// You cannot create an asymmetric CMK or a multi-Region CMK in a custom key
-// store. For information about custom key stores in AWS KMS see Using Custom
-// Key Stores (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// in the AWS Key Management Service Developer Guide .
+// You cannot create an asymmetric KMS key in a custom key store. For information
+// about custom key stores in KMS see Using Custom Key Stores (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
+// in the Key Management Service Developer Guide .
//
-// Cross-account use: No. You cannot use this operation to create a CMK in a
-// different AWS account.
+// Cross-account use: No. You cannot use this operation to create a KMS key
+// in a different Amazon Web Services account.
//
// Required permissions: kms:CreateKey (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy). To use the Tags parameter, kms:TagResource (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy). For examples and information about related permissions, see
-// Allow a user to create CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html#iam-policy-example-create-key)
-// in the AWS Key Management Service Developer Guide.
+// Allow a user to create KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html#iam-policy-example-create-key)
+// in the Key Management Service Developer Guide.
//
// Related operations:
//
@@ -1024,13 +1021,13 @@ func (c *KMS) CreateKeyRequest(input *CreateKeyInput) (req *request.Request, out
// * LimitExceededException
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// * TagException
// The request was rejected because one or more tags are not valid.
//
// * CustomKeyStoreNotFoundException
-// The request was rejected because AWS KMS cannot find a custom key store with
+// The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
//
// * CustomKeyStoreInvalidStateException
@@ -1053,8 +1050,8 @@ func (c *KMS) CreateKeyRequest(input *CreateKeyInput) (req *request.Request, out
// for all other ConnectionState values.
//
// * CloudHsmClusterInvalidConfigurationException
-// The request was rejected because the associated AWS CloudHSM cluster did
-// not meet the configuration requirements for a custom key store.
+// The request was rejected because the associated CloudHSM cluster did not
+// meet the configuration requirements for a custom key store.
//
// * The cluster must be configured with private subnets in at least two
// different Availability Zones in the Region.
@@ -1069,20 +1066,19 @@ func (c *KMS) CreateKeyRequest(input *CreateKeyInput) (req *request.Request, out
// operation.
//
// * The cluster must contain at least as many HSMs as the operation requires.
-// To add HSMs, use the AWS CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
+// To add HSMs, use the CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
// operation. For the CreateCustomKeyStore, UpdateCustomKeyStore, and CreateKey
-// operations, the AWS CloudHSM cluster must have at least two active HSMs,
-// each in a different Availability Zone. For the ConnectCustomKeyStore operation,
-// the AWS CloudHSM must contain at least one active HSM.
-//
-// For information about the requirements for an AWS CloudHSM cluster that is
-// associated with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
-// in the AWS Key Management Service Developer Guide. For information about
-// creating a private subnet for an AWS CloudHSM cluster, see Create a Private
-// Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
-// in the AWS CloudHSM User Guide. For information about cluster security groups,
+// operations, the CloudHSM cluster must have at least two active HSMs, each
+// in a different Availability Zone. For the ConnectCustomKeyStore operation,
+// the CloudHSM must contain at least one active HSM.
+//
+// For information about the requirements for an CloudHSM cluster that is associated
+// with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
+// in the Key Management Service Developer Guide. For information about creating
+// a private subnet for an CloudHSM cluster, see Create a Private Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
+// in the CloudHSM User Guide. For information about cluster security groups,
// see Configure a Default Security Group (https://docs.aws.amazon.com/cloudhsm/latest/userguide/configure-sg.html)
-// in the AWS CloudHSM User Guide .
+// in the CloudHSM User Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/CreateKey
func (c *KMS) CreateKey(input *CreateKeyInput) (*CreateKeyOutput, error) {
@@ -1150,8 +1146,8 @@ func (c *KMS) DecryptRequest(input *DecryptInput) (req *request.Request, output
// Decrypt API operation for AWS Key Management Service.
//
-// Decrypts ciphertext that was encrypted by a AWS KMS customer master key (CMK)
-// using any of the following operations:
+// Decrypts ciphertext that was encrypted by a KMS key using any of the following
+// operations:
//
// * Encrypt
//
@@ -1164,46 +1160,52 @@ func (c *KMS) DecryptRequest(input *DecryptInput) (req *request.Request, output
// * GenerateDataKeyPairWithoutPlaintext
//
// You can use this operation to decrypt ciphertext that was encrypted under
-// a symmetric or asymmetric CMK. When the CMK is asymmetric, you must specify
-// the CMK and the encryption algorithm that was used to encrypt the ciphertext.
-// For information about symmetric and asymmetric CMKs, see Using Symmetric
-// and Asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
-// in the AWS Key Management Service Developer Guide.
+// a symmetric or asymmetric KMS key. When the KMS key is asymmetric, you must
+// specify the KMS key and the encryption algorithm that was used to encrypt
+// the ciphertext. For information about symmetric and asymmetric KMS keys,
+// see Using Symmetric and Asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
+// in the Key Management Service Developer Guide.
//
// The Decrypt operation also decrypts ciphertext that was encrypted outside
-// of AWS KMS by the public key in an AWS KMS asymmetric CMK. However, it cannot
-// decrypt ciphertext produced by other libraries, such as the AWS Encryption
-// SDK (https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/)
+// of KMS by the public key in an KMS asymmetric KMS key. However, it cannot
+// decrypt ciphertext produced by other libraries, such as the Amazon Web Services
+// Encryption SDK (https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/)
// or Amazon S3 client-side encryption (https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html).
-// These libraries return a ciphertext format that is incompatible with AWS
-// KMS.
+// These libraries return a ciphertext format that is incompatible with KMS.
//
-// If the ciphertext was encrypted under a symmetric CMK, the KeyId parameter
-// is optional. AWS KMS can get this information from metadata that it adds
-// to the symmetric ciphertext blob. This feature adds durability to your implementation
+// If the ciphertext was encrypted under a symmetric KMS key, the KeyId parameter
+// is optional. KMS can get this information from metadata that it adds to the
+// symmetric ciphertext blob. This feature adds durability to your implementation
// by ensuring that authorized users can decrypt ciphertext decades after it
-// was encrypted, even if they've lost track of the CMK ID. However, specifying
-// the CMK is always recommended as a best practice. When you use the KeyId
-// parameter to specify a CMK, AWS KMS only uses the CMK you specify. If the
-// ciphertext was encrypted under a different CMK, the Decrypt operation fails.
-// This practice ensures that you use the CMK that you intend.
+// was encrypted, even if they've lost track of the key ID. However, specifying
+// the KMS key is always recommended as a best practice. When you use the KeyId
+// parameter to specify a KMS key, KMS only uses the KMS key you specify. If
+// the ciphertext was encrypted under a different KMS key, the Decrypt operation
+// fails. This practice ensures that you use the KMS key that you intend.
//
// Whenever possible, use key policies to give users permission to call the
-// Decrypt operation on a particular CMK, instead of using IAM policies. Otherwise,
-// you might create an IAM user policy that gives the user Decrypt permission
-// on all CMKs. This user could decrypt ciphertext that was encrypted by CMKs
-// in other accounts if the key policy for the cross-account CMK permits it.
-// If you must use an IAM policy for Decrypt permissions, limit the user to
-// particular CMKs or particular trusted accounts. For details, see Best practices
-// for IAM policies (https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html#iam-policies-best-practices)
-// in the AWS Key Management Service Developer Guide.
-//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
-//
-// Cross-account use: Yes. You can decrypt a ciphertext using a CMK in a different
-// AWS account.
+// Decrypt operation on a particular KMS key, instead of using IAM policies.
+// Otherwise, you might create an IAM user policy that gives the user Decrypt
+// permission on all KMS keys. This user could decrypt ciphertext that was encrypted
+// by KMS keys in other accounts if the key policy for the cross-account KMS
+// key permits it. If you must use an IAM policy for Decrypt permissions, limit
+// the user to particular KMS keys or particular trusted accounts. For details,
+// see Best practices for IAM policies (https://docs.aws.amazon.com/kms/latest/developerguide/iam-policies.html#iam-policies-best-practices)
+// in the Key Management Service Developer Guide.
+//
+// Applications in Amazon Web Services Nitro Enclaves can call this operation
+// by using the Amazon Web Services Nitro Enclaves Development Kit (https://github.com/aws/aws-nitro-enclaves-sdk-c).
+// For information about the supporting parameters, see How Amazon Web Services
+// Nitro Enclaves use KMS (https://docs.aws.amazon.com/kms/latest/developerguide/services-nitro-enclaves.html)
+// in the Key Management Service Developer Guide.
+//
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
+//
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:Decrypt (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -1231,7 +1233,7 @@ func (c *KMS) DecryptRequest(input *DecryptInput) (req *request.Request, output
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * InvalidCiphertextException
// From the Decrypt or ReEncrypt operation, the request was rejected because
@@ -1239,32 +1241,33 @@ func (c *KMS) DecryptRequest(input *DecryptInput) (req *request.Request, output
// the ciphertext, such as the encryption context, is corrupted, missing, or
// otherwise invalid.
//
-// From the ImportKeyMaterial operation, the request was rejected because AWS
-// KMS could not decrypt the encrypted (wrapped) key material.
+// From the ImportKeyMaterial operation, the request was rejected because KMS
+// could not decrypt the encrypted (wrapped) key material.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * IncorrectKeyException
-// The request was rejected because the specified CMK cannot decrypt the data.
-// The KeyId in a Decrypt request and the SourceKeyId in a ReEncrypt request
-// must identify the same CMK that was used to encrypt the ciphertext.
+// The request was rejected because the specified KMS key cannot decrypt the
+// data. The KeyId in a Decrypt request and the SourceKeyId in a ReEncrypt request
+// must identify the same KMS key that was used to encrypt the ciphertext.
//
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -1281,9 +1284,9 @@ func (c *KMS) DecryptRequest(input *DecryptInput) (req *request.Request, output
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/Decrypt
func (c *KMS) Decrypt(input *DecryptInput) (*DecryptOutput, error) {
@@ -1355,20 +1358,20 @@ func (c *KMS) DeleteAliasRequest(input *DeleteAliasInput) (req *request.Request,
// Deletes the specified alias.
//
// Adding, deleting, or updating an alias can allow or deny permission to the
-// CMK. For details, see Using ABAC in AWS KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
-// in the AWS Key Management Service Developer Guide.
+// KMS key. For details, see Using ABAC in KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
+// in the Key Management Service Developer Guide.
//
-// Because an alias is not a property of a CMK, you can delete and change the
-// aliases of a CMK without affecting the CMK. Also, aliases do not appear in
-// the response from the DescribeKey operation. To get the aliases of all CMKs,
-// use the ListAliases operation.
+// Because an alias is not a property of a KMS key, you can delete and change
+// the aliases of a KMS key without affecting the KMS key. Also, aliases do
+// not appear in the response from the DescribeKey operation. To get the aliases
+// of all KMS keys, use the ListAliases operation.
//
-// Each CMK can have multiple aliases. To change the alias of a CMK, use DeleteAlias
-// to delete the current alias and CreateAlias to create a new alias. To associate
-// an existing alias with a different customer master key (CMK), call UpdateAlias.
+// Each KMS key can have multiple aliases. To change the alias of a KMS key,
+// use DeleteAlias to delete the current alias and CreateAlias to create a new
+// alias. To associate an existing alias with a different KMS key, call UpdateAlias.
//
// Cross-account use: No. You cannot perform this operation on an alias in a
-// different AWS account.
+// different Amazon Web Services account.
//
// Required permissions
//
@@ -1376,10 +1379,10 @@ func (c *KMS) DeleteAliasRequest(input *DeleteAliasInput) (req *request.Request,
// on the alias (IAM policy).
//
// * kms:DeleteAlias (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
-// on the CMK (key policy).
+// on the KMS key (key policy).
//
// For details, see Controlling access to aliases (https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html#alias-access)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// Related operations:
//
@@ -1413,9 +1416,9 @@ func (c *KMS) DeleteAliasRequest(input *DeleteAliasInput) (req *request.Request,
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/DeleteAlias
func (c *KMS) DeleteAlias(input *DeleteAliasInput) (*DeleteAliasOutput, error) {
@@ -1485,37 +1488,35 @@ func (c *KMS) DeleteCustomKeyStoreRequest(input *DeleteCustomKeyStoreInput) (req
// DeleteCustomKeyStore API operation for AWS Key Management Service.
//
// Deletes a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
-// This operation does not delete the AWS CloudHSM cluster that is associated
-// with the custom key store, or affect any users or keys in the cluster.
+// This operation does not delete the CloudHSM cluster that is associated with
+// the custom key store, or affect any users or keys in the cluster.
//
-// The custom key store that you delete cannot contain any AWS KMS customer
-// master keys (CMKs) (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#master_keys).
+// The custom key store that you delete cannot contain any KMS KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys).
// Before deleting the key store, verify that you will never need to use any
-// of the CMKs in the key store for any cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations).
-// Then, use ScheduleKeyDeletion to delete the AWS KMS customer master keys
-// (CMKs) from the key store. When the scheduled waiting period expires, the
-// ScheduleKeyDeletion operation deletes the CMKs. Then it makes a best effort
-// to delete the key material from the associated cluster. However, you might
-// need to manually delete the orphaned key material (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-orphaned-key)
+// of the KMS keys in the key store for any cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations).
+// Then, use ScheduleKeyDeletion to delete the KMS keys from the key store.
+// When the scheduled waiting period expires, the ScheduleKeyDeletion operation
+// deletes the KMS keys. Then it makes a best effort to delete the key material
+// from the associated cluster. However, you might need to manually delete the
+// orphaned key material (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-orphaned-key)
// from the cluster and its backups.
//
-// After all CMKs are deleted from AWS KMS, use DisconnectCustomKeyStore to
-// disconnect the key store from AWS KMS. Then, you can delete the custom key
-// store.
+// After all KMS keys are deleted from KMS, use DisconnectCustomKeyStore to
+// disconnect the key store from KMS. Then, you can delete the custom key store.
//
// Instead of deleting the custom key store, consider using DisconnectCustomKeyStore
-// to disconnect it from AWS KMS. While the key store is disconnected, you cannot
-// create or use the CMKs in the key store. But, you do not need to delete CMKs
-// and you can reconnect a disconnected custom key store at any time.
+// to disconnect it from KMS. While the key store is disconnected, you cannot
+// create or use the KMS keys in the key store. But, you do not need to delete
+// KMS keys and you can reconnect a disconnected custom key store at any time.
//
// If the operation succeeds, it returns a JSON object with no properties.
//
// This operation is part of the Custom Key Store feature (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// feature in AWS KMS, which combines the convenience and extensive integration
-// of AWS KMS with the isolation and control of a single-tenant key store.
+// feature in KMS, which combines the convenience and extensive integration
+// of KMS with the isolation and control of a single-tenant key store.
//
// Cross-account use: No. You cannot perform this operation on a custom key
-// store in a different AWS account.
+// store in a different Amazon Web Services account.
//
// Required permissions: kms:DeleteCustomKeyStore (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy)
@@ -1541,10 +1542,10 @@ func (c *KMS) DeleteCustomKeyStoreRequest(input *DeleteCustomKeyStoreInput) (req
//
// Returned Error Types:
// * CustomKeyStoreHasCMKsException
-// The request was rejected because the custom key store contains AWS KMS customer
-// master keys (CMKs). After verifying that you do not need to use the CMKs,
-// use the ScheduleKeyDeletion operation to delete the CMKs. After they are
-// deleted, you can delete the custom key store.
+// The request was rejected because the custom key store contains KMS keys.
+// After verifying that you do not need to use the KMS keys, use the ScheduleKeyDeletion
+// operation to delete the KMS keys. After they are deleted, you can delete
+// the custom key store.
//
// * CustomKeyStoreInvalidStateException
// The request was rejected because of the ConnectionState of the custom key
@@ -1566,7 +1567,7 @@ func (c *KMS) DeleteCustomKeyStoreRequest(input *DeleteCustomKeyStoreInput) (req
// for all other ConnectionState values.
//
// * CustomKeyStoreNotFoundException
-// The request was rejected because AWS KMS cannot find a custom key store with
+// The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
//
// * InternalException
@@ -1641,22 +1642,23 @@ func (c *KMS) DeleteImportedKeyMaterialRequest(input *DeleteImportedKeyMaterialI
// DeleteImportedKeyMaterial API operation for AWS Key Management Service.
//
// Deletes key material that you previously imported. This operation makes the
-// specified customer master key (CMK) unusable. For more information about
-// importing key material into AWS KMS, see Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
-// in the AWS Key Management Service Developer Guide.
+// specified KMS key unusable. For more information about importing key material
+// into KMS, see Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
+// in the Key Management Service Developer Guide.
//
-// When the specified CMK is in the PendingDeletion state, this operation does
-// not change the CMK's state. Otherwise, it changes the CMK's state to PendingImport.
+// When the specified KMS key is in the PendingDeletion state, this operation
+// does not change the KMS key's state. Otherwise, it changes the KMS key's
+// state to PendingImport.
//
// After you delete key material, you can use ImportKeyMaterial to reimport
-// the same key material into the CMK.
+// the same key material into the KMS key.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:DeleteImportedKeyMaterial (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -1699,9 +1701,9 @@ func (c *KMS) DeleteImportedKeyMaterialRequest(input *DeleteImportedKeyMaterialI
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/DeleteImportedKeyMaterial
func (c *KMS) DeleteImportedKeyMaterial(input *DeleteImportedKeyMaterialInput) (*DeleteImportedKeyMaterialOutput, error) {
@@ -1773,32 +1775,32 @@ func (c *KMS) DescribeCustomKeyStoresRequest(input *DescribeCustomKeyStoresInput
// in the account and Region.
//
// This operation is part of the Custom Key Store feature (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// feature in AWS KMS, which combines the convenience and extensive integration
-// of AWS KMS with the isolation and control of a single-tenant key store.
+// feature in KMS, which combines the convenience and extensive integration
+// of KMS with the isolation and control of a single-tenant key store.
//
// By default, this operation returns information about all custom key stores
// in the account and Region. To get only information about a particular custom
// key store, use either the CustomKeyStoreName or CustomKeyStoreId parameter
// (but not both).
//
-// To determine whether the custom key store is connected to its AWS CloudHSM
-// cluster, use the ConnectionState element in the response. If an attempt to
-// connect the custom key store failed, the ConnectionState value is FAILED
-// and the ConnectionErrorCode element in the response indicates the cause of
-// the failure. For help interpreting the ConnectionErrorCode, see CustomKeyStoresListEntry.
+// To determine whether the custom key store is connected to its CloudHSM cluster,
+// use the ConnectionState element in the response. If an attempt to connect
+// the custom key store failed, the ConnectionState value is FAILED and the
+// ConnectionErrorCode element in the response indicates the cause of the failure.
+// For help interpreting the ConnectionErrorCode, see CustomKeyStoresListEntry.
//
// Custom key stores have a DISCONNECTED connection state if the key store has
// never been connected or you use the DisconnectCustomKeyStore operation to
// disconnect it. If your custom key store state is CONNECTED but you are having
-// trouble using it, make sure that its associated AWS CloudHSM cluster is active
+// trouble using it, make sure that its associated CloudHSM cluster is active
// and contains the minimum number of HSMs required for the operation, if any.
//
// For help repairing your custom key store, see the Troubleshooting Custom
// Key Stores (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html)
-// topic in the AWS Key Management Service Developer Guide.
+// topic in the Key Management Service Developer Guide.
//
// Cross-account use: No. You cannot perform this operation on a custom key
-// store in a different AWS account.
+// store in a different Amazon Web Services account.
//
// Required permissions: kms:DescribeCustomKeyStores (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy)
@@ -1824,7 +1826,7 @@ func (c *KMS) DescribeCustomKeyStoresRequest(input *DescribeCustomKeyStoresInput
//
// Returned Error Types:
// * CustomKeyStoreNotFoundException
-// The request was rejected because AWS KMS cannot find a custom key store with
+// The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
//
// * InvalidMarkerException
@@ -1901,41 +1903,45 @@ func (c *KMS) DescribeKeyRequest(input *DescribeKeyInput) (req *request.Request,
// DescribeKey API operation for AWS Key Management Service.
//
-// Provides detailed information about a customer master key (CMK). You can
-// run DescribeKey on a customer managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk)
-// or an AWS managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
+// Provides detailed information about a KMS key. You can run DescribeKey on
+// a customer managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk)
+// or an Amazon Web Services managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
//
// This detailed information includes the key ARN, creation date (and deletion
// date, if applicable), the key state, and the origin and expiration date (if
-// any) of the key material. For CMKs in custom key stores, it includes information
-// about the custom key store, such as the key store ID and the AWS CloudHSM
-// cluster ID. It includes fields, like KeySpec, that help you distinguish symmetric
-// from asymmetric CMKs. It also provides information that is particularly important
-// to asymmetric CMKs, such as the key usage (encryption or signing) and the
-// encryption algorithms or signing algorithms that the CMK supports.
+// any) of the key material. It includes fields, like KeySpec, that help you
+// distinguish symmetric from asymmetric KMS keys. It also provides information
+// that is particularly important to asymmetric keys, such as the key usage
+// (encryption or signing) and the encryption algorithms or signing algorithms
+// that the KMS key supports. For KMS keys in custom key stores, it includes
+// information about the custom key store, such as the key store ID and the
+// CloudHSM cluster ID. For multi-Region keys, it displays the primary key and
+// all related replica keys.
//
// DescribeKey does not return the following information:
//
-// * Aliases associated with the CMK. To get this information, use ListAliases.
+// * Aliases associated with the KMS key. To get this information, use ListAliases.
//
-// * Whether automatic key rotation is enabled on the CMK. To get this information,
-// use GetKeyRotationStatus. Also, some key states prevent a CMK from being
-// automatically rotated. For details, see How Automatic Key Rotation Works
-// (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-how-it-works)
-// in AWS Key Management Service Developer Guide.
+// * Whether automatic key rotation is enabled on the KMS key. To get this
+// information, use GetKeyRotationStatus. Also, some key states prevent a
+// KMS key from being automatically rotated. For details, see How Automatic
+// Key Rotation Works (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-how-it-works)
+// in Key Management Service Developer Guide.
//
-// * Tags on the CMK. To get this information, use ListResourceTags.
+// * Tags on the KMS key. To get this information, use ListResourceTags.
//
-// * Key policies and grants on the CMK. To get this information, use GetKeyPolicy
-// and ListGrants.
+// * Key policies and grants on the KMS key. To get this information, use
+// GetKeyPolicy and ListGrants.
//
-// If you call the DescribeKey operation on a predefined AWS alias, that is,
-// an AWS alias with no key ID, AWS KMS creates an AWS managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#master_keys).
-// Then, it associates the alias with the new CMK, and returns the KeyId and
-// Arn of the new CMK in the response.
+// If you call the DescribeKey operation on a predefined Amazon Web Services
+// alias, that is, an Amazon Web Services alias with no key ID, KMS creates
+// an Amazon Web Services managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
+// Then, it associates the alias with the new KMS key, and returns the KeyId
+// and Arn of the new KMS key in the response.
//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:DescribeKey (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -2047,19 +2053,19 @@ func (c *KMS) DisableKeyRequest(input *DisableKeyInput) (req *request.Request, o
// DisableKey API operation for AWS Key Management Service.
//
-// Sets the state of a customer master key (CMK) to disabled. This change temporarily
-// prevents use of the CMK for cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations).
+// Sets the state of a KMS key to disabled. This change temporarily prevents
+// use of the KMS key for cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations).
//
-// For more information about how key state affects the use of a CMK, see Key
-// state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:DisableKey (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -2094,9 +2100,9 @@ func (c *KMS) DisableKeyRequest(input *DisableKeyInput) (req *request.Request, o
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/DisableKey
func (c *KMS) DisableKey(input *DisableKeyInput) (*DisableKeyOutput, error) {
@@ -2166,21 +2172,21 @@ func (c *KMS) DisableKeyRotationRequest(input *DisableKeyRotationInput) (req *re
// DisableKeyRotation API operation for AWS Key Management Service.
//
// Disables automatic rotation of the key material (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html)
-// for the specified symmetric customer master key (CMK).
+// for the specified symmetric KMS key.
//
-// You cannot enable automatic rotation of asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks),
-// CMKs with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
-// or CMKs in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
+// You cannot enable automatic rotation of asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks),
+// KMS keys with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
+// or KMS keys in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
// To enable or disable automatic rotation of a set of related multi-Region
// keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html#mrk-replica-key),
// set the property on the primary key.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:DisableKeyRotation (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -2204,7 +2210,7 @@ func (c *KMS) DisableKeyRotationRequest(input *DisableKeyRotationInput) (req *re
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * InvalidArnException
// The request was rejected because a specified ARN, or an ARN in a key policy,
@@ -2222,9 +2228,9 @@ func (c *KMS) DisableKeyRotationRequest(input *DisableKeyRotationInput) (req *re
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * UnsupportedOperationException
// The request was rejected because a specified parameter is not supported or
@@ -2298,14 +2304,14 @@ func (c *KMS) DisconnectCustomKeyStoreRequest(input *DisconnectCustomKeyStoreInp
// DisconnectCustomKeyStore API operation for AWS Key Management Service.
//
// Disconnects the custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// from its associated AWS CloudHSM cluster. While a custom key store is disconnected,
-// you can manage the custom key store and its customer master keys (CMKs),
-// but you cannot create or use CMKs in the custom key store. You can reconnect
-// the custom key store at any time.
-//
-// While a custom key store is disconnected, all attempts to create customer
-// master keys (CMKs) in the custom key store or to use existing CMKs in cryptographic
-// operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations)
+// from its associated CloudHSM cluster. While a custom key store is disconnected,
+// you can manage the custom key store and its KMS keys, but you cannot create
+// or use KMS keys in the custom key store. You can reconnect the custom key
+// store at any time.
+//
+// While a custom key store is disconnected, all attempts to create KMS keys
+// in the custom key store or to use existing KMS keys in cryptographic operations
+// (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations)
// will fail. This action can prevent users from storing and accessing sensitive
// data.
//
@@ -2316,11 +2322,11 @@ func (c *KMS) DisconnectCustomKeyStoreRequest(input *DisconnectCustomKeyStoreInp
// If the operation succeeds, it returns a JSON object with no properties.
//
// This operation is part of the Custom Key Store feature (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// feature in AWS KMS, which combines the convenience and extensive integration
-// of AWS KMS with the isolation and control of a single-tenant key store.
+// feature in KMS, which combines the convenience and extensive integration
+// of KMS with the isolation and control of a single-tenant key store.
//
// Cross-account use: No. You cannot perform this operation on a custom key
-// store in a different AWS account.
+// store in a different Amazon Web Services account.
//
// Required permissions: kms:DisconnectCustomKeyStore (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy)
@@ -2365,7 +2371,7 @@ func (c *KMS) DisconnectCustomKeyStoreRequest(input *DisconnectCustomKeyStoreInp
// for all other ConnectionState values.
//
// * CustomKeyStoreNotFoundException
-// The request was rejected because AWS KMS cannot find a custom key store with
+// The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
//
// * InternalException
@@ -2439,15 +2445,15 @@ func (c *KMS) EnableKeyRequest(input *EnableKeyInput) (req *request.Request, out
// EnableKey API operation for AWS Key Management Service.
//
-// Sets the key state of a customer master key (CMK) to enabled. This allows
-// you to use the CMK for cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations).
+// Sets the key state of a KMS key to enabled. This allows you to use the KMS
+// key for cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations).
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:EnableKey (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -2481,15 +2487,15 @@ func (c *KMS) EnableKeyRequest(input *EnableKeyInput) (req *request.Request, out
// * LimitExceededException
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// * InvalidStateException
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/EnableKey
func (c *KMS) EnableKey(input *EnableKeyInput) (*EnableKeyOutput, error) {
@@ -2559,21 +2565,21 @@ func (c *KMS) EnableKeyRotationRequest(input *EnableKeyRotationInput) (req *requ
// EnableKeyRotation API operation for AWS Key Management Service.
//
// Enables automatic rotation of the key material (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html)
-// for the specified symmetric customer master key (CMK).
+// for the specified symmetric KMS key.
//
-// You cannot enable automatic rotation of asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks),
-// CMKs with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
-// or CMKs in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
+// You cannot enable automatic rotation of asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks),
+// KMS keys with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
+// or KMS keys in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
// To enable or disable automatic rotation of a set of related multi-Region
// keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html#mrk-replica-key),
// set the property on the primary key.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:EnableKeyRotation (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -2597,7 +2603,7 @@ func (c *KMS) EnableKeyRotationRequest(input *EnableKeyRotationInput) (req *requ
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * InvalidArnException
// The request was rejected because a specified ARN, or an ARN in a key policy,
@@ -2615,9 +2621,9 @@ func (c *KMS) EnableKeyRotationRequest(input *EnableKeyRotationInput) (req *requ
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * UnsupportedOperationException
// The request was rejected because a specified parameter is not supported or
@@ -2689,55 +2695,56 @@ func (c *KMS) EncryptRequest(input *EncryptInput) (req *request.Request, output
// Encrypt API operation for AWS Key Management Service.
//
-// Encrypts plaintext into ciphertext by using a customer master key (CMK).
-// The Encrypt operation has two primary use cases:
+// Encrypts plaintext into ciphertext by using a KMS key. The Encrypt operation
+// has two primary use cases:
//
// * You can encrypt small amounts of arbitrary data, such as a personal
// identifier or database password, or other sensitive information.
//
-// * You can use the Encrypt operation to move encrypted data from one AWS
-// Region to another. For example, in Region A, generate a data key and use
-// the plaintext key to encrypt your data. Then, in Region A, use the Encrypt
-// operation to encrypt the plaintext data key under a CMK in Region B. Now,
-// you can move the encrypted data and the encrypted data key to Region B.
-// When necessary, you can decrypt the encrypted data key and the encrypted
-// data entirely within in Region B.
+// * You can use the Encrypt operation to move encrypted data from one Amazon
+// Web Services Region to another. For example, in Region A, generate a data
+// key and use the plaintext key to encrypt your data. Then, in Region A,
+// use the Encrypt operation to encrypt the plaintext data key under a KMS
+// key in Region B. Now, you can move the encrypted data and the encrypted
+// data key to Region B. When necessary, you can decrypt the encrypted data
+// key and the encrypted data entirely within in Region B.
//
// You don't need to use the Encrypt operation to encrypt a data key. The GenerateDataKey
// and GenerateDataKeyPair operations return a plaintext data key and an encrypted
// copy of that data key.
//
-// When you encrypt data, you must specify a symmetric or asymmetric CMK to
-// use in the encryption operation. The CMK must have a KeyUsage value of ENCRYPT_DECRYPT.
-// To find the KeyUsage of a CMK, use the DescribeKey operation.
+// When you encrypt data, you must specify a symmetric or asymmetric KMS key
+// to use in the encryption operation. The KMS key must have a KeyUsage value
+// of ENCRYPT_DECRYPT. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// If you use a symmetric CMK, you can use an encryption context to add additional
-// security to your encryption operation. If you specify an EncryptionContext
+// If you use a symmetric KMS key, you can use an encryption context to add
+// additional security to your encryption operation. If you specify an EncryptionContext
// when encrypting data, you must specify the same encryption context (a case-sensitive
// exact match) when decrypting the data. Otherwise, the request to decrypt
// fails with an InvalidCiphertextException. For more information, see Encryption
// Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
-// If you specify an asymmetric CMK, you must also specify the encryption algorithm.
-// The algorithm must be compatible with the CMK type.
+// If you specify an asymmetric KMS key, you must also specify the encryption
+// algorithm. The algorithm must be compatible with the KMS key type.
//
-// When you use an asymmetric CMK to encrypt or reencrypt data, be sure to record
-// the CMK and encryption algorithm that you choose. You will be required to
-// provide the same CMK and encryption algorithm when you decrypt the data.
-// If the CMK and algorithm do not match the values used to encrypt the data,
-// the decrypt operation fails.
+// When you use an asymmetric KMS key to encrypt or reencrypt data, be sure
+// to record the KMS key and encryption algorithm that you choose. You will
+// be required to provide the same KMS key and encryption algorithm when you
+// decrypt the data. If the KMS key and algorithm do not match the values used
+// to encrypt the data, the decrypt operation fails.
//
-// You are not required to supply the CMK ID and encryption algorithm when you
-// decrypt with symmetric CMKs because AWS KMS stores this information in the
-// ciphertext blob. AWS KMS cannot store metadata in ciphertext generated with
-// asymmetric keys. The standard format for asymmetric key ciphertext does not
-// include configurable fields.
+// You are not required to supply the key ID and encryption algorithm when you
+// decrypt with symmetric KMS keys because KMS stores this information in the
+// ciphertext blob. KMS cannot store metadata in ciphertext generated with asymmetric
+// keys. The standard format for asymmetric key ciphertext does not include
+// configurable fields.
//
// The maximum size of the data that you can encrypt varies with the type of
-// CMK and the encryption algorithm that you choose.
+// KMS key and the encryption algorithm that you choose.
//
-// * Symmetric CMKs SYMMETRIC_DEFAULT: 4096 bytes
+// * Symmetric KMS keys SYMMETRIC_DEFAULT: 4096 bytes
//
// * RSA_2048 RSAES_OAEP_SHA_1: 214 bytes RSAES_OAEP_SHA_256: 190 bytes
//
@@ -2745,12 +2752,13 @@ func (c *KMS) EncryptRequest(input *EncryptInput) (req *request.Request, output
//
// * RSA_4096 RSAES_OAEP_SHA_1: 470 bytes RSAES_OAEP_SHA_256: 446 bytes
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:Encrypt (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -2776,11 +2784,11 @@ func (c *KMS) EncryptRequest(input *EncryptInput) (req *request.Request, output
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -2789,17 +2797,18 @@ func (c *KMS) EncryptRequest(input *EncryptInput) (req *request.Request, output
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InvalidGrantTokenException
// The request was rejected because the specified grant token is not valid.
@@ -2812,9 +2821,9 @@ func (c *KMS) EncryptRequest(input *EncryptInput) (req *request.Request, output
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/Encrypt
func (c *KMS) Encrypt(input *EncryptInput) (*EncryptOutput, error) {
@@ -2884,18 +2893,18 @@ func (c *KMS) GenerateDataKeyRequest(input *GenerateDataKeyInput) (req *request.
//
// Generates a unique symmetric data key for client-side encryption. This operation
// returns a plaintext copy of the data key and a copy that is encrypted under
-// a customer master key (CMK) that you specify. You can use the plaintext key
-// to encrypt your data outside of AWS KMS and store the encrypted data key
-// with the encrypted data.
+// a KMS key that you specify. You can use the plaintext key to encrypt your
+// data outside of KMS and store the encrypted data key with the encrypted data.
//
// GenerateDataKey returns a unique data key for each request. The bytes in
-// the plaintext key are not related to the caller or the CMK.
+// the plaintext key are not related to the caller or the KMS key.
//
-// To generate a data key, specify the symmetric CMK that will be used to encrypt
-// the data key. You cannot use an asymmetric CMK to generate data keys. To
-// get the type of your CMK, use the DescribeKey operation. You must also specify
-// the length of the data key. Use either the KeySpec or NumberOfBytes parameters
-// (but not both). For 128-bit and 256-bit data keys, use the KeySpec parameter.
+// To generate a data key, specify the symmetric KMS key that will be used to
+// encrypt the data key. You cannot use an asymmetric KMS key to generate data
+// keys. To get the type of your KMS key, use the DescribeKey operation. You
+// must also specify the length of the data key. Use either the KeySpec or NumberOfBytes
+// parameters (but not both). For 128-bit and 256-bit data keys, use the KeySpec
+// parameter.
//
// To get only an encrypted copy of the data key, use GenerateDataKeyWithoutPlaintext.
// To generate an asymmetric data key pair, use the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext
@@ -2906,41 +2915,48 @@ func (c *KMS) GenerateDataKeyRequest(input *GenerateDataKeyInput) (req *request.
// the same encryption context (a case-sensitive exact match) when decrypting
// the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException.
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// Applications in Amazon Web Services Nitro Enclaves can call this operation
+// by using the Amazon Web Services Nitro Enclaves Development Kit (https://github.com/aws/aws-nitro-enclaves-sdk-c).
+// For information about the supporting parameters, see How Amazon Web Services
+// Nitro Enclaves use KMS (https://docs.aws.amazon.com/kms/latest/developerguide/services-nitro-enclaves.html)
+// in the Key Management Service Developer Guide.
+//
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
// How to use your data key
//
// We recommend that you use the following pattern to encrypt data locally in
// your application. You can write your own code or use a client-side encryption
-// library, such as the AWS Encryption SDK (https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/),
+// library, such as the Amazon Web Services Encryption SDK (https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/),
// the Amazon DynamoDB Encryption Client (https://docs.aws.amazon.com/dynamodb-encryption-client/latest/devguide/),
// or Amazon S3 client-side encryption (https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html)
// to do these tasks for you.
//
-// To encrypt data outside of AWS KMS:
+// To encrypt data outside of KMS:
//
// Use the GenerateDataKey operation to get a data key.
//
// Use the plaintext data key (in the Plaintext field of the response) to encrypt
-// your data outside of AWS KMS. Then erase the plaintext data key from memory.
+// your data outside of KMS. Then erase the plaintext data key from memory.
//
// Store the encrypted data key (in the CiphertextBlob field of the response)
// with the encrypted data.
//
-// To decrypt data outside of AWS KMS:
+// To decrypt data outside of KMS:
//
// Use the Decrypt operation to decrypt the encrypted data key. The operation
// returns a plaintext copy of the data key.
//
-// Use the plaintext data key to decrypt data outside of AWS KMS, then erase
-// the plaintext data key from memory.
+// Use the plaintext data key to decrypt data outside of KMS, then erase the
+// plaintext data key from memory.
//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:GenerateDataKey (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -2970,11 +2986,11 @@ func (c *KMS) GenerateDataKeyRequest(input *GenerateDataKeyInput) (req *request.
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -2983,17 +2999,18 @@ func (c *KMS) GenerateDataKeyRequest(input *GenerateDataKeyInput) (req *request.
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InvalidGrantTokenException
// The request was rejected because the specified grant token is not valid.
@@ -3006,9 +3023,9 @@ func (c *KMS) GenerateDataKeyRequest(input *GenerateDataKeyInput) (req *request.
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/GenerateDataKey
func (c *KMS) GenerateDataKey(input *GenerateDataKeyInput) (*GenerateDataKeyOutput, error) {
@@ -3078,22 +3095,24 @@ func (c *KMS) GenerateDataKeyPairRequest(input *GenerateDataKeyPairInput) (req *
//
// Generates a unique asymmetric data key pair. The GenerateDataKeyPair operation
// returns a plaintext public key, a plaintext private key, and a copy of the
-// private key that is encrypted under the symmetric CMK you specify. You can
-// use the data key pair to perform asymmetric cryptography outside of AWS KMS.
-//
-// GenerateDataKeyPair returns a unique data key pair for each request. The
-// bytes in the keys are not related to the caller or the CMK that is used to
-// encrypt the private key.
+// private key that is encrypted under the symmetric KMS key you specify. You
+// can use the data key pair to perform asymmetric cryptography and implement
+// digital signatures outside of KMS.
//
// You can use the public key that GenerateDataKeyPair returns to encrypt data
-// or verify a signature outside of AWS KMS. Then, store the encrypted private
-// key with the data. When you are ready to decrypt data or sign a message,
-// you can use the Decrypt operation to decrypt the encrypted private key.
+// or verify a signature outside of KMS. Then, store the encrypted private key
+// with the data. When you are ready to decrypt data or sign a message, you
+// can use the Decrypt operation to decrypt the encrypted private key.
+//
+// To generate a data key pair, you must specify a symmetric KMS key to encrypt
+// the private key in a data key pair. You cannot use an asymmetric KMS key
+// or a KMS key in a custom key store. To get the type and origin of your KMS
+// key, use the DescribeKey operation.
//
-// To generate a data key pair, you must specify a symmetric customer master
-// key (CMK) to encrypt the private key in a data key pair. You cannot use an
-// asymmetric CMK or a CMK in a custom key store. To get the type and origin
-// of your CMK, use the DescribeKey operation.
+// Use the KeyPairSpec parameter to choose an RSA or Elliptic Curve (ECC) data
+// key pair. KMS recommends that your use ECC key pairs for signing, and use
+// RSA key pairs for either encryption or signing, but not both. However, KMS
+// cannot enforce any restrictions on the use of data key pairs outside of KMS.
//
// If you are using the data key pair to encrypt data, or for any operation
// where you don't immediately need a private key, consider using the GenerateDataKeyPairWithoutPlaintext
@@ -3103,19 +3122,26 @@ func (c *KMS) GenerateDataKeyPairRequest(input *GenerateDataKeyPairInput) (req *
// to decrypt the data or sign a message, use the Decrypt operation to decrypt
// the encrypted private key in the data key pair.
//
+// GenerateDataKeyPair returns a unique data key pair for each request. The
+// bytes in the keys are not related to the caller or the KMS key that is used
+// to encrypt the private key. The public key is a DER-encoded X.509 SubjectPublicKeyInfo,
+// as specified in RFC 5280 (https://tools.ietf.org/html/rfc5280). The private
+// key is a DER-encoded PKCS8 PrivateKeyInfo, as specified in RFC 5958 (https://tools.ietf.org/html/rfc5958).
+//
// You can use the optional encryption context to add additional security to
// the encryption operation. If you specify an EncryptionContext, you must specify
// the same encryption context (a case-sensitive exact match) when decrypting
// the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException.
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:GenerateDataKeyPair (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -3145,11 +3171,11 @@ func (c *KMS) GenerateDataKeyPairRequest(input *GenerateDataKeyPairInput) (req *
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -3158,17 +3184,18 @@ func (c *KMS) GenerateDataKeyPairRequest(input *GenerateDataKeyPairInput) (req *
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InvalidGrantTokenException
// The request was rejected because the specified grant token is not valid.
@@ -3181,9 +3208,9 @@ func (c *KMS) GenerateDataKeyPairRequest(input *GenerateDataKeyPairInput) (req *
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * UnsupportedOperationException
// The request was rejected because a specified parameter is not supported or
@@ -3257,37 +3284,43 @@ func (c *KMS) GenerateDataKeyPairWithoutPlaintextRequest(input *GenerateDataKeyP
//
// Generates a unique asymmetric data key pair. The GenerateDataKeyPairWithoutPlaintext
// operation returns a plaintext public key and a copy of the private key that
-// is encrypted under the symmetric CMK you specify. Unlike GenerateDataKeyPair,
+// is encrypted under the symmetric KMS key you specify. Unlike GenerateDataKeyPair,
// this operation does not return a plaintext private key.
//
-// To generate a data key pair, you must specify a symmetric customer master
-// key (CMK) to encrypt the private key in the data key pair. You cannot use
-// an asymmetric CMK or a CMK in a custom key store. To get the type and origin
-// of your CMK, use the KeySpec field in the DescribeKey response.
-//
// You can use the public key that GenerateDataKeyPairWithoutPlaintext returns
-// to encrypt data or verify a signature outside of AWS KMS. Then, store the
-// encrypted private key with the data. When you are ready to decrypt data or
-// sign a message, you can use the Decrypt operation to decrypt the encrypted
-// private key.
+// to encrypt data or verify a signature outside of KMS. Then, store the encrypted
+// private key with the data. When you are ready to decrypt data or sign a message,
+// you can use the Decrypt operation to decrypt the encrypted private key.
+//
+// To generate a data key pair, you must specify a symmetric KMS key to encrypt
+// the private key in a data key pair. You cannot use an asymmetric KMS key
+// or a KMS key in a custom key store. To get the type and origin of your KMS
+// key, use the DescribeKey operation.
+//
+// Use the KeyPairSpec parameter to choose an RSA or Elliptic Curve (ECC) data
+// key pair. KMS recommends that your use ECC key pairs for signing, and use
+// RSA key pairs for either encryption or signing, but not both. However, KMS
+// cannot enforce any restrictions on the use of data key pairs outside of KMS.
//
// GenerateDataKeyPairWithoutPlaintext returns a unique data key pair for each
-// request. The bytes in the key are not related to the caller or CMK that is
-// used to encrypt the private key.
+// request. The bytes in the key are not related to the caller or KMS key that
+// is used to encrypt the private key. The public key is a DER-encoded X.509
+// SubjectPublicKeyInfo, as specified in RFC 5280 (https://tools.ietf.org/html/rfc5280).
//
// You can use the optional encryption context to add additional security to
// the encryption operation. If you specify an EncryptionContext, you must specify
// the same encryption context (a case-sensitive exact match) when decrypting
// the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException.
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:GenerateDataKeyPairWithoutPlaintext (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -3317,11 +3350,11 @@ func (c *KMS) GenerateDataKeyPairWithoutPlaintextRequest(input *GenerateDataKeyP
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -3330,17 +3363,18 @@ func (c *KMS) GenerateDataKeyPairWithoutPlaintextRequest(input *GenerateDataKeyP
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InvalidGrantTokenException
// The request was rejected because the specified grant token is not valid.
@@ -3353,9 +3387,9 @@ func (c *KMS) GenerateDataKeyPairWithoutPlaintextRequest(input *GenerateDataKeyP
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * UnsupportedOperationException
// The request was rejected because a specified parameter is not supported or
@@ -3428,8 +3462,8 @@ func (c *KMS) GenerateDataKeyWithoutPlaintextRequest(input *GenerateDataKeyWitho
// GenerateDataKeyWithoutPlaintext API operation for AWS Key Management Service.
//
// Generates a unique symmetric data key. This operation returns a data key
-// that is encrypted under a customer master key (CMK) that you specify. To
-// request an asymmetric data key pair, use the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext
+// that is encrypted under a KMS key that you specify. To request an asymmetric
+// data key pair, use the GenerateDataKeyPair or GenerateDataKeyPairWithoutPlaintext
// operations.
//
// GenerateDataKeyWithoutPlaintext is identical to the GenerateDataKey operation
@@ -3448,13 +3482,12 @@ func (c *KMS) GenerateDataKeyWithoutPlaintextRequest(input *GenerateDataKeyWitho
// never sees the plaintext data key.
//
// GenerateDataKeyWithoutPlaintext returns a unique data key for each request.
-// The bytes in the keys are not related to the caller or CMK that is used to
-// encrypt the private key.
+// The bytes in the keys are not related to the caller or KMS key that is used
+// to encrypt the private key.
//
-// To generate a data key, you must specify the symmetric customer master key
-// (CMK) that is used to encrypt the data key. You cannot use an asymmetric
-// CMK to generate a data key. To get the type of your CMK, use the DescribeKey
-// operation.
+// To generate a data key, you must specify the symmetric KMS key that is used
+// to encrypt the data key. You cannot use an asymmetric KMS key to generate
+// a data key. To get the type of your KMS key, use the DescribeKey operation.
//
// If the operation succeeds, you will find the encrypted copy of the data key
// in the CiphertextBlob field.
@@ -3464,14 +3497,15 @@ func (c *KMS) GenerateDataKeyWithoutPlaintextRequest(input *GenerateDataKeyWitho
// the same encryption context (a case-sensitive exact match) when decrypting
// the encrypted data key. Otherwise, the request to decrypt fails with an InvalidCiphertextException.
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:GenerateDataKeyWithoutPlaintext (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -3501,11 +3535,11 @@ func (c *KMS) GenerateDataKeyWithoutPlaintextRequest(input *GenerateDataKeyWitho
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -3514,17 +3548,18 @@ func (c *KMS) GenerateDataKeyWithoutPlaintextRequest(input *GenerateDataKeyWitho
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InvalidGrantTokenException
// The request was rejected because the specified grant token is not valid.
@@ -3537,9 +3572,9 @@ func (c *KMS) GenerateDataKeyWithoutPlaintextRequest(input *GenerateDataKeyWitho
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/GenerateDataKeyWithoutPlaintext
func (c *KMS) GenerateDataKeyWithoutPlaintext(input *GenerateDataKeyWithoutPlaintextInput) (*GenerateDataKeyWithoutPlaintextOutput, error) {
@@ -3609,13 +3644,19 @@ func (c *KMS) GenerateRandomRequest(input *GenerateRandomInput) (req *request.Re
//
// Returns a random byte string that is cryptographically secure.
//
-// By default, the random byte string is generated in AWS KMS. To generate the
-// byte string in the AWS CloudHSM cluster that is associated with a custom
-// key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html),
+// By default, the random byte string is generated in KMS. To generate the byte
+// string in the CloudHSM cluster that is associated with a custom key store
+// (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html),
// specify the custom key store ID.
//
-// For more information about entropy and random number generation, see AWS
-// Key Management Service Cryptographic Details (https://docs.aws.amazon.com/kms/latest/cryptographic-details/).
+// Applications in Amazon Web Services Nitro Enclaves can call this operation
+// by using the Amazon Web Services Nitro Enclaves Development Kit (https://github.com/aws/aws-nitro-enclaves-sdk-c).
+// For information about the supporting parameters, see How Amazon Web Services
+// Nitro Enclaves use KMS (https://docs.aws.amazon.com/kms/latest/developerguide/services-nitro-enclaves.html)
+// in the Key Management Service Developer Guide.
+//
+// For more information about entropy and random number generation, see Key
+// Management Service Cryptographic Details (https://docs.aws.amazon.com/kms/latest/cryptographic-details/).
//
// Required permissions: kms:GenerateRandom (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy)
@@ -3637,7 +3678,7 @@ func (c *KMS) GenerateRandomRequest(input *GenerateRandomInput) (req *request.Re
// can be retried.
//
// * CustomKeyStoreNotFoundException
-// The request was rejected because AWS KMS cannot find a custom key store with
+// The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
//
// * CustomKeyStoreInvalidStateException
@@ -3725,10 +3766,10 @@ func (c *KMS) GetKeyPolicyRequest(input *GetKeyPolicyInput) (req *request.Reques
// GetKeyPolicy API operation for AWS Key Management Service.
//
-// Gets a key policy attached to the specified customer master key (CMK).
+// Gets a key policy attached to the specified KMS key.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:GetKeyPolicy (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -3763,9 +3804,9 @@ func (c *KMS) GetKeyPolicyRequest(input *GetKeyPolicyInput) (req *request.Reques
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/GetKeyPolicy
func (c *KMS) GetKeyPolicy(input *GetKeyPolicyInput) (*GetKeyPolicyOutput, error) {
@@ -3835,30 +3876,31 @@ func (c *KMS) GetKeyRotationStatusRequest(input *GetKeyRotationStatusInput) (req
//
// Gets a Boolean value that indicates whether automatic rotation of the key
// material (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html)
-// is enabled for the specified customer master key (CMK).
+// is enabled for the specified KMS key.
//
-// You cannot enable automatic rotation of asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks),
-// CMKs with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
-// or CMKs in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
+// You cannot enable automatic rotation of asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks),
+// KMS keys with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
+// or KMS keys in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
// To enable or disable automatic rotation of a set of related multi-Region
// keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html#mrk-replica-key),
-// set the property on the primary key. The key rotation status for these CMKs
-// is always false.
+// set the property on the primary key. The key rotation status for these KMS
+// keys is always false.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
// * Disabled: The key rotation status does not change when you disable a
-// CMK. However, while the CMK is disabled, AWS KMS does not rotate the backing
-// key.
+// KMS key. However, while the KMS key is disabled, KMS does not rotate the
+// key material.
//
-// * Pending deletion: While a CMK is pending deletion, its key rotation
-// status is false and AWS KMS does not rotate the backing key. If you cancel
+// * Pending deletion: While a KMS key is pending deletion, its key rotation
+// status is false and KMS does not rotate the key material. If you cancel
// the deletion, the original key rotation status is restored.
//
-// Cross-account use: Yes. To perform this operation on a CMK in a different
-// AWS account, specify the key ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation on a KMS key in a different
+// Amazon Web Services account, specify the key ARN in the value of the KeyId
+// parameter.
//
// Required permissions: kms:GetKeyRotationStatus (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -3897,9 +3939,9 @@ func (c *KMS) GetKeyRotationStatusRequest(input *GetKeyRotationStatusInput) (req
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * UnsupportedOperationException
// The request was rejected because a specified parameter is not supported or
@@ -3972,19 +4014,20 @@ func (c *KMS) GetParametersForImportRequest(input *GetParametersForImportInput)
// GetParametersForImport API operation for AWS Key Management Service.
//
// Returns the items you need to import key material into a symmetric, customer
-// managed customer master key (CMK). For more information about importing key
-// material into AWS KMS, see Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
-// in the AWS Key Management Service Developer Guide.
+// managed KMS key. For more information about importing key material into KMS,
+// see Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
+// in the Key Management Service Developer Guide.
//
// This operation returns a public key and an import token. Use the public key
// to encrypt the symmetric key material. Store the import token to send with
// a subsequent ImportKeyMaterial request.
//
-// You must specify the key ID of the symmetric CMK into which you will import
-// key material. This CMK's Origin must be EXTERNAL. You must also specify the
-// wrapping algorithm and type of wrapping key (public key) that you will use
-// to encrypt the key material. You cannot perform this operation on an asymmetric
-// CMK or on any CMK in a different AWS account.
+// You must specify the key ID of the symmetric KMS key into which you will
+// import key material. This KMS key's Origin must be EXTERNAL. You must also
+// specify the wrapping algorithm and type of wrapping key (public key) that
+// you will use to encrypt the key material. You cannot perform this operation
+// on an asymmetric KMS key or on any KMS key in a different Amazon Web Services
+// account.
//
// To import key material, you must use the public key and import token from
// the same response. These items are valid for 24 hours. The expiration date
@@ -3992,12 +4035,12 @@ func (c *KMS) GetParametersForImportRequest(input *GetParametersForImportInput)
// expired token in an ImportKeyMaterial request. If your key and token expire,
// send another GetParametersForImport request.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:GetParametersForImport (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -4040,9 +4083,9 @@ func (c *KMS) GetParametersForImportRequest(input *GetParametersForImportInput)
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/GetParametersForImport
func (c *KMS) GetParametersForImport(input *GetParametersForImportInput) (*GetParametersForImportOutput, error) {
@@ -4110,27 +4153,26 @@ func (c *KMS) GetPublicKeyRequest(input *GetPublicKeyInput) (req *request.Reques
// GetPublicKey API operation for AWS Key Management Service.
//
-// Returns the public key of an asymmetric CMK. Unlike the private key of a
-// asymmetric CMK, which never leaves AWS KMS unencrypted, callers with kms:GetPublicKey
-// permission can download the public key of an asymmetric CMK. You can share
-// the public key to allow others to encrypt messages and verify signatures
-// outside of AWS KMS. For information about symmetric and asymmetric CMKs,
-// see Using Symmetric and Asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
-// in the AWS Key Management Service Developer Guide.
+// Returns the public key of an asymmetric KMS key. Unlike the private key of
+// a asymmetric KMS key, which never leaves KMS unencrypted, callers with kms:GetPublicKey
+// permission can download the public key of an asymmetric KMS key. You can
+// share the public key to allow others to encrypt messages and verify signatures
+// outside of KMS. For information about symmetric and asymmetric KMS keys,
+// see Using Symmetric and Asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
+// in the Key Management Service Developer Guide.
//
// You do not need to download the public key. Instead, you can use the public
-// key within AWS KMS by calling the Encrypt, ReEncrypt, or Verify operations
-// with the identifier of an asymmetric CMK. When you use the public key within
-// AWS KMS, you benefit from the authentication, authorization, and logging
-// that are part of every AWS KMS operation. You also reduce of risk of encrypting
-// data that cannot be decrypted. These features are not effective outside of
-// AWS KMS. For details, see Special Considerations for Downloading Public Keys
-// (https://docs.aws.amazon.com/kms/latest/developerguide/download-public-key.html#download-public-key-considerations).
-//
-// To help you use the public key safely outside of AWS KMS, GetPublicKey returns
+// key within KMS by calling the Encrypt, ReEncrypt, or Verify operations with
+// the identifier of an asymmetric KMS key. When you use the public key within
+// KMS, you benefit from the authentication, authorization, and logging that
+// are part of every KMS operation. You also reduce of risk of encrypting data
+// that cannot be decrypted. These features are not effective outside of KMS.
+// For details, see Special Considerations for Downloading Public Keys (https://docs.aws.amazon.com/kms/latest/developerguide/download-public-key.html#download-public-key-considerations).
+//
+// To help you use the public key safely outside of KMS, GetPublicKey returns
// important information about the public key in the response, including:
//
-// * CustomerMasterKeySpec (https://docs.aws.amazon.com/kms/latest/APIReference/API_GetPublicKey.html#KMS-GetPublicKey-response-CustomerMasterKeySpec):
+// * KeySpec (https://docs.aws.amazon.com/kms/latest/APIReference/API_GetPublicKey.html#KMS-GetPublicKey-response-KeySpec):
// The type of key material in the public key, such as RSA_4096 or ECC_NIST_P521.
//
// * KeyUsage (https://docs.aws.amazon.com/kms/latest/APIReference/API_GetPublicKey.html#KMS-GetPublicKey-response-KeyUsage):
@@ -4141,19 +4183,20 @@ func (c *KMS) GetPublicKeyRequest(input *GetPublicKeyInput) (req *request.Reques
// A list of the encryption algorithms or the signing algorithms for the
// key.
//
-// Although AWS KMS cannot enforce these restrictions on external operations,
-// it is crucial that you use this information to prevent the public key from
-// being used improperly. For example, you can prevent a public signing key
-// from being used encrypt data, or prevent a public key from being used with
-// an encryption algorithm that is not supported by AWS KMS. You can also avoid
-// errors, such as using the wrong signing algorithm in a verification operation.
+// Although KMS cannot enforce these restrictions on external operations, it
+// is crucial that you use this information to prevent the public key from being
+// used improperly. For example, you can prevent a public signing key from being
+// used encrypt data, or prevent a public key from being used with an encryption
+// algorithm that is not supported by KMS. You can also avoid errors, such as
+// using the wrong signing algorithm in a verification operation.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:GetPublicKey (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -4173,11 +4216,11 @@ func (c *KMS) GetPublicKeyRequest(input *GetPublicKeyInput) (req *request.Reques
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -4197,17 +4240,18 @@ func (c *KMS) GetPublicKeyRequest(input *GetPublicKeyInput) (req *request.Reques
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InternalException
// The request was rejected because an internal exception occurred. The request
@@ -4217,9 +4261,9 @@ func (c *KMS) GetPublicKeyRequest(input *GetPublicKeyInput) (req *request.Reques
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/GetPublicKey
func (c *KMS) GetPublicKey(input *GetPublicKeyInput) (*GetPublicKeyOutput, error) {
@@ -4288,15 +4332,16 @@ func (c *KMS) ImportKeyMaterialRequest(input *ImportKeyMaterialInput) (req *requ
// ImportKeyMaterial API operation for AWS Key Management Service.
//
-// Imports key material into an existing symmetric AWS KMS customer master key
-// (CMK) that was created without key material. After you successfully import
-// key material into a CMK, you can reimport the same key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html#reimport-key-material)
-// into that CMK, but you cannot import different key material.
+// Imports key material into an existing symmetric KMS KMS key that was created
+// without key material. After you successfully import key material into a KMS
+// key, you can reimport the same key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html#reimport-key-material)
+// into that KMS key, but you cannot import different key material.
//
-// You cannot perform this operation on an asymmetric CMK or on any CMK in a
-// different AWS account. For more information about creating CMKs with no key
-// material and then importing key material, see Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
-// in the AWS Key Management Service Developer Guide.
+// You cannot perform this operation on an asymmetric KMS key or on any KMS
+// key in a different Amazon Web Services account. For more information about
+// creating KMS keys with no key material and then importing key material, see
+// Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
+// in the Key Management Service Developer Guide.
//
// Before using this operation, call GetParametersForImport. Its response includes
// a public key and an import token. Use the public key to encrypt the key material.
@@ -4304,10 +4349,10 @@ func (c *KMS) ImportKeyMaterialRequest(input *ImportKeyMaterialInput) (req *requ
//
// When calling this operation, you must specify the following values:
//
-// * The key ID or key ARN of a CMK with no key material. Its Origin must
-// be EXTERNAL. To create a CMK with no key material, call CreateKey and
-// set the value of its Origin parameter to EXTERNAL. To get the Origin of
-// a CMK, call DescribeKey.)
+// * The key ID or key ARN of a KMS key with no key material. Its Origin
+// must be EXTERNAL. To create a KMS key with no key material, call CreateKey
+// and set the value of its Origin parameter to EXTERNAL. To get the Origin
+// of a KMS key, call DescribeKey.)
//
// * The encrypted key material. To get the public key to encrypt the key
// material, call GetParametersForImport.
@@ -4316,27 +4361,27 @@ func (c *KMS) ImportKeyMaterialRequest(input *ImportKeyMaterialInput) (req *requ
// a public key and token from the same GetParametersForImport response.
//
// * Whether the key material expires and if so, when. If you set an expiration
-// date, AWS KMS deletes the key material from the CMK on the specified date,
-// and the CMK becomes unusable. To use the CMK again, you must reimport
+// date, KMS deletes the key material from the KMS key on the specified date,
+// and the KMS key becomes unusable. To use the KMS key again, you must reimport
// the same key material. The only way to change an expiration date is by
// reimporting the same key material and specifying a new expiration date.
//
-// When this operation is successful, the key state of the CMK changes from
-// PendingImport to Enabled, and you can use the CMK.
+// When this operation is successful, the key state of the KMS key changes from
+// PendingImport to Enabled, and you can use the KMS key.
//
// If this operation fails, use the exception to help determine the problem.
// If the error is related to the key material, the import token, or wrapping
// key, use GetParametersForImport to get a new public key and import token
-// for the CMK and repeat the import procedure. For help, see How To Import
+// for the KMS key and repeat the import procedure. For help, see How To Import
// Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html#importing-keys-overview)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:ImportKeyMaterial (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -4379,9 +4424,9 @@ func (c *KMS) ImportKeyMaterialRequest(input *ImportKeyMaterialInput) (req *requ
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * InvalidCiphertextException
// From the Decrypt or ReEncrypt operation, the request was rejected because
@@ -4389,13 +4434,13 @@ func (c *KMS) ImportKeyMaterialRequest(input *ImportKeyMaterialInput) (req *requ
// the ciphertext, such as the encryption context, is corrupted, missing, or
// otherwise invalid.
//
-// From the ImportKeyMaterial operation, the request was rejected because AWS
-// KMS could not decrypt the encrypted (wrapped) key material.
+// From the ImportKeyMaterial operation, the request was rejected because KMS
+// could not decrypt the encrypted (wrapped) key material.
//
// * IncorrectKeyMaterialException
// The request was rejected because the key material in the request is, expired,
// invalid, or is not the same key material that was previously imported into
-// this customer master key (CMK).
+// this KMS key.
//
// * ExpiredImportTokenException
// The request was rejected because the specified import token is expired. Use
@@ -4404,7 +4449,7 @@ func (c *KMS) ImportKeyMaterialRequest(input *ImportKeyMaterialInput) (req *requ
//
// * InvalidImportTokenException
// The request was rejected because the provided import token is invalid or
-// is associated with a different customer master key (CMK).
+// is associated with a different KMS key.
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/ImportKeyMaterial
func (c *KMS) ImportKeyMaterial(input *ImportKeyMaterialInput) (*ImportKeyMaterialOutput, error) {
@@ -4478,30 +4523,33 @@ func (c *KMS) ListAliasesRequest(input *ListAliasesInput) (req *request.Request,
// ListAliases API operation for AWS Key Management Service.
//
-// Gets a list of aliases in the caller's AWS account and region. For more information
-// about aliases, see CreateAlias.
+// Gets a list of aliases in the caller's Amazon Web Services account and region.
+// For more information about aliases, see CreateAlias.
//
// By default, the ListAliases operation returns all aliases in the account
-// and region. To get only the aliases associated with a particular customer
-// master key (CMK), use the KeyId parameter.
+// and region. To get only the aliases associated with a particular KMS key,
+// use the KeyId parameter.
//
// The ListAliases response can include aliases that you created and associated
-// with your customer managed CMKs, and aliases that AWS created and associated
-// with AWS managed CMKs in your account. You can recognize AWS aliases because
-// their names have the format aws/, such as aws/dynamodb.
+// with your customer managed keys, and aliases that Amazon Web Services created
+// and associated with Amazon Web Services managed keys in your account. You
+// can recognize Amazon Web Services aliases because their names have the format
+// aws/, such as aws/dynamodb.
//
// The response might also include aliases that have no TargetKeyId field. These
-// are predefined aliases that AWS has created but has not yet associated with
-// a CMK. Aliases that AWS creates in your account, including predefined aliases,
-// do not count against your AWS KMS aliases quota (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html#aliases-limit).
+// are predefined aliases that Amazon Web Services has created but has not yet
+// associated with a KMS key. Aliases that Amazon Web Services creates in your
+// account, including predefined aliases, do not count against your KMS aliases
+// quota (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html#aliases-limit).
//
-// Cross-account use: No. ListAliases does not return aliases in other AWS accounts.
+// Cross-account use: No. ListAliases does not return aliases in other Amazon
+// Web Services accounts.
//
// Required permissions: kms:ListAliases (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy)
//
// For details, see Controlling access to aliases (https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html#alias-access)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// Related operations:
//
@@ -4663,19 +4711,25 @@ func (c *KMS) ListGrantsRequest(input *ListGrantsInput) (req *request.Request, o
// ListGrants API operation for AWS Key Management Service.
//
-// Gets a list of all grants for the specified customer master key (CMK).
+// Gets a list of all grants for the specified KMS key.
//
-// You must specify the CMK in all requests. You can filter the grant list by
-// grant ID or grantee principal.
+// You must specify the KMS key in all requests. You can filter the grant list
+// by grant ID or grantee principal.
+//
+// For detailed information about grants, including grant terminology, see Using
+// grants (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html)
+// in the Key Management Service Developer Guide . For examples of working with
+// grants in several programming languages, see Programming grants (https://docs.aws.amazon.com/kms/latest/developerguide/programming-grants.html).
//
// The GranteePrincipal field in the ListGrants response usually contains the
// user or role designated as the grantee principal in the grant. However, when
-// the grantee principal in the grant is an AWS service, the GranteePrincipal
-// field contains the service principal (https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html#principal-services),
+// the grantee principal in the grant is an Amazon Web Services service, the
+// GranteePrincipal field contains the service principal (https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html#principal-services),
// which might represent several different grantee principals.
//
-// Cross-account use: Yes. To perform this operation on a CMK in a different
-// AWS account, specify the key ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation on a KMS key in a different
+// Amazon Web Services account, specify the key ARN in the value of the KeyId
+// parameter.
//
// Required permissions: kms:ListGrants (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -4725,9 +4779,9 @@ func (c *KMS) ListGrantsRequest(input *ListGrantsInput) (req *request.Request, o
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/ListGrants
func (c *KMS) ListGrants(input *ListGrantsInput) (*ListGrantsResponse, error) {
@@ -4853,12 +4907,12 @@ func (c *KMS) ListKeyPoliciesRequest(input *ListKeyPoliciesInput) (req *request.
// ListKeyPolicies API operation for AWS Key Management Service.
//
-// Gets the names of the key policies that are attached to a customer master
-// key (CMK). This operation is designed to get policy names that you can use
-// in a GetKeyPolicy operation. However, the only valid policy name is default.
+// Gets the names of the key policies that are attached to a KMS key. This operation
+// is designed to get policy names that you can use in a GetKeyPolicy operation.
+// However, the only valid policy name is default.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:ListKeyPolicies (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -4897,9 +4951,9 @@ func (c *KMS) ListKeyPoliciesRequest(input *ListKeyPoliciesInput) (req *request.
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/ListKeyPolicies
func (c *KMS) ListKeyPolicies(input *ListKeyPoliciesInput) (*ListKeyPoliciesOutput, error) {
@@ -5025,11 +5079,11 @@ func (c *KMS) ListKeysRequest(input *ListKeysInput) (req *request.Request, outpu
// ListKeys API operation for AWS Key Management Service.
//
-// Gets a list of all customer master keys (CMKs) in the caller's AWS account
-// and Region.
+// Gets a list of all KMS keys in the caller's Amazon Web Services account and
+// Region.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:ListKeys (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy)
@@ -5182,15 +5236,15 @@ func (c *KMS) ListResourceTagsRequest(input *ListResourceTagsInput) (req *reques
// ListResourceTags API operation for AWS Key Management Service.
//
-// Returns all tags on the specified customer master key (CMK).
+// Returns all tags on the specified KMS key.
//
// For general information about tags, including the format and syntax, see
-// Tagging AWS resources (https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html)
+// Tagging Amazon Web Services resources (https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html)
// in the Amazon Web Services General Reference. For information about using
-// tags in AWS KMS, see Tagging keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
+// tags in KMS, see Tagging keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:ListResourceTags (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -5295,24 +5349,28 @@ func (c *KMS) ListRetirableGrantsRequest(input *ListRetirableGrantsInput) (req *
// ListRetirableGrants API operation for AWS Key Management Service.
//
-// Returns information about all grants in the AWS account and Region that have
-// the specified retiring principal. For more information about grants, see
-// Grants (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html)
-// in the AWS Key Management Service Developer Guide .
+// Returns information about all grants in the Amazon Web Services account and
+// Region that have the specified retiring principal.
//
-// You can specify any principal in your AWS account. The grants that are returned
-// include grants for CMKs in your AWS account and other AWS accounts.
+// You can specify any principal in your Amazon Web Services account. The grants
+// that are returned include grants for KMS keys in your Amazon Web Services
+// account and other Amazon Web Services accounts. You might use this operation
+// to determine which grants you may retire. To retire a grant, use the RetireGrant
+// operation.
//
-// You might use this operation to determine which grants you may retire. To
-// retire a grant, use the RetireGrant operation.
+// For detailed information about grants, including grant terminology, see Using
+// grants (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html)
+// in the Key Management Service Developer Guide . For examples of working with
+// grants in several programming languages, see Programming grants (https://docs.aws.amazon.com/kms/latest/developerguide/programming-grants.html).
//
-// Cross-account use: You must specify a principal in your AWS account. However,
-// this operation can return grants in any AWS account. You do not need kms:ListRetirableGrants
-// permission (or any other additional permission) in any AWS account other
-// than your own.
+// Cross-account use: You must specify a principal in your Amazon Web Services
+// account. However, this operation can return grants in any Amazon Web Services
+// account. You do not need kms:ListRetirableGrants permission (or any other
+// additional permission) in any Amazon Web Services account other than your
+// own.
//
// Required permissions: kms:ListRetirableGrants (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
-// (IAM policy) in your AWS account.
+// (IAM policy) in your Amazon Web Services account.
//
// Related operations:
//
@@ -5419,17 +5477,18 @@ func (c *KMS) PutKeyPolicyRequest(input *PutKeyPolicyInput) (req *request.Reques
// PutKeyPolicy API operation for AWS Key Management Service.
//
-// Attaches a key policy to the specified customer master key (CMK).
+// Attaches a key policy to the specified KMS key.
//
// For more information about key policies, see Key Policies (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html)
-// in the AWS Key Management Service Developer Guide. For help writing and formatting
+// in the Key Management Service Developer Guide. For help writing and formatting
// a JSON policy document, see the IAM JSON Policy Reference (https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html)
-// in the IAM User Guide . For examples of adding a key policy in multiple programming
-// languages, see Setting a key policy (https://docs.aws.amazon.com/kms/latest/developerguide/programming-key-policies.html#put-policy)
-// in the AWS Key Management Service Developer Guide.
+// in the Identity and Access Management User Guide . For examples of adding
+// a key policy in multiple programming languages, see Setting a key policy
+// (https://docs.aws.amazon.com/kms/latest/developerguide/programming-key-policies.html#put-policy)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:PutKeyPolicy (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -5471,15 +5530,15 @@ func (c *KMS) PutKeyPolicyRequest(input *PutKeyPolicyInput) (req *request.Reques
// * LimitExceededException
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// * InvalidStateException
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/PutKeyPolicy
func (c *KMS) PutKeyPolicy(input *PutKeyPolicyInput) (*PutKeyPolicyOutput, error) {
@@ -5547,80 +5606,80 @@ func (c *KMS) ReEncryptRequest(input *ReEncryptInput) (req *request.Request, out
// ReEncrypt API operation for AWS Key Management Service.
//
-// Decrypts ciphertext and then reencrypts it entirely within AWS KMS. You can
-// use this operation to change the customer master key (CMK) under which data
-// is encrypted, such as when you manually rotate (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-manually)
-// a CMK or change the CMK that protects a ciphertext. You can also use it to
-// reencrypt ciphertext under the same CMK, such as to change the encryption
-// context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
+// Decrypts ciphertext and then reencrypts it entirely within KMS. You can use
+// this operation to change the KMS key under which data is encrypted, such
+// as when you manually rotate (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html#rotate-keys-manually)
+// a KMS key or change the KMS key that protects a ciphertext. You can also
+// use it to reencrypt ciphertext under the same KMS key, such as to change
+// the encryption context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
// of a ciphertext.
//
// The ReEncrypt operation can decrypt ciphertext that was encrypted by using
-// an AWS KMS CMK in an AWS KMS operation, such as Encrypt or GenerateDataKey.
-// It can also decrypt ciphertext that was encrypted by using the public key
-// of an asymmetric CMK (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks)
-// outside of AWS KMS. However, it cannot decrypt ciphertext produced by other
-// libraries, such as the AWS Encryption SDK (https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/)
+// an KMS KMS key in an KMS operation, such as Encrypt or GenerateDataKey. It
+// can also decrypt ciphertext that was encrypted by using the public key of
+// an asymmetric KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks)
+// outside of KMS. However, it cannot decrypt ciphertext produced by other libraries,
+// such as the Amazon Web Services Encryption SDK (https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/)
// or Amazon S3 client-side encryption (https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html).
-// These libraries return a ciphertext format that is incompatible with AWS
-// KMS.
+// These libraries return a ciphertext format that is incompatible with KMS.
//
// When you use the ReEncrypt operation, you need to provide information for
// the decrypt operation and the subsequent encrypt operation.
//
-// * If your ciphertext was encrypted under an asymmetric CMK, you must use
-// the SourceKeyId parameter to identify the CMK that encrypted the ciphertext.
-// You must also supply the encryption algorithm that was used. This information
-// is required to decrypt the data.
+// * If your ciphertext was encrypted under an asymmetric KMS key, you must
+// use the SourceKeyId parameter to identify the KMS key that encrypted the
+// ciphertext. You must also supply the encryption algorithm that was used.
+// This information is required to decrypt the data.
//
-// * If your ciphertext was encrypted under a symmetric CMK, the SourceKeyId
-// parameter is optional. AWS KMS can get this information from metadata
-// that it adds to the symmetric ciphertext blob. This feature adds durability
+// * If your ciphertext was encrypted under a symmetric KMS key, the SourceKeyId
+// parameter is optional. KMS can get this information from metadata that
+// it adds to the symmetric ciphertext blob. This feature adds durability
// to your implementation by ensuring that authorized users can decrypt ciphertext
-// decades after it was encrypted, even if they've lost track of the CMK
-// ID. However, specifying the source CMK is always recommended as a best
-// practice. When you use the SourceKeyId parameter to specify a CMK, AWS
-// KMS uses only the CMK you specify. If the ciphertext was encrypted under
-// a different CMK, the ReEncrypt operation fails. This practice ensures
-// that you use the CMK that you intend.
+// decades after it was encrypted, even if they've lost track of the key
+// ID. However, specifying the source KMS key is always recommended as a
+// best practice. When you use the SourceKeyId parameter to specify a KMS
+// key, KMS uses only the KMS key you specify. If the ciphertext was encrypted
+// under a different KMS key, the ReEncrypt operation fails. This practice
+// ensures that you use the KMS key that you intend.
//
// * To reencrypt the data, you must use the DestinationKeyId parameter specify
-// the CMK that re-encrypts the data after it is decrypted. You can select
-// a symmetric or asymmetric CMK. If the destination CMK is an asymmetric
-// CMK, you must also provide the encryption algorithm. The algorithm that
-// you choose must be compatible with the CMK. When you use an asymmetric
-// CMK to encrypt or reencrypt data, be sure to record the CMK and encryption
-// algorithm that you choose. You will be required to provide the same CMK
-// and encryption algorithm when you decrypt the data. If the CMK and algorithm
-// do not match the values used to encrypt the data, the decrypt operation
-// fails. You are not required to supply the CMK ID and encryption algorithm
-// when you decrypt with symmetric CMKs because AWS KMS stores this information
-// in the ciphertext blob. AWS KMS cannot store metadata in ciphertext generated
-// with asymmetric keys. The standard format for asymmetric key ciphertext
-// does not include configurable fields.
-//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
-//
-// Cross-account use: Yes. The source CMK and destination CMK can be in different
-// AWS accounts. Either or both CMKs can be in a different account than the
-// caller.
+// the KMS key that re-encrypts the data after it is decrypted. You can select
+// a symmetric or asymmetric KMS key. If the destination KMS key is an asymmetric
+// KMS key, you must also provide the encryption algorithm. The algorithm
+// that you choose must be compatible with the KMS key. When you use an asymmetric
+// KMS key to encrypt or reencrypt data, be sure to record the KMS key and
+// encryption algorithm that you choose. You will be required to provide
+// the same KMS key and encryption algorithm when you decrypt the data. If
+// the KMS key and algorithm do not match the values used to encrypt the
+// data, the decrypt operation fails. You are not required to supply the
+// key ID and encryption algorithm when you decrypt with symmetric KMS keys
+// because KMS stores this information in the ciphertext blob. KMS cannot
+// store metadata in ciphertext generated with asymmetric keys. The standard
+// format for asymmetric key ciphertext does not include configurable fields.
+//
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
+//
+// Cross-account use: Yes. The source KMS key and destination KMS key can be
+// in different Amazon Web Services accounts. Either or both KMS keys can be
+// in a different account than the caller. To specify a KMS key in a different
+// account, you must use its key ARN or alias ARN.
//
// Required permissions:
//
// * kms:ReEncryptFrom (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
-// permission on the source CMK (key policy)
+// permission on the source KMS key (key policy)
//
// * kms:ReEncryptTo (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
-// permission on the destination CMK (key policy)
+// permission on the destination KMS key (key policy)
//
-// To permit reencryption from or to a CMK, include the "kms:ReEncrypt*" permission
-// in your key policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html).
+// To permit reencryption from or to a KMS key, include the "kms:ReEncrypt*"
+// permission in your key policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html).
// This permission is automatically included in the key policy when you use
-// the console to create a CMK. But you must include it manually when you create
-// a CMK programmatically or when you use the PutKeyPolicy operation to set
-// a key policy.
+// the console to create a KMS key. But you must include it manually when you
+// create a KMS key programmatically or when you use the PutKeyPolicy operation
+// to set a key policy.
//
// Related operations:
//
@@ -5645,7 +5704,7 @@ func (c *KMS) ReEncryptRequest(input *ReEncryptInput) (req *request.Request, out
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * InvalidCiphertextException
// From the Decrypt or ReEncrypt operation, the request was rejected because
@@ -5653,17 +5712,17 @@ func (c *KMS) ReEncryptRequest(input *ReEncryptInput) (req *request.Request, out
// the ciphertext, such as the encryption context, is corrupted, missing, or
// otherwise invalid.
//
-// From the ImportKeyMaterial operation, the request was rejected because AWS
-// KMS could not decrypt the encrypted (wrapped) key material.
+// From the ImportKeyMaterial operation, the request was rejected because KMS
+// could not decrypt the encrypted (wrapped) key material.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * IncorrectKeyException
-// The request was rejected because the specified CMK cannot decrypt the data.
-// The KeyId in a Decrypt request and the SourceKeyId in a ReEncrypt request
-// must identify the same CMK that was used to encrypt the ciphertext.
+// The request was rejected because the specified KMS key cannot decrypt the
+// data. The KeyId in a Decrypt request and the SourceKeyId in a ReEncrypt request
+// must identify the same KMS key that was used to encrypt the ciphertext.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -5672,17 +5731,18 @@ func (c *KMS) ReEncryptRequest(input *ReEncryptInput) (req *request.Request, out
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InvalidGrantTokenException
// The request was rejected because the specified grant token is not valid.
@@ -5695,9 +5755,9 @@ func (c *KMS) ReEncryptRequest(input *ReEncryptInput) (req *request.Request, out
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/ReEncrypt
func (c *KMS) ReEncrypt(input *ReEncryptInput) (*ReEncryptOutput, error) {
@@ -5767,33 +5827,34 @@ func (c *KMS) ReplicateKeyRequest(input *ReplicateKeyInput) (req *request.Reques
//
// Replicates a multi-Region key into the specified Region. This operation creates
// a multi-Region replica key based on a multi-Region primary key in a different
-// Region of the same AWS partition. You can create multiple replicas of a primary
-// key, but each must be in a different Region. To create a multi-Region primary
-// key, use the CreateKey operation.
-//
-// This operation supports multi-Region keys, an AWS KMS feature that lets you
-// create multiple interoperable CMKs in different AWS Regions. Because these
-// CMKs have the same key ID, key material, and other metadata, you can use
-// them to encrypt data in one AWS Region and decrypt it in a different AWS
-// Region without making a cross-Region call or exposing the plaintext data.
-// For more information about multi-Region keys, see Using multi-Region keys
-// (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
-// in the AWS Key Management Service Developer Guide.
-//
-// A replica key is a fully-functional CMK that can be used independently of
-// its primary and peer replica keys. A primary key and its replica keys share
-// properties that make them interoperable. They have the same key ID (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-id)
+// Region of the same Amazon Web Services partition. You can create multiple
+// replicas of a primary key, but each must be in a different Region. To create
+// a multi-Region primary key, use the CreateKey operation.
+//
+// This operation supports multi-Region keys, an KMS feature that lets you create
+// multiple interoperable KMS keys in different Amazon Web Services Regions.
+// Because these KMS keys have the same key ID, key material, and other metadata,
+// you can use them interchangeably to encrypt data in one Amazon Web Services
+// Region and decrypt it in a different Amazon Web Services Region without re-encrypting
+// the data or making a cross-Region call. For more information about multi-Region
+// keys, see Using multi-Region keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
+// in the Key Management Service Developer Guide.
+//
+// A replica key is a fully-functional KMS key that can be used independently
+// of its primary and peer replica keys. A primary key and its replica keys
+// share properties that make them interoperable. They have the same key ID
+// (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-id)
// and key material. They also have the same key spec (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-spec),
// key usage (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-usage),
// key material origin (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-origin),
// and automatic key rotation status (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html).
-// AWS KMS automatically synchronizes these shared properties among related
-// multi-Region keys. All other properties of a replica key can differ, including
-// its key policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html),
+// KMS automatically synchronizes these shared properties among related multi-Region
+// keys. All other properties of a replica key can differ, including its key
+// policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html),
// tags (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html),
// aliases (https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html),
// and key state (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html).
-// AWS KMS pricing and quotas for CMKs apply to each primary key and replica
+// KMS pricing and quotas for KMS keys apply to each primary key and replica
// key.
//
// When this operation completes, the new replica key has a transient key state
@@ -5803,31 +5864,31 @@ func (c *KMS) ReplicateKeyRequest(input *ReplicateKeyInput) (req *request.Reques
// it in cryptographic operations. If you are creating and using the replica
// key programmatically, retry on KMSInvalidStateException or call DescribeKey
// to check its KeyState value before using it. For details about the Creating
-// key state, see Key state: Effect on your CMK (kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// key state, see Key state: Effect on your KMS key (kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// The AWS CloudTrail log of a ReplicateKey operation records a ReplicateKey
-// operation in the primary key's Region and a CreateKey operation in the replica
-// key's Region.
+// The CloudTrail log of a ReplicateKey operation records a ReplicateKey operation
+// in the primary key's Region and a CreateKey operation in the replica key's
+// Region.
//
// If you replicate a multi-Region primary key with imported key material, the
// replica key is created with no key material. You must import the same key
// material that you imported into the primary key. For details, see Importing
// key material into multi-Region keys (kms/latest/developerguide/multi-region-keys-import.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// To convert a replica key to a primary key, use the UpdatePrimaryRegion operation.
//
// ReplicateKey uses different default values for the KeyPolicy and Tags parameters
-// than those used in the AWS KMS console. For details, see the parameter descriptions.
+// than those used in the KMS console. For details, see the parameter descriptions.
//
-// Cross-account use: No. You cannot use this operation to create a CMK in a
-// different AWS account.
+// Cross-account use: No. You cannot use this operation to create a replica
+// key in a different Amazon Web Services account.
//
// Required permissions:
//
-// * kms:ReplicateKey on the primary CMK (in the primary CMK's Region). Include
-// this permission in the primary CMK's key policy.
+// * kms:ReplicateKey on the primary key (in the primary key's Region). Include
+// this permission in the primary key's key policy.
//
// * kms:CreateKey in an IAM policy in the replica Region.
//
@@ -5853,7 +5914,7 @@ func (c *KMS) ReplicateKeyRequest(input *ReplicateKeyInput) (req *request.Reques
// exists.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * InvalidArnException
// The request was rejected because a specified ARN, or an ARN in a key policy,
@@ -5863,9 +5924,9 @@ func (c *KMS) ReplicateKeyRequest(input *ReplicateKeyInput) (req *request.Reques
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * InternalException
// The request was rejected because an internal exception occurred. The request
@@ -5874,7 +5935,7 @@ func (c *KMS) ReplicateKeyRequest(input *ReplicateKeyInput) (req *request.Reques
// * LimitExceededException
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// * MalformedPolicyDocumentException
// The request was rejected because the specified policy is not syntactically
@@ -5960,27 +6021,27 @@ func (c *KMS) RetireGrantRequest(input *RetireGrantInput) (req *request.Request,
//
// Deletes a grant. Typically, you retire a grant when you no longer need its
// permissions. To identify the grant to retire, use a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token),
-// or both the grant ID and a key identifier (key ID or key ARN) of the customer
-// master key (CMK). The CreateGrant operation returns both values.
+// or both the grant ID and a key identifier (key ID or key ARN) of the KMS
+// key. The CreateGrant operation returns both values.
//
// This operation can be called by the retiring principal for a grant, by the
// grantee principal if the grant allows the RetireGrant operation, and by the
-// AWS account (root user) in which the grant is created. It can also be called
-// by principals to whom permission for retiring a grant is delegated. For details,
-// see Retiring and revoking grants (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#grant-delete)
-// in the AWS Key Management Service Developer Guide.
+// Amazon Web Services account (root user) in which the grant is created. It
+// can also be called by principals to whom permission for retiring a grant
+// is delegated. For details, see Retiring and revoking grants (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#grant-delete)
+// in the Key Management Service Developer Guide.
//
// For detailed information about grants, including grant terminology, see Using
// grants (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html)
-// in the AWS Key Management Service Developer Guide . For examples of working
-// with grants in several programming languages, see Programming grants (https://docs.aws.amazon.com/kms/latest/developerguide/programming-grants.html).
+// in the Key Management Service Developer Guide . For examples of working with
+// grants in several programming languages, see Programming grants (https://docs.aws.amazon.com/kms/latest/developerguide/programming-grants.html).
//
-// Cross-account use: Yes. You can retire a grant on a CMK in a different AWS
-// account.
+// Cross-account use: Yes. You can retire a grant on a KMS key in a different
+// Amazon Web Services account.
//
// Required permissions::Permission to retire a grant is determined primarily
// by the grant. For details, see Retiring and revoking grants (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#grant-delete)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// Related operations:
//
@@ -6026,9 +6087,9 @@ func (c *KMS) RetireGrantRequest(input *RetireGrantInput) (req *request.Request,
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/RetireGrant
func (c *KMS) RetireGrant(input *RetireGrantInput) (*RetireGrantOutput, error) {
@@ -6100,16 +6161,22 @@ func (c *KMS) RevokeGrantRequest(input *RevokeGrantInput) (req *request.Request,
// Deletes the specified grant. You revoke a grant to terminate the permissions
// that the grant allows. For more information, see Retiring and revoking grants
// (https://docs.aws.amazon.com/kms/latest/developerguide/managing-grants.html#grant-delete)
-// in the AWS Key Management Service Developer Guide .
+// in the Key Management Service Developer Guide .
//
// When you create, retire, or revoke a grant, there might be a brief delay,
-// usually less than five minutes, until the grant is available throughout AWS
-// KMS. This state is known as eventual consistency. For details, see Eventual
-// consistency (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#terms-eventual-consistency)
-// in the AWS Key Management Service Developer Guide .
+// usually less than five minutes, until the grant is available throughout KMS.
+// This state is known as eventual consistency. For details, see Eventual consistency
+// (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#terms-eventual-consistency)
+// in the Key Management Service Developer Guide .
//
-// Cross-account use: Yes. To perform this operation on a CMK in a different
-// AWS account, specify the key ARN in the value of the KeyId parameter.
+// For detailed information about grants, including grant terminology, see Using
+// grants (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html)
+// in the Key Management Service Developer Guide . For examples of working with
+// grants in several programming languages, see Programming grants (https://docs.aws.amazon.com/kms/latest/developerguide/programming-grants.html).
+//
+// Cross-account use: Yes. To perform this operation on a KMS key in a different
+// Amazon Web Services account, specify the key ARN in the value of the KeyId
+// parameter.
//
// Required permissions: kms:RevokeGrant (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy).
@@ -6155,9 +6222,9 @@ func (c *KMS) RevokeGrantRequest(input *RevokeGrantInput) (req *request.Request,
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/RevokeGrant
func (c *KMS) RevokeGrant(input *RevokeGrantInput) (*RevokeGrantOutput, error) {
@@ -6225,49 +6292,49 @@ func (c *KMS) ScheduleKeyDeletionRequest(input *ScheduleKeyDeletionInput) (req *
// ScheduleKeyDeletion API operation for AWS Key Management Service.
//
-// Schedules the deletion of a customer master key (CMK). By default, AWS KMS
-// applies a waiting period of 30 days, but you can specify a waiting period
-// of 7-30 days. When this operation is successful, the key state of the CMK
-// changes to PendingDeletion and the key can't be used in any cryptographic
-// operations. It remains in this state for the duration of the waiting period.
-// Before the waiting period ends, you can use CancelKeyDeletion to cancel the
-// deletion of the CMK. After the waiting period ends, AWS KMS deletes the CMK,
-// its key material, and all AWS KMS data associated with it, including all
-// aliases that refer to it.
-//
-// Deleting a CMK is a destructive and potentially dangerous operation. When
-// a CMK is deleted, all data that was encrypted under the CMK is unrecoverable.
-// (The only exception is a multi-Region replica key.) To prevent the use of
-// a CMK without deleting it, use DisableKey.
-//
-// If you schedule deletion of a CMK from a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html),
-// when the waiting period expires, ScheduleKeyDeletion deletes the CMK from
-// AWS KMS. Then AWS KMS makes a best effort to delete the key material from
-// the associated AWS CloudHSM cluster. However, you might need to manually
-// delete the orphaned key material (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-orphaned-key)
+// Schedules the deletion of a KMS key. By default, KMS applies a waiting period
+// of 30 days, but you can specify a waiting period of 7-30 days. When this
+// operation is successful, the key state of the KMS key changes to PendingDeletion
+// and the key can't be used in any cryptographic operations. It remains in
+// this state for the duration of the waiting period. Before the waiting period
+// ends, you can use CancelKeyDeletion to cancel the deletion of the KMS key.
+// After the waiting period ends, KMS deletes the KMS key, its key material,
+// and all KMS data associated with it, including all aliases that refer to
+// it.
+//
+// Deleting a KMS key is a destructive and potentially dangerous operation.
+// When a KMS key is deleted, all data that was encrypted under the KMS key
+// is unrecoverable. (The only exception is a multi-Region replica key.) To
+// prevent the use of a KMS key without deleting it, use DisableKey.
+//
+// If you schedule deletion of a KMS key from a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html),
+// when the waiting period expires, ScheduleKeyDeletion deletes the KMS key
+// from KMS. Then KMS makes a best effort to delete the key material from the
+// associated CloudHSM cluster. However, you might need to manually delete the
+// orphaned key material (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-orphaned-key)
// from the cluster and its backups.
//
// You can schedule the deletion of a multi-Region primary key and its replica
-// keys at any time. However, AWS KMS will not delete a multi-Region primary
-// key with existing replica keys. If you schedule the deletion of a primary
-// key with replicas, its key state changes to PendingReplicaDeletion and it
-// cannot be replicated or used in cryptographic operations. This status can
-// continue indefinitely. When the last of its replicas keys is deleted (not
-// just scheduled), the key state of the primary key changes to PendingDeletion
-// and its waiting period (PendingWindowInDays) begins. For details, see Deleting
-// multi-Region keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-delete.html)
-// in the AWS Key Management Service Developer Guide.
-//
-// For more information about scheduling a CMK for deletion, see Deleting Customer
-// Master Keys (https://docs.aws.amazon.com/kms/latest/developerguide/deleting-keys.html)
-// in the AWS Key Management Service Developer Guide.
-//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
-//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// keys at any time. However, KMS will not delete a multi-Region primary key
+// with existing replica keys. If you schedule the deletion of a primary key
+// with replicas, its key state changes to PendingReplicaDeletion and it cannot
+// be replicated or used in cryptographic operations. This status can continue
+// indefinitely. When the last of its replicas keys is deleted (not just scheduled),
+// the key state of the primary key changes to PendingDeletion and its waiting
+// period (PendingWindowInDays) begins. For details, see Deleting multi-Region
+// keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-delete.html)
+// in the Key Management Service Developer Guide.
+//
+// For more information about scheduling a KMS key for deletion, see Deleting
+// KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/deleting-keys.html)
+// in the Key Management Service Developer Guide.
+//
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
+//
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:ScheduleKeyDeletion (key policy)
//
@@ -6305,9 +6372,9 @@ func (c *KMS) ScheduleKeyDeletionRequest(input *ScheduleKeyDeletionInput) (req *
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/ScheduleKeyDeletion
func (c *KMS) ScheduleKeyDeletion(input *ScheduleKeyDeletionInput) (*ScheduleKeyDeletionOutput, error) {
@@ -6377,23 +6444,24 @@ func (c *KMS) SignRequest(input *SignInput) (req *request.Request, output *SignO
//
// Creates a digital signature (https://en.wikipedia.org/wiki/Digital_signature)
// for a message or message digest by using the private key in an asymmetric
-// CMK. To verify the signature, use the Verify operation, or use the public
-// key in the same asymmetric CMK outside of AWS KMS. For information about
-// symmetric and asymmetric CMKs, see Using Symmetric and Asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
-// in the AWS Key Management Service Developer Guide.
+// KMS key. To verify the signature, use the Verify operation, or use the public
+// key in the same asymmetric KMS key outside of KMS. For information about
+// symmetric and asymmetric KMS keys, see Using Symmetric and Asymmetric KMS
+// keys (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
+// in the Key Management Service Developer Guide.
//
// Digital signatures are generated and verified by using asymmetric key pair,
-// such as an RSA or ECC pair that is represented by an asymmetric customer
-// master key (CMK). The key owner (or an authorized user) uses their private
-// key to sign a message. Anyone with the public key can verify that the message
-// was signed with that particular private key and that the message hasn't changed
-// since it was signed.
+// such as an RSA or ECC pair that is represented by an asymmetric KMS key.
+// The key owner (or an authorized user) uses their private key to sign a message.
+// Anyone with the public key can verify that the message was signed with that
+// particular private key and that the message hasn't changed since it was signed.
//
// To use the Sign operation, provide the following information:
//
-// * Use the KeyId parameter to identify an asymmetric CMK with a KeyUsage
-// value of SIGN_VERIFY. To get the KeyUsage value of a CMK, use the DescribeKey
-// operation. The caller must have kms:Sign permission on the CMK.
+// * Use the KeyId parameter to identify an asymmetric KMS key with a KeyUsage
+// value of SIGN_VERIFY. To get the KeyUsage value of a KMS key, use the
+// DescribeKey operation. The caller must have kms:Sign permission on the
+// KMS key.
//
// * Use the Message parameter to specify the message or message digest to
// sign. You can submit messages of up to 4096 bytes. To sign a larger message,
@@ -6401,21 +6469,22 @@ func (c *KMS) SignRequest(input *SignInput) (req *request.Request, output *SignO
// in the Message parameter. To indicate whether the message is a full message
// or a digest, use the MessageType parameter.
//
-// * Choose a signing algorithm that is compatible with the CMK.
+// * Choose a signing algorithm that is compatible with the KMS key.
//
-// When signing a message, be sure to record the CMK and the signing algorithm.
+// When signing a message, be sure to record the KMS key and the signing algorithm.
// This information is required to verify the signature.
//
// To verify the signature that this operation generates, use the Verify operation.
// Or use the GetPublicKey operation to download the public key and then use
-// the public key to verify the signature outside of AWS KMS.
+// the public key to verify the signature outside of KMS.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:Sign (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -6435,11 +6504,11 @@ func (c *KMS) SignRequest(input *SignInput) (req *request.Request, output *SignO
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -6448,17 +6517,18 @@ func (c *KMS) SignRequest(input *SignInput) (req *request.Request, output *SignO
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InvalidGrantTokenException
// The request was rejected because the specified grant token is not valid.
@@ -6471,9 +6541,9 @@ func (c *KMS) SignRequest(input *SignInput) (req *request.Request, output *SignO
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/Sign
func (c *KMS) Sign(input *SignInput) (*SignOutput, error) {
@@ -6542,37 +6612,37 @@ func (c *KMS) TagResourceRequest(input *TagResourceInput) (req *request.Request,
// TagResource API operation for AWS Key Management Service.
//
-// Adds or edits tags on a customer managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk).
+// Adds or edits tags on a customer managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk).
//
-// Tagging or untagging a CMK can allow or deny permission to the CMK. For details,
-// see Using ABAC in AWS KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
-// in the AWS Key Management Service Developer Guide.
+// Tagging or untagging a KMS key can allow or deny permission to the KMS key.
+// For details, see Using ABAC in KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
+// in the Key Management Service Developer Guide.
//
// Each tag consists of a tag key and a tag value, both of which are case-sensitive
// strings. The tag value can be an empty (null) string. To add a tag, specify
// a new tag key and a tag value. To edit a tag, specify an existing tag key
// and a new tag value.
//
-// You can use this operation to tag a customer managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk),
-// but you cannot tag an AWS managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk),
-// an AWS owned CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-owned-cmk),
+// You can use this operation to tag a customer managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk),
+// but you cannot tag an Amazon Web Services managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk),
+// an Amazon Web Services owned key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-owned-cmk),
// a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#keystore-concept),
// or an alias (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#alias-concept).
//
-// You can also add tags to a CMK while creating it (CreateKey) or replicating
+// You can also add tags to a KMS key while creating it (CreateKey) or replicating
// it (ReplicateKey).
//
-// For information about using tags in AWS KMS, see Tagging keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
+// For information about using tags in KMS, see Tagging keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
// For general information about tags, including the format and syntax, see
-// Tagging AWS resources (https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html)
+// Tagging Amazon Web Services resources (https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html)
// in the Amazon Web Services General Reference.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:TagResource (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -6611,14 +6681,14 @@ func (c *KMS) TagResourceRequest(input *TagResourceInput) (req *request.Request,
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * LimitExceededException
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// * TagException
// The request was rejected because one or more tags are not valid.
@@ -6690,29 +6760,29 @@ func (c *KMS) UntagResourceRequest(input *UntagResourceInput) (req *request.Requ
// UntagResource API operation for AWS Key Management Service.
//
-// Deletes tags from a customer managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk).
-// To delete a tag, specify the tag key and the CMK.
+// Deletes tags from a customer managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk).
+// To delete a tag, specify the tag key and the KMS key.
//
-// Tagging or untagging a CMK can allow or deny permission to the CMK. For details,
-// see Using ABAC in AWS KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
-// in the AWS Key Management Service Developer Guide.
+// Tagging or untagging a KMS key can allow or deny permission to the KMS key.
+// For details, see Using ABAC in KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
+// in the Key Management Service Developer Guide.
//
// When it succeeds, the UntagResource operation doesn't return any output.
-// Also, if the specified tag key isn't found on the CMK, it doesn't throw an
-// exception or return a response. To confirm that the operation worked, use
-// the ListResourceTags operation.
+// Also, if the specified tag key isn't found on the KMS key, it doesn't throw
+// an exception or return a response. To confirm that the operation worked,
+// use the ListResourceTags operation.
//
-// For information about using tags in AWS KMS, see Tagging keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
+// For information about using tags in KMS, see Tagging keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
// For general information about tags, including the format and syntax, see
-// Tagging AWS resources (https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html)
+// Tagging Amazon Web Services resources (https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html)
// in the Amazon Web Services General Reference.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:UntagResource (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -6751,9 +6821,9 @@ func (c *KMS) UntagResourceRequest(input *UntagResourceInput) (req *request.Requ
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * TagException
// The request was rejected because one or more tags are not valid.
@@ -6825,35 +6895,35 @@ func (c *KMS) UpdateAliasRequest(input *UpdateAliasInput) (req *request.Request,
// UpdateAlias API operation for AWS Key Management Service.
//
-// Associates an existing AWS KMS alias with a different customer master key
-// (CMK). Each alias is associated with only one CMK at a time, although a CMK
-// can have multiple aliases. The alias and the CMK must be in the same AWS
+// Associates an existing KMS alias with a different KMS key. Each alias is
+// associated with only one KMS key at a time, although a KMS key can have multiple
+// aliases. The alias and the KMS key must be in the same Amazon Web Services
// account and Region.
//
// Adding, deleting, or updating an alias can allow or deny permission to the
-// CMK. For details, see Using ABAC in AWS KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
-// in the AWS Key Management Service Developer Guide.
+// KMS key. For details, see Using ABAC in KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
+// in the Key Management Service Developer Guide.
//
-// The current and new CMK must be the same type (both symmetric or both asymmetric),
-// and they must have the same key usage (ENCRYPT_DECRYPT or SIGN_VERIFY). This
-// restriction prevents errors in code that uses aliases. If you must assign
-// an alias to a different type of CMK, use DeleteAlias to delete the old alias
-// and CreateAlias to create a new alias.
+// The current and new KMS key must be the same type (both symmetric or both
+// asymmetric), and they must have the same key usage (ENCRYPT_DECRYPT or SIGN_VERIFY).
+// This restriction prevents errors in code that uses aliases. If you must assign
+// an alias to a different type of KMS key, use DeleteAlias to delete the old
+// alias and CreateAlias to create a new alias.
//
// You cannot use UpdateAlias to change an alias name. To change an alias name,
// use DeleteAlias to delete the old alias and CreateAlias to create a new alias.
//
-// Because an alias is not a property of a CMK, you can create, update, and
-// delete the aliases of a CMK without affecting the CMK. Also, aliases do not
-// appear in the response from the DescribeKey operation. To get the aliases
-// of all CMKs in the account, use the ListAliases operation.
+// Because an alias is not a property of a KMS key, you can create, update,
+// and delete the aliases of a KMS key without affecting the KMS key. Also,
+// aliases do not appear in the response from the DescribeKey operation. To
+// get the aliases of all KMS keys in the account, use the ListAliases operation.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions
//
@@ -6861,13 +6931,13 @@ func (c *KMS) UpdateAliasRequest(input *UpdateAliasInput) (req *request.Request,
// on the alias (IAM policy).
//
// * kms:UpdateAlias (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
-// on the current CMK (key policy).
+// on the current KMS key (key policy).
//
// * kms:UpdateAlias (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
-// on the new CMK (key policy).
+// on the new KMS key (key policy).
//
// For details, see Controlling access to aliases (https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html#alias-access)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// Related operations:
//
@@ -6900,15 +6970,15 @@ func (c *KMS) UpdateAliasRequest(input *UpdateAliasInput) (req *request.Request,
// * LimitExceededException
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
//
// * InvalidStateException
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/UpdateAlias
func (c *KMS) UpdateAlias(input *UpdateAliasInput) (*UpdateAliasOutput, error) {
@@ -6992,28 +7062,28 @@ func (c *KMS) UpdateCustomKeyStoreRequest(input *UpdateCustomKeyStoreInput) (req
// * Use the NewCustomKeyStoreName parameter to change the friendly name
// of the custom key store to the value that you specify.
//
-// * Use the KeyStorePassword parameter tell AWS KMS the current password
-// of the kmsuser crypto user (CU) (https://docs.aws.amazon.com/kms/latest/developerguide/key-store-concepts.html#concept-kmsuser)
-// in the associated AWS CloudHSM cluster. You can use this parameter to
-// fix connection failures (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-password)
-// that occur when AWS KMS cannot log into the associated cluster because
-// the kmsuser password has changed. This value does not change the password
-// in the AWS CloudHSM cluster.
+// * Use the KeyStorePassword parameter tell KMS the current password of
+// the kmsuser crypto user (CU) (https://docs.aws.amazon.com/kms/latest/developerguide/key-store-concepts.html#concept-kmsuser)
+// in the associated CloudHSM cluster. You can use this parameter to fix
+// connection failures (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-password)
+// that occur when KMS cannot log into the associated cluster because the
+// kmsuser password has changed. This value does not change the password
+// in the CloudHSM cluster.
//
// * Use the CloudHsmClusterId parameter to associate the custom key store
-// with a different, but related, AWS CloudHSM cluster. You can use this
-// parameter to repair a custom key store if its AWS CloudHSM cluster becomes
-// corrupted or is deleted, or when you need to create or restore a cluster
-// from a backup.
+// with a different, but related, CloudHSM cluster. You can use this parameter
+// to repair a custom key store if its CloudHSM cluster becomes corrupted
+// or is deleted, or when you need to create or restore a cluster from a
+// backup.
//
// If the operation succeeds, it returns a JSON object with no properties.
//
// This operation is part of the Custom Key Store feature (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
-// feature in AWS KMS, which combines the convenience and extensive integration
-// of AWS KMS with the isolation and control of a single-tenant key store.
+// feature in KMS, which combines the convenience and extensive integration
+// of KMS with the isolation and control of a single-tenant key store.
//
// Cross-account use: No. You cannot perform this operation on a custom key
-// store in a different AWS account.
+// store in a different Amazon Web Services account.
//
// Required permissions: kms:UpdateCustomKeyStore (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (IAM policy)
@@ -7039,7 +7109,7 @@ func (c *KMS) UpdateCustomKeyStoreRequest(input *UpdateCustomKeyStoreInput) (req
//
// Returned Error Types:
// * CustomKeyStoreNotFoundException
-// The request was rejected because AWS KMS cannot find a custom key store with
+// The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
//
// * CustomKeyStoreNameInUseException
@@ -7048,14 +7118,13 @@ func (c *KMS) UpdateCustomKeyStoreRequest(input *UpdateCustomKeyStoreInput) (req
// key store name that is unique in the account.
//
// * CloudHsmClusterNotFoundException
-// The request was rejected because AWS KMS cannot find the AWS CloudHSM cluster
-// with the specified cluster ID. Retry the request with a different cluster
-// ID.
+// The request was rejected because KMS cannot find the CloudHSM cluster with
+// the specified cluster ID. Retry the request with a different cluster ID.
//
// * CloudHsmClusterNotRelatedException
-// The request was rejected because the specified AWS CloudHSM cluster has a
-// different cluster certificate than the original cluster. You cannot use the
-// operation to specify an unrelated cluster.
+// The request was rejected because the specified CloudHSM cluster has a different
+// cluster certificate than the original cluster. You cannot use the operation
+// to specify an unrelated cluster.
//
// Specify a cluster that shares a backup history with the original cluster.
// This includes clusters that were created from a backup of the current cluster,
@@ -7090,15 +7159,15 @@ func (c *KMS) UpdateCustomKeyStoreRequest(input *UpdateCustomKeyStoreInput) (req
// can be retried.
//
// * CloudHsmClusterNotActiveException
-// The request was rejected because the AWS CloudHSM cluster that is associated
+// The request was rejected because the CloudHSM cluster that is associated
// with the custom key store is not active. Initialize and activate the cluster
// and try the command again. For detailed instructions, see Getting Started
// (https://docs.aws.amazon.com/cloudhsm/latest/userguide/getting-started.html)
-// in the AWS CloudHSM User Guide.
+// in the CloudHSM User Guide.
//
// * CloudHsmClusterInvalidConfigurationException
-// The request was rejected because the associated AWS CloudHSM cluster did
-// not meet the configuration requirements for a custom key store.
+// The request was rejected because the associated CloudHSM cluster did not
+// meet the configuration requirements for a custom key store.
//
// * The cluster must be configured with private subnets in at least two
// different Availability Zones in the Region.
@@ -7113,20 +7182,19 @@ func (c *KMS) UpdateCustomKeyStoreRequest(input *UpdateCustomKeyStoreInput) (req
// operation.
//
// * The cluster must contain at least as many HSMs as the operation requires.
-// To add HSMs, use the AWS CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
+// To add HSMs, use the CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
// operation. For the CreateCustomKeyStore, UpdateCustomKeyStore, and CreateKey
-// operations, the AWS CloudHSM cluster must have at least two active HSMs,
-// each in a different Availability Zone. For the ConnectCustomKeyStore operation,
-// the AWS CloudHSM must contain at least one active HSM.
-//
-// For information about the requirements for an AWS CloudHSM cluster that is
-// associated with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
-// in the AWS Key Management Service Developer Guide. For information about
-// creating a private subnet for an AWS CloudHSM cluster, see Create a Private
-// Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
-// in the AWS CloudHSM User Guide. For information about cluster security groups,
+// operations, the CloudHSM cluster must have at least two active HSMs, each
+// in a different Availability Zone. For the ConnectCustomKeyStore operation,
+// the CloudHSM must contain at least one active HSM.
+//
+// For information about the requirements for an CloudHSM cluster that is associated
+// with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
+// in the Key Management Service Developer Guide. For information about creating
+// a private subnet for an CloudHSM cluster, see Create a Private Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
+// in the CloudHSM User Guide. For information about cluster security groups,
// see Configure a Default Security Group (https://docs.aws.amazon.com/cloudhsm/latest/userguide/configure-sg.html)
-// in the AWS CloudHSM User Guide .
+// in the CloudHSM User Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/UpdateCustomKeyStore
func (c *KMS) UpdateCustomKeyStore(input *UpdateCustomKeyStoreInput) (*UpdateCustomKeyStoreOutput, error) {
@@ -7195,15 +7263,15 @@ func (c *KMS) UpdateKeyDescriptionRequest(input *UpdateKeyDescriptionInput) (req
// UpdateKeyDescription API operation for AWS Key Management Service.
//
-// Updates the description of a customer master key (CMK). To see the description
-// of a CMK, use DescribeKey.
+// Updates the description of a KMS key. To see the description of a KMS key,
+// use DescribeKey.
//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
-// Cross-account use: No. You cannot perform this operation on a CMK in a different
-// AWS account.
+// Cross-account use: No. You cannot perform this operation on a KMS key in
+// a different Amazon Web Services account.
//
// Required permissions: kms:UpdateKeyDescription (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -7242,9 +7310,9 @@ func (c *KMS) UpdateKeyDescriptionRequest(input *UpdateKeyDescriptionInput) (req
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/UpdateKeyDescription
func (c *KMS) UpdateKeyDescription(input *UpdateKeyDescriptionInput) (*UpdateKeyDescriptionOutput, error) {
@@ -7320,16 +7388,17 @@ func (c *KMS) UpdatePrimaryRegionRequest(input *UpdatePrimaryRegionInput) (req *
// you have a primary key in us-east-1 and a replica key in eu-west-2. If you
// run UpdatePrimaryRegion with a PrimaryRegion value of eu-west-2, the primary
// key is now the key in eu-west-2, and the key in us-east-1 becomes a replica
-// key. For details, see
-//
-// This operation supports multi-Region keys, an AWS KMS feature that lets you
-// create multiple interoperable CMKs in different AWS Regions. Because these
-// CMKs have the same key ID, key material, and other metadata, you can use
-// them to encrypt data in one AWS Region and decrypt it in a different AWS
-// Region without making a cross-Region call or exposing the plaintext data.
-// For more information about multi-Region keys, see Using multi-Region keys
-// (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
-// in the AWS Key Management Service Developer Guide.
+// key. For details, see Updating the primary Region (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-manage.html#multi-region-update)
+// in the Key Management Service Developer Guide.
+//
+// This operation supports multi-Region keys, an KMS feature that lets you create
+// multiple interoperable KMS keys in different Amazon Web Services Regions.
+// Because these KMS keys have the same key ID, key material, and other metadata,
+// you can use them interchangeably to encrypt data in one Amazon Web Services
+// Region and decrypt it in a different Amazon Web Services Region without re-encrypting
+// the data or making a cross-Region call. For more information about multi-Region
+// keys, see Using multi-Region keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
+// in the Key Management Service Developer Guide.
//
// The primary key of a multi-Region key is the source for properties that are
// always shared by primary and replica keys, including the key material, key
@@ -7340,13 +7409,13 @@ func (c *KMS) UpdatePrimaryRegionRequest(input *UpdatePrimaryRegionInput) (req *
// and automatic key rotation (https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html).
// It's the only key that can be replicated. You cannot delete the primary key
// (https://docs.aws.amazon.com/kms/latest/APIReference/API_ScheduleKeyDeletion.html)
-// until all replicas are deleted.
+// until all replica keys are deleted.
//
// The key ID and primary Region that you specify uniquely identify the replica
// key that will become the primary key. The primary Region must already have
-// a replica key. This operation does not create a CMK in the specified Region.
-// To find the replica keys, use the DescribeKey operation on the primary key
-// or any replica key. To create a replica key, use the ReplicateKey operation.
+// a replica key. This operation does not create a KMS key in the specified
+// Region. To find the replica keys, use the DescribeKey operation on the primary
+// key or any replica key. To create a replica key, use the ReplicateKey operation.
//
// You can run this operation while using the affected multi-Region keys in
// cryptographic operations. This operation should not delay, interrupt, or
@@ -7360,21 +7429,22 @@ func (c *KMS) UpdatePrimaryRegionRequest(input *UpdatePrimaryRegionInput) (req *
// state is Updating, you can use the keys in cryptographic operations, but
// you cannot replicate the new primary key or perform certain management operations,
// such as enabling or disabling these keys. For details about the Updating
-// key state, see Key state: Effect on your CMK (kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
+// key state, see Key state: Effect on your KMS key (kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
//
// This operation does not return any output. To verify that primary key is
// changed, use the DescribeKey operation.
//
-// Cross-account use: No. You cannot use this operation in a different AWS account.
+// Cross-account use: No. You cannot use this operation in a different Amazon
+// Web Services account.
//
// Required permissions:
//
-// * kms:UpdatePrimaryRegion on the current primary CMK (in the primary CMK's
-// Region). Include this permission primary CMK's key policy.
+// * kms:UpdatePrimaryRegion on the current primary key (in the primary key's
+// Region). Include this permission primary key's key policy.
//
-// * kms:UpdatePrimaryRegion on the current replica CMK (in the replica CMK's
-// Region). Include this permission in the replica CMK's key policy.
+// * kms:UpdatePrimaryRegion on the current replica key (in the replica key's
+// Region). Include this permission in the replica key's key policy.
//
// Related operations
//
@@ -7391,7 +7461,7 @@ func (c *KMS) UpdatePrimaryRegionRequest(input *UpdatePrimaryRegionInput) (req *
//
// Returned Error Types:
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * InvalidArnException
// The request was rejected because a specified ARN, or an ARN in a key policy,
@@ -7401,9 +7471,9 @@ func (c *KMS) UpdatePrimaryRegionRequest(input *UpdatePrimaryRegionInput) (req *
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * InternalException
// The request was rejected because an internal exception occurred. The request
@@ -7486,36 +7556,37 @@ func (c *KMS) VerifyRequest(input *VerifyInput) (req *request.Request, output *V
// Verifies a digital signature that was generated by the Sign operation.
//
// Verification confirms that an authorized user signed the message with the
-// specified CMK and signing algorithm, and the message hasn't changed since
+// specified KMS key and signing algorithm, and the message hasn't changed since
// it was signed. If the signature is verified, the value of the SignatureValid
// field in the response is True. If the signature verification fails, the Verify
// operation fails with an KMSInvalidSignatureException exception.
//
// A digital signature is generated by using the private key in an asymmetric
-// CMK. The signature is verified by using the public key in the same asymmetric
-// CMK. For information about symmetric and asymmetric CMKs, see Using Symmetric
-// and Asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
-// in the AWS Key Management Service Developer Guide.
+// KMS key. The signature is verified by using the public key in the same asymmetric
+// KMS key. For information about symmetric and asymmetric KMS keys, see Using
+// Symmetric and Asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html)
+// in the Key Management Service Developer Guide.
//
// To verify a digital signature, you can use the Verify operation. Specify
-// the same asymmetric CMK, message, and signing algorithm that were used to
-// produce the signature.
+// the same asymmetric KMS key, message, and signing algorithm that were used
+// to produce the signature.
//
// You can also verify the digital signature by using the public key of the
-// CMK outside of AWS KMS. Use the GetPublicKey operation to download the public
-// key in the asymmetric CMK and then use the public key to verify the signature
-// outside of AWS KMS. The advantage of using the Verify operation is that it
-// is performed within AWS KMS. As a result, it's easy to call, the operation
-// is performed within the FIPS boundary, it is logged in AWS CloudTrail, and
-// you can use key policy and IAM policy to determine who is authorized to use
-// the CMK to verify signatures.
-//
-// The CMK that you use for this operation must be in a compatible key state.
-// For details, see Key state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide.
-//
-// Cross-account use: Yes. To perform this operation with a CMK in a different
-// AWS account, specify the key ARN or alias ARN in the value of the KeyId parameter.
+// KMS key outside of KMS. Use the GetPublicKey operation to download the public
+// key in the asymmetric KMS key and then use the public key to verify the signature
+// outside of KMS. The advantage of using the Verify operation is that it is
+// performed within KMS. As a result, it's easy to call, the operation is performed
+// within the FIPS boundary, it is logged in CloudTrail, and you can use key
+// policy and IAM policy to determine who is authorized to use the KMS key to
+// verify signatures.
+//
+// The KMS key that you use for this operation must be in a compatible key state.
+// For details, see Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide.
+//
+// Cross-account use: Yes. To perform this operation with a KMS key in a different
+// Amazon Web Services account, specify the key ARN or alias ARN in the value
+// of the KeyId parameter.
//
// Required permissions: kms:Verify (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// (key policy)
@@ -7535,11 +7606,11 @@ func (c *KMS) VerifyRequest(input *VerifyInput) (req *request.Request, output *V
// be found.
//
// * DisabledException
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
//
// * KeyUnavailableException
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
//
// * DependencyTimeoutException
// The system timed out while trying to fulfill the request. The request can
@@ -7548,17 +7619,18 @@ func (c *KMS) VerifyRequest(input *VerifyInput) (req *request.Request, output *V
// * InvalidKeyUsageException
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
//
// * InvalidGrantTokenException
// The request was rejected because the specified grant token is not valid.
@@ -7571,14 +7643,14 @@ func (c *KMS) VerifyRequest(input *VerifyInput) (req *request.Request, output *V
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
//
// * KMSInvalidSignatureException
// The request was rejected because the signature verification failed. Signature
// verification fails when it cannot confirm that signature was produced by
-// signing the specified message with the specified CMK and signing algorithm.
+// signing the specified message with the specified KMS key and signing algorithm.
//
// See also, https://docs.aws.amazon.com/goto/WebAPI/kms-2014-11-01/Verify
func (c *KMS) Verify(input *VerifyInput) (*VerifyOutput, error) {
@@ -7616,11 +7688,12 @@ type AliasListEntry struct {
// Region. Formatted as Unix time.
CreationDate *time.Time `type:"timestamp"`
- // Date and time that the alias was most recently associated with a CMK in the
- // account and Region. Formatted as Unix time.
+ // Date and time that the alias was most recently associated with a KMS key
+ // in the account and Region. Formatted as Unix time.
LastUpdatedDate *time.Time `type:"timestamp"`
- // String that contains the key identifier of the CMK associated with the alias.
+ // String that contains the key identifier of the KMS key associated with the
+ // alias.
TargetKeyId *string `min:"1" type:"string"`
}
@@ -7724,9 +7797,9 @@ func (s *AlreadyExistsException) RequestID() string {
type CancelKeyDeletionInput struct {
_ struct{} `type:"structure"`
- // Identifies the customer master key (CMK) whose deletion is being canceled.
+ // Identifies the KMS key whose deletion is being canceled.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -7734,7 +7807,7 @@ type CancelKeyDeletionInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -7776,7 +7849,7 @@ type CancelKeyDeletionOutput struct {
_ struct{} `type:"structure"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK whose deletion is canceled.
+ // of the KMS key whose deletion is canceled.
KeyId *string `min:"1" type:"string"`
}
@@ -7796,10 +7869,10 @@ func (s *CancelKeyDeletionOutput) SetKeyId(v string) *CancelKeyDeletionOutput {
return s
}
-// The request was rejected because the specified AWS CloudHSM cluster is already
+// The request was rejected because the specified CloudHSM cluster is already
// associated with a custom key store or it shares a backup history with a cluster
// that is associated with a custom key store. Each custom key store must be
-// associated with a different AWS CloudHSM cluster.
+// associated with a different CloudHSM cluster.
//
// Clusters that share a backup history have the same cluster certificate. To
// view the cluster certificate of a cluster, use the DescribeClusters (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_DescribeClusters.html)
@@ -7859,8 +7932,8 @@ func (s *CloudHsmClusterInUseException) RequestID() string {
return s.RespMetadata.RequestID
}
-// The request was rejected because the associated AWS CloudHSM cluster did
-// not meet the configuration requirements for a custom key store.
+// The request was rejected because the associated CloudHSM cluster did not
+// meet the configuration requirements for a custom key store.
//
// * The cluster must be configured with private subnets in at least two
// different Availability Zones in the Region.
@@ -7875,20 +7948,19 @@ func (s *CloudHsmClusterInUseException) RequestID() string {
// operation.
//
// * The cluster must contain at least as many HSMs as the operation requires.
-// To add HSMs, use the AWS CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
+// To add HSMs, use the CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
// operation. For the CreateCustomKeyStore, UpdateCustomKeyStore, and CreateKey
-// operations, the AWS CloudHSM cluster must have at least two active HSMs,
-// each in a different Availability Zone. For the ConnectCustomKeyStore operation,
-// the AWS CloudHSM must contain at least one active HSM.
-//
-// For information about the requirements for an AWS CloudHSM cluster that is
-// associated with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
-// in the AWS Key Management Service Developer Guide. For information about
-// creating a private subnet for an AWS CloudHSM cluster, see Create a Private
-// Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
-// in the AWS CloudHSM User Guide. For information about cluster security groups,
+// operations, the CloudHSM cluster must have at least two active HSMs, each
+// in a different Availability Zone. For the ConnectCustomKeyStore operation,
+// the CloudHSM must contain at least one active HSM.
+//
+// For information about the requirements for an CloudHSM cluster that is associated
+// with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
+// in the Key Management Service Developer Guide. For information about creating
+// a private subnet for an CloudHSM cluster, see Create a Private Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
+// in the CloudHSM User Guide. For information about cluster security groups,
// see Configure a Default Security Group (https://docs.aws.amazon.com/cloudhsm/latest/userguide/configure-sg.html)
-// in the AWS CloudHSM User Guide .
+// in the CloudHSM User Guide .
type CloudHsmClusterInvalidConfigurationException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -7944,11 +8016,11 @@ func (s *CloudHsmClusterInvalidConfigurationException) RequestID() string {
return s.RespMetadata.RequestID
}
-// The request was rejected because the AWS CloudHSM cluster that is associated
+// The request was rejected because the CloudHSM cluster that is associated
// with the custom key store is not active. Initialize and activate the cluster
// and try the command again. For detailed instructions, see Getting Started
// (https://docs.aws.amazon.com/cloudhsm/latest/userguide/getting-started.html)
-// in the AWS CloudHSM User Guide.
+// in the CloudHSM User Guide.
type CloudHsmClusterNotActiveException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -8004,9 +8076,8 @@ func (s *CloudHsmClusterNotActiveException) RequestID() string {
return s.RespMetadata.RequestID
}
-// The request was rejected because AWS KMS cannot find the AWS CloudHSM cluster
-// with the specified cluster ID. Retry the request with a different cluster
-// ID.
+// The request was rejected because KMS cannot find the CloudHSM cluster with
+// the specified cluster ID. Retry the request with a different cluster ID.
type CloudHsmClusterNotFoundException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -8062,9 +8133,9 @@ func (s *CloudHsmClusterNotFoundException) RequestID() string {
return s.RespMetadata.RequestID
}
-// The request was rejected because the specified AWS CloudHSM cluster has a
-// different cluster certificate than the original cluster. You cannot use the
-// operation to specify an unrelated cluster.
+// The request was rejected because the specified CloudHSM cluster has a different
+// cluster certificate than the original cluster. You cannot use the operation
+// to specify an unrelated cluster.
//
// Specify a cluster that shares a backup history with the original cluster.
// This includes clusters that were created from a backup of the current cluster,
@@ -8194,21 +8265,21 @@ type CreateAliasInput struct {
// The AliasName value must be string of 1-256 characters. It can contain only
// alphanumeric characters, forward slashes (/), underscores (_), and dashes
// (-). The alias name cannot begin with alias/aws/. The alias/aws/ prefix is
- // reserved for AWS managed CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
+ // reserved for Amazon Web Services managed keys (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
//
// AliasName is a required field
AliasName *string `min:"1" type:"string" required:"true"`
- // Associates the alias with the specified customer managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk).
- // The CMK must be in the same AWS Region.
+ // Associates the alias with the specified customer managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk).
+ // The KMS key must be in the same Amazon Web Services Region.
//
- // A valid CMK ID is required. If you supply a null or empty string value, this
+ // A valid key ID is required. If you supply a null or empty string value, this
// operation returns an error.
//
// For help finding the key ID and ARN, see Finding the Key ID and ARN (https://docs.aws.amazon.com/kms/latest/developerguide/viewing-keys.html#find-cmk-id-arn)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide .
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -8216,7 +8287,7 @@ type CreateAliasInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// TargetKeyId is a required field
TargetKeyId *string `min:"1" type:"string" required:"true"`
@@ -8283,28 +8354,28 @@ func (s CreateAliasOutput) GoString() string {
type CreateCustomKeyStoreInput struct {
_ struct{} `type:"structure"`
- // Identifies the AWS CloudHSM cluster for the custom key store. Enter the cluster
- // ID of any active AWS CloudHSM cluster that is not already associated with
- // a custom key store. To find the cluster ID, use the DescribeClusters (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_DescribeClusters.html)
+ // Identifies the CloudHSM cluster for the custom key store. Enter the cluster
+ // ID of any active CloudHSM cluster that is not already associated with a custom
+ // key store. To find the cluster ID, use the DescribeClusters (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_DescribeClusters.html)
// operation.
//
// CloudHsmClusterId is a required field
CloudHsmClusterId *string `min:"19" type:"string" required:"true"`
// Specifies a friendly name for the custom key store. The name must be unique
- // in your AWS account.
+ // in your Amazon Web Services account.
//
// CustomKeyStoreName is a required field
CustomKeyStoreName *string `min:"1" type:"string" required:"true"`
// Enter the password of the kmsuser crypto user (CU) account (https://docs.aws.amazon.com/kms/latest/developerguide/key-store-concepts.html#concept-kmsuser)
- // in the specified AWS CloudHSM cluster. AWS KMS logs into the cluster as this
- // user to manage key material on your behalf.
+ // in the specified CloudHSM cluster. KMS logs into the cluster as this user
+ // to manage key material on your behalf.
//
// The password must be a string of 7 to 32 characters. Its value is case sensitive.
//
- // This parameter tells AWS KMS the kmsuser account password; it does not change
- // the password in the AWS CloudHSM cluster.
+ // This parameter tells KMS the kmsuser account password; it does not change
+ // the password in the CloudHSM cluster.
//
// KeyStorePassword is a required field
KeyStorePassword *string `min:"7" type:"string" required:"true" sensitive:"true"`
@@ -8413,51 +8484,52 @@ type CreateGrantInput struct {
// Specifies a grant constraint.
//
- // AWS KMS supports the EncryptionContextEquals and EncryptionContextSubset
- // grant constraints. Each constraint value can include up to 8 encryption context
+ // KMS supports the EncryptionContextEquals and EncryptionContextSubset grant
+ // constraints. Each constraint value can include up to 8 encryption context
// pairs. The encryption context value in each constraint cannot exceed 384
// characters.
//
- // These grant constraints allow a cryptographic operation (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations)
- // only when the encryption context in the request matches (EncryptionContextEquals)
- // or includes (EncryptionContextSubset) the encryption context specified in
- // this structure. For more information about encryption context, see Encryption
- // Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide . For information about
- // grant constraints, see Using grant constraints (https://docs.aws.amazon.com/kms/latest/developerguide/create-grant-overview.html#grant-constraints)
- // in the AWS Key Management Service Developer Guide.
+ // These grant constraints allow the permissions in the grant only when the
+ // encryption context in the request matches (EncryptionContextEquals) or includes
+ // (EncryptionContextSubset) the encryption context specified in this structure.
+ // For information about grant constraints, see Using grant constraints (https://docs.aws.amazon.com/kms/latest/developerguide/create-grant-overview.html#grant-constraints)
+ // in the Key Management Service Developer Guide. For more information about
+ // encryption context, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
+ // in the Key Management Service Developer Guide .
//
// The encryption context grant constraints are supported only on operations
// that include an encryption context. You cannot use an encryption context
- // grant constraint for cryptographic operations with asymmetric CMKs or for
- // management operations, such as DescribeKey or RetireGrant.
+ // grant constraint for cryptographic operations with asymmetric KMS keys or
+ // for management operations, such as DescribeKey or RetireGrant.
Constraints *GrantConstraints `type:"structure"`
// A list of grant tokens.
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
// The identity that gets the permissions specified in the grant.
//
// To specify the principal, use the Amazon Resource Name (ARN) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)
- // of an AWS principal. Valid AWS principals include AWS accounts (root), IAM
- // users, IAM roles, federated users, and assumed role users. For examples of
- // the ARN syntax to use for specifying a principal, see AWS Identity and Access
- // Management (IAM) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-iam)
- // in the Example ARNs section of the AWS General Reference.
+ // of an Amazon Web Services principal. Valid Amazon Web Services principals
+ // include Amazon Web Services accounts (root), IAM users, IAM roles, federated
+ // users, and assumed role users. For examples of the ARN syntax to use for
+ // specifying a principal, see Amazon Web Services Identity and Access Management
+ // (IAM) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-iam)
+ // in the Example ARNs section of the Amazon Web Services General Reference.
//
// GranteePrincipal is a required field
GranteePrincipal *string `min:"1" type:"string" required:"true"`
- // Identifies the customer master key (CMK) for the grant. The grant gives principals
- // permission to use this CMK.
+ // Identifies the KMS key for the grant. The grant gives principals permission
+ // to use this KMS key.
//
- // Specify the key ID or key ARN of the CMK. To specify a CMK in a different
- // AWS account, you must use the key ARN.
+ // Specify the key ID or key ARN of the KMS key. To specify a KMS key in a different
+ // Amazon Web Services account, you must use the key ARN.
//
// For example:
//
@@ -8465,7 +8537,7 @@ type CreateGrantInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -8486,25 +8558,31 @@ type CreateGrantInput struct {
// A list of operations that the grant permits.
//
- // The operation must be supported on the CMK. For example, you cannot create
- // a grant for a symmetric CMK that allows the Sign operation, or a grant for
- // an asymmetric CMK that allows the GenerateDataKey operation. If you try,
- // AWS KMS returns a ValidationError exception. For details, see Grant operations
+ // The operation must be supported on the KMS key. For example, you cannot create
+ // a grant for a symmetric KMS key that allows the Sign operation, or a grant
+ // for an asymmetric KMS key that allows the GenerateDataKey operation. If you
+ // try, KMS returns a ValidationError exception. For details, see Grant operations
// (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#terms-grant-operations)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
//
// Operations is a required field
Operations []*string `type:"list" required:"true"`
- // The principal that is given permission to retire the grant by using RetireGrant
- // operation.
+ // The principal that has permission to use the RetireGrant operation to retire
+ // the grant.
//
// To specify the principal, use the Amazon Resource Name (ARN) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)
- // of an AWS principal. Valid AWS principals include AWS accounts (root), IAM
- // users, federated users, and assumed role users. For examples of the ARN syntax
- // to use for specifying a principal, see AWS Identity and Access Management
- // (IAM) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-iam)
- // in the Example ARNs section of the AWS General Reference.
+ // of an Amazon Web Services principal. Valid Amazon Web Services principals
+ // include Amazon Web Services accounts (root), IAM users, federated users,
+ // and assumed role users. For examples of the ARN syntax to use for specifying
+ // a principal, see Amazon Web Services Identity and Access Management (IAM)
+ // (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-iam)
+ // in the Example ARNs section of the Amazon Web Services General Reference.
+ //
+ // The grant determines the retiring principal. Other principals might have
+ // permission to retire the grant or revoke the grant. For details, see RevokeGrant
+ // and Retiring and revoking grants (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#grant-delete)
+ // in the Key Management Service Developer Guide.
RetiringPrincipal *string `min:"1" type:"string"`
}
@@ -8603,8 +8681,9 @@ type CreateGrantOutput struct {
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantToken *string `min:"1" type:"string"`
}
@@ -8635,61 +8714,79 @@ type CreateKeyInput struct {
// A flag to indicate whether to bypass the key policy lockout safety check.
//
- // Setting this value to true increases the risk that the CMK becomes unmanageable.
+ // Setting this value to true increases the risk that the KMS key becomes unmanageable.
// Do not set this value to true indiscriminately.
//
// For more information, refer to the scenario in the Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-root-enable-iam)
- // section in the AWS Key Management Service Developer Guide .
+ // section in the Key Management Service Developer Guide .
//
// Use this parameter only when you include a policy in the request and you
// intend to prevent the principal that is making the request from making a
- // subsequent PutKeyPolicy request on the CMK.
+ // subsequent PutKeyPolicy request on the KMS key.
//
// The default value is false.
BypassPolicyLockoutSafetyCheck *bool `type:"boolean"`
- // Creates the CMK in the specified custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
- // and the key material in its associated AWS CloudHSM cluster. To create a
- // CMK in a custom key store, you must also specify the Origin parameter with
- // a value of AWS_CLOUDHSM. The AWS CloudHSM cluster that is associated with
- // the custom key store must have at least two active HSMs, each in a different
+ // Creates the KMS key in the specified custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
+ // and the key material in its associated CloudHSM cluster. To create a KMS
+ // key in a custom key store, you must also specify the Origin parameter with
+ // a value of AWS_CLOUDHSM. The CloudHSM cluster that is associated with the
+ // custom key store must have at least two active HSMs, each in a different
// Availability Zone in the Region.
//
- // This parameter is valid only for symmetric CMKs and regional CMKs. You cannot
- // create an asymmetric CMK or a multi-Region CMK in a custom key store.
+ // This parameter is valid only for symmetric KMS keys and regional KMS keys.
+ // You cannot create an asymmetric KMS key or a multi-Region key in a custom
+ // key store.
//
// To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
//
- // The response includes the custom key store ID and the ID of the AWS CloudHSM
+ // The response includes the custom key store ID and the ID of the CloudHSM
// cluster.
//
// This operation is part of the Custom Key Store feature (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
- // feature in AWS KMS, which combines the convenience and extensive integration
- // of AWS KMS with the isolation and control of a single-tenant key store.
+ // feature in KMS, which combines the convenience and extensive integration
+ // of KMS with the isolation and control of a single-tenant key store.
CustomKeyStoreId *string `min:"1" type:"string"`
- // Specifies the type of CMK to create. The default value, SYMMETRIC_DEFAULT,
- // creates a CMK with a 256-bit symmetric key for encryption and decryption.
- // For help choosing a key spec for your CMK, see How to Choose Your CMK Configuration
- // (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-choose.html)
- // in the AWS Key Management Service Developer Guide.
- //
- // The CustomerMasterKeySpec determines whether the CMK contains a symmetric
- // key or an asymmetric key pair. It also determines the encryption algorithms
- // or signing algorithms that the CMK supports. You can't change the CustomerMasterKeySpec
- // after the CMK is created. To further restrict the algorithms that can be
- // used with the CMK, use a condition key in its key policy or IAM policy. For
+ // Instead, use the KeySpec parameter.
+ //
+ // The KeySpec and CustomerMasterKeySpec parameters work the same way. Only
+ // the names differ. We recommend that you use KeySpec parameter in your code.
+ // However, to avoid breaking changes, KMS will support both parameters.
+ //
+ // Deprecated: This parameter has been deprecated. Instead, use the KeySpec parameter.
+ CustomerMasterKeySpec *string `deprecated:"true" type:"string" enum:"CustomerMasterKeySpec"`
+
+ // A description of the KMS key.
+ //
+ // Use a description that helps you decide whether the KMS key is appropriate
+ // for a task. The default value is an empty string (no description).
+ //
+ // To set or change the description after the key is created, use UpdateKeyDescription.
+ Description *string `type:"string"`
+
+ // Specifies the type of KMS key to create. The default value, SYMMETRIC_DEFAULT,
+ // creates a KMS key with a 256-bit symmetric key for encryption and decryption.
+ // For help choosing a key spec for your KMS key, see How to Choose Your KMS
+ // key Configuration (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-choose.html)
+ // in the Key Management Service Developer Guide .
+ //
+ // The KeySpec determines whether the KMS key contains a symmetric key or an
+ // asymmetric key pair. It also determines the encryption algorithms or signing
+ // algorithms that the KMS key supports. You can't change the KeySpec after
+ // the KMS key is created. To further restrict the algorithms that can be used
+ // with the KMS key, use a condition key in its key policy or IAM policy. For
// more information, see kms:EncryptionAlgorithm (https://docs.aws.amazon.com/kms/latest/developerguide/policy-conditions.html#conditions-kms-encryption-algorithm)
// or kms:Signing Algorithm (https://docs.aws.amazon.com/kms/latest/developerguide/policy-conditions.html#conditions-kms-signing-algorithm)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide .
//
- // AWS services that are integrated with AWS KMS (http://aws.amazon.com/kms/features/#AWS_Service_Integration)
- // use symmetric CMKs to protect your data. These services do not support asymmetric
- // CMKs. For help determining whether a CMK is symmetric or asymmetric, see
- // Identifying Symmetric and Asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/find-symm-asymm.html)
- // in the AWS Key Management Service Developer Guide.
+ // Amazon Web Services services that are integrated with KMS (http://aws.amazon.com/kms/features/#AWS_Service_Integration)
+ // use symmetric KMS keys to protect your data. These services do not support
+ // asymmetric KMS keys. For help determining whether a KMS key is symmetric
+ // or asymmetric, see Identifying Symmetric and Asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/find-symm-asymm.html)
+ // in the Key Management Service Developer Guide.
//
- // AWS KMS supports the following key specs for CMKs:
+ // KMS supports the following key specs for KMS keys:
//
// * Symmetric key (default) SYMMETRIC_DEFAULT (AES-256-GCM)
//
@@ -8700,118 +8797,115 @@ type CreateKeyInput struct {
//
// * Other asymmetric elliptic curve key pairs ECC_SECG_P256K1 (secp256k1),
// commonly used for cryptocurrencies.
- CustomerMasterKeySpec *string `type:"string" enum:"CustomerMasterKeySpec"`
-
- // A description of the CMK.
- //
- // Use a description that helps you decide whether the CMK is appropriate for
- // a task. The default value is an empty string (no description).
- Description *string `type:"string"`
+ KeySpec *string `type:"string" enum:"KeySpec"`
// Determines the cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations)
- // for which you can use the CMK. The default value is ENCRYPT_DECRYPT. This
- // parameter is required only for asymmetric CMKs. You can't change the KeyUsage
- // value after the CMK is created.
+ // for which you can use the KMS key. The default value is ENCRYPT_DECRYPT.
+ // This parameter is required only for asymmetric KMS keys. You can't change
+ // the KeyUsage value after the KMS key is created.
//
// Select only one valid value.
//
- // * For symmetric CMKs, omit the parameter or specify ENCRYPT_DECRYPT.
+ // * For symmetric KMS keys, omit the parameter or specify ENCRYPT_DECRYPT.
//
- // * For asymmetric CMKs with RSA key material, specify ENCRYPT_DECRYPT or
- // SIGN_VERIFY.
+ // * For asymmetric KMS keys with RSA key material, specify ENCRYPT_DECRYPT
+ // or SIGN_VERIFY.
//
- // * For asymmetric CMKs with ECC key material, specify SIGN_VERIFY.
+ // * For asymmetric KMS keys with ECC key material, specify SIGN_VERIFY.
KeyUsage *string `type:"string" enum:"KeyUsageType"`
- // Creates a multi-Region primary key that you can replicate into other AWS
- // Regions. You cannot change this value after you create the CMK.
+ // Creates a multi-Region primary key that you can replicate into other Amazon
+ // Web Services Regions. You cannot change this value after you create the KMS
+ // key.
//
- // For a multi-Region key, set this parameter to True. For a single-Region CMK,
- // omit this parameter or set it to False. The default value is False.
+ // For a multi-Region key, set this parameter to True. For a single-Region KMS
+ // key, omit this parameter or set it to False. The default value is False.
//
- // This operation supports multi-Region keys, an AWS KMS feature that lets you
- // create multiple interoperable CMKs in different AWS Regions. Because these
- // CMKs have the same key ID, key material, and other metadata, you can use
- // them to encrypt data in one AWS Region and decrypt it in a different AWS
- // Region without making a cross-Region call or exposing the plaintext data.
- // For more information about multi-Region keys, see Using multi-Region keys
- // (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
- // in the AWS Key Management Service Developer Guide.
+ // This operation supports multi-Region keys, an KMS feature that lets you create
+ // multiple interoperable KMS keys in different Amazon Web Services Regions.
+ // Because these KMS keys have the same key ID, key material, and other metadata,
+ // you can use them interchangeably to encrypt data in one Amazon Web Services
+ // Region and decrypt it in a different Amazon Web Services Region without re-encrypting
+ // the data or making a cross-Region call. For more information about multi-Region
+ // keys, see Using multi-Region keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
+ // in the Key Management Service Developer Guide.
//
// This value creates a primary key, not a replica. To create a replica key,
// use the ReplicateKey operation.
//
- // You can create a symmetric or asymmetric multi-Region CMK, and you can create
- // a multi-Region CMK with imported key material. However, you cannot create
- // a multi-Region CMK in a custom key store.
+ // You can create a symmetric or asymmetric multi-Region key, and you can create
+ // a multi-Region key with imported key material. However, you cannot create
+ // a multi-Region key in a custom key store.
MultiRegion *bool `type:"boolean"`
- // The source of the key material for the CMK. You cannot change the origin
- // after you create the CMK. The default is AWS_KMS, which means that AWS KMS
+ // The source of the key material for the KMS key. You cannot change the origin
+ // after you create the KMS key. The default is AWS_KMS, which means that KMS
// creates the key material.
//
- // To create a CMK with no key material (for imported key material), set the
- // value to EXTERNAL. For more information about importing key material into
- // AWS KMS, see Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
- // in the AWS Key Management Service Developer Guide. This value is valid only
- // for symmetric CMKs.
+ // To create a KMS key with no key material (for imported key material), set
+ // the value to EXTERNAL. For more information about importing key material
+ // into KMS, see Importing Key Material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html)
+ // in the Key Management Service Developer Guide. This value is valid only for
+ // symmetric KMS keys.
//
- // To create a CMK in an AWS KMS custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
- // and create its key material in the associated AWS CloudHSM cluster, set this
+ // To create a KMS key in an KMS custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
+ // and create its key material in the associated CloudHSM cluster, set this
// value to AWS_CLOUDHSM. You must also use the CustomKeyStoreId parameter to
- // identify the custom key store. This value is valid only for symmetric CMKs.
+ // identify the custom key store. This value is valid only for symmetric KMS
+ // keys.
Origin *string `type:"string" enum:"OriginType"`
- // The key policy to attach to the CMK.
+ // The key policy to attach to the KMS key.
//
// If you provide a key policy, it must meet the following criteria:
//
// * If you don't set BypassPolicyLockoutSafetyCheck to true, the key policy
// must allow the principal that is making the CreateKey request to make
- // a subsequent PutKeyPolicy request on the CMK. This reduces the risk that
- // the CMK becomes unmanageable. For more information, refer to the scenario
- // in the Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-root-enable-iam)
- // section of the AWS Key Management Service Developer Guide .
+ // a subsequent PutKeyPolicy request on the KMS key. This reduces the risk
+ // that the KMS key becomes unmanageable. For more information, refer to
+ // the scenario in the Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-root-enable-iam)
+ // section of the Key Management Service Developer Guide .
//
// * Each statement in the key policy must contain one or more principals.
- // The principals in the key policy must exist and be visible to AWS KMS.
- // When you create a new AWS principal (for example, an IAM user or role),
- // you might need to enforce a delay before including the new principal in
- // a key policy because the new principal might not be immediately visible
- // to AWS KMS. For more information, see Changes that I make are not always
- // immediately visible (https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_eventual-consistency)
- // in the AWS Identity and Access Management User Guide.
- //
- // If you do not provide a key policy, AWS KMS attaches a default key policy
- // to the CMK. For more information, see Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default)
- // in the AWS Key Management Service Developer Guide.
+ // The principals in the key policy must exist and be visible to KMS. When
+ // you create a new Amazon Web Services principal (for example, an IAM user
+ // or role), you might need to enforce a delay before including the new principal
+ // in a key policy because the new principal might not be immediately visible
+ // to KMS. For more information, see Changes that I make are not always immediately
+ // visible (https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_eventual-consistency)
+ // in the Amazon Web Services Identity and Access Management User Guide.
+ //
+ // If you do not provide a key policy, KMS attaches a default key policy to
+ // the KMS key. For more information, see Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default)
+ // in the Key Management Service Developer Guide.
//
// The key policy size quota is 32 kilobytes (32768 bytes).
//
// For help writing and formatting a JSON policy document, see the IAM JSON
// Policy Reference (https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies.html)
- // in the IAM User Guide .
+ // in the Identity and Access Management User Guide .
Policy *string `min:"1" type:"string"`
- // Assigns one or more tags to the CMK. Use this parameter to tag the CMK when
- // it is created. To tag an existing CMK, use the TagResource operation.
+ // Assigns one or more tags to the KMS key. Use this parameter to tag the KMS
+ // key when it is created. To tag an existing KMS key, use the TagResource operation.
//
- // Tagging or untagging a CMK can allow or deny permission to the CMK. For details,
- // see Using ABAC in AWS KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
- // in the AWS Key Management Service Developer Guide.
+ // Tagging or untagging a KMS key can allow or deny permission to the KMS key.
+ // For details, see Using ABAC in KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
+ // in the Key Management Service Developer Guide.
//
// To use this parameter, you must have kms:TagResource (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// permission in an IAM policy.
//
// Each tag consists of a tag key and a tag value. Both the tag key and the
// tag value are required, but the tag value can be an empty (null) string.
- // You cannot have more than one tag on a CMK with the same tag key. If you
- // specify an existing tag key with a different tag value, AWS KMS replaces
+ // You cannot have more than one tag on a KMS key with the same tag key. If
+ // you specify an existing tag key with a different tag value, KMS replaces
// the current tag value with the specified one.
//
- // When you assign tags to an AWS resource, AWS generates a cost allocation
- // report with usage and costs aggregated by tags. Tags can also be used to
- // control access to a CMK. For details, see Tagging Keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
+ // When you add tags to an Amazon Web Services resource, Amazon Web Services
+ // generates a cost allocation report with usage and costs aggregated by tags.
+ // Tags can also be used to control access to a KMS key. For details, see Tagging
+ // Keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
Tags []*Tag `type:"list"`
}
@@ -8875,6 +8969,12 @@ func (s *CreateKeyInput) SetDescription(v string) *CreateKeyInput {
return s
}
+// SetKeySpec sets the KeySpec field's value.
+func (s *CreateKeyInput) SetKeySpec(v string) *CreateKeyInput {
+ s.KeySpec = &v
+ return s
+}
+
// SetKeyUsage sets the KeyUsage field's value.
func (s *CreateKeyInput) SetKeyUsage(v string) *CreateKeyInput {
s.KeyUsage = &v
@@ -8908,7 +9008,7 @@ func (s *CreateKeyInput) SetTags(v []*Tag) *CreateKeyInput {
type CreateKeyOutput struct {
_ struct{} `type:"structure"`
- // Metadata associated with the CMK.
+ // Metadata associated with the KMS key.
KeyMetadata *KeyMetadata `type:"structure"`
}
@@ -8928,10 +9028,10 @@ func (s *CreateKeyOutput) SetKeyMetadata(v *KeyMetadata) *CreateKeyOutput {
return s
}
-// The request was rejected because the custom key store contains AWS KMS customer
-// master keys (CMKs). After verifying that you do not need to use the CMKs,
-// use the ScheduleKeyDeletion operation to delete the CMKs. After they are
-// deleted, you can delete the custom key store.
+// The request was rejected because the custom key store contains KMS keys.
+// After verifying that you do not need to use the KMS keys, use the ScheduleKeyDeletion
+// operation to delete the KMS keys. After they are deleted, you can delete
+// the custom key store.
type CustomKeyStoreHasCMKsException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -9117,7 +9217,7 @@ func (s *CustomKeyStoreNameInUseException) RequestID() string {
return s.RespMetadata.RequestID
}
-// The request was rejected because AWS KMS cannot find a custom key store with
+// The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
type CustomKeyStoreNotFoundException struct {
_ struct{} `type:"structure"`
@@ -9179,84 +9279,83 @@ func (s *CustomKeyStoreNotFoundException) RequestID() string {
type CustomKeyStoresListEntry struct {
_ struct{} `type:"structure"`
- // A unique identifier for the AWS CloudHSM cluster that is associated with
- // the custom key store.
+ // A unique identifier for the CloudHSM cluster that is associated with the
+ // custom key store.
CloudHsmClusterId *string `min:"19" type:"string"`
// Describes the connection error. This field appears in the response only when
// the ConnectionState is FAILED. For help resolving these errors, see How to
// Fix a Connection Failure (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-failed)
- // in AWS Key Management Service Developer Guide.
+ // in Key Management Service Developer Guide.
//
// Valid values are:
//
- // * CLUSTER_NOT_FOUND - AWS KMS cannot find the AWS CloudHSM cluster with
- // the specified cluster ID.
+ // * CLUSTER_NOT_FOUND - KMS cannot find the CloudHSM cluster with the specified
+ // cluster ID.
//
- // * INSUFFICIENT_CLOUDHSM_HSMS - The associated AWS CloudHSM cluster does
- // not contain any active HSMs. To connect a custom key store to its AWS
- // CloudHSM cluster, the cluster must contain at least one active HSM.
+ // * INSUFFICIENT_CLOUDHSM_HSMS - The associated CloudHSM cluster does not
+ // contain any active HSMs. To connect a custom key store to its CloudHSM
+ // cluster, the cluster must contain at least one active HSM.
//
- // * INTERNAL_ERROR - AWS KMS could not complete the request due to an internal
+ // * INTERNAL_ERROR - KMS could not complete the request due to an internal
// error. Retry the request. For ConnectCustomKeyStore requests, disconnect
// the custom key store before trying to connect again.
//
- // * INVALID_CREDENTIALS - AWS KMS does not have the correct password for
- // the kmsuser crypto user in the AWS CloudHSM cluster. Before you can connect
- // your custom key store to its AWS CloudHSM cluster, you must change the
- // kmsuser account password and update the key store password value for the
- // custom key store.
+ // * INVALID_CREDENTIALS - KMS does not have the correct password for the
+ // kmsuser crypto user in the CloudHSM cluster. Before you can connect your
+ // custom key store to its CloudHSM cluster, you must change the kmsuser
+ // account password and update the key store password value for the custom
+ // key store.
//
- // * NETWORK_ERRORS - Network errors are preventing AWS KMS from connecting
- // to the custom key store.
+ // * NETWORK_ERRORS - Network errors are preventing KMS from connecting to
+ // the custom key store.
//
- // * SUBNET_NOT_FOUND - A subnet in the AWS CloudHSM cluster configuration
- // was deleted. If AWS KMS cannot find all of the subnets in the cluster
- // configuration, attempts to connect the custom key store to the AWS CloudHSM
- // cluster fail. To fix this error, create a cluster from a recent backup
- // and associate it with your custom key store. (This process creates a new
- // cluster configuration with a VPC and private subnets.) For details, see
- // How to Fix a Connection Failure (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-failed)
- // in the AWS Key Management Service Developer Guide.
+ // * SUBNET_NOT_FOUND - A subnet in the CloudHSM cluster configuration was
+ // deleted. If KMS cannot find all of the subnets in the cluster configuration,
+ // attempts to connect the custom key store to the CloudHSM cluster fail.
+ // To fix this error, create a cluster from a recent backup and associate
+ // it with your custom key store. (This process creates a new cluster configuration
+ // with a VPC and private subnets.) For details, see How to Fix a Connection
+ // Failure (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#fix-keystore-failed)
+ // in the Key Management Service Developer Guide.
//
// * USER_LOCKED_OUT - The kmsuser CU account is locked out of the associated
- // AWS CloudHSM cluster due to too many failed password attempts. Before
- // you can connect your custom key store to its AWS CloudHSM cluster, you
- // must change the kmsuser account password and update the key store password
- // value for the custom key store.
+ // CloudHSM cluster due to too many failed password attempts. Before you
+ // can connect your custom key store to its CloudHSM cluster, you must change
+ // the kmsuser account password and update the key store password value for
+ // the custom key store.
//
// * USER_LOGGED_IN - The kmsuser CU account is logged into the the associated
- // AWS CloudHSM cluster. This prevents AWS KMS from rotating the kmsuser
- // account password and logging into the cluster. Before you can connect
- // your custom key store to its AWS CloudHSM cluster, you must log the kmsuser
- // CU out of the cluster. If you changed the kmsuser password to log into
- // the cluster, you must also and update the key store password value for
- // the custom key store. For help, see How to Log Out and Reconnect (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#login-kmsuser-2)
- // in the AWS Key Management Service Developer Guide.
- //
- // * USER_NOT_FOUND - AWS KMS cannot find a kmsuser CU account in the associated
- // AWS CloudHSM cluster. Before you can connect your custom key store to
- // its AWS CloudHSM cluster, you must create a kmsuser CU account in the
- // cluster, and then update the key store password value for the custom key
- // store.
+ // CloudHSM cluster. This prevents KMS from rotating the kmsuser account
+ // password and logging into the cluster. Before you can connect your custom
+ // key store to its CloudHSM cluster, you must log the kmsuser CU out of
+ // the cluster. If you changed the kmsuser password to log into the cluster,
+ // you must also and update the key store password value for the custom key
+ // store. For help, see How to Log Out and Reconnect (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html#login-kmsuser-2)
+ // in the Key Management Service Developer Guide.
+ //
+ // * USER_NOT_FOUND - KMS cannot find a kmsuser CU account in the associated
+ // CloudHSM cluster. Before you can connect your custom key store to its
+ // CloudHSM cluster, you must create a kmsuser CU account in the cluster,
+ // and then update the key store password value for the custom key store.
ConnectionErrorCode *string `type:"string" enum:"ConnectionErrorCodeType"`
- // Indicates whether the custom key store is connected to its AWS CloudHSM cluster.
+ // Indicates whether the custom key store is connected to its CloudHSM cluster.
//
- // You can create and use CMKs in your custom key stores only when its connection
+ // You can create and use KMS keys in your custom key stores only when its connection
// state is CONNECTED.
//
// The value is DISCONNECTED if the key store has never been connected or you
// use the DisconnectCustomKeyStore operation to disconnect it. If the value
// is CONNECTED but you are having trouble using the custom key store, make
- // sure that its associated AWS CloudHSM cluster is active and contains at least
+ // sure that its associated CloudHSM cluster is active and contains at least
// one active HSM.
//
// A value of FAILED indicates that an attempt to connect was unsuccessful.
// The ConnectionErrorCode field in the response indicates the cause of the
// failure. For help resolving a connection failure, see Troubleshooting a Custom
// Key Store (https://docs.aws.amazon.com/kms/latest/developerguide/fix-keystore.html)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
ConnectionState *string `type:"string" enum:"ConnectionStateType"`
// The date and time when the custom key store was created.
@@ -9268,8 +9367,8 @@ type CustomKeyStoresListEntry struct {
// The user-specified friendly name for the custom key store.
CustomKeyStoreName *string `min:"1" type:"string"`
- // The trust anchor certificate of the associated AWS CloudHSM cluster. When
- // you initialize the cluster (https://docs.aws.amazon.com/cloudhsm/latest/userguide/initialize-cluster.html#sign-csr),
+ // The trust anchor certificate of the associated CloudHSM cluster. When you
+ // initialize the cluster (https://docs.aws.amazon.com/cloudhsm/latest/userguide/initialize-cluster.html#sign-csr),
// you create this certificate and save it in the customerCA.crt file.
TrustAnchorCertificate *string `min:"1" type:"string"`
}
@@ -9341,47 +9440,47 @@ type DecryptInput struct {
// a different algorithm, the Decrypt operation fails.
//
// This parameter is required only when the ciphertext was encrypted under an
- // asymmetric CMK. The default value, SYMMETRIC_DEFAULT, represents the only
- // supported algorithm that is valid for symmetric CMKs.
+ // asymmetric KMS key. The default value, SYMMETRIC_DEFAULT, represents the
+ // only supported algorithm that is valid for symmetric KMS keys.
EncryptionAlgorithm *string `type:"string" enum:"EncryptionAlgorithmSpec"`
// Specifies the encryption context to use when decrypting the data. An encryption
// context is valid only for cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations)
- // with a symmetric CMK. The standard asymmetric encryption algorithms that
- // AWS KMS uses do not support an encryption context.
+ // with a symmetric KMS key. The standard asymmetric encryption algorithms that
+ // KMS uses do not support an encryption context.
//
// An encryption context is a collection of non-secret key-value pairs that
// represents additional authenticated data. When you use an encryption context
// to encrypt data, you must specify the same (an exact case-sensitive match)
// encryption context to decrypt the data. An encryption context is optional
- // when encrypting with a symmetric CMK, but it is highly recommended.
+ // when encrypting with a symmetric KMS key, but it is highly recommended.
//
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
EncryptionContext map[string]*string `type:"map"`
// A list of grant tokens.
//
// Use a grant token when your permission to call this operation comes from
- // a newly created grant that has not yet achieved eventual consistency. Use
- // a grant token when your permission to call this operation comes from a new
- // grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // a new grant that has not yet achieved eventual consistency. For more information,
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Specifies the customer master key (CMK) that AWS KMS uses to decrypt the
- // ciphertext. Enter a key ID of the CMK that was used to encrypt the ciphertext.
+ // Specifies the KMS key that KMS uses to decrypt the ciphertext. Enter a key
+ // ID of the KMS key that was used to encrypt the ciphertext.
//
// This parameter is required only when the ciphertext was encrypted under an
- // asymmetric CMK. If you used a symmetric CMK, AWS KMS can get the CMK from
- // metadata that it adds to the symmetric ciphertext blob. However, it is always
- // recommended as a best practice. This practice ensures that you use the CMK
- // that you intend.
+ // asymmetric KMS key. If you used a symmetric KMS key, KMS can get the KMS
+ // key from metadata that it adds to the symmetric ciphertext blob. However,
+ // it is always recommended as a best practice. This practice ensures that you
+ // use the KMS key that you intend.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -9393,8 +9492,8 @@ type DecryptInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
KeyId *string `min:"1" type:"string"`
}
@@ -9464,11 +9563,11 @@ type DecryptOutput struct {
EncryptionAlgorithm *string `type:"string" enum:"EncryptionAlgorithmSpec"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK that was used to decrypt the ciphertext.
+ // of the KMS key that was used to decrypt the ciphertext.
KeyId *string `min:"1" type:"string"`
- // Decrypted plaintext data. When you use the HTTP API or the AWS CLI, the value
- // is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // Decrypted plaintext data. When you use the HTTP API or the Amazon Web Services
+ // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// Plaintext is automatically base64 encoded/decoded by the SDK.
Plaintext []byte `min:"1" type:"blob" sensitive:"true"`
@@ -9617,10 +9716,10 @@ func (s DeleteCustomKeyStoreOutput) GoString() string {
type DeleteImportedKeyMaterialInput struct {
_ struct{} `type:"structure"`
- // Identifies the CMK from which you are deleting imported key material. The
- // Origin of the CMK must be EXTERNAL.
+ // Identifies the KMS key from which you are deleting imported key material.
+ // The Origin of the KMS key must be EXTERNAL.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -9628,7 +9727,7 @@ type DeleteImportedKeyMaterialInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -9759,7 +9858,7 @@ type DescribeCustomKeyStoresInput struct {
CustomKeyStoreName *string `min:"1" type:"string"`
// Use this parameter to specify the maximum number of items to return. When
- // this value is present, AWS KMS does not return more than the specified number
+ // this value is present, KMS does not return more than the specified number
// of items, but it might return fewer.
Limit *int64 `min:"1" type:"integer"`
@@ -9877,19 +9976,22 @@ type DescribeKeyInput struct {
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Describes the specified customer master key (CMK).
+ // Describes the specified KMS key.
//
- // If you specify a predefined AWS alias (an AWS alias with no key ID), KMS
- // associates the alias with an AWS managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#master_keys)
+ // If you specify a predefined Amazon Web Services alias (an Amazon Web Services
+ // alias with no key ID), KMS associates the alias with an Amazon Web Services
+ // managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html##aws-managed-cmk)
// and returns its KeyId and Arn in the response.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -9901,8 +10003,8 @@ type DescribeKeyInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -9972,9 +10074,9 @@ func (s *DescribeKeyOutput) SetKeyMetadata(v *KeyMetadata) *DescribeKeyOutput {
type DisableKeyInput struct {
_ struct{} `type:"structure"`
- // Identifies the customer master key (CMK) to disable.
+ // Identifies the KMS key to disable.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -9982,7 +10084,7 @@ type DisableKeyInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -10037,12 +10139,12 @@ func (s DisableKeyOutput) GoString() string {
type DisableKeyRotationInput struct {
_ struct{} `type:"structure"`
- // Identifies a symmetric customer master key (CMK). You cannot enable or disable
- // automatic rotation of asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html#asymmetric-cmks),
- // CMKs with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
- // or CMKs in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
+ // Identifies a symmetric KMS key. You cannot enable or disable automatic rotation
+ // of asymmetric KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symmetric-asymmetric.html#asymmetric-cmks),
+ // KMS keys with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
+ // or KMS keys in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -10050,7 +10152,7 @@ type DisableKeyRotationInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -10102,7 +10204,7 @@ func (s DisableKeyRotationOutput) GoString() string {
return s.String()
}
-// The request was rejected because the specified CMK is not enabled.
+// The request was rejected because the specified KMS key is not enabled.
type DisabledException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -10217,9 +10319,9 @@ func (s DisconnectCustomKeyStoreOutput) GoString() string {
type EnableKeyInput struct {
_ struct{} `type:"structure"`
- // Identifies the customer master key (CMK) to enable.
+ // Identifies the KMS key to enable.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -10227,7 +10329,7 @@ type EnableKeyInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -10282,15 +10384,15 @@ func (s EnableKeyOutput) GoString() string {
type EnableKeyRotationInput struct {
_ struct{} `type:"structure"`
- // Identifies a symmetric customer master key (CMK). You cannot enable automatic
- // rotation of asymmetric CMKs (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks),
- // CMKs with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
- // or CMKs in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
+ // Identifies a symmetric KMS key. You cannot enable automatic rotation of asymmetric
+ // KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#asymmetric-cmks),
+ // KMS keys with imported key material (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys.html),
+ // or KMS keys in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
// To enable or disable automatic rotation of a set of related multi-Region
// keys (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html#mrk-replica-key),
// set the property on the primary key.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -10298,7 +10400,7 @@ type EnableKeyRotationInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -10353,42 +10455,44 @@ func (s EnableKeyRotationOutput) GoString() string {
type EncryptInput struct {
_ struct{} `type:"structure"`
- // Specifies the encryption algorithm that AWS KMS will use to encrypt the plaintext
- // message. The algorithm must be compatible with the CMK that you specify.
+ // Specifies the encryption algorithm that KMS will use to encrypt the plaintext
+ // message. The algorithm must be compatible with the KMS key that you specify.
//
- // This parameter is required only for asymmetric CMKs. The default value, SYMMETRIC_DEFAULT,
- // is the algorithm used for symmetric CMKs. If you are using an asymmetric
- // CMK, we recommend RSAES_OAEP_SHA_256.
+ // This parameter is required only for asymmetric KMS keys. The default value,
+ // SYMMETRIC_DEFAULT, is the algorithm used for symmetric KMS keys. If you are
+ // using an asymmetric KMS key, we recommend RSAES_OAEP_SHA_256.
EncryptionAlgorithm *string `type:"string" enum:"EncryptionAlgorithmSpec"`
// Specifies the encryption context that will be used to encrypt the data. An
// encryption context is valid only for cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations)
- // with a symmetric CMK. The standard asymmetric encryption algorithms that
- // AWS KMS uses do not support an encryption context.
+ // with a symmetric KMS key. The standard asymmetric encryption algorithms that
+ // KMS uses do not support an encryption context.
//
// An encryption context is a collection of non-secret key-value pairs that
// represents additional authenticated data. When you use an encryption context
// to encrypt data, you must specify the same (an exact case-sensitive match)
// encryption context to decrypt the data. An encryption context is optional
- // when encrypting with a symmetric CMK, but it is highly recommended.
+ // when encrypting with a symmetric KMS key, but it is highly recommended.
//
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
EncryptionContext map[string]*string `type:"map"`
// A list of grant tokens.
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Identifies the customer master key (CMK) to use in the encryption operation.
+ // Identifies the KMS key to use in the encryption operation.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -10400,8 +10504,8 @@ type EncryptInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -10479,8 +10583,8 @@ func (s *EncryptInput) SetPlaintext(v []byte) *EncryptInput {
type EncryptOutput struct {
_ struct{} `type:"structure"`
- // The encrypted plaintext. When you use the HTTP API or the AWS CLI, the value
- // is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // The encrypted plaintext. When you use the HTTP API or the Amazon Web Services
+ // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// CiphertextBlob is automatically base64 encoded/decoded by the SDK.
CiphertextBlob []byte `min:"1" type:"blob"`
@@ -10489,7 +10593,7 @@ type EncryptOutput struct {
EncryptionAlgorithm *string `type:"string" enum:"EncryptionAlgorithmSpec"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK that was used to encrypt the plaintext.
+ // of the KMS key that was used to encrypt the plaintext.
KeyId *string `min:"1" type:"string"`
}
@@ -10589,25 +10693,27 @@ type GenerateDataKeyInput struct {
// represents additional authenticated data. When you use an encryption context
// to encrypt data, you must specify the same (an exact case-sensitive match)
// encryption context to decrypt the data. An encryption context is optional
- // when encrypting with a symmetric CMK, but it is highly recommended.
+ // when encrypting with a symmetric KMS key, but it is highly recommended.
//
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
EncryptionContext map[string]*string `type:"map"`
// A list of grant tokens.
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Identifies the symmetric CMK that encrypts the data key.
+ // Identifies the symmetric KMS key that encrypts the data key.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -10619,8 +10725,8 @@ type GenerateDataKeyInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -10703,20 +10809,20 @@ func (s *GenerateDataKeyInput) SetNumberOfBytes(v int64) *GenerateDataKeyInput {
type GenerateDataKeyOutput struct {
_ struct{} `type:"structure"`
- // The encrypted copy of the data key. When you use the HTTP API or the AWS
- // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // The encrypted copy of the data key. When you use the HTTP API or the Amazon
+ // Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// CiphertextBlob is automatically base64 encoded/decoded by the SDK.
CiphertextBlob []byte `min:"1" type:"blob"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK that encrypted the data key.
+ // of the KMS key that encrypted the data key.
KeyId *string `min:"1" type:"string"`
- // The plaintext data key. When you use the HTTP API or the AWS CLI, the value
- // is Base64-encoded. Otherwise, it is not Base64-encoded. Use this data key
- // to encrypt your data outside of KMS. Then, remove it from memory as soon
- // as possible.
+ // The plaintext data key. When you use the HTTP API or the Amazon Web Services
+ // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded. Use
+ // this data key to encrypt your data outside of KMS. Then, remove it from memory
+ // as soon as possible.
//
// Plaintext is automatically base64 encoded/decoded by the SDK.
Plaintext []byte `min:"1" type:"blob" sensitive:"true"`
@@ -10760,27 +10866,30 @@ type GenerateDataKeyPairInput struct {
// represents additional authenticated data. When you use an encryption context
// to encrypt data, you must specify the same (an exact case-sensitive match)
// encryption context to decrypt the data. An encryption context is optional
- // when encrypting with a symmetric CMK, but it is highly recommended.
+ // when encrypting with a symmetric KMS key, but it is highly recommended.
//
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
EncryptionContext map[string]*string `type:"map"`
// A list of grant tokens.
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Specifies the symmetric CMK that encrypts the private key in the data key
- // pair. You cannot specify an asymmetric CMK or a CMK in a custom key store.
- // To get the type and origin of your CMK, use the DescribeKey operation.
+ // Specifies the symmetric KMS key that encrypts the private key in the data
+ // key pair. You cannot specify an asymmetric KMS key or a KMS key in a custom
+ // key store. To get the type and origin of your KMS key, use the DescribeKey
+ // operation.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -10792,18 +10901,18 @@ type GenerateDataKeyPairInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
// Determines the type of data key pair that is generated.
//
- // The AWS KMS rule that restricts the use of asymmetric RSA CMKs to encrypt
+ // The KMS rule that restricts the use of asymmetric RSA KMS keys to encrypt
// and decrypt or to sign and verify (but not both), and the rule that permits
- // you to use ECC CMKs only to sign and verify, are not effective outside of
- // AWS KMS.
+ // you to use ECC KMS keys only to sign and verify, are not effective on data
+ // key pairs, which are used outside of KMS.
//
// KeyPairSpec is a required field
KeyPairSpec *string `type:"string" required:"true" enum:"DataKeyPairSpec"`
@@ -10866,20 +10975,20 @@ type GenerateDataKeyPairOutput struct {
_ struct{} `type:"structure"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK that encrypted the private key.
+ // of the KMS key that encrypted the private key.
KeyId *string `min:"1" type:"string"`
// The type of data key pair that was generated.
KeyPairSpec *string `type:"string" enum:"DataKeyPairSpec"`
- // The encrypted copy of the private key. When you use the HTTP API or the AWS
- // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // The encrypted copy of the private key. When you use the HTTP API or the Amazon
+ // Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// PrivateKeyCiphertextBlob is automatically base64 encoded/decoded by the SDK.
PrivateKeyCiphertextBlob []byte `min:"1" type:"blob"`
- // The plaintext copy of the private key. When you use the HTTP API or the AWS
- // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // The plaintext copy of the private key. When you use the HTTP API or the Amazon
+ // Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// PrivateKeyPlaintext is automatically base64 encoded/decoded by the SDK.
PrivateKeyPlaintext []byte `min:"1" type:"blob" sensitive:"true"`
@@ -10940,28 +11049,30 @@ type GenerateDataKeyPairWithoutPlaintextInput struct {
// represents additional authenticated data. When you use an encryption context
// to encrypt data, you must specify the same (an exact case-sensitive match)
// encryption context to decrypt the data. An encryption context is optional
- // when encrypting with a symmetric CMK, but it is highly recommended.
+ // when encrypting with a symmetric KMS key, but it is highly recommended.
//
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
EncryptionContext map[string]*string `type:"map"`
// A list of grant tokens.
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Specifies the CMK that encrypts the private key in the data key pair. You
- // must specify a symmetric CMK. You cannot use an asymmetric CMK or a CMK in
- // a custom key store. To get the type and origin of your CMK, use the DescribeKey
- // operation.
+ // Specifies the KMS key that encrypts the private key in the data key pair.
+ // You must specify a symmetric KMS key. You cannot use an asymmetric KMS key
+ // or a KMS key in a custom key store. To get the type and origin of your KMS
+ // key, use the DescribeKey operation.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -10973,18 +11084,18 @@ type GenerateDataKeyPairWithoutPlaintextInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
// Determines the type of data key pair that is generated.
//
- // The AWS KMS rule that restricts the use of asymmetric RSA CMKs to encrypt
+ // The KMS rule that restricts the use of asymmetric RSA KMS keys to encrypt
// and decrypt or to sign and verify (but not both), and the rule that permits
- // you to use ECC CMKs only to sign and verify, are not effective outside of
- // AWS KMS.
+ // you to use ECC KMS keys only to sign and verify, are not effective on data
+ // key pairs, which are used outside of KMS.
//
// KeyPairSpec is a required field
KeyPairSpec *string `type:"string" required:"true" enum:"DataKeyPairSpec"`
@@ -11047,14 +11158,14 @@ type GenerateDataKeyPairWithoutPlaintextOutput struct {
_ struct{} `type:"structure"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK that encrypted the private key.
+ // of the KMS key that encrypted the private key.
KeyId *string `min:"1" type:"string"`
// The type of data key pair that was generated.
KeyPairSpec *string `type:"string" enum:"DataKeyPairSpec"`
- // The encrypted copy of the private key. When you use the HTTP API or the AWS
- // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // The encrypted copy of the private key. When you use the HTTP API or the Amazon
+ // Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// PrivateKeyCiphertextBlob is automatically base64 encoded/decoded by the SDK.
PrivateKeyCiphertextBlob []byte `min:"1" type:"blob"`
@@ -11109,26 +11220,27 @@ type GenerateDataKeyWithoutPlaintextInput struct {
// represents additional authenticated data. When you use an encryption context
// to encrypt data, you must specify the same (an exact case-sensitive match)
// encryption context to decrypt the data. An encryption context is optional
- // when encrypting with a symmetric CMK, but it is highly recommended.
+ // when encrypting with a symmetric KMS key, but it is highly recommended.
//
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
EncryptionContext map[string]*string `type:"map"`
// A list of grant tokens.
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // The identifier of the symmetric customer master key (CMK) that encrypts the
- // data key.
+ // The identifier of the symmetric KMS key that encrypts the data key.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -11140,8 +11252,8 @@ type GenerateDataKeyWithoutPlaintextInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -11219,14 +11331,14 @@ func (s *GenerateDataKeyWithoutPlaintextInput) SetNumberOfBytes(v int64) *Genera
type GenerateDataKeyWithoutPlaintextOutput struct {
_ struct{} `type:"structure"`
- // The encrypted data key. When you use the HTTP API or the AWS CLI, the value
- // is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // The encrypted data key. When you use the HTTP API or the Amazon Web Services
+ // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// CiphertextBlob is automatically base64 encoded/decoded by the SDK.
CiphertextBlob []byte `min:"1" type:"blob"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK that encrypted the data key.
+ // of the KMS key that encrypted the data key.
KeyId *string `min:"1" type:"string"`
}
@@ -11255,7 +11367,7 @@ func (s *GenerateDataKeyWithoutPlaintextOutput) SetKeyId(v string) *GenerateData
type GenerateRandomInput struct {
_ struct{} `type:"structure"`
- // Generates the random byte string in the AWS CloudHSM cluster that is associated
+ // Generates the random byte string in the CloudHSM cluster that is associated
// with the specified custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html).
// To find the ID of a custom key store, use the DescribeCustomKeyStores operation.
CustomKeyStoreId *string `min:"1" type:"string"`
@@ -11305,8 +11417,8 @@ func (s *GenerateRandomInput) SetNumberOfBytes(v int64) *GenerateRandomInput {
type GenerateRandomOutput struct {
_ struct{} `type:"structure"`
- // The random byte string. When you use the HTTP API or the AWS CLI, the value
- // is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // The random byte string. When you use the HTTP API or the Amazon Web Services
+ // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// Plaintext is automatically base64 encoded/decoded by the SDK.
Plaintext []byte `min:"1" type:"blob" sensitive:"true"`
@@ -11331,9 +11443,9 @@ func (s *GenerateRandomOutput) SetPlaintext(v []byte) *GenerateRandomOutput {
type GetKeyPolicyInput struct {
_ struct{} `type:"structure"`
- // Gets the key policy for the specified customer master key (CMK).
+ // Gets the key policy for the specified KMS key.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -11341,7 +11453,7 @@ type GetKeyPolicyInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -11423,10 +11535,10 @@ func (s *GetKeyPolicyOutput) SetPolicy(v string) *GetKeyPolicyOutput {
type GetKeyRotationStatusInput struct {
_ struct{} `type:"structure"`
- // Gets the rotation status for the specified customer master key (CMK).
+ // Gets the rotation status for the specified KMS key.
//
- // Specify the key ID or key ARN of the CMK. To specify a CMK in a different
- // AWS account, you must use the key ARN.
+ // Specify the key ID or key ARN of the KMS key. To specify a KMS key in a different
+ // Amazon Web Services account, you must use the key ARN.
//
// For example:
//
@@ -11434,7 +11546,7 @@ type GetKeyRotationStatusInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -11498,10 +11610,10 @@ func (s *GetKeyRotationStatusOutput) SetKeyRotationEnabled(v bool) *GetKeyRotati
type GetParametersForImportInput struct {
_ struct{} `type:"structure"`
- // The identifier of the symmetric CMK into which you will import key material.
- // The Origin of the CMK must be EXTERNAL.
+ // The identifier of the symmetric KMS key into which you will import key material.
+ // The Origin of the KMS key must be EXTERNAL.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -11509,7 +11621,7 @@ type GetParametersForImportInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -11517,7 +11629,7 @@ type GetParametersForImportInput struct {
// The algorithm you will use to encrypt the key material before importing it
// with ImportKeyMaterial. For more information, see Encrypt the Key Material
// (https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys-encrypt-key-material.html)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
//
// WrappingAlgorithm is a required field
WrappingAlgorithm *string `type:"string" required:"true" enum:"AlgorithmSpec"`
@@ -11588,8 +11700,8 @@ type GetParametersForImportOutput struct {
ImportToken []byte `min:"1" type:"blob"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK to use in a subsequent ImportKeyMaterial request. This is the
- // same CMK specified in the GetParametersForImport request.
+ // of the KMS key to use in a subsequent ImportKeyMaterial request. This is
+ // the same KMS key specified in the GetParametersForImport request.
KeyId *string `min:"1" type:"string"`
// The time at which the import token and public key are no longer valid. After
@@ -11645,15 +11757,17 @@ type GetPublicKeyInput struct {
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Identifies the asymmetric CMK that includes the public key.
+ // Identifies the asymmetric KMS key that includes the public key.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -11665,8 +11779,8 @@ type GetPublicKeyInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -11713,41 +11827,49 @@ func (s *GetPublicKeyInput) SetKeyId(v string) *GetPublicKeyInput {
type GetPublicKeyOutput struct {
_ struct{} `type:"structure"`
- // The type of the of the public key that was downloaded.
- CustomerMasterKeySpec *string `type:"string" enum:"CustomerMasterKeySpec"`
+ // Instead, use the KeySpec field in the GetPublicKey response.
+ //
+ // The KeySpec and CustomerMasterKeySpec fields have the same value. We recommend
+ // that you use the KeySpec field in your code. However, to avoid breaking changes,
+ // KMS will support both fields.
+ //
+ // Deprecated: This field has been deprecated. Instead, use the KeySpec field.
+ CustomerMasterKeySpec *string `deprecated:"true" type:"string" enum:"CustomerMasterKeySpec"`
- // The encryption algorithms that AWS KMS supports for this key.
+ // The encryption algorithms that KMS supports for this key.
//
- // This information is critical. If a public key encrypts data outside of AWS
- // KMS by using an unsupported encryption algorithm, the ciphertext cannot be
- // decrypted.
+ // This information is critical. If a public key encrypts data outside of KMS
+ // by using an unsupported encryption algorithm, the ciphertext cannot be decrypted.
//
// This field appears in the response only when the KeyUsage of the public key
// is ENCRYPT_DECRYPT.
EncryptionAlgorithms []*string `type:"list"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the asymmetric CMK from which the public key was downloaded.
+ // of the asymmetric KMS key from which the public key was downloaded.
KeyId *string `min:"1" type:"string"`
+ // The type of the of the public key that was downloaded.
+ KeySpec *string `type:"string" enum:"KeySpec"`
+
// The permitted use of the public key. Valid values are ENCRYPT_DECRYPT or
// SIGN_VERIFY.
//
// This information is critical. If a public key with SIGN_VERIFY key usage
- // encrypts data outside of AWS KMS, the ciphertext cannot be decrypted.
+ // encrypts data outside of KMS, the ciphertext cannot be decrypted.
KeyUsage *string `type:"string" enum:"KeyUsageType"`
// The exported public key.
//
// The value is a DER-encoded X.509 public key, also known as SubjectPublicKeyInfo
// (SPKI), as defined in RFC 5280 (https://tools.ietf.org/html/rfc5280). When
- // you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise,
- // it is not Base64-encoded.
+ // you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded.
+ // Otherwise, it is not Base64-encoded.
//
// PublicKey is automatically base64 encoded/decoded by the SDK.
PublicKey []byte `min:"1" type:"blob"`
- // The signing algorithms that AWS KMS supports for this key.
+ // The signing algorithms that KMS supports for this key.
//
// This field appears in the response only when the KeyUsage of the public key
// is SIGN_VERIFY.
@@ -11782,6 +11904,12 @@ func (s *GetPublicKeyOutput) SetKeyId(v string) *GetPublicKeyOutput {
return s
}
+// SetKeySpec sets the KeySpec field's value.
+func (s *GetPublicKeyOutput) SetKeySpec(v string) *GetPublicKeyOutput {
+ s.KeySpec = &v
+ return s
+}
+
// SetKeyUsage sets the KeyUsage field's value.
func (s *GetPublicKeyOutput) SetKeyUsage(v string) *GetPublicKeyOutput {
s.KeyUsage = &v
@@ -11804,11 +11932,11 @@ func (s *GetPublicKeyOutput) SetSigningAlgorithms(v []*string) *GetPublicKeyOutp
// in the grant only when the operation request includes the specified encryption
// context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context).
//
-// AWS KMS applies the grant constraints only to cryptographic operations that
-// support an encryption context, that is, all cryptographic operations with
-// a symmetric CMK (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#symmetric-cmks).
+// KMS applies the grant constraints only to cryptographic operations that support
+// an encryption context, that is, all cryptographic operations with a symmetric
+// KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/symm-asymm-concepts.html#symmetric-cmks).
// Grant constraints are not applied to operations that do not support an encryption
-// context, such as cryptographic operations with asymmetric CMKs and management
+// context, such as cryptographic operations with asymmetric KMS keys and management
// operations, such as DescribeKey or RetireGrant.
//
// In a cryptographic operation, the encryption context in the decryption operation
@@ -11822,7 +11950,7 @@ func (s *GetPublicKeyOutput) SetSigningAlgorithms(v []*string) *GetPublicKeyOutp
// only by case. To require a fully case-sensitive encryption context, use the
// kms:EncryptionContext: and kms:EncryptionContextKeys conditions in an IAM
// or key policy. For details, see kms:EncryptionContext: (https://docs.aws.amazon.com/kms/latest/developerguide/policy-conditions.html#conditions-kms-encryption-context)
-// in the AWS Key Management Service Developer Guide .
+// in the Key Management Service Developer Guide .
type GrantConstraints struct {
_ struct{} `type:"structure"`
@@ -11880,16 +12008,15 @@ type GrantListEntry struct {
//
// The GranteePrincipal field in the ListGrants response usually contains the
// user or role designated as the grantee principal in the grant. However, when
- // the grantee principal in the grant is an AWS service, the GranteePrincipal
- // field contains the service principal (https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html#principal-services),
+ // the grantee principal in the grant is an Amazon Web Services service, the
+ // GranteePrincipal field contains the service principal (https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html#principal-services),
// which might represent several different grantee principals.
GranteePrincipal *string `min:"1" type:"string"`
- // The AWS account under which the grant was issued.
+ // The Amazon Web Services account under which the grant was issued.
IssuingAccount *string `min:"1" type:"string"`
- // The unique identifier for the customer master key (CMK) to which the grant
- // applies.
+ // The unique identifier for the KMS key to which the grant applies.
KeyId *string `min:"1" type:"string"`
// The friendly name that identifies the grant. If a name was provided in the
@@ -11994,11 +12121,11 @@ type ImportKeyMaterialInput struct {
// ImportToken is a required field
ImportToken []byte `min:"1" type:"blob" required:"true"`
- // The identifier of the symmetric CMK that receives the imported key material.
- // The CMK's Origin must be EXTERNAL. This must be the same CMK specified in
- // the KeyID parameter of the corresponding GetParametersForImport request.
+ // The identifier of the symmetric KMS key that receives the imported key material.
+ // The KMS key's Origin must be EXTERNAL. This must be the same KMS key specified
+ // in the KeyID parameter of the corresponding GetParametersForImport request.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -12006,13 +12133,13 @@ type ImportKeyMaterialInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
// The time at which the imported key material expires. When the key material
- // expires, AWS KMS deletes the key material and the CMK becomes unusable. You
+ // expires, KMS deletes the key material and the KMS key becomes unusable. You
// must omit this parameter when the ExpirationModel parameter is set to KEY_MATERIAL_DOES_NOT_EXPIRE.
// Otherwise it is required.
ValidTo *time.Time `type:"timestamp"`
@@ -12100,9 +12227,9 @@ func (s ImportKeyMaterialOutput) GoString() string {
return s.String()
}
-// The request was rejected because the specified CMK cannot decrypt the data.
-// The KeyId in a Decrypt request and the SourceKeyId in a ReEncrypt request
-// must identify the same CMK that was used to encrypt the ciphertext.
+// The request was rejected because the specified KMS key cannot decrypt the
+// data. The KeyId in a Decrypt request and the SourceKeyId in a ReEncrypt request
+// must identify the same KMS key that was used to encrypt the ciphertext.
type IncorrectKeyException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -12160,7 +12287,7 @@ func (s *IncorrectKeyException) RequestID() string {
// The request was rejected because the key material in the request is, expired,
// invalid, or is not the same key material that was previously imported into
-// this customer master key (CMK).
+// this KMS key.
type IncorrectKeyMaterialException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -12217,7 +12344,7 @@ func (s *IncorrectKeyMaterialException) RequestID() string {
}
// The request was rejected because the trust anchor certificate in the request
-// is not the trust anchor certificate for the specified AWS CloudHSM cluster.
+// is not the trust anchor certificate for the specified CloudHSM cluster.
//
// When you initialize the cluster (https://docs.aws.amazon.com/cloudhsm/latest/userguide/initialize-cluster.html#sign-csr),
// you create the trust anchor certificate and save it in the customerCA.crt
@@ -12452,8 +12579,8 @@ func (s *InvalidArnException) RequestID() string {
// the ciphertext, such as the encryption context, is corrupted, missing, or
// otherwise invalid.
//
-// From the ImportKeyMaterial operation, the request was rejected because AWS
-// KMS could not decrypt the encrypted (wrapped) key material.
+// From the ImportKeyMaterial operation, the request was rejected because KMS
+// could not decrypt the encrypted (wrapped) key material.
type InvalidCiphertextException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -12622,7 +12749,7 @@ func (s *InvalidGrantTokenException) RequestID() string {
}
// The request was rejected because the provided import token is invalid or
-// is associated with a different customer master key (CMK).
+// is associated with a different KMS key.
type InvalidImportTokenException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -12680,17 +12807,18 @@ func (s *InvalidImportTokenException) RequestID() string {
// The request was rejected for one of the following reasons:
//
-// * The KeyUsage value of the CMK is incompatible with the API operation.
+// * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
-// is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+// is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
-// must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+// must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+// operation.
//
-// To find the encryption or signing algorithms supported for a particular CMK,
-// use the DescribeKey operation.
+// To find the encryption or signing algorithms supported for a particular KMS
+// key, use the DescribeKey operation.
type InvalidKeyUsageException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -12806,9 +12934,9 @@ func (s *InvalidMarkerException) RequestID() string {
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
-// For more information about how key state affects the use of a CMK, see How
-// Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
-// in the AWS Key Management Service Developer Guide .
+// For more information about how key state affects the use of a KMS key, see
+// Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+// in the Key Management Service Developer Guide .
type InvalidStateException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -12866,7 +12994,7 @@ func (s *InvalidStateException) RequestID() string {
// The request was rejected because the signature verification failed. Signature
// verification fails when it cannot confirm that signature was produced by
-// signing the specified message with the specified CMK and signing algorithm.
+// signing the specified message with the specified KMS key and signing algorithm.
type KMSInvalidSignatureException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -12955,125 +13083,134 @@ func (s *KeyListEntry) SetKeyId(v string) *KeyListEntry {
return s
}
-// Contains metadata about a customer master key (CMK).
+// Contains metadata about a KMS key.
//
// This data type is used as a response element for the CreateKey and DescribeKey
// operations.
type KeyMetadata struct {
_ struct{} `type:"structure"`
- // The twelve-digit account ID of the AWS account that owns the CMK.
+ // The twelve-digit account ID of the Amazon Web Services account that owns
+ // the KMS key.
AWSAccountId *string `type:"string"`
- // The Amazon Resource Name (ARN) of the CMK. For examples, see AWS Key Management
- // Service (AWS KMS) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-kms)
- // in the Example ARNs section of the AWS General Reference.
+ // The Amazon Resource Name (ARN) of the KMS key. For examples, see Key Management
+ // Service (KMS) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-kms)
+ // in the Example ARNs section of the Amazon Web Services General Reference.
Arn *string `min:"20" type:"string"`
- // The cluster ID of the AWS CloudHSM cluster that contains the key material
- // for the CMK. When you create a CMK in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html),
- // AWS KMS creates the key material for the CMK in the associated AWS CloudHSM
- // cluster. This value is present only when the CMK is created in a custom key
- // store.
+ // The cluster ID of the CloudHSM cluster that contains the key material for
+ // the KMS key. When you create a KMS key in a custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html),
+ // KMS creates the key material for the KMS key in the associated CloudHSM cluster.
+ // This value is present only when the KMS key is created in a custom key store.
CloudHsmClusterId *string `min:"19" type:"string"`
- // The date and time when the CMK was created.
+ // The date and time when the KMS key was created.
CreationDate *time.Time `type:"timestamp"`
// A unique identifier for the custom key store (https://docs.aws.amazon.com/kms/latest/developerguide/custom-key-store-overview.html)
- // that contains the CMK. This value is present only when the CMK is created
- // in a custom key store.
+ // that contains the KMS key. This value is present only when the KMS key is
+ // created in a custom key store.
CustomKeyStoreId *string `min:"1" type:"string"`
- // Describes the type of key material in the CMK.
- CustomerMasterKeySpec *string `type:"string" enum:"CustomerMasterKeySpec"`
+ // Instead, use the KeySpec field.
+ //
+ // The KeySpec and CustomerMasterKeySpec fields have the same value. We recommend
+ // that you use the KeySpec field in your code. However, to avoid breaking changes,
+ // KMS will support both fields.
+ //
+ // Deprecated: This field has been deprecated. Instead, use the KeySpec field.
+ CustomerMasterKeySpec *string `deprecated:"true" type:"string" enum:"CustomerMasterKeySpec"`
- // The date and time after which AWS KMS deletes this CMK. This value is present
- // only when the CMK is scheduled for deletion, that is, when its KeyState is
- // PendingDeletion.
+ // The date and time after which KMS deletes this KMS key. This value is present
+ // only when the KMS key is scheduled for deletion, that is, when its KeyState
+ // is PendingDeletion.
//
// When the primary key in a multi-Region key is scheduled for deletion but
// still has replica keys, its key state is PendingReplicaDeletion and the length
// of its waiting period is displayed in the PendingDeletionWindowInDays field.
DeletionDate *time.Time `type:"timestamp"`
- // The description of the CMK.
+ // The description of the KMS key.
Description *string `type:"string"`
- // Specifies whether the CMK is enabled. When KeyState is Enabled this value
+ // Specifies whether the KMS key is enabled. When KeyState is Enabled this value
// is true, otherwise it is false.
Enabled *bool `type:"boolean"`
- // The encryption algorithms that the CMK supports. You cannot use the CMK with
- // other encryption algorithms within AWS KMS.
+ // The encryption algorithms that the KMS key supports. You cannot use the KMS
+ // key with other encryption algorithms within KMS.
//
- // This value is present only when the KeyUsage of the CMK is ENCRYPT_DECRYPT.
+ // This value is present only when the KeyUsage of the KMS key is ENCRYPT_DECRYPT.
EncryptionAlgorithms []*string `type:"list"`
- // Specifies whether the CMK's key material expires. This value is present only
- // when Origin is EXTERNAL, otherwise this value is omitted.
+ // Specifies whether the KMS key's key material expires. This value is present
+ // only when Origin is EXTERNAL, otherwise this value is omitted.
ExpirationModel *string `type:"string" enum:"ExpirationModelType"`
- // The globally unique identifier for the CMK.
+ // The globally unique identifier for the KMS key.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
- // The manager of the CMK. CMKs in your AWS account are either customer managed
- // or AWS managed. For more information about the difference, see Customer Master
- // Keys (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#master_keys)
- // in the AWS Key Management Service Developer Guide.
+ // The manager of the KMS key. KMS keys in your Amazon Web Services account
+ // are either customer managed or Amazon Web Services managed. For more information
+ // about the difference, see KMS keys (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys)
+ // in the Key Management Service Developer Guide.
KeyManager *string `type:"string" enum:"KeyManagerType"`
- // The current status of the CMK.
+ // Describes the type of key material in the KMS key.
+ KeySpec *string `type:"string" enum:"KeySpec"`
+
+ // The current status of the KMS key.
//
- // For more information about how key state affects the use of a CMK, see Key
- // state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
- // in the AWS Key Management Service Developer Guide.
+ // For more information about how key state affects the use of a KMS key, see
+ // Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+ // in the Key Management Service Developer Guide.
KeyState *string `type:"string" enum:"KeyState"`
// The cryptographic operations (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations)
- // for which you can use the CMK.
+ // for which you can use the KMS key.
KeyUsage *string `type:"string" enum:"KeyUsageType"`
- // Indicates whether the CMK is a multi-Region (True) or regional (False) key.
- // This value is True for multi-Region primary and replica CMKs and False for
- // regional CMKs.
+ // Indicates whether the KMS key is a multi-Region (True) or regional (False)
+ // key. This value is True for multi-Region primary and replica keys and False
+ // for regional KMS keys.
//
// For more information about multi-Region keys, see Using multi-Region keys
// (https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
MultiRegion *bool `type:"boolean"`
- // Lists the primary and replica CMKs in same multi-Region CMK. This field is
+ // Lists the primary and replica keys in same multi-Region key. This field is
// present only when the value of the MultiRegion field is True.
//
- // For more information about any listed CMK, use the DescribeKey operation.
+ // For more information about any listed KMS key, use the DescribeKey operation.
//
- // * MultiRegionKeyType indicates whether the CMK is a PRIMARY or REPLICA
+ // * MultiRegionKeyType indicates whether the KMS key is a PRIMARY or REPLICA
// key.
//
// * PrimaryKey displays the key ARN and Region of the primary key. This
- // field displays the current CMK if it is the primary key.
+ // field displays the current KMS key if it is the primary key.
//
// * ReplicaKeys displays the key ARNs and Regions of all replica keys. This
- // field includes the current CMK if it is a replica key.
+ // field includes the current KMS key if it is a replica key.
MultiRegionConfiguration *MultiRegionConfiguration `type:"structure"`
- // The source of the CMK's key material. When this value is AWS_KMS, AWS KMS
- // created the key material. When this value is EXTERNAL, the key material was
- // imported from your existing key management infrastructure or the CMK lacks
- // key material. When this value is AWS_CLOUDHSM, the key material was created
- // in the AWS CloudHSM cluster associated with a custom key store.
+ // The source of the key material for the KMS key. When this value is AWS_KMS,
+ // KMS created the key material. When this value is EXTERNAL, the key material
+ // was imported or the KMS key doesn't have any key material. When this value
+ // is AWS_CLOUDHSM, the key material was created in the CloudHSM cluster associated
+ // with a custom key store.
Origin *string `type:"string" enum:"OriginType"`
// The waiting period before the primary key in a multi-Region key is deleted.
// This waiting period begins when the last of its replica keys is deleted.
- // This value is present only when the KeyState of the CMK is PendingReplicaDeletion.
- // That indicates that the CMK is the primary key in a multi-Region key, it
- // is scheduled for deletion, and it still has existing replica keys.
+ // This value is present only when the KeyState of the KMS key is PendingReplicaDeletion.
+ // That indicates that the KMS key is the primary key in a multi-Region key,
+ // it is scheduled for deletion, and it still has existing replica keys.
//
- // When a regional CMK or a replica key in a multi-Region key is scheduled for
+ // When a single-Region KMS key or a multi-Region replica key is scheduled for
// deletion, its deletion date is displayed in the DeletionDate field. However,
// when the primary key in a multi-Region key is scheduled for deletion, its
// waiting period doesn't begin until all of its replica keys are deleted. This
@@ -13082,15 +13219,15 @@ type KeyMetadata struct {
// to PendingDeletion and the deletion date appears in the DeletionDate field.
PendingDeletionWindowInDays *int64 `min:"1" type:"integer"`
- // The signing algorithms that the CMK supports. You cannot use the CMK with
- // other signing algorithms within AWS KMS.
+ // The signing algorithms that the KMS key supports. You cannot use the KMS
+ // key with other signing algorithms within KMS.
//
- // This field appears only when the KeyUsage of the CMK is SIGN_VERIFY.
+ // This field appears only when the KeyUsage of the KMS key is SIGN_VERIFY.
SigningAlgorithms []*string `type:"list"`
// The time at which the imported key material expires. When the key material
- // expires, AWS KMS deletes the key material and the CMK becomes unusable. This
- // value is present only for CMKs whose Origin is EXTERNAL and whose ExpirationModel
+ // expires, KMS deletes the key material and the KMS key becomes unusable. This
+ // value is present only for KMS keys whose Origin is EXTERNAL and whose ExpirationModel
// is KEY_MATERIAL_EXPIRES, otherwise this value is omitted.
ValidTo *time.Time `type:"timestamp"`
}
@@ -13183,6 +13320,12 @@ func (s *KeyMetadata) SetKeyManager(v string) *KeyMetadata {
return s
}
+// SetKeySpec sets the KeySpec field's value.
+func (s *KeyMetadata) SetKeySpec(v string) *KeyMetadata {
+ s.KeySpec = &v
+ return s
+}
+
// SetKeyState sets the KeyState field's value.
func (s *KeyMetadata) SetKeyState(v string) *KeyMetadata {
s.KeyState = &v
@@ -13231,8 +13374,8 @@ func (s *KeyMetadata) SetValidTo(v time.Time) *KeyMetadata {
return s
}
-// The request was rejected because the specified CMK was not available. You
-// can retry the request.
+// The request was rejected because the specified KMS key was not available.
+// You can retry the request.
type KeyUnavailableException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -13290,7 +13433,7 @@ func (s *KeyUnavailableException) RequestID() string {
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
-// in the AWS Key Management Service Developer Guide.
+// in the Key Management Service Developer Guide.
type LimitExceededException struct {
_ struct{} `type:"structure"`
RespMetadata protocol.ResponseMetadata `json:"-" xml:"-"`
@@ -13349,13 +13492,13 @@ func (s *LimitExceededException) RequestID() string {
type ListAliasesInput struct {
_ struct{} `type:"structure"`
- // Lists only aliases that are associated with the specified CMK. Enter a CMK
- // in your AWS account.
+ // Lists only aliases that are associated with the specified KMS key. Enter
+ // a KMS key in your Amazon Web Services account.
//
// This parameter is optional. If you omit it, ListAliases returns all aliases
// in the account and Region.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -13363,11 +13506,11 @@ type ListAliasesInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
KeyId *string `min:"1" type:"string"`
// Use this parameter to specify the maximum number of items to return. When
- // this value is present, AWS KMS does not return more than the specified number
+ // this value is present, KMS does not return more than the specified number
// of items, but it might return fewer.
//
// This value is optional. If you include a value, it must be between 1 and
@@ -13483,11 +13626,10 @@ type ListGrantsInput struct {
// for the grant.
GranteePrincipal *string `min:"1" type:"string"`
- // Returns only grants for the specified customer master key (CMK). This parameter
- // is required.
+ // Returns only grants for the specified KMS key. This parameter is required.
//
- // Specify the key ID or key ARN of the CMK. To specify a CMK in a different
- // AWS account, you must use the key ARN.
+ // Specify the key ID or key ARN of the KMS key. To specify a KMS key in a different
+ // Amazon Web Services account, you must use the key ARN.
//
// For example:
//
@@ -13495,13 +13637,13 @@ type ListGrantsInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
// Use this parameter to specify the maximum number of items to return. When
- // this value is present, AWS KMS does not return more than the specified number
+ // this value is present, KMS does not return more than the specified number
// of items, but it might return fewer.
//
// This value is optional. If you include a value, it must be between 1 and
@@ -13630,9 +13772,9 @@ func (s *ListGrantsResponse) SetTruncated(v bool) *ListGrantsResponse {
type ListKeyPoliciesInput struct {
_ struct{} `type:"structure"`
- // Gets the names of key policies for the specified customer master key (CMK).
+ // Gets the names of key policies for the specified KMS key.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -13640,13 +13782,13 @@ type ListKeyPoliciesInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
// Use this parameter to specify the maximum number of items to return. When
- // this value is present, AWS KMS does not return more than the specified number
+ // this value is present, KMS does not return more than the specified number
// of items, but it might return fewer.
//
// This value is optional. If you include a value, it must be between 1 and
@@ -13760,7 +13902,7 @@ type ListKeysInput struct {
_ struct{} `type:"structure"`
// Use this parameter to specify the maximum number of items to return. When
- // this value is present, AWS KMS does not return more than the specified number
+ // this value is present, KMS does not return more than the specified number
// of items, but it might return fewer.
//
// This value is optional. If you include a value, it must be between 1 and
@@ -13814,7 +13956,7 @@ func (s *ListKeysInput) SetMarker(v string) *ListKeysInput {
type ListKeysOutput struct {
_ struct{} `type:"structure"`
- // A list of customer master keys (CMKs).
+ // A list of KMS keys.
Keys []*KeyListEntry `type:"list"`
// When Truncated is true, this element is present and contains the value to
@@ -13859,9 +14001,9 @@ func (s *ListKeysOutput) SetTruncated(v bool) *ListKeysOutput {
type ListResourceTagsInput struct {
_ struct{} `type:"structure"`
- // Gets tags on the specified customer master key (CMK).
+ // Gets tags on the specified KMS key.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -13869,13 +14011,13 @@ type ListResourceTagsInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
// Use this parameter to specify the maximum number of items to return. When
- // this value is present, AWS KMS does not return more than the specified number
+ // this value is present, KMS does not return more than the specified number
// of items, but it might return fewer.
//
// This value is optional. If you include a value, it must be between 1 and
@@ -13952,9 +14094,9 @@ type ListResourceTagsOutput struct {
// A list of tags. Each tag consists of a tag key and a tag value.
//
- // Tagging or untagging a CMK can allow or deny permission to the CMK. For details,
- // see Using ABAC in AWS KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
- // in the AWS Key Management Service Developer Guide.
+ // Tagging or untagging a KMS key can allow or deny permission to the KMS key.
+ // For details, see Using ABAC in KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
+ // in the Key Management Service Developer Guide.
Tags []*Tag `type:"list"`
// A flag that indicates whether there are more items in the list. When this
@@ -13996,7 +14138,7 @@ type ListRetirableGrantsInput struct {
_ struct{} `type:"structure"`
// Use this parameter to specify the maximum number of items to return. When
- // this value is present, AWS KMS does not return more than the specified number
+ // this value is present, KMS does not return more than the specified number
// of items, but it might return fewer.
//
// This value is optional. If you include a value, it must be between 1 and
@@ -14009,13 +14151,13 @@ type ListRetirableGrantsInput struct {
Marker *string `min:"1" type:"string"`
// The retiring principal for which to list grants. Enter a principal in your
- // AWS account.
+ // Amazon Web Services account.
//
// To specify the retiring principal, use the Amazon Resource Name (ARN) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)
- // of an AWS principal. Valid AWS principals include AWS accounts (root), IAM
- // users, federated users, and assumed role users. For examples of the ARN syntax
- // for specifying a principal, see AWS Identity and Access Management (IAM)
- // (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-iam)
+ // of an Amazon Web Services principal. Valid Amazon Web Services principals
+ // include Amazon Web Services accounts (root), IAM users, federated users,
+ // and assumed role users. For examples of the ARN syntax for specifying a principal,
+ // see Amazon Web Services Identity and Access Management (IAM) (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html#arn-syntax-iam)
// in the Example ARNs section of the Amazon Web Services General Reference.
//
// RetiringPrincipal is a required field
@@ -14129,22 +14271,22 @@ func (s *MalformedPolicyDocumentException) RequestID() string {
return s.RespMetadata.RequestID
}
-// Describes the configuration of this multi-Region CMK. This field appears
-// only when the CMK is a primary or replica of a multi-Region CMK.
+// Describes the configuration of this multi-Region key. This field appears
+// only when the KMS key is a primary or replica of a multi-Region key.
//
-// For more information about any listed CMK, use the DescribeKey operation.
+// For more information about any listed KMS key, use the DescribeKey operation.
type MultiRegionConfiguration struct {
_ struct{} `type:"structure"`
- // Indicates whether the CMK is a PRIMARY or REPLICA key.
+ // Indicates whether the KMS key is a PRIMARY or REPLICA key.
MultiRegionKeyType *string `type:"string" enum:"MultiRegionKeyType"`
// Displays the key ARN and Region of the primary key. This field includes the
- // current CMK if it is the primary key.
+ // current KMS key if it is the primary key.
PrimaryKey *MultiRegionKey `type:"structure"`
// displays the key ARNs and Regions of all replica keys. This field includes
- // the current CMK if it is a replica key.
+ // the current KMS key if it is a replica key.
ReplicaKeys []*MultiRegionKey `type:"list"`
}
@@ -14183,7 +14325,8 @@ type MultiRegionKey struct {
// Displays the key ARN of a primary or replica key of a multi-Region key.
Arn *string `min:"20" type:"string"`
- // Displays the AWS Region of a primary or replica key in a multi-Region key.
+ // Displays the Amazon Web Services Region of a primary or replica key in a
+ // multi-Region key.
Region *string `min:"1" type:"string"`
}
@@ -14271,21 +14414,22 @@ type PutKeyPolicyInput struct {
// A flag to indicate whether to bypass the key policy lockout safety check.
//
- // Setting this value to true increases the risk that the CMK becomes unmanageable.
+ // Setting this value to true increases the risk that the KMS key becomes unmanageable.
// Do not set this value to true indiscriminately.
//
// For more information, refer to the scenario in the Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-root-enable-iam)
- // section in the AWS Key Management Service Developer Guide.
+ // section in the Key Management Service Developer Guide.
//
// Use this parameter only when you intend to prevent the principal that is
- // making the request from making a subsequent PutKeyPolicy request on the CMK.
+ // making the request from making a subsequent PutKeyPolicy request on the KMS
+ // key.
//
// The default value is false.
BypassPolicyLockoutSafetyCheck *bool `type:"boolean"`
- // Sets the key policy on the specified customer master key (CMK).
+ // Sets the key policy on the specified KMS key.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -14293,34 +14437,34 @@ type PutKeyPolicyInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
- // The key policy to attach to the CMK.
+ // The key policy to attach to the KMS key.
//
// The key policy must meet the following criteria:
//
// * If you don't set BypassPolicyLockoutSafetyCheck to true, the key policy
// must allow the principal that is making the PutKeyPolicy request to make
- // a subsequent PutKeyPolicy request on the CMK. This reduces the risk that
- // the CMK becomes unmanageable. For more information, refer to the scenario
- // in the Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-root-enable-iam)
- // section of the AWS Key Management Service Developer Guide.
+ // a subsequent PutKeyPolicy request on the KMS key. This reduces the risk
+ // that the KMS key becomes unmanageable. For more information, refer to
+ // the scenario in the Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-root-enable-iam)
+ // section of the Key Management Service Developer Guide.
//
// * Each statement in the key policy must contain one or more principals.
- // The principals in the key policy must exist and be visible to AWS KMS.
- // When you create a new AWS principal (for example, an IAM user or role),
- // you might need to enforce a delay before including the new principal in
- // a key policy because the new principal might not be immediately visible
- // to AWS KMS. For more information, see Changes that I make are not always
- // immediately visible (https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_eventual-consistency)
- // in the AWS Identity and Access Management User Guide.
+ // The principals in the key policy must exist and be visible to KMS. When
+ // you create a new Amazon Web Services principal (for example, an IAM user
+ // or role), you might need to enforce a delay before including the new principal
+ // in a key policy because the new principal might not be immediately visible
+ // to KMS. For more information, see Changes that I make are not always immediately
+ // visible (https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_eventual-consistency)
+ // in the Amazon Web Services Identity and Access Management User Guide.
//
// The key policy cannot exceed 32 kilobytes (32768 bytes). For more information,
// see Resource Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/resource-limits.html)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
//
// Policy is a required field
Policy *string `min:"1" type:"string" required:"true"`
@@ -14417,37 +14561,38 @@ type ReEncryptInput struct {
// CiphertextBlob is a required field
CiphertextBlob []byte `min:"1" type:"blob" required:"true"`
- // Specifies the encryption algorithm that AWS KMS will use to reecrypt the
- // data after it has decrypted it. The default value, SYMMETRIC_DEFAULT, represents
- // the encryption algorithm used for symmetric CMKs.
+ // Specifies the encryption algorithm that KMS will use to reecrypt the data
+ // after it has decrypted it. The default value, SYMMETRIC_DEFAULT, represents
+ // the encryption algorithm used for symmetric KMS keys.
//
- // This parameter is required only when the destination CMK is an asymmetric
- // CMK.
+ // This parameter is required only when the destination KMS key is an asymmetric
+ // KMS key.
DestinationEncryptionAlgorithm *string `type:"string" enum:"EncryptionAlgorithmSpec"`
// Specifies that encryption context to use when the reencrypting the data.
//
- // A destination encryption context is valid only when the destination CMK is
- // a symmetric CMK. The standard ciphertext format for asymmetric CMKs does
- // not include fields for metadata.
+ // A destination encryption context is valid only when the destination KMS key
+ // is a symmetric KMS key. The standard ciphertext format for asymmetric KMS
+ // keys does not include fields for metadata.
//
// An encryption context is a collection of non-secret key-value pairs that
// represents additional authenticated data. When you use an encryption context
// to encrypt data, you must specify the same (an exact case-sensitive match)
// encryption context to decrypt the data. An encryption context is optional
- // when encrypting with a symmetric CMK, but it is highly recommended.
+ // when encrypting with a symmetric KMS key, but it is highly recommended.
//
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
DestinationEncryptionContext map[string]*string `type:"map"`
- // A unique identifier for the CMK that is used to reencrypt the data. Specify
- // a symmetric or asymmetric CMK with a KeyUsage value of ENCRYPT_DECRYPT. To
- // find the KeyUsage value of a CMK, use the DescribeKey operation.
+ // A unique identifier for the KMS key that is used to reencrypt the data. Specify
+ // a symmetric or asymmetric KMS key with a KeyUsage value of ENCRYPT_DECRYPT.
+ // To find the KeyUsage value of a KMS key, use the DescribeKey operation.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -14459,8 +14604,8 @@ type ReEncryptInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// DestinationKeyId is a required field
DestinationKeyId *string `min:"1" type:"string" required:"true"`
@@ -14469,19 +14614,20 @@ type ReEncryptInput struct {
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Specifies the encryption algorithm that AWS KMS will use to decrypt the ciphertext
+ // Specifies the encryption algorithm that KMS will use to decrypt the ciphertext
// before it is reencrypted. The default value, SYMMETRIC_DEFAULT, represents
- // the algorithm used for symmetric CMKs.
+ // the algorithm used for symmetric KMS keys.
//
// Specify the same algorithm that was used to encrypt the ciphertext. If you
// specify a different algorithm, the decrypt attempt fails.
//
// This parameter is required only when the ciphertext was encrypted under an
- // asymmetric CMK.
+ // asymmetric KMS key.
SourceEncryptionAlgorithm *string `type:"string" enum:"EncryptionAlgorithmSpec"`
// Specifies the encryption context to use to decrypt the ciphertext. Enter
@@ -14491,25 +14637,26 @@ type ReEncryptInput struct {
// represents additional authenticated data. When you use an encryption context
// to encrypt data, you must specify the same (an exact case-sensitive match)
// encryption context to decrypt the data. An encryption context is optional
- // when encrypting with a symmetric CMK, but it is highly recommended.
+ // when encrypting with a symmetric KMS key, but it is highly recommended.
//
// For more information, see Encryption Context (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#encrypt_context)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
SourceEncryptionContext map[string]*string `type:"map"`
- // Specifies the customer master key (CMK) that AWS KMS will use to decrypt
- // the ciphertext before it is re-encrypted. Enter a key ID of the CMK that
- // was used to encrypt the ciphertext.
+ // Specifies the KMS key that KMS will use to decrypt the ciphertext before
+ // it is re-encrypted. Enter a key ID of the KMS key that was used to encrypt
+ // the ciphertext.
//
// This parameter is required only when the ciphertext was encrypted under an
- // asymmetric CMK. If you used a symmetric CMK, AWS KMS can get the CMK from
- // metadata that it adds to the symmetric ciphertext blob. However, it is always
- // recommended as a best practice. This practice ensures that you use the CMK
- // that you intend.
+ // asymmetric KMS key. If you used a symmetric KMS key, KMS can get the KMS
+ // key from metadata that it adds to the symmetric ciphertext blob. However,
+ // it is always recommended as a best practice. This practice ensures that you
+ // use the KMS key that you intend.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -14521,8 +14668,8 @@ type ReEncryptInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
SourceKeyId *string `min:"1" type:"string"`
}
@@ -14612,8 +14759,8 @@ func (s *ReEncryptInput) SetSourceKeyId(v string) *ReEncryptInput {
type ReEncryptOutput struct {
_ struct{} `type:"structure"`
- // The reencrypted data. When you use the HTTP API or the AWS CLI, the value
- // is Base64-encoded. Otherwise, it is not Base64-encoded.
+ // The reencrypted data. When you use the HTTP API or the Amazon Web Services
+ // CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.
//
// CiphertextBlob is automatically base64 encoded/decoded by the SDK.
CiphertextBlob []byte `min:"1" type:"blob"`
@@ -14622,14 +14769,14 @@ type ReEncryptOutput struct {
DestinationEncryptionAlgorithm *string `type:"string" enum:"EncryptionAlgorithmSpec"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK that was used to reencrypt the data.
+ // of the KMS key that was used to reencrypt the data.
KeyId *string `min:"1" type:"string"`
// The encryption algorithm that was used to decrypt the ciphertext before it
// was reencrypted.
SourceEncryptionAlgorithm *string `type:"string" enum:"EncryptionAlgorithmSpec"`
- // Unique identifier of the CMK used to originally encrypt the data.
+ // Unique identifier of the KMS key used to originally encrypt the data.
SourceKeyId *string `min:"1" type:"string"`
}
@@ -14678,29 +14825,28 @@ type ReplicateKeyInput struct {
// A flag to indicate whether to bypass the key policy lockout safety check.
//
- // Setting this value to true increases the risk that the CMK becomes unmanageable.
+ // Setting this value to true increases the risk that the KMS key becomes unmanageable.
// Do not set this value to true indiscriminately.
//
// For more information, refer to the scenario in the Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-root-enable-iam)
- // section in the AWS Key Management Service Developer Guide.
+ // section in the Key Management Service Developer Guide.
//
// Use this parameter only when you intend to prevent the principal that is
- // making the request from making a subsequent PutKeyPolicy request on the CMK.
+ // making the request from making a subsequent PutKeyPolicy request on the KMS
+ // key.
//
// The default value is false.
BypassPolicyLockoutSafetyCheck *bool `type:"boolean"`
- // A description of the CMK. Use a description that helps you decide whether
- // the CMK is appropriate for a task. The default value is an empty string (no
- // description).
+ // A description of the KMS key. The default value is an empty string (no description).
//
// The description is not a shared property of multi-Region keys. You can specify
// the same description or a different description for each key in a set of
- // related multi-Region keys. AWS KMS does not synchronize this property.
+ // related multi-Region keys. KMS does not synchronize this property.
Description *string `type:"string"`
// Identifies the multi-Region primary key that is being replicated. To determine
- // whether a CMK is a multi-Region primary key, use the DescribeKey operation
+ // whether a KMS key is a multi-Region primary key, use the DescribeKey operation
// to check the value of the MultiRegionKeyType property.
//
// Specify the key ID or key ARN of a multi-Region primary key.
@@ -14711,52 +14857,54 @@ type ReplicateKeyInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/mrk-1234abcd12ab34cd56ef1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
- // The key policy to attach to the CMK. This parameter is optional. If you do
- // not provide a key policy, AWS KMS attaches the default key policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default)
- // to the CMK.
+ // The key policy to attach to the KMS key. This parameter is optional. If you
+ // do not provide a key policy, KMS attaches the default key policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default)
+ // to the KMS key.
//
// The key policy is not a shared property of multi-Region keys. You can specify
// the same key policy or a different key policy for each key in a set of related
- // multi-Region keys. AWS KMS does not synchronize this property.
+ // multi-Region keys. KMS does not synchronize this property.
//
// If you provide a key policy, it must meet the following criteria:
//
// * If you don't set BypassPolicyLockoutSafetyCheck to true, the key policy
- // must give the caller kms:PutKeyPolicy permission on the replica CMK. This
- // reduces the risk that the CMK becomes unmanageable. For more information,
+ // must give the caller kms:PutKeyPolicy permission on the replica key. This
+ // reduces the risk that the KMS key becomes unmanageable. For more information,
// refer to the scenario in the Default Key Policy (https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html#key-policy-default-allow-root-enable-iam)
- // section of the AWS Key Management Service Developer Guide .
+ // section of the Key Management Service Developer Guide .
//
// * Each statement in the key policy must contain one or more principals.
- // The principals in the key policy must exist and be visible to AWS KMS.
- // When you create a new AWS principal (for example, an IAM user or role),
- // you might need to enforce a delay before including the new principal in
- // a key policy because the new principal might not be immediately visible
- // to AWS KMS. For more information, see Changes that I make are not always
- // immediately visible (https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_eventual-consistency)
- // in the AWS Identity and Access Management User Guide.
+ // The principals in the key policy must exist and be visible to KMS. When
+ // you create a new Amazon Web Services principal (for example, an IAM user
+ // or role), you might need to enforce a delay before including the new principal
+ // in a key policy because the new principal might not be immediately visible
+ // to KMS. For more information, see Changes that I make are not always immediately
+ // visible (https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_general.html#troubleshoot_general_eventual-consistency)
+ // in the Identity and Access Management User Guide .
//
// * The key policy size quota is 32 kilobytes (32768 bytes).
Policy *string `min:"1" type:"string"`
- // The Region ID of the AWS Region for this replica key.
+ // The Region ID of the Amazon Web Services Region for this replica key.
//
- // Enter the Region ID, such as us-east-1 or ap-southeast-2. For a list of AWS
- // Regions in which AWS KMS is supported, see AWS KMS service endpoints (https://docs.aws.amazon.com/general/latest/gr/kms.html#kms_region)
- // in the Amazon Web Services General Reference.
+ // Enter the Region ID, such as us-east-1 or ap-southeast-2. For a list of Amazon
+ // Web Services Regions in which KMS is supported, see KMS service endpoints
+ // (https://docs.aws.amazon.com/general/latest/gr/kms.html#kms_region) in the
+ // Amazon Web Services General Reference.
//
- // The replica must be in a different AWS Region than its primary key and other
- // replicas of that primary key, but in the same AWS partition. AWS KMS must
- // be available in the replica Region. If the Region is not enabled by default,
- // the AWS account must be enabled in the Region.
+ // The replica must be in a different Amazon Web Services Region than its primary
+ // key and other replicas of that primary key, but in the same Amazon Web Services
+ // partition. KMS must be available in the replica Region. If the Region is
+ // not enabled by default, the Amazon Web Services account must be enabled in
+ // the Region.
//
- // For information about AWS partitions, see Amazon Resource Names (ARNs) in
- // the Amazon Web Services General Reference. (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)
+ // For information about Amazon Web Services partitions, see Amazon Resource
+ // Names (ARNs) in the Amazon Web Services General Reference. (https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html)
// For information about enabling and disabling Regions, see Enabling a Region
// (https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable)
// and Disabling a Region (https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-disable)
@@ -14766,28 +14914,30 @@ type ReplicateKeyInput struct {
ReplicaRegion *string `min:"1" type:"string" required:"true"`
// Assigns one or more tags to the replica key. Use this parameter to tag the
- // CMK when it is created. To tag an existing CMK, use the TagResource operation.
+ // KMS key when it is created. To tag an existing KMS key, use the TagResource
+ // operation.
//
- // Tagging or untagging a CMK can allow or deny permission to the CMK. For details,
- // see Using ABAC in AWS KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
- // in the AWS Key Management Service Developer Guide.
+ // Tagging or untagging a KMS key can allow or deny permission to the KMS key.
+ // For details, see Using ABAC in KMS (https://docs.aws.amazon.com/kms/latest/developerguide/abac.html)
+ // in the Key Management Service Developer Guide.
//
// To use this parameter, you must have kms:TagResource (https://docs.aws.amazon.com/kms/latest/developerguide/kms-api-permissions-reference.html)
// permission in an IAM policy.
//
// Tags are not a shared property of multi-Region keys. You can specify the
// same tags or different tags for each key in a set of related multi-Region
- // keys. AWS KMS does not synchronize this property.
+ // keys. KMS does not synchronize this property.
//
// Each tag consists of a tag key and a tag value. Both the tag key and the
// tag value are required, but the tag value can be an empty (null) string.
- // You cannot have more than one tag on a CMK with the same tag key. If you
- // specify an existing tag key with a different tag value, AWS KMS replaces
+ // You cannot have more than one tag on a KMS key with the same tag key. If
+ // you specify an existing tag key with a different tag value, KMS replaces
// the current tag value with the specified one.
//
- // When you assign tags to an AWS resource, AWS generates a cost allocation
- // report with usage and costs aggregated by tags. Tags can also be used to
- // control access to a CMK. For details, see Tagging Keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
+ // When you add tags to an Amazon Web Services resource, Amazon Web Services
+ // generates a cost allocation report with usage and costs aggregated by tags.
+ // Tags can also be used to control access to a KMS key. For details, see Tagging
+ // Keys (https://docs.aws.amazon.com/kms/latest/developerguide/tagging-keys.html).
Tags []*Tag `type:"list"`
}
@@ -14875,11 +15025,11 @@ func (s *ReplicateKeyInput) SetTags(v []*Tag) *ReplicateKeyInput {
type ReplicateKeyOutput struct {
_ struct{} `type:"structure"`
- // Displays details about the new replica CMK, including its Amazon Resource
+ // Displays details about the new replica key, including its Amazon Resource
// Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
// and key state (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html).
- // It also includes the ARN and AWS Region of its primary key and other replica
- // keys.
+ // It also includes the ARN and Amazon Web Services Region of its primary key
+ // and other replica keys.
ReplicaKeyMetadata *KeyMetadata `type:"structure"`
// The key policy of the new replica key. The value is a key policy document
@@ -14934,11 +15084,11 @@ type RetireGrantInput struct {
// Only the CreateGrant operation returns a grant token. For details, see Grant
// token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
// and Eventual consistency (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#terms-eventual-consistency)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
GrantToken *string `min:"1" type:"string"`
- // The key ARN CMK associated with the grant. To find the key ARN, use the ListKeys
- // operation.
+ // The key ARN KMS key associated with the grant. To find the key ARN, use the
+ // ListKeys operation.
//
// For example: arn:aws:kms:us-east-2:444455556666:key/1234abcd-12ab-34cd-56ef-1234567890ab
KeyId *string `min:"1" type:"string"`
@@ -15014,11 +15164,11 @@ type RevokeGrantInput struct {
// GrantId is a required field
GrantId *string `min:"1" type:"string" required:"true"`
- // A unique identifier for the customer master key (CMK) associated with the
- // grant. To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // A unique identifier for the KMS key associated with the grant. To get the
+ // key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
- // Specify the key ID or key ARN of the CMK. To specify a CMK in a different
- // AWS account, you must use the key ARN.
+ // Specify the key ID or key ARN of the KMS key. To specify a KMS key in a different
+ // Amazon Web Services account, you must use the key ARN.
//
// For example:
//
@@ -15026,7 +15176,7 @@ type RevokeGrantInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -15093,9 +15243,9 @@ func (s RevokeGrantOutput) GoString() string {
type ScheduleKeyDeletionInput struct {
_ struct{} `type:"structure"`
- // The unique identifier of the customer master key (CMK) to delete.
+ // The unique identifier of the KMS key to delete.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -15103,15 +15253,15 @@ type ScheduleKeyDeletionInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
// The waiting period, specified in number of days. After the waiting period
- // ends, AWS KMS deletes the customer master key (CMK).
+ // ends, KMS deletes the KMS key.
//
- // If the CMK is a multi-Region primary key with replicas, the waiting period
+ // If the KMS key is a multi-Region primary key with replicas, the waiting period
// begins when the last of its replica keys is deleted. Otherwise, the waiting
// period begins immediately.
//
@@ -15164,27 +15314,27 @@ func (s *ScheduleKeyDeletionInput) SetPendingWindowInDays(v int64) *ScheduleKeyD
type ScheduleKeyDeletionOutput struct {
_ struct{} `type:"structure"`
- // The date and time after which AWS KMS deletes the customer master key (CMK).
+ // The date and time after which KMS deletes the KMS key.
//
- // If the CMK is a multi-Region primary key with replica keys, this field does
- // not appear. The deletion date for the primary key isn't known until its last
- // replica key is deleted.
+ // If the KMS key is a multi-Region primary key with replica keys, this field
+ // does not appear. The deletion date for the primary key isn't known until
+ // its last replica key is deleted.
DeletionDate *time.Time `type:"timestamp"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the CMK whose deletion is scheduled.
+ // of the KMS key whose deletion is scheduled.
KeyId *string `min:"1" type:"string"`
- // The current status of the CMK.
+ // The current status of the KMS key.
//
- // For more information about how key state affects the use of a CMK, see Key
- // state: Effect on your CMK (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
- // in the AWS Key Management Service Developer Guide.
+ // For more information about how key state affects the use of a KMS key, see
+ // Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+ // in the Key Management Service Developer Guide.
KeyState *string `type:"string" enum:"KeyState"`
- // The waiting period before the CMK is deleted.
+ // The waiting period before the KMS key is deleted.
//
- // If the CMK is a multi-Region primary key with replicas, the waiting period
+ // If the KMS key is a multi-Region primary key with replicas, the waiting period
// begins when the last of its replica keys is deleted. Otherwise, the waiting
// period begins immediately.
PendingWindowInDays *int64 `min:"1" type:"integer"`
@@ -15231,17 +15381,19 @@ type SignInput struct {
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Identifies an asymmetric CMK. AWS KMS uses the private key in the asymmetric
- // CMK to sign the message. The KeyUsage type of the CMK must be SIGN_VERIFY.
- // To find the KeyUsage of a CMK, use the DescribeKey operation.
+ // Identifies an asymmetric KMS key. KMS uses the private key in the asymmetric
+ // KMS key to sign the message. The KeyUsage type of the KMS key must be SIGN_VERIFY.
+ // To find the KeyUsage of a KMS key, use the DescribeKey operation.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -15253,8 +15405,8 @@ type SignInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -15262,23 +15414,23 @@ type SignInput struct {
// Specifies the message or message digest to sign. Messages can be 0-4096 bytes.
// To sign a larger message, provide the message digest.
//
- // If you provide a message, AWS KMS generates a hash digest of the message
- // and then signs it.
+ // If you provide a message, KMS generates a hash digest of the message and
+ // then signs it.
//
// Message is automatically base64 encoded/decoded by the SDK.
//
// Message is a required field
Message []byte `min:"1" type:"blob" required:"true" sensitive:"true"`
- // Tells AWS KMS whether the value of the Message parameter is a message or
- // message digest. The default value, RAW, indicates a message. To indicate
- // a message digest, enter DIGEST.
+ // Tells KMS whether the value of the Message parameter is a message or message
+ // digest. The default value, RAW, indicates a message. To indicate a message
+ // digest, enter DIGEST.
MessageType *string `type:"string" enum:"MessageType"`
// Specifies the signing algorithm to use when signing the message.
//
// Choose an algorithm that is compatible with the type and size of the specified
- // asymmetric CMK.
+ // asymmetric KMS key.
//
// SigningAlgorithm is a required field
SigningAlgorithm *string `type:"string" required:"true" enum:"SigningAlgorithmSpec"`
@@ -15353,7 +15505,7 @@ type SignOutput struct {
_ struct{} `type:"structure"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the asymmetric CMK that was used to sign the message.
+ // of the asymmetric KMS key that was used to sign the message.
KeyId *string `min:"1" type:"string"`
// The cryptographic signature that was generated for the message.
@@ -15367,8 +15519,8 @@ type SignOutput struct {
// This is the most commonly used signature format and is appropriate for
// most uses.
//
- // When you use the HTTP API or the AWS CLI, the value is Base64-encoded. Otherwise,
- // it is not Base64-encoded.
+ // When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded.
+ // Otherwise, it is not Base64-encoded.
//
// Signature is automatically base64 encoded/decoded by the SDK.
Signature []byte `min:"1" type:"blob"`
@@ -15410,7 +15562,7 @@ func (s *SignOutput) SetSigningAlgorithm(v string) *SignOutput {
//
// For information about the rules that apply to tag keys and tag values, see
// User-Defined Tag Restrictions (https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/allocation-tag-restrictions.html)
-// in the AWS Billing and Cost Management User Guide.
+// in the Amazon Web Services Billing and Cost Management User Guide.
type Tag struct {
_ struct{} `type:"structure"`
@@ -15525,9 +15677,9 @@ func (s *TagException) RequestID() string {
type TagResourceInput struct {
_ struct{} `type:"structure"`
- // Identifies a customer managed CMK in the account and Region.
+ // Identifies a customer managed key in the account and Region.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -15535,7 +15687,7 @@ type TagResourceInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -15545,8 +15697,8 @@ type TagResourceInput struct {
// Each tag consists of a tag key and a tag value. The tag value can be an empty
// (null) string.
//
- // You cannot have more than one tag on a CMK with the same tag key. If you
- // specify an existing tag key with a different tag value, AWS KMS replaces
+ // You cannot have more than one tag on a KMS key with the same tag key. If
+ // you specify an existing tag key with a different tag value, KMS replaces
// the current tag value with the specified one.
//
// Tags is a required field
@@ -15678,9 +15830,9 @@ func (s *UnsupportedOperationException) RequestID() string {
type UntagResourceInput struct {
_ struct{} `type:"structure"`
- // Identifies the CMK from which you are removing tags.
+ // Identifies the KMS key from which you are removing tags.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -15688,7 +15840,7 @@ type UntagResourceInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -15757,22 +15909,23 @@ func (s UntagResourceOutput) GoString() string {
type UpdateAliasInput struct {
_ struct{} `type:"structure"`
- // Identifies the alias that is changing its CMK. This value must begin with
- // alias/ followed by the alias name, such as alias/ExampleAlias. You cannot
+ // Identifies the alias that is changing its KMS key. This value must begin
+ // with alias/ followed by the alias name, such as alias/ExampleAlias. You cannot
// use UpdateAlias to change the alias name.
//
// AliasName is a required field
AliasName *string `min:"1" type:"string" required:"true"`
- // Identifies the customer managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk)
+ // Identifies the customer managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#customer-cmk)
// to associate with the alias. You don't have permission to associate an alias
- // with an AWS managed CMK (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
+ // with an Amazon Web Services managed key (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
//
- // The CMK must be in the same AWS account and Region as the alias. Also, the
- // new target CMK must be the same type as the current target CMK (both symmetric
- // or both asymmetric) and they must have the same key usage.
+ // The KMS key must be in the same Amazon Web Services account and Region as
+ // the alias. Also, the new target KMS key must be the same type as the current
+ // target KMS key (both symmetric or both asymmetric) and they must have the
+ // same key usage.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -15780,9 +15933,9 @@ type UpdateAliasInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
- // To verify that the alias is mapped to the correct CMK, use ListAliases.
+ // To verify that the alias is mapped to the correct KMS key, use ListAliases.
//
// TargetKeyId is a required field
TargetKeyId *string `min:"1" type:"string" required:"true"`
@@ -15849,7 +16002,7 @@ func (s UpdateAliasOutput) GoString() string {
type UpdateCustomKeyStoreInput struct {
_ struct{} `type:"structure"`
- // Associates the custom key store with a related AWS CloudHSM cluster.
+ // Associates the custom key store with a related CloudHSM cluster.
//
// Enter the cluster ID of the cluster that you used to create the custom key
// store or a cluster that shares a backup history and has the same cluster
@@ -15868,16 +16021,16 @@ type UpdateCustomKeyStoreInput struct {
// CustomKeyStoreId is a required field
CustomKeyStoreId *string `min:"1" type:"string" required:"true"`
- // Enter the current password of the kmsuser crypto user (CU) in the AWS CloudHSM
+ // Enter the current password of the kmsuser crypto user (CU) in the CloudHSM
// cluster that is associated with the custom key store.
//
- // This parameter tells AWS KMS the current password of the kmsuser crypto user
- // (CU). It does not set or change the password of any users in the AWS CloudHSM
+ // This parameter tells KMS the current password of the kmsuser crypto user
+ // (CU). It does not set or change the password of any users in the CloudHSM
// cluster.
KeyStorePassword *string `min:"7" type:"string" sensitive:"true"`
// Changes the friendly name of the custom key store to the value that you specify.
- // The custom key store name must be unique in the AWS account.
+ // The custom key store name must be unique in the Amazon Web Services account.
NewCustomKeyStoreName *string `min:"1" type:"string"`
}
@@ -15957,14 +16110,14 @@ func (s UpdateCustomKeyStoreOutput) GoString() string {
type UpdateKeyDescriptionInput struct {
_ struct{} `type:"structure"`
- // New description for the CMK.
+ // New description for the KMS key.
//
// Description is a required field
Description *string `type:"string" required:"true"`
- // Updates the description of the specified customer master key (CMK).
+ // Updates the description of the specified KMS key.
//
- // Specify the key ID or key ARN of the CMK.
+ // Specify the key ID or key ARN of the KMS key.
//
// For example:
//
@@ -15972,7 +16125,7 @@ type UpdateKeyDescriptionInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -16036,8 +16189,8 @@ func (s UpdateKeyDescriptionOutput) GoString() string {
type UpdatePrimaryRegionInput struct {
_ struct{} `type:"structure"`
- // Identifies the current primary key. When the operation completes, this CMK
- // will be a replica key.
+ // Identifies the current primary key. When the operation completes, this KMS
+ // key will be a replica key.
//
// Specify the key ID or key ARN of a multi-Region primary key.
//
@@ -16047,13 +16200,14 @@ type UpdatePrimaryRegionInput struct {
//
// * Key ARN: arn:aws:kms:us-east-2:111122223333:key/mrk-1234abcd12ab34cd56ef1234567890ab
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
- // The AWS Region of the new primary key. Enter the Region ID, such as us-east-1
- // or ap-southeast-2. There must be an existing replica key in this Region.
+ // The Amazon Web Services Region of the new primary key. Enter the Region ID,
+ // such as us-east-1 or ap-southeast-2. There must be an existing replica key
+ // in this Region.
//
// When the operation completes, the multi-Region key in this Region will be
// the primary key.
@@ -16127,17 +16281,19 @@ type VerifyInput struct {
//
// Use a grant token when your permission to call this operation comes from
// a new grant that has not yet achieved eventual consistency. For more information,
- // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#grant_token)
- // in the AWS Key Management Service Developer Guide.
+ // see Grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grants.html#grant_token)
+ // and Using a grant token (https://docs.aws.amazon.com/kms/latest/developerguide/grant-manage.html#using-grant-token)
+ // in the Key Management Service Developer Guide.
GrantTokens []*string `type:"list"`
- // Identifies the asymmetric CMK that will be used to verify the signature.
- // This must be the same CMK that was used to generate the signature. If you
- // specify a different CMK, the signature verification fails.
+ // Identifies the asymmetric KMS key that will be used to verify the signature.
+ // This must be the same KMS key that was used to generate the signature. If
+ // you specify a different KMS key, the signature verification fails.
//
- // To specify a CMK, use its key ID, key ARN, alias name, or alias ARN. When
- // using an alias name, prefix it with "alias/". To specify a CMK in a different
- // AWS account, you must use the key ARN or alias ARN.
+ // To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN.
+ // When using an alias name, prefix it with "alias/". To specify a KMS key in
+ // a different Amazon Web Services account, you must use the key ARN or alias
+ // ARN.
//
// For example:
//
@@ -16149,8 +16305,8 @@ type VerifyInput struct {
//
// * Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
//
- // To get the key ID and key ARN for a CMK, use ListKeys or DescribeKey. To
- // get the alias name and alias ARN, use ListAliases.
+ // To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.
+ // To get the alias name and alias ARN, use ListAliases.
//
// KeyId is a required field
KeyId *string `min:"1" type:"string" required:"true"`
@@ -16168,9 +16324,9 @@ type VerifyInput struct {
// Message is a required field
Message []byte `min:"1" type:"blob" required:"true" sensitive:"true"`
- // Tells AWS KMS whether the value of the Message parameter is a message or
- // message digest. The default value, RAW, indicates a message. To indicate
- // a message digest, enter DIGEST.
+ // Tells KMS whether the value of the Message parameter is a message or message
+ // digest. The default value, RAW, indicates a message. To indicate a message
+ // digest, enter DIGEST.
//
// Use the DIGEST value only when the value of the Message parameter is a message
// digest. If you use the DIGEST value with a raw message, the security of the
@@ -16272,7 +16428,7 @@ type VerifyOutput struct {
_ struct{} `type:"structure"`
// The Amazon Resource Name (key ARN (https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#key-id-key-ARN))
- // of the asymmetric CMK that was used to verify the signature.
+ // of the asymmetric KMS key that was used to verify the signature.
KeyId *string `min:"1" type:"string"`
// A Boolean value that indicates whether the signature was verified. A value
@@ -16613,6 +16769,46 @@ func KeyManagerType_Values() []string {
}
}
+const (
+ // KeySpecRsa2048 is a KeySpec enum value
+ KeySpecRsa2048 = "RSA_2048"
+
+ // KeySpecRsa3072 is a KeySpec enum value
+ KeySpecRsa3072 = "RSA_3072"
+
+ // KeySpecRsa4096 is a KeySpec enum value
+ KeySpecRsa4096 = "RSA_4096"
+
+ // KeySpecEccNistP256 is a KeySpec enum value
+ KeySpecEccNistP256 = "ECC_NIST_P256"
+
+ // KeySpecEccNistP384 is a KeySpec enum value
+ KeySpecEccNistP384 = "ECC_NIST_P384"
+
+ // KeySpecEccNistP521 is a KeySpec enum value
+ KeySpecEccNistP521 = "ECC_NIST_P521"
+
+ // KeySpecEccSecgP256k1 is a KeySpec enum value
+ KeySpecEccSecgP256k1 = "ECC_SECG_P256K1"
+
+ // KeySpecSymmetricDefault is a KeySpec enum value
+ KeySpecSymmetricDefault = "SYMMETRIC_DEFAULT"
+)
+
+// KeySpec_Values returns all elements of the KeySpec enum
+func KeySpec_Values() []string {
+ return []string{
+ KeySpecRsa2048,
+ KeySpecRsa3072,
+ KeySpecRsa4096,
+ KeySpecEccNistP256,
+ KeySpecEccNistP384,
+ KeySpecEccNistP521,
+ KeySpecEccSecgP256k1,
+ KeySpecSymmetricDefault,
+ }
+}
+
const (
// KeyStateCreating is a KeyState enum value
KeyStateCreating = "Creating"
diff --git a/service/kms/doc.go b/service/kms/doc.go
index c4c21250201..64050c2253a 100644
--- a/service/kms/doc.go
+++ b/service/kms/doc.go
@@ -3,21 +3,26 @@
// Package kms provides the client and types for making API
// requests to AWS Key Management Service.
//
-// AWS Key Management Service (AWS KMS) is an encryption and key management
-// web service. This guide describes the AWS KMS operations that you can call
-// programmatically. For general information about AWS KMS, see the AWS Key
-// Management Service Developer Guide (https://docs.aws.amazon.com/kms/latest/developerguide/).
-//
-// AWS provides SDKs that consist of libraries and sample code for various programming
-// languages and platforms (Java, Ruby, .Net, macOS, Android, etc.). The SDKs
-// provide a convenient way to create programmatic access to AWS KMS and other
-// AWS services. For example, the SDKs take care of tasks such as signing requests
-// (see below), managing errors, and retrying requests automatically. For more
-// information about the AWS SDKs, including how to download and install them,
-// see Tools for Amazon Web Services (http://aws.amazon.com/tools/).
-//
-// We recommend that you use the AWS SDKs to make programmatic API calls to
-// AWS KMS.
+// Key Management Service (KMS) is an encryption and key management web service.
+// This guide describes the KMS operations that you can call programmatically.
+// For general information about KMS, see the Key Management Service Developer
+// Guide (https://docs.aws.amazon.com/kms/latest/developerguide/).
+//
+// KMS is replacing the term customer master key (CMK) with KMS key and KMS
+// key. The concept has not changed. To prevent breaking changes, KMS is keeping
+// some variations of this term.
+//
+// Amazon Web Services provides SDKs that consist of libraries and sample code
+// for various programming languages and platforms (Java, Ruby, .Net, macOS,
+// Android, etc.). The SDKs provide a convenient way to create programmatic
+// access to KMS and other Amazon Web Services services. For example, the SDKs
+// take care of tasks such as signing requests (see below), managing errors,
+// and retrying requests automatically. For more information about the Amazon
+// Web Services SDKs, including how to download and install them, see Tools
+// for Amazon Web Services (http://aws.amazon.com/tools/).
+//
+// We recommend that you use the Amazon Web Services SDKs to make programmatic
+// API calls to KMS.
//
// Clients must support TLS (Transport Layer Security) 1.0. We recommend TLS
// 1.2. Clients must also support cipher suites with Perfect Forward Secrecy
@@ -28,30 +33,31 @@
// Signing Requests
//
// Requests must be signed by using an access key ID and a secret access key.
-// We strongly recommend that you do not use your AWS account (root) access
-// key ID and secret key for everyday work with AWS KMS. Instead, use the access
-// key ID and secret access key for an IAM user. You can also use the AWS Security
-// Token Service to generate temporary security credentials that you can use
-// to sign requests.
+// We strongly recommend that you do not use your Amazon Web Services account
+// (root) access key ID and secret key for everyday work with KMS. Instead,
+// use the access key ID and secret access key for an IAM user. You can also
+// use the Amazon Web Services Security Token Service to generate temporary
+// security credentials that you can use to sign requests.
//
-// All AWS KMS operations require Signature Version 4 (https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html).
+// All KMS operations require Signature Version 4 (https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html).
//
// Logging API Requests
//
-// AWS KMS supports AWS CloudTrail, a service that logs AWS API calls and related
-// events for your AWS account and delivers them to an Amazon S3 bucket that
-// you specify. By using the information collected by CloudTrail, you can determine
-// what requests were made to AWS KMS, who made the request, when it was made,
-// and so on. To learn more about CloudTrail, including how to turn it on and
-// find your log files, see the AWS CloudTrail User Guide (https://docs.aws.amazon.com/awscloudtrail/latest/userguide/).
+// KMS supports CloudTrail, a service that logs Amazon Web Services API calls
+// and related events for your Amazon Web Services account and delivers them
+// to an Amazon S3 bucket that you specify. By using the information collected
+// by CloudTrail, you can determine what requests were made to KMS, who made
+// the request, when it was made, and so on. To learn more about CloudTrail,
+// including how to turn it on and find your log files, see the CloudTrail User
+// Guide (https://docs.aws.amazon.com/awscloudtrail/latest/userguide/).
//
// Additional Resources
//
// For more information about credentials and request signing, see the following:
//
-// * AWS Security Credentials (https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html)
+// * Amazon Web Services Security Credentials (https://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html)
// - This topic provides general information about the types of credentials
-// used for accessing AWS.
+// used to access Amazon Web Services.
//
// * Temporary Security Credentials (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html)
// - This section of the IAM User Guide describes how to create and use temporary
diff --git a/service/kms/errors.go b/service/kms/errors.go
index 911bf576ebf..7f5a1f0ba82 100644
--- a/service/kms/errors.go
+++ b/service/kms/errors.go
@@ -18,10 +18,10 @@ const (
// ErrCodeCloudHsmClusterInUseException for service response error code
// "CloudHsmClusterInUseException".
//
- // The request was rejected because the specified AWS CloudHSM cluster is already
+ // The request was rejected because the specified CloudHSM cluster is already
// associated with a custom key store or it shares a backup history with a cluster
// that is associated with a custom key store. Each custom key store must be
- // associated with a different AWS CloudHSM cluster.
+ // associated with a different CloudHSM cluster.
//
// Clusters that share a backup history have the same cluster certificate. To
// view the cluster certificate of a cluster, use the DescribeClusters (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_DescribeClusters.html)
@@ -31,8 +31,8 @@ const (
// ErrCodeCloudHsmClusterInvalidConfigurationException for service response error code
// "CloudHsmClusterInvalidConfigurationException".
//
- // The request was rejected because the associated AWS CloudHSM cluster did
- // not meet the configuration requirements for a custom key store.
+ // The request was rejected because the associated CloudHSM cluster did not
+ // meet the configuration requirements for a custom key store.
//
// * The cluster must be configured with private subnets in at least two
// different Availability Zones in the Region.
@@ -47,46 +47,44 @@ const (
// operation.
//
// * The cluster must contain at least as many HSMs as the operation requires.
- // To add HSMs, use the AWS CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
+ // To add HSMs, use the CloudHSM CreateHsm (https://docs.aws.amazon.com/cloudhsm/latest/APIReference/API_CreateHsm.html)
// operation. For the CreateCustomKeyStore, UpdateCustomKeyStore, and CreateKey
- // operations, the AWS CloudHSM cluster must have at least two active HSMs,
- // each in a different Availability Zone. For the ConnectCustomKeyStore operation,
- // the AWS CloudHSM must contain at least one active HSM.
- //
- // For information about the requirements for an AWS CloudHSM cluster that is
- // associated with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
- // in the AWS Key Management Service Developer Guide. For information about
- // creating a private subnet for an AWS CloudHSM cluster, see Create a Private
- // Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
- // in the AWS CloudHSM User Guide. For information about cluster security groups,
+ // operations, the CloudHSM cluster must have at least two active HSMs, each
+ // in a different Availability Zone. For the ConnectCustomKeyStore operation,
+ // the CloudHSM must contain at least one active HSM.
+ //
+ // For information about the requirements for an CloudHSM cluster that is associated
+ // with a custom key store, see Assemble the Prerequisites (https://docs.aws.amazon.com/kms/latest/developerguide/create-keystore.html#before-keystore)
+ // in the Key Management Service Developer Guide. For information about creating
+ // a private subnet for an CloudHSM cluster, see Create a Private Subnet (https://docs.aws.amazon.com/cloudhsm/latest/userguide/create-subnets.html)
+ // in the CloudHSM User Guide. For information about cluster security groups,
// see Configure a Default Security Group (https://docs.aws.amazon.com/cloudhsm/latest/userguide/configure-sg.html)
- // in the AWS CloudHSM User Guide .
+ // in the CloudHSM User Guide .
ErrCodeCloudHsmClusterInvalidConfigurationException = "CloudHsmClusterInvalidConfigurationException"
// ErrCodeCloudHsmClusterNotActiveException for service response error code
// "CloudHsmClusterNotActiveException".
//
- // The request was rejected because the AWS CloudHSM cluster that is associated
+ // The request was rejected because the CloudHSM cluster that is associated
// with the custom key store is not active. Initialize and activate the cluster
// and try the command again. For detailed instructions, see Getting Started
// (https://docs.aws.amazon.com/cloudhsm/latest/userguide/getting-started.html)
- // in the AWS CloudHSM User Guide.
+ // in the CloudHSM User Guide.
ErrCodeCloudHsmClusterNotActiveException = "CloudHsmClusterNotActiveException"
// ErrCodeCloudHsmClusterNotFoundException for service response error code
// "CloudHsmClusterNotFoundException".
//
- // The request was rejected because AWS KMS cannot find the AWS CloudHSM cluster
- // with the specified cluster ID. Retry the request with a different cluster
- // ID.
+ // The request was rejected because KMS cannot find the CloudHSM cluster with
+ // the specified cluster ID. Retry the request with a different cluster ID.
ErrCodeCloudHsmClusterNotFoundException = "CloudHsmClusterNotFoundException"
// ErrCodeCloudHsmClusterNotRelatedException for service response error code
// "CloudHsmClusterNotRelatedException".
//
- // The request was rejected because the specified AWS CloudHSM cluster has a
- // different cluster certificate than the original cluster. You cannot use the
- // operation to specify an unrelated cluster.
+ // The request was rejected because the specified CloudHSM cluster has a different
+ // cluster certificate than the original cluster. You cannot use the operation
+ // to specify an unrelated cluster.
//
// Specify a cluster that shares a backup history with the original cluster.
// This includes clusters that were created from a backup of the current cluster,
@@ -101,10 +99,10 @@ const (
// ErrCodeCustomKeyStoreHasCMKsException for service response error code
// "CustomKeyStoreHasCMKsException".
//
- // The request was rejected because the custom key store contains AWS KMS customer
- // master keys (CMKs). After verifying that you do not need to use the CMKs,
- // use the ScheduleKeyDeletion operation to delete the CMKs. After they are
- // deleted, you can delete the custom key store.
+ // The request was rejected because the custom key store contains KMS keys.
+ // After verifying that you do not need to use the KMS keys, use the ScheduleKeyDeletion
+ // operation to delete the KMS keys. After they are deleted, you can delete
+ // the custom key store.
ErrCodeCustomKeyStoreHasCMKsException = "CustomKeyStoreHasCMKsException"
// ErrCodeCustomKeyStoreInvalidStateException for service response error code
@@ -140,7 +138,7 @@ const (
// ErrCodeCustomKeyStoreNotFoundException for service response error code
// "CustomKeyStoreNotFoundException".
//
- // The request was rejected because AWS KMS cannot find a custom key store with
+ // The request was rejected because KMS cannot find a custom key store with
// the specified key store name or ID.
ErrCodeCustomKeyStoreNotFoundException = "CustomKeyStoreNotFoundException"
@@ -154,7 +152,7 @@ const (
// ErrCodeDisabledException for service response error code
// "DisabledException".
//
- // The request was rejected because the specified CMK is not enabled.
+ // The request was rejected because the specified KMS key is not enabled.
ErrCodeDisabledException = "DisabledException"
// ErrCodeExpiredImportTokenException for service response error code
@@ -168,9 +166,9 @@ const (
// ErrCodeIncorrectKeyException for service response error code
// "IncorrectKeyException".
//
- // The request was rejected because the specified CMK cannot decrypt the data.
- // The KeyId in a Decrypt request and the SourceKeyId in a ReEncrypt request
- // must identify the same CMK that was used to encrypt the ciphertext.
+ // The request was rejected because the specified KMS key cannot decrypt the
+ // data. The KeyId in a Decrypt request and the SourceKeyId in a ReEncrypt request
+ // must identify the same KMS key that was used to encrypt the ciphertext.
ErrCodeIncorrectKeyException = "IncorrectKeyException"
// ErrCodeIncorrectKeyMaterialException for service response error code
@@ -178,14 +176,14 @@ const (
//
// The request was rejected because the key material in the request is, expired,
// invalid, or is not the same key material that was previously imported into
- // this customer master key (CMK).
+ // this KMS key.
ErrCodeIncorrectKeyMaterialException = "IncorrectKeyMaterialException"
// ErrCodeIncorrectTrustAnchorException for service response error code
// "IncorrectTrustAnchorException".
//
// The request was rejected because the trust anchor certificate in the request
- // is not the trust anchor certificate for the specified AWS CloudHSM cluster.
+ // is not the trust anchor certificate for the specified CloudHSM cluster.
//
// When you initialize the cluster (https://docs.aws.amazon.com/cloudhsm/latest/userguide/initialize-cluster.html#sign-csr),
// you create the trust anchor certificate and save it in the customerCA.crt
@@ -220,8 +218,8 @@ const (
// the ciphertext, such as the encryption context, is corrupted, missing, or
// otherwise invalid.
//
- // From the ImportKeyMaterial operation, the request was rejected because AWS
- // KMS could not decrypt the encrypted (wrapped) key material.
+ // From the ImportKeyMaterial operation, the request was rejected because KMS
+ // could not decrypt the encrypted (wrapped) key material.
ErrCodeInvalidCiphertextException = "InvalidCiphertextException"
// ErrCodeInvalidGrantIdException for service response error code
@@ -240,7 +238,7 @@ const (
// "InvalidImportTokenException".
//
// The request was rejected because the provided import token is invalid or
- // is associated with a different customer master key (CMK).
+ // is associated with a different KMS key.
ErrCodeInvalidImportTokenException = "InvalidImportTokenException"
// ErrCodeInvalidKeyUsageException for service response error code
@@ -248,17 +246,18 @@ const (
//
// The request was rejected for one of the following reasons:
//
- // * The KeyUsage value of the CMK is incompatible with the API operation.
+ // * The KeyUsage value of the KMS key is incompatible with the API operation.
//
// * The encryption algorithm or signing algorithm specified for the operation
- // is incompatible with the type of key material in the CMK (CustomerMasterKeySpec).
+ // is incompatible with the type of key material in the KMS key (KeySpec).
//
// For encrypting, decrypting, re-encrypting, and generating data keys, the
// KeyUsage must be ENCRYPT_DECRYPT. For signing and verifying, the KeyUsage
- // must be SIGN_VERIFY. To find the KeyUsage of a CMK, use the DescribeKey operation.
+ // must be SIGN_VERIFY. To find the KeyUsage of a KMS key, use the DescribeKey
+ // operation.
//
- // To find the encryption or signing algorithms supported for a particular CMK,
- // use the DescribeKey operation.
+ // To find the encryption or signing algorithms supported for a particular KMS
+ // key, use the DescribeKey operation.
ErrCodeInvalidKeyUsageException = "InvalidKeyUsageException"
// ErrCodeInvalidMarkerException for service response error code
@@ -274,9 +273,9 @@ const (
// The request was rejected because the state of the specified resource is not
// valid for this request.
//
- // For more information about how key state affects the use of a CMK, see How
- // Key State Affects Use of a Customer Master Key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
- // in the AWS Key Management Service Developer Guide .
+ // For more information about how key state affects the use of a KMS key, see
+ // Key state: Effect on your KMS key (https://docs.aws.amazon.com/kms/latest/developerguide/key-state.html)
+ // in the Key Management Service Developer Guide .
ErrCodeInvalidStateException = "KMSInvalidStateException"
// ErrCodeKMSInvalidSignatureException for service response error code
@@ -284,14 +283,14 @@ const (
//
// The request was rejected because the signature verification failed. Signature
// verification fails when it cannot confirm that signature was produced by
- // signing the specified message with the specified CMK and signing algorithm.
+ // signing the specified message with the specified KMS key and signing algorithm.
ErrCodeKMSInvalidSignatureException = "KMSInvalidSignatureException"
// ErrCodeKeyUnavailableException for service response error code
// "KeyUnavailableException".
//
- // The request was rejected because the specified CMK was not available. You
- // can retry the request.
+ // The request was rejected because the specified KMS key was not available.
+ // You can retry the request.
ErrCodeKeyUnavailableException = "KeyUnavailableException"
// ErrCodeLimitExceededException for service response error code
@@ -299,7 +298,7 @@ const (
//
// The request was rejected because a quota was exceeded. For more information,
// see Quotas (https://docs.aws.amazon.com/kms/latest/developerguide/limits.html)
- // in the AWS Key Management Service Developer Guide.
+ // in the Key Management Service Developer Guide.
ErrCodeLimitExceededException = "LimitExceededException"
// ErrCodeMalformedPolicyDocumentException for service response error code
diff --git a/service/kms/examples_test.go b/service/kms/examples_test.go
index 8194f13d998..713919d0369 100644
--- a/service/kms/examples_test.go
+++ b/service/kms/examples_test.go
@@ -25,9 +25,9 @@ func parseTime(layout, value string) *time.Time {
return &t
}
-// To cancel deletion of a customer master key (CMK)
+// To cancel deletion of a KMS key
//
-// The following example cancels deletion of the specified CMK.
+// The following example cancels deletion of the specified KMS key.
func ExampleKMS_CancelKeyDeletion_shared00() {
svc := kms.New(session.New())
input := &kms.CancelKeyDeletionInput{
@@ -64,7 +64,7 @@ func ExampleKMS_CancelKeyDeletion_shared00() {
// To create an alias
//
-// The following example creates an alias for the specified customer master key (CMK).
+// The following example creates an alias for the specified KMS key.
func ExampleKMS_CreateAlias_shared00() {
svc := kms.New(session.New())
input := &kms.CreateAliasInput{
@@ -107,7 +107,7 @@ func ExampleKMS_CreateAlias_shared00() {
// To create a grant
//
// The following example creates a grant that allows the specified IAM role to encrypt
-// data with the specified customer master key (CMK).
+// data with the specified KMS key.
func ExampleKMS_CreateGrant_shared00() {
svc := kms.New(session.New())
input := &kms.CreateGrantInput{
@@ -153,9 +153,9 @@ func ExampleKMS_CreateGrant_shared00() {
fmt.Println(result)
}
-// To create a customer master key (CMK)
+// To create a KMS key
//
-// The following example creates a CMK.
+// The following example creates a KMS key.
func ExampleKMS_CreateKey_shared00() {
svc := kms.New(session.New())
input := &kms.CreateKeyInput{
@@ -207,8 +207,7 @@ func ExampleKMS_CreateKey_shared00() {
// To decrypt data
//
-// The following example decrypts data that was encrypted with a customer master key
-// (CMK) in AWS KMS.
+// The following example decrypts data that was encrypted with a KMS key.
func ExampleKMS_Decrypt_shared00() {
svc := kms.New(session.New())
input := &kms.DecryptInput{
@@ -291,8 +290,7 @@ func ExampleKMS_DeleteAlias_shared00() {
// To delete imported key material
//
-// The following example deletes the imported key material from the specified customer
-// master key (CMK).
+// The following example deletes the imported key material from the specified KMS key.
func ExampleKMS_DeleteImportedKeyMaterial_shared00() {
svc := kms.New(session.New())
input := &kms.DeleteImportedKeyMaterialInput{
@@ -329,9 +327,9 @@ func ExampleKMS_DeleteImportedKeyMaterial_shared00() {
fmt.Println(result)
}
-// To get details about a customer master key (CMK)
+// To get details about a KMS key
//
-// The following example gets metadata about a symmetric CMK.
+// The following example gets metadata about a symmetric KMS key.
func ExampleKMS_DescribeKey_shared00() {
svc := kms.New(session.New())
input := &kms.DescribeKeyInput{
@@ -364,9 +362,9 @@ func ExampleKMS_DescribeKey_shared00() {
fmt.Println(result)
}
-// To disable a customer master key (CMK)
+// To disable a KMS key
//
-// The following example disables the specified CMK.
+// The following example disables the specified KMS key.
func ExampleKMS_DisableKey_shared00() {
svc := kms.New(session.New())
input := &kms.DisableKeyInput{
@@ -404,7 +402,7 @@ func ExampleKMS_DisableKey_shared00() {
// To disable automatic rotation of key material
//
// The following example disables automatic annual rotation of the key material for
-// the specified CMK.
+// the specified KMS key.
func ExampleKMS_DisableKeyRotation_shared00() {
svc := kms.New(session.New())
input := &kms.DisableKeyRotationInput{
@@ -443,9 +441,9 @@ func ExampleKMS_DisableKeyRotation_shared00() {
fmt.Println(result)
}
-// To enable a customer master key (CMK)
+// To enable a KMS key
//
-// The following example enables the specified CMK.
+// The following example enables the specified KMS key.
func ExampleKMS_EnableKey_shared00() {
svc := kms.New(session.New())
input := &kms.EnableKeyInput{
@@ -485,7 +483,7 @@ func ExampleKMS_EnableKey_shared00() {
// To enable automatic rotation of key material
//
// The following example enables automatic annual rotation of the key material for the
-// specified CMK.
+// specified KMS key.
func ExampleKMS_EnableKeyRotation_shared00() {
svc := kms.New(session.New())
input := &kms.EnableKeyRotationInput{
@@ -526,7 +524,7 @@ func ExampleKMS_EnableKeyRotation_shared00() {
// To encrypt data
//
-// The following example encrypts data with the specified customer master key (CMK).
+// The following example encrypts data with the specified KMS key.
func ExampleKMS_Encrypt_shared00() {
svc := kms.New(session.New())
input := &kms.EncryptInput{
@@ -572,7 +570,7 @@ func ExampleKMS_Encrypt_shared00() {
//
// The following example generates a 256-bit symmetric data encryption key (data key)
// in two formats. One is the unencrypted (plainext) data key, and the other is the
-// data key encrypted with the specified customer master key (CMK).
+// data key encrypted with the specified KMS key.
func ExampleKMS_GenerateDataKey_shared00() {
svc := kms.New(session.New())
input := &kms.GenerateDataKeyInput{
@@ -617,8 +615,7 @@ func ExampleKMS_GenerateDataKey_shared00() {
// To generate an encrypted data key
//
// The following example generates an encrypted copy of a 256-bit symmetric data encryption
-// key (data key). The data key is encrypted with the specified customer master key
-// (CMK).
+// key (data key). The data key is encrypted with the specified KMS key.
func ExampleKMS_GenerateDataKeyWithoutPlaintext_shared00() {
svc := kms.New(session.New())
input := &kms.GenerateDataKeyWithoutPlaintextInput{
@@ -662,7 +659,7 @@ func ExampleKMS_GenerateDataKeyWithoutPlaintext_shared00() {
// To generate random data
//
-// The following example uses AWS KMS to generate 32 bytes of random data.
+// The following example generates 32 bytes of random data.
func ExampleKMS_GenerateRandom_shared00() {
svc := kms.New(session.New())
input := &kms.GenerateRandomInput{
@@ -697,8 +694,7 @@ func ExampleKMS_GenerateRandom_shared00() {
// To retrieve a key policy
//
-// The following example retrieves the key policy for the specified customer master
-// key (CMK).
+// The following example retrieves the key policy for the specified KMS key.
func ExampleKMS_GetKeyPolicy_shared00() {
svc := kms.New(session.New())
input := &kms.GetKeyPolicyInput{
@@ -734,10 +730,10 @@ func ExampleKMS_GetKeyPolicy_shared00() {
fmt.Println(result)
}
-// To retrieve the rotation status for a customer master key (CMK)
+// To retrieve the rotation status for a KMS key
//
// The following example retrieves the status of automatic annual rotation of the key
-// material for the specified CMK.
+// material for the specified KMS key.
func ExampleKMS_GetKeyRotationStatus_shared00() {
svc := kms.New(session.New())
input := &kms.GetKeyRotationStatusInput{
@@ -774,10 +770,10 @@ func ExampleKMS_GetKeyRotationStatus_shared00() {
fmt.Println(result)
}
-// To retrieve the public key and import token for a customer master key (CMK)
+// To retrieve the public key and import token for a KMS key
//
// The following example retrieves the public key and import token for the specified
-// CMK.
+// KMS key.
func ExampleKMS_GetParametersForImport_shared00() {
svc := kms.New(session.New())
input := &kms.GetParametersForImportInput{
@@ -816,9 +812,9 @@ func ExampleKMS_GetParametersForImport_shared00() {
fmt.Println(result)
}
-// To import key material into a customer master key (CMK)
+// To import key material into a KMS key
//
-// The following example imports key material into the specified CMK.
+// The following example imports key material into the specified KMS key.
func ExampleKMS_ImportKeyMaterial_shared00() {
svc := kms.New(session.New())
input := &kms.ImportKeyMaterialInput{
@@ -901,9 +897,9 @@ func ExampleKMS_ListAliases_shared00() {
fmt.Println(result)
}
-// To list grants for a customer master key (CMK)
+// To list grants for a KMS key
//
-// The following example lists grants for the specified CMK.
+// The following example lists grants for the specified KMS key.
func ExampleKMS_ListGrants_shared00() {
svc := kms.New(session.New())
input := &kms.ListGrantsInput{
@@ -942,9 +938,9 @@ func ExampleKMS_ListGrants_shared00() {
fmt.Println(result)
}
-// To list key policies for a customer master key (CMK)
+// To list key policies for a KMS key
//
-// The following example lists key policies for the specified CMK.
+// The following example lists key policies for the specified KMS key.
func ExampleKMS_ListKeyPolicies_shared00() {
svc := kms.New(session.New())
input := &kms.ListKeyPoliciesInput{
@@ -979,9 +975,9 @@ func ExampleKMS_ListKeyPolicies_shared00() {
fmt.Println(result)
}
-// To list customer master keys (CMKs)
+// To list KMS keys
//
-// The following example lists CMKs.
+// The following example lists KMS keys.
func ExampleKMS_ListKeys_shared00() {
svc := kms.New(session.New())
input := &kms.ListKeysInput{}
@@ -1010,9 +1006,9 @@ func ExampleKMS_ListKeys_shared00() {
fmt.Println(result)
}
-// To list tags for a customer master key (CMK)
+// To list tags for a KMS key
//
-// The following example lists tags for a CMK.
+// The following example lists tags for a KMS key.
func ExampleKMS_ListResourceTags_shared00() {
svc := kms.New(session.New())
input := &kms.ListResourceTagsInput{
@@ -1083,9 +1079,9 @@ func ExampleKMS_ListRetirableGrants_shared00() {
fmt.Println(result)
}
-// To attach a key policy to a customer master key (CMK)
+// To attach a key policy to a KMS key
//
-// The following example attaches a key policy to the specified CMK.
+// The following example attaches a key policy to the specified KMS key.
func ExampleKMS_PutKeyPolicy_shared00() {
svc := kms.New(session.New())
input := &kms.PutKeyPolicyInput{
@@ -1130,7 +1126,7 @@ func ExampleKMS_PutKeyPolicy_shared00() {
// To reencrypt data
//
-// The following example reencrypts data with the specified CMK.
+// The following example reencrypts data with the specified KMS key.
func ExampleKMS_ReEncrypt_shared00() {
svc := kms.New(session.New())
input := &kms.ReEncryptInput{
@@ -1258,9 +1254,9 @@ func ExampleKMS_RevokeGrant_shared00() {
fmt.Println(result)
}
-// To schedule a customer master key (CMK) for deletion
+// To schedule a KMS key for deletion
//
-// The following example schedules the specified CMK for deletion.
+// The following example schedules the specified KMS key for deletion.
func ExampleKMS_ScheduleKeyDeletion_shared00() {
svc := kms.New(session.New())
input := &kms.ScheduleKeyDeletionInput{
@@ -1296,9 +1292,9 @@ func ExampleKMS_ScheduleKeyDeletion_shared00() {
fmt.Println(result)
}
-// To tag a customer master key (CMK)
+// To tag a KMS key
//
-// The following example tags a CMK.
+// The following example tags a KMS key.
func ExampleKMS_TagResource_shared00() {
svc := kms.New(session.New())
input := &kms.TagResourceInput{
@@ -1341,9 +1337,9 @@ func ExampleKMS_TagResource_shared00() {
fmt.Println(result)
}
-// To remove tags from a customer master key (CMK)
+// To remove tags from a KMS key
//
-// The following example removes tags from a CMK.
+// The following example removes tags from a KMS key.
func ExampleKMS_UntagResource_shared00() {
svc := kms.New(session.New())
input := &kms.UntagResourceInput{
@@ -1384,8 +1380,7 @@ func ExampleKMS_UntagResource_shared00() {
// To update an alias
//
-// The following example updates the specified alias to refer to the specified customer
-// master key (CMK).
+// The following example updates the specified alias to refer to the specified KMS key.
func ExampleKMS_UpdateAlias_shared00() {
svc := kms.New(session.New())
input := &kms.UpdateAliasInput{
@@ -1421,13 +1416,13 @@ func ExampleKMS_UpdateAlias_shared00() {
fmt.Println(result)
}
-// To update the description of a customer master key (CMK)
+// To update the description of a KMS key
//
-// The following example updates the description of the specified CMK.
+// The following example updates the description of the specified KMS key.
func ExampleKMS_UpdateKeyDescription_shared00() {
svc := kms.New(session.New())
input := &kms.UpdateKeyDescriptionInput{
- Description: aws.String("Example description that indicates the intended use of this CMK."),
+ Description: aws.String("Example description that indicates the intended use of this KMS key."),
KeyId: aws.String("1234abcd-12ab-34cd-56ef-1234567890ab"),
}