Copyright | (c) 2013-2021 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay <brendan.g.hay+amazonka@gmail.com> |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | None |
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
- kms:UpdateAlias on the alias (IAM policy).
- kms:UpdateAlias on the current KMS key (key policy).
- kms:UpdateAlias on the new KMS key (key policy).
For details, see Controlling access to aliases in the Key Management Service Developer Guide.
Related operations:
- CreateAlias
- DeleteAlias
- ListAliases
Synopsis
- data UpdateAlias = UpdateAlias' {
- aliasName :: Text
- targetKeyId :: Text
- newUpdateAlias :: Text -> Text -> UpdateAlias
- updateAlias_aliasName :: Lens' UpdateAlias Text
- updateAlias_targetKeyId :: Lens' UpdateAlias Text
- data UpdateAliasResponse = UpdateAliasResponse' {
- newUpdateAliasResponse :: UpdateAliasResponse
Creating a Request
data UpdateAlias Source #
See: newUpdateAlias
smart constructor.
UpdateAlias' | |
|
Instances
Create a value of UpdateAlias
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:aliasName:UpdateAlias'
, updateAlias_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.
$sel:targetKeyId:UpdateAlias'
, updateAlias_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:
- 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 KMS key, use ListKeys or DescribeKey.
To verify that the alias is mapped to the correct KMS key, use ListAliases.
Request Lenses
updateAlias_aliasName :: Lens' UpdateAlias Text Source #
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.
updateAlias_targetKeyId :: Lens' UpdateAlias Text Source #
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:
- 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 KMS key, use ListKeys or DescribeKey.
To verify that the alias is mapped to the correct KMS key, use ListAliases.
Destructuring the Response
data UpdateAliasResponse Source #
See: newUpdateAliasResponse
smart constructor.
Instances
Eq UpdateAliasResponse Source # | |
Defined in Amazonka.KMS.UpdateAlias (==) :: UpdateAliasResponse -> UpdateAliasResponse -> Bool # (/=) :: UpdateAliasResponse -> UpdateAliasResponse -> Bool # | |
Read UpdateAliasResponse Source # | |
Defined in Amazonka.KMS.UpdateAlias | |
Show UpdateAliasResponse Source # | |
Defined in Amazonka.KMS.UpdateAlias showsPrec :: Int -> UpdateAliasResponse -> ShowS # show :: UpdateAliasResponse -> String # showList :: [UpdateAliasResponse] -> ShowS # | |
Generic UpdateAliasResponse Source # | |
Defined in Amazonka.KMS.UpdateAlias type Rep UpdateAliasResponse :: Type -> Type # from :: UpdateAliasResponse -> Rep UpdateAliasResponse x # to :: Rep UpdateAliasResponse x -> UpdateAliasResponse # | |
NFData UpdateAliasResponse Source # | |
Defined in Amazonka.KMS.UpdateAlias rnf :: UpdateAliasResponse -> () # | |
type Rep UpdateAliasResponse Source # | |
newUpdateAliasResponse :: UpdateAliasResponse Source #
Create a value of UpdateAliasResponse
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.