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: get_key_policy
kms_put_key_policy(KeyId, PolicyName, Policy,
BypassPolicyLockoutSafetyCheck)
An empty list.
[required] A unique identifier for the customer master key (CMK).
Specify the key ID or the Amazon Resource Name (ARN) of the CMK.
For example:
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
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
list_keys
or describe_key
.
[required] The name of the key policy. The only valid value is default
.
[required] 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
put_key_policy
request to make a subsequent
put_key_policy
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.
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
put_key_policy
request on the CMK.
The default value is false.
svc$put_key_policy(
KeyId = "string",
PolicyName = "string",
Policy = "string",
BypassPolicyLockoutSafetyCheck = TRUE|FALSE
)
if (FALSE) {
# The following example attaches a key policy to the specified CMK.
svc$put_key_policy(
KeyId = "1234abcd-12ab-34cd-56ef-1234567890ab",
Policy = "{\n \"Version\": \"2012-10-17\",\n \"Id\": \"custom-policy-2016-...",
PolicyName = "default"
)
}
Run the code above in your browser using DataLab