AWS Key Management Service 2014-11-01

CancelKeyDeletion

$result = $client->cancelKeyDeletion([/* ... */]);
$promise = $client->cancelKeyDeletionAsync([/* ... */]);

Parameter Syntax

$result = $client->cancelKeyDeletion([
    'KeyId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'KeyId' => '<string>',
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To cancel deletion of a customer master key (CMK)

The following example cancels deletion of the specified CMK.

$result = $client->cancelKeyDeletion([
    'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab', // 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.
]);

Result syntax:

[
    'KeyId' => 'arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab', // The ARN of the CMK whose deletion you canceled.
]

ConnectCustomKeyStore

$result = $client->connectCustomKeyStore([/* ... */]);
$promise = $client->connectCustomKeyStoreAsync([/* ... */]);

Parameter Syntax

$result = $client->connectCustomKeyStore([
    'CustomKeyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• CloudHsmClusterNotActiveException:

  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.

• CustomKeyStoreInvalidStateException:

  The request was rejected because of the ConnectionState of the custom key store. To get the ConnectionState of a custom key store, use the DescribeCustomKeyStores operation.

  This exception is thrown under the following conditions:

  • You requested the CreateKey or GenerateRandom operation in a custom key store that is not connected. These operations are valid only when the custom key store ConnectionState is CONNECTED.

  • You requested the UpdateCustomKeyStore or DeleteCustomKeyStore operation on a custom key store that is not disconnected. This operation is valid only when the custom key store ConnectionState is DISCONNECTED.

  • You requested the ConnectCustomKeyStore operation on a custom key store with a ConnectionState of DISCONNECTING or FAILED. This operation is valid for all other ConnectionState values.

• CustomKeyStoreNotFoundException:

  The request was rejected because AWS KMS cannot find a custom key store with the specified key store name or ID.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request 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 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 .

CreateAlias

$result = $client->createAlias([/* ... */]);
$promise = $client->createAliasAsync([/* ... */]);

Parameter Syntax

$result = $client->createAlias([
    'AliasName' => '<string>', // REQUIRED
    'TargetKeyId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• AlreadyExistsException:

  The request was rejected because it attempted to create a resource that already exists.

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• InvalidAliasNameException:

  The request was rejected because the specified alias name is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• LimitExceededException:

  The request was rejected because a quota was exceeded. For more information, see Quotas in the AWS Key Management Service Developer Guide.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To create an alias

The following example creates an alias for the specified customer master key (CMK).

$result = $client->createAlias([
    'AliasName' => 'alias/ExampleAlias', // 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' => '1234abcd-12ab-34cd-56ef-1234567890ab', // 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.
]);

CreateCustomKeyStore

$result = $client->createCustomKeyStore([/* ... */]);
$promise = $client->createCustomKeyStoreAsync([/* ... */]);

Parameter Syntax

$result = $client->createCustomKeyStore([
    'CloudHsmClusterId' => '<string>', // REQUIRED
    'CustomKeyStoreName' => '<string>', // REQUIRED
    'KeyStorePassword' => '<string>', // REQUIRED
    'TrustAnchorCertificate' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'CustomKeyStoreId' => '<string>',
]

Result Details

Errors

• CloudHsmClusterInUseException:

  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.

• CustomKeyStoreNameInUseException:

  The request was rejected because the specified custom key store name is already assigned to another custom key store in the account. Try again with a custom 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.

• KMSInternalException:

  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 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.

• 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.

  When you initialize the cluster, 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 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 .

CreateGrant

$result = $client->createGrant([/* ... */]);
$promise = $client->createGrantAsync([/* ... */]);

Parameter Syntax

$result = $client->createGrant([
    'Constraints' => [
        'EncryptionContextEquals' => ['<string>', ...],
        'EncryptionContextSubset' => ['<string>', ...],
    ],
    'GrantTokens' => ['<string>', ...],
    'GranteePrincipal' => '<string>', // REQUIRED
    'KeyId' => '<string>', // REQUIRED
    'Name' => '<string>',
    'Operations' => ['<string>', ...], // REQUIRED
    'RetiringPrincipal' => '<string>',
]);

Parameter Details

Result Syntax

[
    'GrantId' => '<string>',
    'GrantToken' => '<string>',
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• InvalidGrantTokenException:

  The request was rejected because the specified grant token is not valid.

• LimitExceededException:

  The request was rejected because a quota was exceeded. For more information, see Quotas in the AWS Key Management Service Developer Guide.

• KMSInvalidStateException:

  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 .

Examples

Example 1: 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).

$result = $client->createGrant([
    'GranteePrincipal' => 'arn:aws:iam::111122223333:role/ExampleRole', // The identity that is given permission to perform the operations specified in the grant.
    'KeyId' => 'arn:aws:kms:us-east-2:444455556666:key/1234abcd-12ab-34cd-56ef-1234567890ab', // 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.
    'Operations' => [
        'Encrypt',
        'Decrypt',
    ], // A list of operations that the grant allows.
]);

Result syntax:

[
    'GrantId' => '0c237476b39f8bc44e45212e08498fbe3151305030726c0590dd8d3e9f3d6a60', // The unique identifier of the grant.
    'GrantToken' => 'AQpAM2RhZTk1MGMyNTk2ZmZmMzEyYWVhOWViN2I1MWM4Mzc0MWFiYjc0ZDE1ODkyNGFlNTIzODZhMzgyZjBlNGY3NiKIAgEBAgB4Pa6VDCWW__MSrqnre1HIN0Grt00ViSSuUjhqOC8OT3YAAADfMIHcBgkqhkiG9w0BBwaggc4wgcsCAQAwgcUGCSqGSIb3DQEHATAeBglghkgBZQMEAS4wEQQMmqLyBTAegIn9XlK5AgEQgIGXZQjkBcl1dykDdqZBUQ6L1OfUivQy7JVYO2-ZJP7m6f1g8GzV47HX5phdtONAP7K_HQIflcgpkoCqd_fUnE114mSmiagWkbQ5sqAVV3ov-VeqgrvMe5ZFEWLMSluvBAqdjHEdMIkHMlhlj4ENZbzBfo9Wxk8b8SnwP4kc4gGivedzFXo-dwN8fxjjq_ZZ9JFOj2ijIbj5FyogDCN0drOfi8RORSEuCEmPvjFRMFAwcmwFkN2NPp89amA', // The grant token.
]

CreateKey

$result = $client->createKey([/* ... */]);
$promise = $client->createKeyAsync([/* ... */]);

Parameter Syntax

$result = $client->createKey([
    'BypassPolicyLockoutSafetyCheck' => true || false,
    'CustomKeyStoreId' => '<string>',
    'CustomerMasterKeySpec' => 'RSA_2048|RSA_3072|RSA_4096|ECC_NIST_P256|ECC_NIST_P384|ECC_NIST_P521|ECC_SECG_P256K1|SYMMETRIC_DEFAULT',
    'Description' => '<string>',
    'KeyUsage' => 'SIGN_VERIFY|ENCRYPT_DECRYPT',
    'MultiRegion' => true || false,
    'Origin' => 'AWS_KMS|EXTERNAL|AWS_CLOUDHSM',
    'Policy' => '<string>',
    'Tags' => [
        [
            'TagKey' => '<string>', // REQUIRED
            'TagValue' => '<string>', // REQUIRED
        ],
        // ...
    ],
]);

Parameter Details

Result Syntax

[
    'KeyMetadata' => [
        'AWSAccountId' => '<string>',
        'Arn' => '<string>',
        'CloudHsmClusterId' => '<string>',
        'CreationDate' => <DateTime>,
        'CustomKeyStoreId' => '<string>',
        'CustomerMasterKeySpec' => 'RSA_2048|RSA_3072|RSA_4096|ECC_NIST_P256|ECC_NIST_P384|ECC_NIST_P521|ECC_SECG_P256K1|SYMMETRIC_DEFAULT',
        'DeletionDate' => <DateTime>,
        'Description' => '<string>',
        'Enabled' => true || false,
        'EncryptionAlgorithms' => ['<string>', ...],
        'ExpirationModel' => 'KEY_MATERIAL_EXPIRES|KEY_MATERIAL_DOES_NOT_EXPIRE',
        'KeyId' => '<string>',
        'KeyManager' => 'AWS|CUSTOMER',
        'KeyState' => 'Creating|Enabled|Disabled|PendingDeletion|PendingImport|PendingReplicaDeletion|Unavailable|Updating',
        'KeyUsage' => 'SIGN_VERIFY|ENCRYPT_DECRYPT',
        'MultiRegion' => true || false,
        'MultiRegionConfiguration' => [
            'MultiRegionKeyType' => 'PRIMARY|REPLICA',
            'PrimaryKey' => [
                'Arn' => '<string>',
                'Region' => '<string>',
            ],
            'ReplicaKeys' => [
                [
                    'Arn' => '<string>',
                    'Region' => '<string>',
                ],
                // ...
            ],
        ],
        'Origin' => 'AWS_KMS|EXTERNAL|AWS_CLOUDHSM',
        'PendingDeletionWindowInDays' => <integer>,
        'SigningAlgorithms' => ['<string>', ...],
        'ValidTo' => <DateTime>,
    ],
]

Result Details

Errors

• MalformedPolicyDocumentException:

  The request was rejected because the specified policy is not syntactically or semantically correct.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• UnsupportedOperationException:

  The request was rejected because a specified parameter is not supported or a specified resource is not valid for this operation.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• LimitExceededException:

  The request was rejected because a quota was exceeded. For more information, see Quotas in the AWS 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 specified key store name or ID.

• CustomKeyStoreInvalidStateException:

  The request was rejected because of the ConnectionState of the custom key store. To get the ConnectionState of a custom key store, use the DescribeCustomKeyStores operation.

  This exception is thrown under the following conditions:

  • You requested the CreateKey or GenerateRandom operation in a custom key store that is not connected. These operations are valid only when the custom key store ConnectionState is CONNECTED.

  • You requested the UpdateCustomKeyStore or DeleteCustomKeyStore operation on a custom key store that is not disconnected. This operation is valid only when the custom key store ConnectionState is DISCONNECTED.

  • You requested the ConnectCustomKeyStore operation on a custom key store with a ConnectionState of DISCONNECTING or FAILED. This operation is valid 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 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 .

Examples

Example 1: To create a customer master key (CMK)

The following example creates a CMK.

$result = $client->createKey([
    'Tags' => [
        [
            'TagKey' => 'CreatedBy',
            'TagValue' => 'ExampleUser',
        ],
    ], // One or more tags. Each tag consists of a tag key and a tag value.
]);

Result syntax:

[
    'KeyMetadata' => [
        'AWSAccountId' => '111122223333',
        'Arn' => 'arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab',
        'CreationDate' => ,
        'Description' => '',
        'Enabled' => 1,
        'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab',
        'KeyManager' => 'CUSTOMER',
        'KeyState' => 'Enabled',
        'KeyUsage' => 'ENCRYPT_DECRYPT',
        'Origin' => 'AWS_KMS',
    ], // An object that contains information about the CMK created by this operation.
]

Decrypt

$result = $client->decrypt([/* ... */]);
$promise = $client->decryptAsync([/* ... */]);

Parameter Syntax

$result = $client->decrypt([
    'CiphertextBlob' => <string || resource || Psr\Http\Message\StreamInterface>, // REQUIRED
    'EncryptionAlgorithm' => 'SYMMETRIC_DEFAULT|RSAES_OAEP_SHA_1|RSAES_OAEP_SHA_256',
    'EncryptionContext' => ['<string>', ...],
    'GrantTokens' => ['<string>', ...],
    'KeyId' => '<string>',
]);

Parameter Details

Result Syntax

[
    'EncryptionAlgorithm' => 'SYMMETRIC_DEFAULT|RSAES_OAEP_SHA_1|RSAES_OAEP_SHA_256',
    'KeyId' => '<string>',
    'Plaintext' => <string || resource || Psr\Http\Message\StreamInterface>,
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• InvalidCiphertextException:

  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.

• KeyUnavailableException:

  The request was rejected because the specified CMK 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.

• InvalidKeyUsageException:

  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.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• InvalidGrantTokenException:

  The request was rejected because the specified grant token is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To decrypt data

The following example decrypts data that was encrypted with a customer master key (CMK) in AWS KMS.

$result = $client->decrypt([
    'CiphertextBlob' => <BLOB>, // The encrypted data (ciphertext).
    'KeyId' => 'arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab', // A key identifier for the CMK to use to decrypt the data.
]);

Result syntax:

[
    'KeyId' => 'arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab', // The Amazon Resource Name (ARN) of the CMK that was used to decrypt the data.
    'Plaintext' => <BLOB>, // The decrypted (plaintext) data.
]

DeleteAlias

$result = $client->deleteAlias([/* ... */]);
$promise = $client->deleteAliasAsync([/* ... */]);

Parameter Syntax

$result = $client->deleteAlias([
    'AliasName' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To delete an alias

The following example deletes the specified alias.

$result = $client->deleteAlias([
    'AliasName' => 'alias/ExampleAlias', // The alias to delete.
]);

DeleteCustomKeyStore

$result = $client->deleteCustomKeyStore([/* ... */]);
$promise = $client->deleteCustomKeyStoreAsync([/* ... */]);

Parameter Syntax

$result = $client->deleteCustomKeyStore([
    'CustomKeyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• 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.

• CustomKeyStoreInvalidStateException:

  The request was rejected because of the ConnectionState of the custom key store. To get the ConnectionState of a custom key store, use the DescribeCustomKeyStores operation.

  This exception is thrown under the following conditions:

  • You requested the CreateKey or GenerateRandom operation in a custom key store that is not connected. These operations are valid only when the custom key store ConnectionState is CONNECTED.

  • You requested the UpdateCustomKeyStore or DeleteCustomKeyStore operation on a custom key store that is not disconnected. This operation is valid only when the custom key store ConnectionState is DISCONNECTED.

  • You requested the ConnectCustomKeyStore operation on a custom key store with a ConnectionState of DISCONNECTING or FAILED. This operation is valid for all other ConnectionState values.

• CustomKeyStoreNotFoundException:

  The request was rejected because AWS KMS cannot find a custom key store with the specified key store name or ID.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

DeleteImportedKeyMaterial

$result = $client->deleteImportedKeyMaterial([/* ... */]);
$promise = $client->deleteImportedKeyMaterialAsync([/* ... */]);

Parameter Syntax

$result = $client->deleteImportedKeyMaterial([
    'KeyId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• UnsupportedOperationException:

  The request was rejected because a specified parameter is not supported or a specified resource is not valid for this operation.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To delete imported key material

The following example deletes the imported key material from the specified customer master key (CMK).

$result = $client->deleteImportedKeyMaterial([
    'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab', // 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.
]);

DescribeCustomKeyStores

$result = $client->describeCustomKeyStores([/* ... */]);
$promise = $client->describeCustomKeyStoresAsync([/* ... */]);

Parameter Syntax

$result = $client->describeCustomKeyStores([
    'CustomKeyStoreId' => '<string>',
    'CustomKeyStoreName' => '<string>',
    'Limit' => <integer>,
    'Marker' => '<string>',
]);

Parameter Details

Result Syntax

[
    'CustomKeyStores' => [
        [
            'CloudHsmClusterId' => '<string>',
            'ConnectionErrorCode' => 'INVALID_CREDENTIALS|CLUSTER_NOT_FOUND|NETWORK_ERRORS|INTERNAL_ERROR|INSUFFICIENT_CLOUDHSM_HSMS|USER_LOCKED_OUT|USER_NOT_FOUND|USER_LOGGED_IN|SUBNET_NOT_FOUND',
            'ConnectionState' => 'CONNECTED|CONNECTING|FAILED|DISCONNECTED|DISCONNECTING',
            'CreationDate' => <DateTime>,
            'CustomKeyStoreId' => '<string>',
            'CustomKeyStoreName' => '<string>',
            'TrustAnchorCertificate' => '<string>',
        ],
        // ...
    ],
    'NextMarker' => '<string>',
    'Truncated' => true || false,
]

Result Details

Errors

• CustomKeyStoreNotFoundException:

  The request was rejected because AWS KMS cannot find a custom key store with the specified key store name or ID.

• InvalidMarkerException:

  The request was rejected because the marker that specifies where pagination should next begin is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

DescribeKey

$result = $client->describeKey([/* ... */]);
$promise = $client->describeKeyAsync([/* ... */]);

Parameter Syntax

$result = $client->describeKey([
    'GrantTokens' => ['<string>', ...],
    'KeyId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'KeyMetadata' => [
        'AWSAccountId' => '<string>',
        'Arn' => '<string>',
        'CloudHsmClusterId' => '<string>',
        'CreationDate' => <DateTime>,
        'CustomKeyStoreId' => '<string>',
        'CustomerMasterKeySpec' => 'RSA_2048|RSA_3072|RSA_4096|ECC_NIST_P256|ECC_NIST_P384|ECC_NIST_P521|ECC_SECG_P256K1|SYMMETRIC_DEFAULT',
        'DeletionDate' => <DateTime>,
        'Description' => '<string>',
        'Enabled' => true || false,
        'EncryptionAlgorithms' => ['<string>', ...],
        'ExpirationModel' => 'KEY_MATERIAL_EXPIRES|KEY_MATERIAL_DOES_NOT_EXPIRE',
        'KeyId' => '<string>',
        'KeyManager' => 'AWS|CUSTOMER',
        'KeyState' => 'Creating|Enabled|Disabled|PendingDeletion|PendingImport|PendingReplicaDeletion|Unavailable|Updating',
        'KeyUsage' => 'SIGN_VERIFY|ENCRYPT_DECRYPT',
        'MultiRegion' => true || false,
        'MultiRegionConfiguration' => [
            'MultiRegionKeyType' => 'PRIMARY|REPLICA',
            'PrimaryKey' => [
                'Arn' => '<string>',
                'Region' => '<string>',
            ],
            'ReplicaKeys' => [
                [
                    'Arn' => '<string>',
                    'Region' => '<string>',
                ],
                // ...
            ],
        ],
        'Origin' => 'AWS_KMS|EXTERNAL|AWS_CLOUDHSM',
        'PendingDeletionWindowInDays' => <integer>,
        'SigningAlgorithms' => ['<string>', ...],
        'ValidTo' => <DateTime>,
    ],
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

Examples

Example 1: To get details about a customer master key (CMK)

The following example gets metadata about a symmetric CMK.

$result = $client->describeKey([
    'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab', // 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.
]);

Result syntax:

[
    'KeyMetadata' => [
        'AWSAccountId' => '111122223333',
        'Arn' => 'arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab',
        'CreationDate' => ,
        'CustomerMasterKeySpec' => 'SYMMETRIC_DEFAULT',
        'Description' => '',
        'Enabled' => 1,
        'EncryptionAlgorithms' => [
            'SYMMETRIC_DEFAULT',
        ],
        'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab',
        'KeyManager' => 'CUSTOMER',
        'KeyState' => 'Enabled',
        'KeyUsage' => 'ENCRYPT_DECRYPT',
        'MultiRegion' => ,
        'Origin' => 'AWS_KMS',
    ], // An object that contains information about the specified CMK.
]

DisableKey

$result = $client->disableKey([/* ... */]);
$promise = $client->disableKeyAsync([/* ... */]);

Parameter Syntax

$result = $client->disableKey([
    'KeyId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To disable a customer master key (CMK)

The following example disables the specified CMK.

$result = $client->disableKey([
    'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab', // The identifier of the CMK to disable. You can use the key ID or the Amazon Resource Name (ARN) of the CMK.
]);

DisableKeyRotation

$result = $client->disableKeyRotation([/* ... */]);
$promise = $client->disableKeyRotationAsync([/* ... */]);

Parameter Syntax

$result = $client->disableKeyRotation([
    'KeyId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

• UnsupportedOperationException:

  The request was rejected because a specified parameter is not supported or a specified resource is not valid for this operation.

Examples

Example 1: To disable automatic rotation of key material

The following example disables automatic annual rotation of the key material for the specified CMK.

$result = $client->disableKeyRotation([
    'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab', // 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.
]);

DisconnectCustomKeyStore

$result = $client->disconnectCustomKeyStore([/* ... */]);
$promise = $client->disconnectCustomKeyStoreAsync([/* ... */]);

Parameter Syntax

$result = $client->disconnectCustomKeyStore([
    'CustomKeyStoreId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• CustomKeyStoreInvalidStateException:

  The request was rejected because of the ConnectionState of the custom key store. To get the ConnectionState of a custom key store, use the DescribeCustomKeyStores operation.

  This exception is thrown under the following conditions:

  • You requested the CreateKey or GenerateRandom operation in a custom key store that is not connected. These operations are valid only when the custom key store ConnectionState is CONNECTED.

  • You requested the UpdateCustomKeyStore or DeleteCustomKeyStore operation on a custom key store that is not disconnected. This operation is valid only when the custom key store ConnectionState is DISCONNECTED.

  • You requested the ConnectCustomKeyStore operation on a custom key store with a ConnectionState of DISCONNECTING or FAILED. This operation is valid for all other ConnectionState values.

• CustomKeyStoreNotFoundException:

  The request was rejected because AWS KMS cannot find a custom key store with the specified key store name or ID.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

EnableKey

$result = $client->enableKey([/* ... */]);
$promise = $client->enableKeyAsync([/* ... */]);

Parameter Syntax

$result = $client->enableKey([
    'KeyId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• LimitExceededException:

  The request was rejected because a quota was exceeded. For more information, see Quotas in the AWS Key Management Service Developer Guide.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To enable a customer master key (CMK)

The following example enables the specified CMK.

$result = $client->enableKey([
    'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab', // The identifier of the CMK to enable. You can use the key ID or the Amazon Resource Name (ARN) of the CMK.
]);

EnableKeyRotation

$result = $client->enableKeyRotation([/* ... */]);
$promise = $client->enableKeyRotationAsync([/* ... */]);

Parameter Syntax

$result = $client->enableKeyRotation([
    'KeyId' => '<string>', // REQUIRED
]);

Parameter Details

Result Syntax

[]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• InvalidArnException:

  The request was rejected because a specified ARN, or an ARN in a key policy, is not valid.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

• UnsupportedOperationException:

  The request was rejected because a specified parameter is not supported or a specified resource is not valid for this operation.

Examples

Example 1: To enable automatic rotation of key material

The following example enables automatic annual rotation of the key material for the specified CMK.

$result = $client->enableKeyRotation([
    'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab', // 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.
]);

Encrypt

$result = $client->encrypt([/* ... */]);
$promise = $client->encryptAsync([/* ... */]);

Parameter Syntax

$result = $client->encrypt([
    'EncryptionAlgorithm' => 'SYMMETRIC_DEFAULT|RSAES_OAEP_SHA_1|RSAES_OAEP_SHA_256',
    'EncryptionContext' => ['<string>', ...],
    'GrantTokens' => ['<string>', ...],
    'KeyId' => '<string>', // REQUIRED
    'Plaintext' => <string || resource || Psr\Http\Message\StreamInterface>, // REQUIRED
]);

Parameter Details

Result Syntax

[
    'CiphertextBlob' => <string || resource || Psr\Http\Message\StreamInterface>,
    'EncryptionAlgorithm' => 'SYMMETRIC_DEFAULT|RSAES_OAEP_SHA_1|RSAES_OAEP_SHA_256',
    'KeyId' => '<string>',
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• KeyUnavailableException:

  The request was rejected because the specified CMK was not available. You can retry the request.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• InvalidKeyUsageException:

  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.

• InvalidGrantTokenException:

  The request was rejected because the specified grant token is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To encrypt data

The following example encrypts data with the specified customer master key (CMK).

$result = $client->encrypt([
    'KeyId' => '1234abcd-12ab-34cd-56ef-1234567890ab', // 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.
    'Plaintext' => <BLOB>, // The data to encrypt.
]);

Result syntax:

[
    'CiphertextBlob' => <BLOB>, // The encrypted data (ciphertext).
    'KeyId' => 'arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab', // The ARN of the CMK that was used to encrypt the data.
]

GenerateDataKey

$result = $client->generateDataKey([/* ... */]);
$promise = $client->generateDataKeyAsync([/* ... */]);

Parameter Syntax

$result = $client->generateDataKey([
    'EncryptionContext' => ['<string>', ...],
    'GrantTokens' => ['<string>', ...],
    'KeyId' => '<string>', // REQUIRED
    'KeySpec' => 'AES_256|AES_128',
    'NumberOfBytes' => <integer>,
]);

Parameter Details

Result Syntax

[
    'CiphertextBlob' => <string || resource || Psr\Http\Message\StreamInterface>,
    'KeyId' => '<string>',
    'Plaintext' => <string || resource || Psr\Http\Message\StreamInterface>,
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• KeyUnavailableException:

  The request was rejected because the specified CMK was not available. You can retry the request.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• InvalidKeyUsageException:

  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.

• InvalidGrantTokenException:

  The request was rejected because the specified grant token is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

Examples

Example 1: To generate a data key

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).

$result = $client->generateDataKey([
    'KeyId' => 'alias/ExampleAlias', // 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.
    'KeySpec' => 'AES_256', // Specifies the type of data key to return.
]);

Result syntax:

[
    'CiphertextBlob' => <BLOB>, // The encrypted data key.
    'KeyId' => 'arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab', // The ARN of the CMK that was used to encrypt the data key.
    'Plaintext' => <BLOB>, // The unencrypted (plaintext) data key.
]

GenerateDataKeyPair

$result = $client->generateDataKeyPair([/* ... */]);
$promise = $client->generateDataKeyPairAsync([/* ... */]);

Parameter Syntax

$result = $client->generateDataKeyPair([
    'EncryptionContext' => ['<string>', ...],
    'GrantTokens' => ['<string>', ...],
    'KeyId' => '<string>', // REQUIRED
    'KeyPairSpec' => 'RSA_2048|RSA_3072|RSA_4096|ECC_NIST_P256|ECC_NIST_P384|ECC_NIST_P521|ECC_SECG_P256K1', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'KeyId' => '<string>',
    'KeyPairSpec' => 'RSA_2048|RSA_3072|RSA_4096|ECC_NIST_P256|ECC_NIST_P384|ECC_NIST_P521|ECC_SECG_P256K1',
    'PrivateKeyCiphertextBlob' => <string || resource || Psr\Http\Message\StreamInterface>,
    'PrivateKeyPlaintext' => <string || resource || Psr\Http\Message\StreamInterface>,
    'PublicKey' => <string || resource || Psr\Http\Message\StreamInterface>,
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• KeyUnavailableException:

  The request was rejected because the specified CMK was not available. You can retry the request.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• InvalidKeyUsageException:

  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.

• InvalidGrantTokenException:

  The request was rejected because the specified grant token is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

• UnsupportedOperationException:

  The request was rejected because a specified parameter is not supported or a specified resource is not valid for this operation.

GenerateDataKeyPairWithoutPlaintext

$result = $client->generateDataKeyPairWithoutPlaintext([/* ... */]);
$promise = $client->generateDataKeyPairWithoutPlaintextAsync([/* ... */]);

Parameter Syntax

$result = $client->generateDataKeyPairWithoutPlaintext([
    'EncryptionContext' => ['<string>', ...],
    'GrantTokens' => ['<string>', ...],
    'KeyId' => '<string>', // REQUIRED
    'KeyPairSpec' => 'RSA_2048|RSA_3072|RSA_4096|ECC_NIST_P256|ECC_NIST_P384|ECC_NIST_P521|ECC_SECG_P256K1', // REQUIRED
]);

Parameter Details

Result Syntax

[
    'KeyId' => '<string>',
    'KeyPairSpec' => 'RSA_2048|RSA_3072|RSA_4096|ECC_NIST_P256|ECC_NIST_P384|ECC_NIST_P521|ECC_SECG_P256K1',
    'PrivateKeyCiphertextBlob' => <string || resource || Psr\Http\Message\StreamInterface>,
    'PublicKey' => <string || resource || Psr\Http\Message\StreamInterface>,
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• KeyUnavailableException:

  The request was rejected because the specified CMK was not available. You can retry the request.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• InvalidKeyUsageException:

  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.

• InvalidGrantTokenException:

  The request was rejected because the specified grant token is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

• UnsupportedOperationException:

  The request was rejected because a specified parameter is not supported or a specified resource is not valid for this operation.

GenerateDataKeyWithoutPlaintext

$result = $client->generateDataKeyWithoutPlaintext([/* ... */]);
$promise = $client->generateDataKeyWithoutPlaintextAsync([/* ... */]);

Parameter Syntax

$result = $client->generateDataKeyWithoutPlaintext([
    'EncryptionContext' => ['<string>', ...],
    'GrantTokens' => ['<string>', ...],
    'KeyId' => '<string>', // REQUIRED
    'KeySpec' => 'AES_256|AES_128',
    'NumberOfBytes' => <integer>,
]);

Parameter Details

Result Syntax

[
    'CiphertextBlob' => <string || resource || Psr\Http\Message\StreamInterface>,
    'KeyId' => '<string>',
]

Result Details

Errors

• NotFoundException:

  The request was rejected because the specified entity or resource could not be found.

• DisabledException:

  The request was rejected because the specified CMK is not enabled.

• KeyUnavailableException:

  The request was rejected because the specified CMK was not available. You can retry the request.

• DependencyTimeoutException:

  The system timed out while trying to fulfill the request. The request can be retried.

• InvalidKeyUsageException:

  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.

• InvalidGrantTokenException:

  The request was rejected because the specified grant token is not valid.

• KMSInternalException:

  The request was rejected because an internal exception occurred. The request can be retried.

• KMSInvalidStateException:

  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 .

Examples

Example 1: 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).

$result = $client->generateDataKeyWithoutPlaintext([
    'KeyId' => 'alias/ExampleAlias', // 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.
    'KeySpec' => 'AES_256', // Specifies the type of data key to return.
]);

Result syntax:

[
    'CiphertextBlob' => <BLOB>, // The encrypted data key.
    'KeyId' => 'arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab', // The ARN of the CMK that was used to encrypt the data key.
]

GenerateRandom

$result = $client->generateRandom([/* ... */]);
$promise = $client->generateRandomAsync([/* ... */]);

Parameter Syntax

$result = $client->generateRandom([
    'CustomKeyStoreId' => '<string>',
    'NumberOfBytes' => <integer>,
]);

Parameter Details

Result Syntax

[
    'Plaintext' => <string || resource || Psr\Http\Message\StreamInterface>,
]

Result Details