Module Smaws_Client_KMS

KMS client library built on EIO.

Types

type xks_proxy_vpc_endpoint_service_not_found_exception = {
  1. message : string option;
}

The request was rejected because KMS could not find the specified VPC endpoint service. Use DescribeCustomKeyStores to verify the VPC endpoint service name for the external key store. Also, confirm that the Allow principals list for the VPC endpoint service includes the KMS service principal for the Region, such as cks.kms.us-east-1.amazonaws.com.

type xks_proxy_vpc_endpoint_service_invalid_configuration_exception = {
  1. message : string option;
}

The request was rejected because the Amazon VPC endpoint service configuration does not fulfill the requirements for an external key store. To identify the cause, see the error message that accompanies the exception and review the requirements for Amazon VPC endpoint service connectivity for an external key store.

type xks_proxy_vpc_endpoint_service_in_use_exception = {
  1. message : string option;
}

The request was rejected because the specified Amazon VPC endpoint service is already associated with another external key store in this Amazon Web Services Region. Each external key store in a Region must use a different Amazon VPC endpoint service.

type xks_proxy_uri_unreachable_exception = {
  1. message : string option;
}

KMS was unable to reach the specified XksProxyUriPath. The path must be reachable before you create the external key store or update its settings.

This exception is also thrown when the external key store proxy response to a GetHealthStatus request indicates that all external key manager instances are unavailable.

type xks_proxy_uri_in_use_exception = {
  1. message : string option;
}

The request was rejected because the concatenation of the XksProxyUriEndpoint and XksProxyUriPath is already associated with another external key store in this Amazon Web Services Region. Each external key store in a Region must use a unique external key store proxy API address.

type xks_proxy_uri_endpoint_in_use_exception = {
  1. message : string option;
}

The request was rejected because the XksProxyUriEndpoint is already associated with another external key store in this Amazon Web Services Region. To identify the cause, see the error message that accompanies the exception.

type xks_proxy_invalid_response_exception = {
  1. message : string option;
}

KMS cannot interpret the response it received from the external key store proxy. The problem might be a poorly constructed response, but it could also be a transient network issue. If you see this error repeatedly, report it to the proxy vendor.

type xks_proxy_invalid_configuration_exception = {
  1. message : string option;
}

The request was rejected because the external key store proxy is not configured correctly. To identify the cause, see the error message that accompanies the exception.

type xks_proxy_incorrect_authentication_credential_exception = {
  1. message : string option;
}

The request was rejected because the proxy credentials failed to authenticate to the specified external key store proxy. The specified external key store proxy rejected a status request from KMS due to invalid credentials. This can indicate an error in the credentials or in the identification of the external key store proxy.

type xks_proxy_connectivity_type =
  1. | VPC_ENDPOINT_SERVICE
  2. | PUBLIC_ENDPOINT
type xks_proxy_configuration_type = {
  1. vpc_endpoint_service_name : string option;
    (*

    The Amazon VPC endpoint service used to communicate with the external key store proxy. This field appears only when the external key store proxy uses an Amazon VPC endpoint service to communicate with KMS.

    *)
  2. uri_path : string option;
    (*

    The path to the external key store proxy APIs.

    *)
  3. uri_endpoint : string option;
    (*

    The URI endpoint for the external key store proxy.

    If the external key store proxy has a public endpoint, it is displayed here.

    If the external key store proxy uses an Amazon VPC endpoint service name, this field displays the private DNS name associated with the VPC endpoint service.

    *)
  4. access_key_id : string option;
    (*

    The part of the external key store proxy authentication credential that uniquely identifies the secret access key.

    *)
  5. connectivity : xks_proxy_connectivity_type option;
    (*

    Indicates whether the external key store proxy uses a public endpoint or an Amazon VPC endpoint service to communicate with KMS.

    *)
}

Detailed information about the external key store proxy (XKS proxy). Your external key store proxy translates KMS requests into a format that your external key manager can understand. These fields appear in a DescribeCustomKeyStores response only when the CustomKeyStoreType is EXTERNAL_KEY_STORE.

type xks_proxy_authentication_credential_type = {
  1. raw_secret_access_key : string;
    (*

    A secret string of 43-64 characters. Valid characters are a-z, A-Z, 0-9, /, +, and =.

    *)
  2. access_key_id : string;
    (*

    A unique identifier for the raw secret access key.

    *)
}

KMS uses the authentication credential to sign requests that it sends to the external key store proxy (XKS proxy) on your behalf. You establish these credentials on your external key store proxy and report them to KMS.

The XksProxyAuthenticationCredential includes two required elements.

type xks_key_not_found_exception = {
  1. message : string option;
}

The request was rejected because the external key store proxy could not find the external key. This exception is thrown when the value of the XksKeyId parameter doesn't identify a key in the external key manager associated with the external key proxy.

Verify that the XksKeyId represents an existing key in the external key manager. Use the key identifier that the external key store proxy uses to identify the key. For details, see the documentation provided with your external key store proxy or key manager.

type xks_key_invalid_configuration_exception = {
  1. message : string option;
}

The request was rejected because the external key specified by the XksKeyId parameter did not meet the configuration requirements for an external key store.

The external key must be an AES-256 symmetric key that is enabled and performs encryption and decryption.

type xks_key_configuration_type = {
  1. id : string option;
    (*

    The ID of the external key in its external key manager. This is the ID that the external key store proxy uses to identify the external key.

    *)
}

Information about the external keythat is associated with a KMS key in an external key store.

This element appears in a CreateKey or DescribeKey response only for a KMS key in an external key store.

The external key is a symmetric encryption key that is hosted by an external key manager outside of Amazon Web Services. When you use the KMS key in an external key store in a cryptographic operation, the cryptographic operation is performed in the external key manager using the specified external key. For more information, see External key in the Key Management Service Developer Guide.

type xks_key_already_in_use_exception = {
  1. message : string option;
}

The request was rejected because the (XksKeyId) is already associated with another KMS key in this external key store. Each KMS key in an external key store must be associated with a different external key.

type wrapping_key_spec =
  1. | SM2
  2. | RSA_4096
  3. | RSA_3072
  4. | RSA_2048
type signing_algorithm_spec =
  1. | SM2DSA
  2. | ECDSA_SHA_512
  3. | ECDSA_SHA_384
  4. | ECDSA_SHA_256
  5. | RSASSA_PKCS1_V1_5_SHA_512
  6. | RSASSA_PKCS1_V1_5_SHA_384
  7. | RSASSA_PKCS1_V1_5_SHA_256
  8. | RSASSA_PSS_SHA_512
  9. | RSASSA_PSS_SHA_384
  10. | RSASSA_PSS_SHA_256
type verify_response = {
  1. signing_algorithm : signing_algorithm_spec option;
    (*

    The signing algorithm that was used to verify the signature.

    *)
  2. signature_valid : bool option;
    (*

    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.

    *)
  3. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the asymmetric KMS key that was used to verify the signature.

    *)
}
type message_type =
  1. | DIGEST
  2. | RAW
type verify_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. grant_tokens : string list option;
    (*

    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.

    *)
  3. signing_algorithm : signing_algorithm_spec;
    (*

    The signing algorithm that was used to sign the message. If you submit a different algorithm, the signature verification fails.

    *)
  4. signature : bytes;
    (*

    The signature that the Sign operation generated.

    *)
  5. message_type : message_type option;
    (*

    Tells KMS whether the value of the Message parameter should be hashed as part of the signing algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which are already hashed.

    When the value of MessageType is RAW, KMS uses the standard signing algorithm, which begins with a hash function. When the value is DIGEST, KMS skips the hashing step in the signing algorithm.

    Use the DIGEST value only when the value of the Message parameter is a message digest. If you use the DIGEST value with an unhashed message, the security of the verification operation can be compromised.

    When the value of MessageTypeis DIGEST, the length of the Message value must match the length of hashed messages for the specified signing algorithm.

    You can submit a message digest and omit the MessageType or specify RAW so the digest is hashed again while signing. However, if the signed message is hashed once while signing, but twice while verifying, verification fails, even when the message hasn't changed.

    The hashing algorithm in that Verify uses is based on the SigningAlgorithm value.

    • Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
    • Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
    • Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
    • SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
    *)
  6. message : bytes;
    (*

    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.

    *)
  7. key_id : string;
    (*

    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.

    *)
}
type mac_algorithm_spec =
  1. | HMAC_SHA_512
  2. | HMAC_SHA_384
  3. | HMAC_SHA_256
  4. | HMAC_SHA_224
type verify_mac_response = {
  1. mac_algorithm : mac_algorithm_spec option;
    (*

    The MAC algorithm used in the verification.

    *)
  2. mac_valid : bool option;
    (*

    A Boolean value that indicates whether the HMAC was verified. A value of True indicates that the HMAC (Mac) was generated with the specified Message, HMAC KMS key (KeyID) and MacAlgorithm..

    If the HMAC is not verified, the VerifyMac operation fails with a KMSInvalidMacException exception. This exception indicates that one or more of the inputs changed since the HMAC was computed.

    *)
  3. key_id : string option;
    (*

    The HMAC KMS key used in the verification.

    *)
}
type verify_mac_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. grant_tokens : string list option;
    (*

    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.

    *)
  3. mac : bytes;
    (*

    The HMAC to verify. Enter the HMAC that was generated by the GenerateMac operation when you specified the same message, HMAC KMS key, and MAC algorithm as the values specified in this request.

    *)
  4. mac_algorithm : mac_algorithm_spec;
    (*

    The MAC algorithm that will be used in the verification. Enter the same MAC algorithm that was used to compute the HMAC. This algorithm must be supported by the HMAC KMS key identified by the KeyId parameter.

    *)
  5. key_id : string;
    (*

    The KMS key that will be used in the verification.

    Enter a key ID of the KMS key that was used to generate the HMAC. If you identify a different KMS key, the VerifyMac operation fails.

    *)
  6. message : bytes;
    (*

    The message that will be used in the verification. Enter the same message that was used to generate the HMAC.

    GenerateMac and VerifyMac do not provide special handling for message digests. If you generated an HMAC for a hash digest of a message, you must verify the HMAC for the same hash digest.

    *)
}
type not_found_exception = {
  1. message : string option;
}

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

type kms_invalid_state_exception = {
  1. message : string option;
}

The request was rejected because the state of the specified resource is not valid for this request.

This exceptions means one of the following:

  • The key state of the KMS key is not compatible with the operation.

    To find the key state, use the DescribeKey operation. For more information about which key states are compatible with each KMS operation, see Key states of KMS keys in the Key Management Service Developer Guide.

  • For cryptographic operations on KMS keys in custom key stores, this exception represents a general failure with many possible causes. To identify the cause, see the error message that accompanies the exception.
type kms_invalid_mac_exception = {
  1. message : string option;
}

The request was rejected because the HMAC verification failed. HMAC verification fails when the HMAC computed by using the specified message, HMAC KMS key, and MAC algorithm does not match the HMAC specified in the request.

type kms_internal_exception = {
  1. message : string option;
}

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

type key_unavailable_exception = {
  1. message : string option;
}

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

type invalid_key_usage_exception = {
  1. message : string option;
}

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 messages, the KeyUsage must be SIGN_VERIFY. For generating and verifying message authentication codes (MACs), the KeyUsage must be GENERATE_VERIFY_MAC. For deriving key agreement secrets, the KeyUsage must be KEY_AGREEMENT. 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.

type invalid_grant_token_exception = {
  1. message : string option;
}

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

type dry_run_operation_exception = {
  1. message : string option;
}

The request was rejected because the DryRun parameter was specified.

type disabled_exception = {
  1. message : string option;
}

The request was rejected because the specified KMS key is not enabled.

type kms_invalid_signature_exception = {
  1. message : string option;
}

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.

type dependency_timeout_exception = {
  1. message : string option;
}

The system timed out while trying to fulfill the request. You can retry the request.

type update_primary_region_request = {
  1. primary_region : string;
    (*

    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.

    *)
  2. key_id : string;
    (*

    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:

    • Key ID: mrk-1234abcd12ab34cd56ef1234567890ab
    • Key ARN: arn:aws:kms:us-east-2:111122223333:key/mrk-1234abcd12ab34cd56ef1234567890ab

    To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.

    *)
}
type unsupported_operation_exception = {
  1. message : string option;
}

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

type invalid_arn_exception = {
  1. message : string option;
}

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

type update_key_description_request = {
  1. description : string;
    (*

    New description for the KMS key.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    *)
  2. key_id : string;
    (*

    Updates the description of the specified KMS key.

    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.

    *)
}
type update_custom_key_store_response = unit
type update_custom_key_store_request = {
  1. xks_proxy_connectivity : xks_proxy_connectivity_type option;
    (*

    Changes the connectivity setting for the external key store. To indicate that the external key store proxy uses a Amazon VPC endpoint service to communicate with KMS, specify VPC_ENDPOINT_SERVICE. Otherwise, specify PUBLIC_ENDPOINT.

    If you change the XksProxyConnectivity to VPC_ENDPOINT_SERVICE, you must also change the XksProxyUriEndpoint and add an XksProxyVpcEndpointServiceName value.

    If you change the XksProxyConnectivity to PUBLIC_ENDPOINT, you must also change the XksProxyUriEndpoint and specify a null or empty string for the XksProxyVpcEndpointServiceName value.

    To change this value, the external key store must be disconnected.

    *)
  2. xks_proxy_authentication_credential : xks_proxy_authentication_credential_type option;
    (*

    Changes the credentials that KMS uses to sign requests to the external key store proxy (XKS proxy). This parameter is valid only for custom key stores with a CustomKeyStoreType of EXTERNAL_KEY_STORE.

    You must specify both the AccessKeyId and SecretAccessKey value in the authentication credential, even if you are only updating one value.

    This parameter doesn't establish or change your authentication credentials on the proxy. It just tells KMS the credential that you established with your external key store proxy. For example, if you rotate the credential on your external key store proxy, you can use this parameter to update the credential in KMS.

    You can change this value when the external key store is connected or disconnected.

    *)
  3. xks_proxy_vpc_endpoint_service_name : string option;
    (*

    Changes the name that KMS uses to identify the Amazon VPC endpoint service for your external key store proxy (XKS proxy). This parameter is valid when the CustomKeyStoreType is EXTERNAL_KEY_STORE and the XksProxyConnectivity is VPC_ENDPOINT_SERVICE.

    To change this value, the external key store must be disconnected.

    *)
  4. xks_proxy_uri_path : string option;
    (*

    Changes the base path to the proxy APIs for this external key store. To find this value, see the documentation for your external key manager and external key store proxy (XKS proxy). This parameter is valid only for custom key stores with a CustomKeyStoreType of EXTERNAL_KEY_STORE.

    The value must start with / and must end with /kms/xks/v1, where v1 represents the version of the KMS external key store proxy API. You can include an optional prefix between the required elements such as

    /{i example}/kms/xks/v1

    .

    The combined XksProxyUriEndpoint and XksProxyUriPath values must be unique in the Amazon Web Services account and Region.

    You can change this value when the external key store is connected or disconnected.

    *)
  5. xks_proxy_uri_endpoint : string option;
    (*

    Changes the URI endpoint that KMS uses to connect to your external key store proxy (XKS proxy). This parameter is valid only for custom key stores with a CustomKeyStoreType of EXTERNAL_KEY_STORE.

    For external key stores with an XksProxyConnectivity value of PUBLIC_ENDPOINT, the protocol must be HTTPS.

    For external key stores with an XksProxyConnectivity value of VPC_ENDPOINT_SERVICE, specify https:// followed by the private DNS name associated with the VPC endpoint service. Each external key store must use a different private DNS name.

    The combined XksProxyUriEndpoint and XksProxyUriPath values must be unique in the Amazon Web Services account and Region.

    To change this value, the external key store must be disconnected.

    *)
  6. cloud_hsm_cluster_id : string option;
    (*

    Associates the custom key store with a related CloudHSM cluster. This parameter is valid only for custom key stores with a CustomKeyStoreType of AWS_CLOUDHSM.

    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.

    To change this value, the CloudHSM key store must be disconnected.

    *)
  7. key_store_password : string option;
    (*

    Enter the current password of the kmsuser crypto user (CU) in the CloudHSM cluster that is associated with the custom key store. This parameter is valid only for custom key stores with a CustomKeyStoreType of 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.

    To change this value, the CloudHSM key store must be disconnected.

    *)
  8. new_custom_key_store_name : string option;
    (*

    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.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    To change this value, an CloudHSM key store must be disconnected. An external key store can be connected or disconnected.

    *)
  9. custom_key_store_id : string;
    (*

    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.

    *)
}
type custom_key_store_not_found_exception = {
  1. message : string option;
}

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

type custom_key_store_name_in_use_exception = {
  1. message : string option;
}

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.

type custom_key_store_invalid_state_exception = {
  1. message : string option;
}

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 ConnectCustomKeyStore operation on a custom key store with a ConnectionState of DISCONNECTING or FAILED. This operation is valid for all other ConnectionState values. To reconnect a custom key store in a FAILED state, disconnect it (DisconnectCustomKeyStore), then connect it (ConnectCustomKeyStore).
  • You requested the CreateKey operation in a custom key store that is not connected. This operations is valid only when the custom key store ConnectionState is CONNECTED.
  • You requested the DisconnectCustomKeyStore operation on a custom key store with a ConnectionState of DISCONNECTING or DISCONNECTED. This operation is valid for all other ConnectionState values.
  • 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 GenerateRandom operation in an CloudHSM key store that is not connected. This operation is valid only when the CloudHSM key store ConnectionState is CONNECTED.

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 for an CloudHSM key store.

Specify an CloudHSM 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.

CloudHSM clusters that share a backup history have the same cluster certificate. To view the cluster certificate of an CloudHSM cluster, use the DescribeClusters operation.

type cloud_hsm_cluster_not_found_exception = {
  1. message : string option;
}

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 cloud_hsm_cluster_not_active_exception = {
  1. message : string option;
}

The request was rejected because the CloudHSM cluster associated with the CloudHSM 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.

type cloud_hsm_cluster_invalid_configuration_exception = {
  1. message : string option;
}

The request was rejected because the associated CloudHSM cluster did not meet the configuration requirements for an CloudHSM key store.

  • The CloudHSM 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--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 CloudHSM cluster. Do not delete or change them. To get information about a particular security group, use the DescribeSecurityGroups operation.
  • The CloudHSM 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 an CloudHSM 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.

type update_alias_request = {
  1. target_key_id : string;
    (*

    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 or both HMAC) 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.

    *)
  2. alias_name : string;
    (*

    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.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    *)
}
type limit_exceeded_exception = {
  1. message : string option;
}

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

type untag_resource_request = {
  1. tag_keys : string list;
    (*

    One or more tag keys. Specify only the tag keys, not the tag values.

    *)
  2. key_id : string;
    (*

    Identifies the KMS key from which you are removing tags.

    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.

    *)
}
type tag_exception = {
  1. message : string option;
}

The request was rejected because one or more tags are not valid.

type tag = {
  1. tag_value : string;
    (*

    The value of the tag.

    *)
  2. tag_key : string;
    (*

    The key of the tag.

    *)
}

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.

Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

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.

type tag_resource_request = {
  1. tags : tag list;
    (*

    One or more tags. Each tag consists of a tag key and a tag value. The tag value can be an empty (null) string.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    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.

    *)
  2. key_id : string;
    (*

    Identifies a customer managed key in the account and Region.

    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.

    *)
}
type sign_response = {
  1. signing_algorithm : signing_algorithm_spec option;
    (*

    The signing algorithm that was used to sign the message.

    *)
  2. signature : bytes option;
    (*

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

    *)
  3. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the asymmetric KMS key that was used to sign the message.

    *)
}
type sign_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. signing_algorithm : signing_algorithm_spec;
    (*

    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. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.

    *)
  3. grant_tokens : string list option;
    (*

    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.

    *)
  4. message_type : message_type option;
    (*

    Tells KMS whether the value of the Message parameter should be hashed as part of the signing algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which are already hashed.

    When the value of MessageType is RAW, KMS uses the standard signing algorithm, which begins with a hash function. When the value is DIGEST, KMS skips the hashing step in the signing algorithm.

    Use the DIGEST value only when the value of the Message parameter is a message digest. If you use the DIGEST value with an unhashed message, the security of the signing operation can be compromised.

    When the value of MessageTypeis DIGEST, the length of the Message value must match the length of hashed messages for the specified signing algorithm.

    You can submit a message digest and omit the MessageType or specify RAW so the digest is hashed again while signing. However, this can cause verification failures when verifying with a system that assumes a single hash.

    The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.

    • Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
    • Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
    • Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
    • SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
    *)
  5. message : bytes;
    (*

    Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message, provide a message digest.

    If you provide a message digest, use the DIGEST value of MessageType to prevent the digest from being hashed again while signing.

    *)
  6. key_id : string;
    (*

    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.

    *)
}
type key_state =
  1. | Updating
  2. | Unavailable
  3. | PendingReplicaDeletion
  4. | PendingImport
  5. | PendingDeletion
  6. | Disabled
  7. | Enabled
  8. | Creating
type schedule_key_deletion_response = {
  1. pending_window_in_days : int option;
    (*

    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.

    *)
  2. key_state : key_state option;
    (*

    The current status of the KMS key.

    For more information about how key state affects the use of a KMS key, see Key states of KMS keys in the Key Management Service Developer Guide.

    *)
  3. deletion_date : float option;
    (*

    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.

    *)
  4. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key whose deletion is scheduled.

    *)
}
type schedule_key_deletion_request = {
  1. pending_window_in_days : int option;
    (*

    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 replica keys, 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. You can use the kms:ScheduleKeyDeletionPendingWindowInDays condition key to further constrain the values that principals can specify in the PendingWindowInDays parameter.

    *)
  2. key_id : string;
    (*

    The unique identifier of the KMS key to delete.

    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.

    *)
}
type conflict_exception = {
  1. message : string option;
}

The request was rejected because an automatic rotation of this key is currently in progress or scheduled to begin within the next 20 minutes.

type rotate_key_on_demand_response = {
  1. key_id : string option;
    (*

    Identifies the symmetric encryption KMS key that you initiated on-demand rotation on.

    *)
}
type rotate_key_on_demand_request = {
  1. key_id : string;
    (*

    Identifies a symmetric encryption KMS key. You cannot perform on-demand rotation of asymmetric KMS keys, HMAC KMS keys, KMS keys with imported key material, or KMS keys in a custom key store. To perform on-demand rotation of a set of related multi-Region keys, invoke the on-demand rotation on the primary key.

    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.

    *)
}
type invalid_grant_id_exception = {
  1. message : string option;
}

The request was rejected because the specified GrantId is not valid.

type revoke_grant_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. grant_id : string;
    (*

    Identifies the grant to revoke. To get the grant ID, use CreateGrant, ListGrants, or ListRetirableGrants.

    *)
  3. key_id : string;
    (*

    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:

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

    *)
}
type retire_grant_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. grant_id : string option;
    (*

    Identifies the grant to retire. To get the grant ID, use CreateGrant, ListGrants, or ListRetirableGrants.

    • Grant ID Example - 0123456789012345678901234567890123456789012345678901234567890123
    *)
  3. key_id : string option;
    (*

    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

    *)
  4. grant_token : string option;
    (*

    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.

    *)
}
type malformed_policy_document_exception = {
  1. message : string option;
}

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

type already_exists_exception = {
  1. message : string option;
}

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

type key_usage_type =
  1. | KEY_AGREEMENT
  2. | GENERATE_VERIFY_MAC
  3. | ENCRYPT_DECRYPT
  4. | SIGN_VERIFY
type origin_type =
  1. | EXTERNAL_KEY_STORE
  2. | AWS_CLOUDHSM
  3. | EXTERNAL
  4. | AWS_KMS
type expiration_model_type =
  1. | KEY_MATERIAL_DOES_NOT_EXPIRE
  2. | KEY_MATERIAL_EXPIRES
type key_manager_type =
  1. | CUSTOMER
  2. | AWS
type customer_master_key_spec =
  1. | SM2
  2. | HMAC_512
  3. | HMAC_384
  4. | HMAC_256
  5. | HMAC_224
  6. | SYMMETRIC_DEFAULT
  7. | ECC_SECG_P256K1
  8. | ECC_NIST_P521
  9. | ECC_NIST_P384
  10. | ECC_NIST_P256
  11. | RSA_4096
  12. | RSA_3072
  13. | RSA_2048
type key_spec =
  1. | SM2
  2. | HMAC_512
  3. | HMAC_384
  4. | HMAC_256
  5. | HMAC_224
  6. | SYMMETRIC_DEFAULT
  7. | ECC_SECG_P256K1
  8. | ECC_NIST_P521
  9. | ECC_NIST_P384
  10. | ECC_NIST_P256
  11. | RSA_4096
  12. | RSA_3072
  13. | RSA_2048
type encryption_algorithm_spec =
  1. | SM2PKE
  2. | RSAES_OAEP_SHA_256
  3. | RSAES_OAEP_SHA_1
  4. | SYMMETRIC_DEFAULT
type key_agreement_algorithm_spec =
  1. | ECDH
type multi_region_key_type =
  1. | REPLICA
  2. | PRIMARY
type multi_region_key = {
  1. region : string option;
    (*

    Displays the Amazon Web Services Region of a primary or replica key in a multi-Region key.

    *)
  2. arn : string option;
    (*

    Displays the key ARN of a primary or replica key of a multi-Region key.

    *)
}

Describes the primary or replica key in a multi-Region key.

type multi_region_configuration = {
  1. replica_keys : multi_region_key list option;
    (*

    displays the key ARNs and Regions of all replica keys. This field includes the current KMS key if it is a replica key.

    *)
  2. primary_key : multi_region_key option;
    (*

    Displays the key ARN and Region of the primary key. This field includes the current KMS key if it is the primary key.

    *)
  3. multi_region_key_type : multi_region_key_type option;
    (*

    Indicates whether the KMS key is a PRIMARY or REPLICA key.

    *)
}

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.

type key_metadata = {
  1. xks_key_configuration : xks_key_configuration_type option;
    (*

    Information about the external key that is associated with a KMS key in an external key store.

    For more information, see External key in the Key Management Service Developer Guide.

    *)
  2. mac_algorithms : mac_algorithm_spec list option;
    (*

    The message authentication code (MAC) algorithm that the HMAC KMS key supports.

    This value is present only when the KeyUsage of the KMS key is GENERATE_VERIFY_MAC.

    *)
  3. pending_deletion_window_in_days : int option;
    (*

    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.

    *)
  4. multi_region_configuration : multi_region_configuration option;
    (*

    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.
    *)
  5. multi_region : bool option;
    (*

    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 Multi-Region keys in KMS in the Key Management Service Developer Guide.

    *)
  6. key_agreement_algorithms : key_agreement_algorithm_spec list option;
    (*

    The key agreement algorithm used to derive a shared secret.

    *)
  7. signing_algorithms : signing_algorithm_spec list option;
    (*

    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.

    *)
  8. encryption_algorithms : encryption_algorithm_spec list option;
    (*

    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.

    *)
  9. key_spec : key_spec option;
    (*

    Describes the type of key material in the KMS key.

    *)
  10. customer_master_key_spec : customer_master_key_spec option;
    (*

    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 supports both fields.

    *)
  11. key_manager : key_manager_type option;
    (*

    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.

    *)
  12. expiration_model : expiration_model_type option;
    (*

    Specifies whether the KMS key's key material expires. This value is present only when Origin is EXTERNAL, otherwise this value is omitted.

    *)
  13. cloud_hsm_cluster_id : string option;
    (*

    The cluster ID of the CloudHSM cluster that contains the key material for the KMS key. When you create a KMS key in an CloudHSM custom key store, KMS creates the key material for the KMS key in the associated CloudHSM cluster. This field is present only when the KMS key is created in an CloudHSM key store.

    *)
  14. custom_key_store_id : string option;
    (*

    A unique identifier for the custom key store that contains the KMS key. This field is present only when the KMS key is created in a custom key store.

    *)
  15. origin : origin_type option;
    (*

    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.

    *)
  16. valid_to : float option;
    (*

    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.

    *)
  17. deletion_date : float option;
    (*

    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.

    *)
  18. key_state : key_state option;
    (*

    The current status of the KMS key.

    For more information about how key state affects the use of a KMS key, see Key states of KMS keys in the Key Management Service Developer Guide.

    *)
  19. key_usage : key_usage_type option;
    (*

    The cryptographic operations for which you can use the KMS key.

    *)
  20. description : string option;
    (*

    The description of the KMS key.

    *)
  21. enabled : bool option;
    (*

    Specifies whether the KMS key is enabled. When KeyState is Enabled this value is true, otherwise it is false.

    *)
  22. creation_date : float option;
    (*

    The date and time when the KMS key was created.

    *)
  23. arn : string option;
    (*

    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.

    *)
  24. key_id : string;
    (*

    The globally unique identifier for the KMS key.

    *)
  25. aws_account_id : string option;
    (*

    The twelve-digit account ID of the Amazon Web Services account that owns the KMS key.

    *)
}

Contains metadata about a KMS key.

This data type is used as a response element for the CreateKey, DescribeKey, and ReplicateKey operations.

type replicate_key_response = {
  1. replica_tags : tag list option;
    (*

    The tags on the new replica key. The value is a list of tag key and tag value pairs.

    *)
  2. replica_policy : string option;
    (*

    The key policy of the new replica key. The value is a key policy document in JSON format.

    *)
  3. replica_key_metadata : key_metadata option;
    (*

    Displays details about the new replica key, including its Amazon Resource Name (key ARN) and Key states of KMS keys. It also includes the ARN and Amazon Web Services Region of its primary key and other replica keys.

    *)
}
type replicate_key_request = {
  1. tags : tag list option;
    (*

    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.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see ABAC for 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.

    *)
  2. description : string option;
    (*

    A description of the KMS key. The default value is an empty string (no description).

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    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.

    *)
  3. bypass_policy_lockout_safety_check : bool option;
    (*

    Skips ("bypasses") the key policy lockout safety check. The default value is false.

    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, see Default key policy 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.

    *)
  4. policy : string option;
    (*

    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:

    • The key policy must allow the calling principal to make a subsequent PutKeyPolicy request on the KMS key. This reduces the risk that the KMS key becomes unmanageable. For more information, see Default key policy in the Key Management Service Developer Guide. (To omit this condition, set BypassPolicyLockoutSafetyCheck to true.)
    • 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, 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.

    A key policy document can include only the following characters:

    • Printable ASCII characters from the space character (\u0020) through the end of the ASCII character range.
    • Printable characters in the Basic Latin and Latin-1 Supplement character set (through \u00FF).
    • The tab (\u0009), line feed (\u000A), and carriage return (\u000D) special characters

    For information about key policies, see Key policies in KMS 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.

    *)
  5. replica_region : string;
    (*

    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.

    HMAC KMS keys are not supported in all Amazon Web Services Regions. If you try to replicate an HMAC KMS key in an Amazon Web Services Region in which HMAC keys are not supported, the ReplicateKey operation returns an UnsupportedOperationException. For a list of Regions in which HMAC KMS keys are supported, see HMAC keys in KMS in the Key Management Service Developer Guide.

    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.

    *)
  6. key_id : string;
    (*

    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:

    • Key ID: mrk-1234abcd12ab34cd56ef1234567890ab
    • Key ARN: arn:aws:kms:us-east-2:111122223333:key/mrk-1234abcd12ab34cd56ef1234567890ab

    To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey.

    *)
}
type invalid_ciphertext_exception = {
  1. message : string option;
}

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.

type incorrect_key_exception = {
  1. message : string option;
}

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 re_encrypt_response = {
  1. destination_encryption_algorithm : encryption_algorithm_spec option;
    (*

    The encryption algorithm that was used to reencrypt the data.

    *)
  2. source_encryption_algorithm : encryption_algorithm_spec option;
    (*

    The encryption algorithm that was used to decrypt the ciphertext before it was reencrypted.

    *)
  3. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key that was used to reencrypt the data.

    *)
  4. source_key_id : string option;
    (*

    Unique identifier of the KMS key used to originally encrypt the data.

    *)
  5. ciphertext_blob : bytes option;
    (*

    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.

    *)
}
type re_encrypt_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. grant_tokens : string list option;
    (*

    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.

    *)
  3. destination_encryption_algorithm : encryption_algorithm_spec option;
    (*

    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 encryption KMS keys.

    This parameter is required only when the destination KMS key is an asymmetric KMS key.

    *)
  4. source_encryption_algorithm : encryption_algorithm_spec option;
    (*

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

    *)
  5. destination_encryption_context : (string * string) list option;
    (*

    Specifies that encryption context to use when the reencrypting the data.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    A destination encryption context is valid only when the destination KMS key is a symmetric encryption 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 represent 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 supported only on operations with symmetric encryption KMS keys. On operations with symmetric encryption KMS keys, an encryption context is optional, but it is strongly recommended.

    For more information, see Encryption context in the Key Management Service Developer Guide.

    *)
  6. destination_key_id : string;
    (*

    A unique identifier for the KMS key that is used to reencrypt the data. Specify a symmetric encryption KMS key or an 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.

    *)
  7. source_key_id : string option;
    (*

    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. If you identify a different KMS key, the ReEncrypt operation throws an IncorrectKeyException.

    This parameter is required only when the ciphertext was encrypted under an asymmetric KMS key. If you used a symmetric encryption 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.

    *)
  8. source_encryption_context : (string * string) list option;
    (*

    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 represent 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 supported only on operations with symmetric encryption KMS keys. On operations with symmetric encryption KMS keys, an encryption context is optional, but it is strongly recommended.

    For more information, see Encryption context in the Key Management Service Developer Guide.

    *)
  9. ciphertext_blob : bytes;
    (*

    Ciphertext of the data to reencrypt.

    *)
}
type put_key_policy_request = {
  1. bypass_policy_lockout_safety_check : bool option;
    (*

    Skips ("bypasses") the key policy lockout safety check. The default value is false.

    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, see Default key policy 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.

    *)
  2. policy : string;
    (*

    The key policy to attach to the KMS key.

    The key policy must meet the following criteria:

    • The key policy must allow the calling principal to make a subsequent PutKeyPolicy request on the KMS key. This reduces the risk that the KMS key becomes unmanageable. For more information, see Default key policy in the Key Management Service Developer Guide. (To omit this condition, set BypassPolicyLockoutSafetyCheck to true.)
    • 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, 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.

    A key policy document can include only the following characters:

    • Printable ASCII characters from the space character (\u0020) through the end of the ASCII character range.
    • Printable characters in the Basic Latin and Latin-1 Supplement character set (through \u00FF).
    • The tab (\u0009), line feed (\u000A), and carriage return (\u000D) special characters

    For information about key policies, see Key policies in KMS 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.

    *)
  3. policy_name : string option;
    (*

    The name of the key policy. If no policy name is specified, the default value is default. The only valid value is default.

    *)
  4. key_id : string;
    (*

    Sets the key policy on the specified KMS key.

    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.

    *)
}
type invalid_marker_exception = {
  1. message : string option;
}

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

type grant_operation =
  1. | DeriveSharedSecret
  2. | VerifyMac
  3. | GenerateMac
  4. | GenerateDataKeyPairWithoutPlaintext
  5. | GenerateDataKeyPair
  6. | DescribeKey
  7. | RetireGrant
  8. | CreateGrant
  9. | GetPublicKey
  10. | Verify
  11. | Sign
  12. | ReEncryptTo
  13. | ReEncryptFrom
  14. | GenerateDataKeyWithoutPlaintext
  15. | GenerateDataKey
  16. | Encrypt
  17. | Decrypt
type grant_constraints = {
  1. encryption_context_equals : (string * string) list option;
    (*

    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.

    *)
  2. encryption_context_subset : (string * string) list option;
    (*

    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.

    *)
}

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.

type grant_list_entry = {
  1. constraints : grant_constraints option;
    (*

    A list of key-value pairs that must be present in the encryption context of certain subsequent operations that the grant allows.

    *)
  2. operations : grant_operation list option;
    (*

    The list of operations permitted by the grant.

    *)
  3. issuing_account : string option;
    (*

    The Amazon Web Services account under which the grant was issued.

    *)
  4. retiring_principal : string option;
    (*

    The principal that can retire the grant.

    *)
  5. grantee_principal : string option;
    (*

    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.

    *)
  6. creation_date : float option;
    (*

    The date and time when the grant was created.

    *)
  7. name : string option;
    (*

    The friendly name that identifies the grant. If a name was provided in the CreateGrant request, that name is returned. Otherwise this value is null.

    *)
  8. grant_id : string option;
    (*

    The unique identifier for the grant.

    *)
  9. key_id : string option;
    (*

    The unique identifier for the KMS key to which the grant applies.

    *)
}

Contains information about a grant.

type list_grants_response = {
  1. truncated : bool option;
    (*

    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 this response to the Marker parameter in a subsequent request.

    *)
  2. next_marker : string option;
    (*

    When Truncated is true, this element is present and contains the value to use for the Marker parameter in a subsequent request.

    *)
  3. grants : grant_list_entry list option;
    (*

    A list of grants.

    *)
}
type list_retirable_grants_request = {
  1. retiring_principal : string;
    (*

    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 principals include Amazon Web Services accounts, IAM users, IAM roles, federated users, and assumed role users. For help with the ARN syntax for a principal, see IAM ARNs in the Identity and Access Management User Guide.

    *)
  2. marker : string option;
    (*

    Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

    *)
  3. limit : int option;
    (*

    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.

    *)
}
type list_resource_tags_response = {
  1. truncated : bool option;
    (*

    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 this response to the Marker parameter in a subsequent request.

    *)
  2. next_marker : string option;
    (*

    When Truncated is true, this element is present and contains the value to use for the Marker parameter in a subsequent request.

    Do not assume or infer any information from this value.

    *)
  3. tags : tag list option;
    (*

    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 ABAC for KMS in the Key Management Service Developer Guide.

    *)
}
type list_resource_tags_request = {
  1. marker : string option;
    (*

    Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

    Do not attempt to construct this value. Use only the value of NextMarker from the truncated response you just received.

    *)
  2. limit : int option;
    (*

    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.

    *)
  3. key_id : string;
    (*

    Gets tags on the specified KMS key.

    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.

    *)
}
type key_list_entry = {
  1. key_arn : string option;
    (*

    ARN of the key.

    *)
  2. key_id : string option;
    (*

    Unique identifier of the key.

    *)
}

Contains information about each entry in the key list.

type list_keys_response = {
  1. truncated : bool option;
    (*

    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 this response to the Marker parameter in a subsequent request.

    *)
  2. next_marker : string option;
    (*

    When Truncated is true, this element is present and contains the value to use for the Marker parameter in a subsequent request.

    *)
  3. keys : key_list_entry list option;
    (*

    A list of KMS keys.

    *)
}
type list_keys_request = {
  1. marker : string option;
    (*

    Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

    *)
  2. limit : int option;
    (*

    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.

    *)
}
type rotation_type =
  1. | ON_DEMAND
  2. | AUTOMATIC
type rotations_list_entry = {
  1. rotation_type : rotation_type option;
    (*

    Identifies whether the key material rotation was a scheduled automatic rotation or an on-demand rotation.

    *)
  2. rotation_date : float option;
    (*

    Date and time that the key material rotation completed. Formatted as Unix time.

    *)
  3. key_id : string option;
    (*

    Unique identifier of the key.

    *)
}

Contains information about completed key material rotations.

type list_key_rotations_response = {
  1. truncated : bool option;
    (*

    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 this response to the Marker parameter in a subsequent request.

    *)
  2. next_marker : string option;
    (*

    When Truncated is true, this element is present and contains the value to use for the Marker parameter in a subsequent request.

    *)
  3. rotations : rotations_list_entry list option;
    (*

    A list of completed key material rotations.

    *)
}
type list_key_rotations_request = {
  1. marker : string option;
    (*

    Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

    *)
  2. limit : int option;
    (*

    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.

    *)
  3. key_id : string;
    (*

    Gets the key rotations for the specified KMS key.

    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.

    *)
}
type list_key_policies_response = {
  1. truncated : bool option;
    (*

    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 this response to the Marker parameter in a subsequent request.

    *)
  2. next_marker : string option;
    (*

    When Truncated is true, this element is present and contains the value to use for the Marker parameter in a subsequent request.

    *)
  3. policy_names : string list option;
    (*

    A list of key policy names. The only valid value is default.

    *)
}
type list_key_policies_request = {
  1. marker : string option;
    (*

    Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

    *)
  2. limit : int option;
    (*

    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.

    *)
  3. key_id : string;
    (*

    Gets the names of key policies for the specified KMS key.

    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.

    *)
}
type list_grants_request = {
  1. grantee_principal : string option;
    (*

    Returns only grants where the specified principal is the grantee principal for the grant.

    *)
  2. grant_id : string option;
    (*

    Returns only the grant with the specified grant ID. The grant ID uniquely identifies the grant.

    *)
  3. key_id : string;
    (*

    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:

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

    *)
  4. marker : string option;
    (*

    Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

    *)
  5. limit : int option;
    (*

    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.

    *)
}
type alias_list_entry = {
  1. last_updated_date : float option;
    (*

    Date and time that the alias was most recently associated with a KMS key in the account and Region. Formatted as Unix time.

    *)
  2. creation_date : float option;
    (*

    Date and time that the alias was most recently created in the account and Region. Formatted as Unix time.

    *)
  3. target_key_id : string option;
    (*

    String that contains the key identifier of the KMS key associated with the alias.

    *)
  4. alias_arn : string option;
    (*

    String that contains the key ARN.

    *)
  5. alias_name : string option;
    (*

    String that contains the alias. This value begins with alias/.

    *)
}

Contains information about an alias.

type list_aliases_response = {
  1. truncated : bool option;
    (*

    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 this response to the Marker parameter in a subsequent request.

    *)
  2. next_marker : string option;
    (*

    When Truncated is true, this element is present and contains the value to use for the Marker parameter in a subsequent request.

    *)
  3. aliases : alias_list_entry list option;
    (*

    A list of aliases.

    *)
}
type list_aliases_request = {
  1. marker : string option;
    (*

    Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

    *)
  2. limit : int option;
    (*

    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.

    *)
  3. key_id : string option;
    (*

    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:

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

    *)
}
type invalid_import_token_exception = {
  1. message : string option;
}

The request was rejected because the provided import token is invalid or is associated with a different KMS key.

type incorrect_key_material_exception = {
  1. message : string option;
}

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.

type expired_import_token_exception = {
  1. message : string option;
}

The request was rejected because the specified import token is expired. Use GetParametersForImport to get a new import token and public key, use the new public key to encrypt the key material, and then try the request again.

type import_key_material_response = unit
type import_key_material_request = {
  1. expiration_model : expiration_model_type option;
    (*

    Specifies whether the key material expires. The default is KEY_MATERIAL_EXPIRES. For help with this choice, see Setting an expiration time in the Key Management Service Developer Guide.

    When the value of ExpirationModel is KEY_MATERIAL_EXPIRES, you must specify a value for the ValidTo parameter. When value is KEY_MATERIAL_DOES_NOT_EXPIRE, you must omit the ValidTo parameter.

    You cannot change the ExpirationModel or ValidTo values for the current import after the request completes. To change either value, you must reimport the key material.

    *)
  2. valid_to : float option;
    (*

    The date and time when the imported key material expires. This parameter is required when the value of the ExpirationModel parameter is KEY_MATERIAL_EXPIRES. Otherwise it is not valid.

    The value of this parameter must be a future date and time. The maximum value is 365 days from the request date.

    When the key material expires, KMS deletes the key material from the KMS key. Without its key material, the KMS key is unusable. To use the KMS key in cryptographic operations, you must reimport the same key material.

    You cannot change the ExpirationModel or ValidTo values for the current import after the request completes. To change either value, you must delete (DeleteImportedKeyMaterial) and reimport the key material.

    *)
  3. encrypted_key_material : bytes;
    (*

    The encrypted key material to import. The key material must be encrypted under the public wrapping key that GetParametersForImport returned, using the wrapping algorithm that you specified in the same GetParametersForImport request.

    *)
  4. import_token : bytes;
    (*

    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.

    *)
  5. key_id : string;
    (*

    The identifier of the KMS key that will be associated with the imported key material. This must be the same KMS key specified in the KeyID parameter of the corresponding GetParametersForImport request. The Origin of the KMS key must be EXTERNAL and its KeyState must be PendingImport.

    The KMS key can be a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key, including a multi-Region key of any supported type. You cannot perform this operation on a KMS key in a custom key store, or on a KMS key in a different Amazon Web Services account.

    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.

    *)
}
type get_public_key_response = {
  1. key_agreement_algorithms : key_agreement_algorithm_spec list option;
    (*

    The key agreement algorithm used to derive a shared secret. This field is present only when the KMS key has a KeyUsage value of KEY_AGREEMENT.

    *)
  2. signing_algorithms : signing_algorithm_spec list option;
    (*

    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.

    *)
  3. encryption_algorithms : encryption_algorithm_spec list option;
    (*

    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.

    *)
  4. key_usage : key_usage_type option;
    (*

    The permitted use of the public key. Valid values for asymmetric key pairs are ENCRYPT_DECRYPT, SIGN_VERIFY, and KEY_AGREEMENT.

    This information is critical. For example, if a public key with SIGN_VERIFY key usage encrypts data outside of KMS, the ciphertext cannot be decrypted.

    *)
  5. key_spec : key_spec option;
    (*

    The type of the of the public key that was downloaded.

    *)
  6. customer_master_key_spec : customer_master_key_spec option;
    (*

    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 supports both fields.

    *)
  7. public_key : bytes option;
    (*

    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.

    *)
  8. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the asymmetric KMS key from which the public key was downloaded.

    *)
}
type get_public_key_request = {
  1. grant_tokens : string list option;
    (*

    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.

    *)
  2. key_id : string;
    (*

    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.

    *)
}
type get_parameters_for_import_response = {
  1. parameters_valid_to : float option;
    (*

    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.

    *)
  2. public_key : bytes option;
    (*

    The public key to use to encrypt the key material before importing it with ImportKeyMaterial.

    *)
  3. import_token : bytes option;
    (*

    The import token to send in a subsequent ImportKeyMaterial request.

    *)
  4. key_id : string option;
    (*

    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.

    *)
}
type algorithm_spec =
  1. | SM2PKE
  2. | RSA_AES_KEY_WRAP_SHA_256
  3. | RSA_AES_KEY_WRAP_SHA_1
  4. | RSAES_OAEP_SHA_256
  5. | RSAES_OAEP_SHA_1
  6. | RSAES_PKCS1_V1_5
type get_parameters_for_import_request = {
  1. wrapping_key_spec : wrapping_key_spec;
    (*

    The type of RSA public key to return in the response. You will use this wrapping key with the specified wrapping algorithm to protect your key material during import.

    Use the longest RSA wrapping key that is practical.

    You cannot use an RSA_2048 public key to directly wrap an ECC_NIST_P521 private key. Instead, use an RSA_AES wrapping algorithm or choose a longer RSA public key.

    *)
  2. wrapping_algorithm : algorithm_spec;
    (*

    The algorithm you will use with the RSA public key (PublicKey) in the response to protect your key material during import. For more information, see Select a wrapping algorithm in the Key Management Service Developer Guide.

    For RSA_AES wrapping algorithms, you encrypt your key material with an AES key that you generate, then encrypt your AES key with the RSA public key from KMS. For RSAES wrapping algorithms, you encrypt your key material directly with the RSA public key from KMS.

    The wrapping algorithms that you can use depend on the type of key material that you are importing. To import an RSA private key, you must use an RSA_AES wrapping algorithm.

    • RSA_AES_KEY_WRAP_SHA_256 — Supported for wrapping RSA and ECC key material.
    • RSA_AES_KEY_WRAP_SHA_1 — Supported for wrapping RSA and ECC key material.
    • RSAES_OAEP_SHA_256 — Supported for all types of key material, except RSA key material (private key).

      You cannot use the RSAES_OAEP_SHA_256 wrapping algorithm with the RSA_2048 wrapping key spec to wrap ECC_NIST_P521 key material.

    • RSAES_OAEP_SHA_1 — Supported for all types of key material, except RSA key material (private key).

      You cannot use the RSAES_OAEP_SHA_1 wrapping algorithm with the RSA_2048 wrapping key spec to wrap ECC_NIST_P521 key material.

    • RSAES_PKCS1_V1_5 (Deprecated) — As of October 10, 2023, KMS does not support the RSAES_PKCS1_V1_5 wrapping algorithm.
    *)
  3. key_id : string;
    (*

    The identifier of the KMS key that will be associated with the imported key material. The Origin of the KMS key must be EXTERNAL.

    All KMS key types are supported, including multi-Region keys. However, you cannot import key material into a KMS key in a custom key store.

    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.

    *)
}
type get_key_rotation_status_response = {
  1. on_demand_rotation_start_date : float option;
    (*

    Identifies the date and time that an in progress on-demand rotation was initiated.

    The KMS API follows an eventual consistency model due to the distributed nature of the system. As a result, there might be a slight delay between initiating on-demand key rotation and the rotation's completion. Once the on-demand rotation is complete, use ListKeyRotations to view the details of the on-demand rotation.

    *)
  2. next_rotation_date : float option;
    (*

    The next date that KMS will automatically rotate the key material.

    *)
  3. rotation_period_in_days : int option;
    (*

    The number of days between each automatic rotation. The default value is 365 days.

    *)
  4. key_id : string option;
    (*

    Identifies the specified symmetric encryption KMS key.

    *)
  5. key_rotation_enabled : bool option;
    (*

    A Boolean value that specifies whether key rotation is enabled.

    *)
}
type get_key_rotation_status_request = {
  1. key_id : string;
    (*

    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:

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

    *)
}
type get_key_policy_response = {
  1. policy_name : string option;
    (*

    The name of the key policy. The only valid value is default.

    *)
  2. policy : string option;
    (*

    A key policy document in JSON format.

    *)
}
type get_key_policy_request = {
  1. policy_name : string option;
    (*

    Specifies the name of the key policy. If no policy name is specified, the default value is default. The only valid name is default. To get the names of key policies, use ListKeyPolicies.

    *)
  2. key_id : string;
    (*

    Gets the key policy for the specified KMS key.

    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.

    *)
}
type generate_random_response = {
  1. ciphertext_for_recipient : bytes option;
    (*

    The plaintext random bytes encrypted with the public key from the Nitro enclave. This ciphertext can be decrypted only by using a private key in the Nitro enclave.

    This field is included in the response only when the Recipient parameter in the request includes a valid attestation document from an Amazon Web Services Nitro enclave. For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  2. plaintext : bytes option;
    (*

    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.

    If the response includes the CiphertextForRecipient field, the Plaintext field is null or empty.

    *)
}
type key_encryption_mechanism =
  1. | RSAES_OAEP_SHA_256
type recipient_info = {
  1. attestation_document : bytes option;
    (*

    The attestation document for an Amazon Web Services Nitro Enclave. This document includes the enclave's public key.

    *)
  2. key_encryption_algorithm : key_encryption_mechanism option;
    (*

    The encryption algorithm that KMS should use with the public key for an Amazon Web Services Nitro Enclave to encrypt plaintext values for the response. The only valid value is RSAES_OAEP_SHA_256.

    *)
}

Contains information about the party that receives the response from the API operation.

This data type is designed to support Amazon Web Services Nitro Enclaves, which lets you create an isolated compute environment in Amazon EC2. For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

type generate_random_request = {
  1. recipient : recipient_info option;
    (*

    A signed attestation document from an Amazon Web Services Nitro enclave and the encryption algorithm to use with the enclave's public key. The only valid encryption algorithm is RSAES_OAEP_SHA_256.

    This parameter only supports attestation documents for Amazon Web Services Nitro Enclaves. To include this parameter, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK.

    When you use this parameter, instead of returning plaintext bytes, KMS encrypts the plaintext bytes under the public key in the attestation document, and returns the resulting ciphertext in the CiphertextForRecipient field in the response. This ciphertext can be decrypted only with the private key in the enclave. The Plaintext field in the response is null or empty.

    For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  2. custom_key_store_id : string option;
    (*

    Generates the random byte string in the CloudHSM cluster that is associated with the specified CloudHSM key store. To find the ID of a custom key store, use the DescribeCustomKeyStores operation.

    External key store IDs are not valid for this parameter. If you specify the ID of an external key store, GenerateRandom throws an UnsupportedOperationException.

    *)
  3. number_of_bytes : int option;
    (*

    The length of the random byte string. This parameter is required.

    *)
}
type generate_mac_response = {
  1. key_id : string option;
    (*

    The HMAC KMS key used in the operation.

    *)
  2. mac_algorithm : mac_algorithm_spec option;
    (*

    The MAC algorithm that was used to generate the HMAC.

    *)
  3. mac : bytes option;
    (*

    The hash-based message authentication code (HMAC) that was generated for the specified message, HMAC KMS key, and MAC algorithm.

    This is the standard, raw HMAC defined in RFC 2104.

    *)
}
type generate_mac_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. grant_tokens : string list option;
    (*

    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.

    *)
  3. mac_algorithm : mac_algorithm_spec;
    (*

    The MAC algorithm used in the operation.

    The algorithm must be compatible with the HMAC KMS key that you specify. To find the MAC algorithms that your HMAC KMS key supports, use the DescribeKey operation and see the MacAlgorithms field in the DescribeKey response.

    *)
  4. key_id : string;
    (*

    The HMAC KMS key to use in the operation. The MAC algorithm computes the HMAC for the message and the key as described in RFC 2104.

    To identify an HMAC KMS key, use the DescribeKey operation and see the KeySpec field in the response.

    *)
  5. message : bytes;
    (*

    The message to be hashed. Specify a message of up to 4,096 bytes.

    GenerateMac and VerifyMac do not provide special handling for message digests. If you generate an HMAC for a hash digest of a message, you must verify the HMAC of the same hash digest.

    *)
}
type generate_data_key_without_plaintext_response = {
  1. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key that encrypted the data key.

    *)
  2. ciphertext_blob : bytes option;
    (*

    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.

    *)
}
type data_key_spec =
  1. | AES_128
  2. | AES_256
type generate_data_key_without_plaintext_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. grant_tokens : string list option;
    (*

    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.

    *)
  3. number_of_bytes : int option;
    (*

    The length of the data key in bytes. For example, use the value 64 to generate a 512-bit data key (64 bytes is 512 bits). For common key lengths (128-bit and 256-bit symmetric keys), we recommend that you use the KeySpec field instead of this one.

    *)
  4. key_spec : data_key_spec option;
    (*

    The length of the data key. Use AES_128 to generate a 128-bit symmetric key, or AES_256 to generate a 256-bit symmetric key.

    *)
  5. encryption_context : (string * string) list option;
    (*

    Specifies the encryption context that will be used when encrypting the data key.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    An encryption context is a collection of non-secret key-value pairs that represent 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 supported only on operations with symmetric encryption KMS keys. On operations with symmetric encryption KMS keys, an encryption context is optional, but it is strongly recommended.

    For more information, see Encryption context in the Key Management Service Developer Guide.

    *)
  6. key_id : string;
    (*

    Specifies the symmetric encryption KMS key that encrypts the data key. 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.

    *)
}
type data_key_pair_spec =
  1. | SM2
  2. | ECC_SECG_P256K1
  3. | ECC_NIST_P521
  4. | ECC_NIST_P384
  5. | ECC_NIST_P256
  6. | RSA_4096
  7. | RSA_3072
  8. | RSA_2048
type generate_data_key_pair_without_plaintext_response = {
  1. key_pair_spec : data_key_pair_spec option;
    (*

    The type of data key pair that was generated.

    *)
  2. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key that encrypted the private key.

    *)
  3. public_key : bytes option;
    (*

    The public key (in plaintext). When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.

    *)
  4. private_key_ciphertext_blob : bytes option;
    (*

    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.

    *)
}
type generate_data_key_pair_without_plaintext_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. grant_tokens : string list option;
    (*

    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.

    *)
  3. key_pair_spec : data_key_pair_spec;
    (*

    Determines the type of data key pair that is generated.

    The KMS rule that restricts the use of asymmetric RSA and SM2 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. The SM2 key spec is only available in China Regions.

    *)
  4. key_id : string;
    (*

    Specifies the symmetric encryption 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.

    *)
  5. encryption_context : (string * string) list option;
    (*

    Specifies the encryption context that will be used when encrypting the private key in the data key pair.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    An encryption context is a collection of non-secret key-value pairs that represent 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 supported only on operations with symmetric encryption KMS keys. On operations with symmetric encryption KMS keys, an encryption context is optional, but it is strongly recommended.

    For more information, see Encryption context in the Key Management Service Developer Guide.

    *)
}
type generate_data_key_pair_response = {
  1. ciphertext_for_recipient : bytes option;
    (*

    The plaintext private data key encrypted with the public key from the Nitro enclave. This ciphertext can be decrypted only by using a private key in the Nitro enclave.

    This field is included in the response only when the Recipient parameter in the request includes a valid attestation document from an Amazon Web Services Nitro enclave. For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  2. key_pair_spec : data_key_pair_spec option;
    (*

    The type of data key pair that was generated.

    *)
  3. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key that encrypted the private key.

    *)
  4. public_key : bytes option;
    (*

    The public key (in plaintext). When you use the HTTP API or the Amazon Web Services CLI, the value is Base64-encoded. Otherwise, it is not Base64-encoded.

    *)
  5. private_key_plaintext : bytes option;
    (*

    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.

    If the response includes the CiphertextForRecipient field, the PrivateKeyPlaintext field is null or empty.

    *)
  6. private_key_ciphertext_blob : bytes option;
    (*

    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.

    *)
}
type generate_data_key_pair_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. recipient : recipient_info option;
    (*

    A signed attestation document from an Amazon Web Services Nitro enclave and the encryption algorithm to use with the enclave's public key. The only valid encryption algorithm is RSAES_OAEP_SHA_256.

    This parameter only supports attestation documents for Amazon Web Services Nitro Enclaves. To call DeriveSharedSecret for an Amazon Web Services Nitro Enclaves, use the Amazon Web Services Nitro Enclaves SDK to generate the attestation document and then use the Recipient parameter from any Amazon Web Services SDK to provide the attestation document for the enclave.

    When you use this parameter, instead of returning a plaintext copy of the private data key, KMS encrypts the plaintext private data key under the public key in the attestation document, and returns the resulting ciphertext in the CiphertextForRecipient field in the response. This ciphertext can be decrypted only with the private key in the enclave. The CiphertextBlob field in the response contains a copy of the private data key encrypted under the KMS key specified by the KeyId parameter. The PrivateKeyPlaintext field in the response is null or empty.

    For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  3. grant_tokens : string list option;
    (*

    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.

    *)
  4. key_pair_spec : data_key_pair_spec;
    (*

    Determines the type of data key pair that is generated.

    The KMS rule that restricts the use of asymmetric RSA and SM2 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. The SM2 key spec is only available in China Regions.

    *)
  5. key_id : string;
    (*

    Specifies the symmetric encryption 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.

    *)
  6. encryption_context : (string * string) list option;
    (*

    Specifies the encryption context that will be used when encrypting the private key in the data key pair.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    An encryption context is a collection of non-secret key-value pairs that represent 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 supported only on operations with symmetric encryption KMS keys. On operations with symmetric encryption KMS keys, an encryption context is optional, but it is strongly recommended.

    For more information, see Encryption context in the Key Management Service Developer Guide.

    *)
}
type generate_data_key_response = {
  1. ciphertext_for_recipient : bytes option;
    (*

    The plaintext data key encrypted with the public key from the Nitro enclave. This ciphertext can be decrypted only by using a private key in the Nitro enclave.

    This field is included in the response only when the Recipient parameter in the request includes a valid attestation document from an Amazon Web Services Nitro enclave. For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  2. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key that encrypted the data key.

    *)
  3. plaintext : bytes option;
    (*

    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.

    If the response includes the CiphertextForRecipient field, the Plaintext field is null or empty.

    *)
  4. ciphertext_blob : bytes option;
    (*

    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.

    *)
}
type generate_data_key_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. recipient : recipient_info option;
    (*

    A signed attestation document from an Amazon Web Services Nitro enclave and the encryption algorithm to use with the enclave's public key. The only valid encryption algorithm is RSAES_OAEP_SHA_256.

    This parameter only supports attestation documents for Amazon Web Services Nitro Enclaves. To include this parameter, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK.

    When you use this parameter, instead of returning the plaintext data key, KMS encrypts the plaintext data key under the public key in the attestation document, and returns the resulting ciphertext in the CiphertextForRecipient field in the response. This ciphertext can be decrypted only with the private key in the enclave. The CiphertextBlob field in the response contains a copy of the data key encrypted under the KMS key specified by the KeyId parameter. The Plaintext field in the response is null or empty.

    For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  3. grant_tokens : string list option;
    (*

    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.

    *)
  4. key_spec : data_key_spec option;
    (*

    Specifies the length of the data key. Use AES_128 to generate a 128-bit symmetric key, or AES_256 to generate a 256-bit symmetric key.

    You must specify either the KeySpec or the NumberOfBytes parameter (but not both) in every GenerateDataKey request.

    *)
  5. number_of_bytes : int option;
    (*

    Specifies the length of the data key in bytes. For example, use the value 64 to generate a 512-bit data key (64 bytes is 512 bits). For 128-bit (16-byte) and 256-bit (32-byte) data keys, use the KeySpec parameter.

    You must specify either the KeySpec or the NumberOfBytes parameter (but not both) in every GenerateDataKey request.

    *)
  6. encryption_context : (string * string) list option;
    (*

    Specifies the encryption context that will be used when encrypting the data key.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    An encryption context is a collection of non-secret key-value pairs that represent 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 supported only on operations with symmetric encryption KMS keys. On operations with symmetric encryption KMS keys, an encryption context is optional, but it is strongly recommended.

    For more information, see Encryption context in the Key Management Service Developer Guide.

    *)
  7. key_id : string;
    (*

    Specifies the symmetric encryption KMS key that encrypts the data key. 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.

    *)
}
type encrypt_response = {
  1. encryption_algorithm : encryption_algorithm_spec option;
    (*

    The encryption algorithm that was used to encrypt the plaintext.

    *)
  2. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key that was used to encrypt the plaintext.

    *)
  3. ciphertext_blob : bytes option;
    (*

    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.

    *)
}
type encrypt_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. encryption_algorithm : encryption_algorithm_spec option;
    (*

    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 encryption KMS keys. If you are using an asymmetric KMS key, we recommend RSAES_OAEP_SHA_256.

    The SM2PKE algorithm is only available in China Regions.

    *)
  3. grant_tokens : string list option;
    (*

    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.

    *)
  4. encryption_context : (string * string) list option;
    (*

    Specifies the encryption context that will be used to encrypt the data. An encryption context is valid only for cryptographic operations with a symmetric encryption KMS key. The standard asymmetric encryption algorithms and HMAC algorithms that KMS uses do not support an encryption context.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    An encryption context is a collection of non-secret key-value pairs that represent 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 supported only on operations with symmetric encryption KMS keys. On operations with symmetric encryption KMS keys, an encryption context is optional, but it is strongly recommended.

    For more information, see Encryption context in the Key Management Service Developer Guide.

    *)
  5. plaintext : bytes;
    (*

    Data to be encrypted.

    *)
  6. key_id : string;
    (*

    Identifies the KMS key to use in the encryption operation. The KMS key must have a KeyUsage of ENCRYPT_DECRYPT. 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.

    *)
}
type enable_key_rotation_request = {
  1. rotation_period_in_days : int option;
    (*

    Use this parameter to specify a custom period of time between each rotation date. If no value is specified, the default value is 365 days.

    The rotation period defines the number of days after you enable automatic key rotation that KMS will rotate your key material, and the number of days between each automatic rotation thereafter.

    You can use the kms:RotationPeriodInDays condition key to further constrain the values that principals can specify in the RotationPeriodInDays parameter.

    *)
  2. key_id : string;
    (*

    Identifies a symmetric encryption KMS key. You cannot enable automatic rotation of asymmetric KMS keys, HMAC 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:

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

    *)
}
type enable_key_request = {
  1. key_id : string;
    (*

    Identifies the KMS key to enable.

    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.

    *)
}
type disconnect_custom_key_store_response = unit
type disconnect_custom_key_store_request = {
  1. custom_key_store_id : string;
    (*

    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.

    *)
}
type disable_key_rotation_request = {
  1. key_id : string;
    (*

    Identifies a symmetric encryption KMS key. You cannot enable or disable automatic rotation of asymmetric KMS keys, HMAC 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:

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

    *)
}
type disable_key_request = {
  1. key_id : string;
    (*

    Identifies the KMS key to disable.

    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.

    *)
}
type describe_key_response = {
  1. key_metadata : key_metadata option;
    (*

    Metadata associated with the key.

    *)
}
type describe_key_request = {
  1. grant_tokens : string list option;
    (*

    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.

    *)
  2. key_id : string;
    (*

    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.

    *)
}
type connection_state_type =
  1. | DISCONNECTING
  2. | DISCONNECTED
  3. | FAILED
  4. | CONNECTING
  5. | CONNECTED
type connection_error_code_type =
  1. | XKS_PROXY_INVALID_TLS_CONFIGURATION
  2. | XKS_PROXY_TIMED_OUT
  3. | XKS_VPC_ENDPOINT_SERVICE_INVALID_CONFIGURATION
  4. | XKS_PROXY_INVALID_CONFIGURATION
  5. | XKS_PROXY_INVALID_RESPONSE
  6. | XKS_VPC_ENDPOINT_SERVICE_NOT_FOUND
  7. | XKS_PROXY_NOT_REACHABLE
  8. | XKS_PROXY_ACCESS_DENIED
  9. | INSUFFICIENT_FREE_ADDRESSES_IN_SUBNET
  10. | SUBNET_NOT_FOUND
  11. | USER_LOGGED_IN
  12. | USER_NOT_FOUND
  13. | USER_LOCKED_OUT
  14. | INSUFFICIENT_CLOUDHSM_HSMS
  15. | INTERNAL_ERROR
  16. | NETWORK_ERRORS
  17. | CLUSTER_NOT_FOUND
  18. | INVALID_CREDENTIALS
type custom_key_store_type =
  1. | EXTERNAL_KEY_STORE
  2. | AWS_CLOUDHSM
type custom_key_stores_list_entry = {
  1. xks_proxy_configuration : xks_proxy_configuration_type option;
    (*

    Configuration settings for the external key store proxy (XKS proxy). The external key store proxy translates KMS requests into a format that your external key manager can understand. The proxy configuration includes connection information that KMS requires.

    This field appears only when the CustomKeyStoreType is EXTERNAL_KEY_STORE.

    *)
  2. custom_key_store_type : custom_key_store_type option;
    (*

    Indicates the type of the custom key store. AWS_CLOUDHSM indicates a custom key store backed by an CloudHSM cluster. EXTERNAL_KEY_STORE indicates a custom key store backed by an external key store proxy and external key manager outside of Amazon Web Services.

    *)
  3. creation_date : float option;
    (*

    The date and time when the custom key store was created.

    *)
  4. connection_error_code : connection_error_code_type option;
    (*

    Describes the connection error. This field appears in the response only when the ConnectionState is FAILED.

    Many failures can be resolved by updating the properties of the custom key store. To update a custom key store, disconnect it (DisconnectCustomKeyStore), correct the errors (UpdateCustomKeyStore), and try to connect again (ConnectCustomKeyStore). For additional help resolving these errors, see How to Fix a Connection Failure in Key Management Service Developer Guide.

    All custom key stores:

    • 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.
    • NETWORK_ERRORS — Network errors are preventing KMS from connecting the custom key store to its backing key store.

    CloudHSM key stores:

    • 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.
    • INSUFFICIENT_FREE_ADDRESSES_IN_SUBNET — At least one private subnet associated with the CloudHSM cluster doesn't have any available IP addresses. A CloudHSM key store connection requires one free IP address in each of the associated private subnets, although two are preferable. For details, see How to Fix a Connection Failure in the Key Management Service Developer Guide.
    • INVALID_CREDENTIALS — The KeyStorePassword for the custom key store doesn't match the current password of 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 KeyStorePassword value for 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 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.

    External key stores:

    • INVALID_CREDENTIALS — One or both of the XksProxyAuthenticationCredential values is not valid on the specified external key store proxy.
    • XKS_PROXY_ACCESS_DENIED — KMS requests are denied access to the external key store proxy. If the external key store proxy has authorization rules, verify that they permit KMS to communicate with the proxy on your behalf.
    • XKS_PROXY_INVALID_CONFIGURATION — A configuration error is preventing the external key store from connecting to its proxy. Verify the value of the XksProxyUriPath.
    • XKS_PROXY_INVALID_RESPONSE — KMS cannot interpret the response from the external key store proxy. If you see this connection error code repeatedly, notify your external key store proxy vendor.
    • XKS_PROXY_INVALID_TLS_CONFIGURATION — KMS cannot connect to the external key store proxy because the TLS configuration is invalid. Verify that the XKS proxy supports TLS 1.2 or 1.3. Also, verify that the TLS certificate is not expired, and that it matches the hostname in the XksProxyUriEndpoint value, and that it is signed by a certificate authority included in the Trusted Certificate Authorities list.
    • XKS_PROXY_NOT_REACHABLE — KMS can't communicate with your external key store proxy. Verify that the XksProxyUriEndpoint and XksProxyUriPath are correct. Use the tools for your external key store proxy to verify that the proxy is active and available on its network. Also, verify that your external key manager instances are operating properly. Connection attempts fail with this connection error code if the proxy reports that all external key manager instances are unavailable.
    • XKS_PROXY_TIMED_OUT — KMS can connect to the external key store proxy, but the proxy does not respond to KMS in the time allotted. If you see this connection error code repeatedly, notify your external key store proxy vendor.
    • XKS_VPC_ENDPOINT_SERVICE_INVALID_CONFIGURATION — The Amazon VPC endpoint service configuration doesn't conform to the requirements for an KMS external key store.

      • The VPC endpoint service must be an endpoint service for interface endpoints in the caller's Amazon Web Services account.
      • It must have a network load balancer (NLB) connected to at least two subnets, each in a different Availability Zone.
      • The Allow principals list must include the KMS service principal for the Region,

        cks.kms..amazonaws.com

        , such as cks.kms.us-east-1.amazonaws.com.

      • It must not require acceptance of connection requests.
      • It must have a private DNS name. The private DNS name for an external key store with VPC_ENDPOINT_SERVICE connectivity must be unique in its Amazon Web Services Region.
      • The domain of the private DNS name must have a verification status of verified.
      • The TLS certificate specifies the private DNS hostname at which the endpoint is reachable.
    • XKS_VPC_ENDPOINT_SERVICE_NOT_FOUND — KMS can't find the VPC endpoint service that it uses to communicate with the external key store proxy. Verify that the XksProxyVpcEndpointServiceName is correct and the KMS service principal has service consumer permissions on the Amazon VPC endpoint service.
    *)
  5. connection_state : connection_state_type option;
    (*

    Indicates whether the custom key store is connected to its backing key store. For an CloudHSM key store, the ConnectionState indicates whether it is connected to its CloudHSM cluster. For an external key store, the ConnectionState indicates whether it is connected to the external key store proxy that communicates with your external key manager.

    You can create and use KMS keys in your custom key stores only when its ConnectionState is CONNECTED.

    The ConnectionState value is DISCONNECTED only 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 the backing key store is reachable and active. For an CloudHSM key store, verify that its associated CloudHSM cluster is active and contains at least one active HSM. For an external key store, verify that the external key store proxy and external key manager are connected and enabled.

    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.

    *)
  6. trust_anchor_certificate : string option;
    (*

    The trust anchor certificate of the CloudHSM cluster associated with an CloudHSM key store. When you initialize the cluster, you create this certificate and save it in the customerCA.crt file.

    This field appears only when the CustomKeyStoreType is AWS_CLOUDHSM.

    *)
  7. cloud_hsm_cluster_id : string option;
    (*

    A unique identifier for the CloudHSM cluster that is associated with an CloudHSM key store. This field appears only when the CustomKeyStoreType is AWS_CLOUDHSM.

    *)
  8. custom_key_store_name : string option;
    (*

    The user-specified friendly name for the custom key store.

    *)
  9. custom_key_store_id : string option;
    (*

    A unique identifier for the custom key store.

    *)
}

Contains information about each custom key store in the custom key store list.

type describe_custom_key_stores_response = {
  1. truncated : bool option;
    (*

    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 this response to the Marker parameter in a subsequent request.

    *)
  2. next_marker : string option;
    (*

    When Truncated is true, this element is present and contains the value to use for the Marker parameter in a subsequent request.

    *)
  3. custom_key_stores : custom_key_stores_list_entry list option;
    (*

    Contains metadata about each custom key store.

    *)
}
type describe_custom_key_stores_request = {
  1. marker : string option;
    (*

    Use this parameter in a subsequent request after you receive a response with truncated results. Set it to the value of NextMarker from the truncated response you just received.

    *)
  2. limit : int option;
    (*

    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.

    *)
  3. custom_key_store_name : string option;
    (*

    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, provide either the CustomKeyStoreId or CustomKeyStoreName parameter, but not both.

    *)
  4. custom_key_store_id : string option;
    (*

    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, provide either the CustomKeyStoreId or CustomKeyStoreName parameter, but not both.

    *)
}
type derive_shared_secret_response = {
  1. key_origin : origin_type option;
    (*

    The source of the key material for the specified 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.

    The only valid values for DeriveSharedSecret are AWS_KMS and EXTERNAL. DeriveSharedSecret does not support KMS keys with a KeyOrigin value of AWS_CLOUDHSM or EXTERNAL_KEY_STORE.

    *)
  2. key_agreement_algorithm : key_agreement_algorithm_spec option;
    (*

    Identifies the key agreement algorithm used to derive the shared secret.

    *)
  3. ciphertext_for_recipient : bytes option;
    (*

    The plaintext shared secret encrypted with the public key in the attestation document.

    This field is included in the response only when the Recipient parameter in the request includes a valid attestation document from an Amazon Web Services Nitro enclave. For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  4. shared_secret : bytes option;
    (*

    The raw secret derived from the specified key agreement algorithm, private key in the asymmetric KMS key, and your peer's public key.

    If the response includes the CiphertextForRecipient field, the SharedSecret field is null or empty.

    *)
  5. key_id : string option;
    (*

    Identifies the KMS key used to derive the shared secret.

    *)
}
type derive_shared_secret_request = {
  1. recipient : recipient_info option;
    (*

    A signed attestation document from an Amazon Web Services Nitro enclave and the encryption algorithm to use with the enclave's public key. The only valid encryption algorithm is RSAES_OAEP_SHA_256.

    This parameter only supports attestation documents for Amazon Web Services Nitro Enclaves. To call DeriveSharedSecret for an Amazon Web Services Nitro Enclaves, use the Amazon Web Services Nitro Enclaves SDK to generate the attestation document and then use the Recipient parameter from any Amazon Web Services SDK to provide the attestation document for the enclave.

    When you use this parameter, instead of returning a plaintext copy of the shared secret, KMS encrypts the plaintext shared secret under the public key in the attestation document, and returns the resulting ciphertext in the CiphertextForRecipient field in the response. This ciphertext can be decrypted only with the private key in the enclave. The CiphertextBlob field in the response contains the encrypted shared secret derived from the KMS key specified by the KeyId parameter and public key specified by the PublicKey parameter. The SharedSecret field in the response is null or empty.

    For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  2. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  3. grant_tokens : string list option;
    (*

    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.

    *)
  4. public_key : bytes;
    (*

    Specifies the public key in your peer's NIST-recommended elliptic curve (ECC) or SM2 (China Regions only) key pair.

    The public key must be a DER-encoded X.509 public key, also known as SubjectPublicKeyInfo (SPKI), as defined in RFC 5280.

    GetPublicKey returns the public key of an asymmetric KMS key pair in the required DER-encoded format.

    If you use Amazon Web Services CLI version 1, you must provide the DER-encoded X.509 public key in a file. Otherwise, the Amazon Web Services CLI Base64-encodes the public key a second time, resulting in a ValidationException.

    You can specify the public key as binary data in a file using fileb (

    fileb://

    ) or in-line using a Base64 encoded string.

    *)
  5. key_agreement_algorithm : key_agreement_algorithm_spec;
    (*

    Specifies the key agreement algorithm used to derive the shared secret. The only valid value is ECDH.

    *)
  6. key_id : string;
    (*

    Identifies an asymmetric NIST-recommended ECC or SM2 (China Regions only) KMS key. KMS uses the private key in the specified key pair to derive the shared secret. The key usage of the KMS key must be KEY_AGREEMENT. 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.

    *)
}
type delete_imported_key_material_request = {
  1. key_id : string;
    (*

    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:

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

    *)
}
type custom_key_store_has_cm_ks_exception = {
  1. message : string option;
}

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 delete_custom_key_store_response = unit
type delete_custom_key_store_request = {
  1. custom_key_store_id : string;
    (*

    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.

    *)
}
type delete_alias_request = {
  1. alias_name : string;
    (*

    The alias to be deleted. The alias name must begin with alias/ followed by the alias name, such as alias/ExampleAlias.

    *)
}
type decrypt_response = {
  1. ciphertext_for_recipient : bytes option;
    (*

    The plaintext data encrypted with the public key in the attestation document.

    This field is included in the response only when the Recipient parameter in the request includes a valid attestation document from an Amazon Web Services Nitro enclave. For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  2. encryption_algorithm : encryption_algorithm_spec option;
    (*

    The encryption algorithm that was used to decrypt the ciphertext.

    *)
  3. plaintext : bytes option;
    (*

    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.

    If the response includes the CiphertextForRecipient field, the Plaintext field is null or empty.

    *)
  4. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key that was used to decrypt the ciphertext.

    *)
}
type decrypt_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. recipient : recipient_info option;
    (*

    A signed attestation document from an Amazon Web Services Nitro enclave and the encryption algorithm to use with the enclave's public key. The only valid encryption algorithm is RSAES_OAEP_SHA_256.

    This parameter only supports attestation documents for Amazon Web Services Nitro Enclaves. To include this parameter, use the Amazon Web Services Nitro Enclaves SDK or any Amazon Web Services SDK.

    When you use this parameter, instead of returning the plaintext data, KMS encrypts the plaintext data with the public key in the attestation document, and returns the resulting ciphertext in the CiphertextForRecipient field in the response. This ciphertext can be decrypted only with the private key in the enclave. The Plaintext field in the response is null or empty.

    For information about the interaction between KMS and Amazon Web Services Nitro Enclaves, see How Amazon Web Services Nitro Enclaves uses KMS in the Key Management Service Developer Guide.

    *)
  3. encryption_algorithm : encryption_algorithm_spec option;
    (*

    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 encryption KMS keys.

    *)
  4. key_id : string option;
    (*

    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. If you identify a different KMS key, the Decrypt operation throws an IncorrectKeyException.

    This parameter is required only when the ciphertext was encrypted under an asymmetric KMS key. If you used a symmetric encryption 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.

    *)
  5. grant_tokens : string list option;
    (*

    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.

    *)
  6. encryption_context : (string * string) list option;
    (*

    Specifies the encryption context to use when decrypting the data. An encryption context is valid only for cryptographic operations with a symmetric encryption KMS key. The standard asymmetric encryption algorithms and HMAC algorithms that KMS uses do not support an encryption context.

    An encryption context is a collection of non-secret key-value pairs that represent 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 supported only on operations with symmetric encryption KMS keys. On operations with symmetric encryption KMS keys, an encryption context is optional, but it is strongly recommended.

    For more information, see Encryption context in the Key Management Service Developer Guide.

    *)
  7. ciphertext_blob : bytes;
    (*

    Ciphertext to be decrypted. The blob includes metadata.

    *)
}
type create_key_response = {
  1. key_metadata : key_metadata option;
    (*

    Metadata associated with the KMS key.

    *)
}
type create_key_request = {
  1. xks_key_id : string option;
    (*

    Identifies the external key that serves as key material for the KMS key in an external key store. Specify the ID that the external key store proxy uses to refer to the external key. For help, see the documentation for your external key store proxy.

    This parameter is required for a KMS key with an Origin value of EXTERNAL_KEY_STORE. It is not valid for KMS keys with any other Origin value.

    The external key must be an existing 256-bit AES symmetric encryption key hosted outside of Amazon Web Services in an external key manager associated with the external key store specified by the CustomKeyStoreId parameter. This key must be enabled and configured to perform encryption and decryption. Each KMS key in an external key store must use a different external key. For details, see Requirements for a KMS key in an external key store in the Key Management Service Developer Guide.

    Each KMS key in an external key store is associated two backing keys. One is key material that KMS generates. The other is the external key specified by this parameter. When you use the KMS key in an external key store to encrypt data, the encryption operation is performed first by KMS using the KMS key material, and then by the external key manager using the specified external key, a process known as double encryption. For details, see Double encryption in the Key Management Service Developer Guide.

    *)
  2. multi_region : bool option;
    (*

    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 Multi-Region keys in KMS 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.

    *)
  3. tags : tag list option;
    (*

    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.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    Tagging or untagging a KMS key can allow or deny permission to the KMS key. For details, see ABAC for 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.

    *)
  4. bypass_policy_lockout_safety_check : bool option;
    (*

    Skips ("bypasses") the key policy lockout safety check. The default value is false.

    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, see Default key policy 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.

    *)
  5. custom_key_store_id : string option;
    (*

    Creates the KMS key in the specified custom key store. The ConnectionState of the custom key store must be CONNECTED. To find the CustomKeyStoreID and ConnectionState use the DescribeCustomKeyStores operation.

    This parameter is valid only for symmetric encryption KMS keys in a single Region. You cannot create any other type of KMS key in a custom key store.

    When you create a KMS key in an CloudHSM key store, KMS generates a non-exportable 256-bit symmetric key in its associated CloudHSM cluster and associates it with the KMS key. When you create a KMS key in an external key store, you must use the XksKeyId parameter to specify an external key that serves as key material for the KMS key.

    *)
  6. origin : origin_type option;
    (*

    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 this value to EXTERNAL. For more information about importing key material into KMS, see Importing Key Material in the Key Management Service Developer Guide. The EXTERNAL origin value is valid only for symmetric KMS keys.

    To create a KMS key in an CloudHSM 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 CloudHSM key store. The KeySpec value must be SYMMETRIC_DEFAULT.

    To create a KMS key in an external key store, set this value to EXTERNAL_KEY_STORE. You must also use the CustomKeyStoreId parameter to identify the external key store and the XksKeyId parameter to identify the associated external key. The KeySpec value must be SYMMETRIC_DEFAULT.

    *)
  7. key_spec : key_spec option;
    (*

    Specifies the type of KMS key to create. The default value, SYMMETRIC_DEFAULT, creates a KMS key with a 256-bit AES-GCM key that is used for encryption and decryption, except in China Regions, where it creates a 128-bit symmetric key that uses SM4 encryption. For help choosing a key spec for your KMS key, see Choosing a KMS key type 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 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, kms:MacAlgorithm or kms:Signing Algorithm in the Key Management Service Developer Guide.

    Amazon Web Services services that are integrated with KMS use symmetric encryption KMS keys to protect your data. These services do not support asymmetric KMS keys or HMAC KMS keys.

    KMS supports the following key specs for KMS keys:

    • Symmetric encryption key (default)

      • SYMMETRIC_DEFAULT
    • HMAC keys (symmetric)

      • HMAC_224
      • HMAC_256
      • HMAC_384
      • HMAC_512
    • Asymmetric RSA key pairs (encryption and decryption -or- signing and verification)

      • RSA_2048
      • RSA_3072
      • RSA_4096
    • Asymmetric NIST-recommended elliptic curve key pairs (signing and verification -or- deriving shared secrets)

      • ECC_NIST_P256 (secp256r1)
      • ECC_NIST_P384 (secp384r1)
      • ECC_NIST_P521 (secp521r1)
    • Other asymmetric elliptic curve key pairs (signing and verification)

      • ECC_SECG_P256K1 (secp256k1), commonly used for cryptocurrencies.
    • SM2 key pairs (encryption and decryption -or- signing and verification -or- deriving shared secrets)

      • SM2 (China Regions only)
    *)
  8. customer_master_key_spec : customer_master_key_spec option;
    (*

    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 supports both parameters.

    *)
  9. key_usage : key_usage_type option;
    (*

    Determines the cryptographic operations for which you can use the KMS key. The default value is ENCRYPT_DECRYPT. This parameter is optional when you are creating a symmetric encryption KMS key; otherwise, it is required. You can't change the KeyUsage value after the KMS key is created.

    Select only one valid value.

    • For symmetric encryption KMS keys, omit the parameter or specify ENCRYPT_DECRYPT.
    • For HMAC KMS keys (symmetric), specify GENERATE_VERIFY_MAC.
    • For asymmetric KMS keys with RSA key pairs, specify ENCRYPT_DECRYPT or SIGN_VERIFY.
    • For asymmetric KMS keys with NIST-recommended elliptic curve key pairs, specify SIGN_VERIFY or KEY_AGREEMENT.
    • For asymmetric KMS keys with ECC_SECG_P256K1 key pairs specify SIGN_VERIFY.
    • For asymmetric KMS keys with SM2 key pairs (China Regions only), specify ENCRYPT_DECRYPT, SIGN_VERIFY, or KEY_AGREEMENT.
    *)
  10. description : string option;
    (*

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

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    To set or change the description after the key is created, use UpdateKeyDescription.

    *)
  11. policy : string option;
    (*

    The key policy to attach to the KMS key.

    If you provide a key policy, it must meet the following criteria:

    • The key policy must allow the calling principal to make a subsequent PutKeyPolicy request on the KMS key. This reduces the risk that the KMS key becomes unmanageable. For more information, see Default key policy in the Key Management Service Developer Guide. (To omit this condition, set BypassPolicyLockoutSafetyCheck to true.)
    • 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, 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.

    *)
}
type create_grant_response = {
  1. grant_id : string option;
    (*

    The unique identifier for the grant.

    You can use the GrantId in a ListGrants, RetireGrant, or RevokeGrant operation.

    *)
  2. grant_token : string option;
    (*

    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.

    *)
}
type create_grant_request = {
  1. dry_run : bool option;
    (*

    Checks if your request will succeed. DryRun is an optional parameter.

    To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.

    *)
  2. name : string option;
    (*

    A friendly name for the grant. Use this value to prevent the unintended creation of duplicate grants when retrying this request.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    When this value is absent, all CreateGrant requests result in a new grant with a unique GrantId even if all the supplied parameters are identical. This can result in unintended duplicates when you retry the CreateGrant request.

    When this value is present, you can retry a CreateGrant request with identical parameters; if the grant already exists, the original GrantId is returned without creating a new grant. Note that the returned grant token is unique with every CreateGrant request, even when a duplicate GrantId is returned. All grant tokens for the same grant ID can be used interchangeably.

    *)
  3. grant_tokens : string list option;
    (*

    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.

    *)
  4. constraints : grant_constraints option;
    (*

    Specifies a grant constraint.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    KMS supports the EncryptionContextEquals and EncryptionContextSubset grant constraints, which allow the permissions in the grant only when the encryption context in the request matches (EncryptionContextEquals) or includes (EncryptionContextSubset) the encryption context specified in the constraint.

    The encryption context grant constraints are supported only on grant operations that include an EncryptionContext parameter, such as cryptographic operations on symmetric encryption KMS keys. Grants with grant constraints can include the DescribeKey and RetireGrant operations, but the constraint doesn't apply to these operations. If a grant with a grant constraint includes the CreateGrant operation, the constraint requires that any grants created with the CreateGrant permission have an equally strict or stricter encryption context constraint.

    You cannot use an encryption context grant constraint for cryptographic operations with asymmetric KMS keys or HMAC KMS keys. Operations with these keys don't support an encryption context.

    Each constraint value can include up to 8 encryption context pairs. The encryption context value in each constraint cannot exceed 384 characters. 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.

    *)
  5. operations : grant_operation list;
    (*

    A list of operations that the grant permits.

    This list must include only operations that are permitted in a grant. Also, the operation must be supported on the KMS key. For example, you cannot create a grant for a symmetric encryption 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.

    *)
  6. retiring_principal : string option;
    (*

    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 principals include Amazon Web Services accounts, IAM users, IAM roles, federated users, and assumed role users. For help with the ARN syntax for a principal, see IAM ARNs in the Identity and Access Management User Guide.

    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.

    *)
  7. grantee_principal : string;
    (*

    The identity that gets the permissions specified in the grant.

    To specify the grantee principal, use the Amazon Resource Name (ARN) of an Amazon Web Services principal. Valid principals include Amazon Web Services accounts, IAM users, IAM roles, federated users, and assumed role users. For help with the ARN syntax for a principal, see IAM ARNs in the Identity and Access Management User Guide.

    *)
  8. key_id : string;
    (*

    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:

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

    *)
}
type incorrect_trust_anchor_exception = {
  1. message : string option;
}

The request was rejected because the trust anchor certificate in the request to create an CloudHSM key store is not the trust anchor certificate for the specified CloudHSM cluster.

When you initialize the CloudHSM cluster, you create the trust anchor certificate and save it in the customerCA.crt file.

type cloud_hsm_cluster_in_use_exception = {
  1. message : string option;
}

The request was rejected because the specified CloudHSM cluster is already associated with an CloudHSM key store in the account, or it shares a backup history with an CloudHSM key store in the account. Each CloudHSM key store in the account must be associated with a different CloudHSM cluster.

CloudHSM clusters that share a backup history have the same cluster certificate. To view the cluster certificate of an CloudHSM cluster, use the DescribeClusters operation.

type create_custom_key_store_response = {
  1. custom_key_store_id : string option;
    (*

    A unique identifier for the new custom key store.

    *)
}
type create_custom_key_store_request = {
  1. xks_proxy_connectivity : xks_proxy_connectivity_type option;
    (*

    Indicates how KMS communicates with the external key store proxy. This parameter is required for custom key stores with a CustomKeyStoreType of EXTERNAL_KEY_STORE.

    If the external key store proxy uses a public endpoint, specify PUBLIC_ENDPOINT. If the external key store proxy uses a Amazon VPC endpoint service for communication with KMS, specify VPC_ENDPOINT_SERVICE. For help making this choice, see Choosing a connectivity option in the Key Management Service Developer Guide.

    An Amazon VPC endpoint service keeps your communication with KMS in a private address space entirely within Amazon Web Services, but it requires more configuration, including establishing a Amazon VPC with multiple subnets, a VPC endpoint service, a network load balancer, and a verified private DNS name. A public endpoint is simpler to set up, but it might be slower and might not fulfill your security requirements. You might consider testing with a public endpoint, and then establishing a VPC endpoint service for production tasks. Note that this choice does not determine the location of the external key store proxy. Even if you choose a VPC endpoint service, the proxy can be hosted within the VPC or outside of Amazon Web Services such as in your corporate data center.

    *)
  2. xks_proxy_authentication_credential : xks_proxy_authentication_credential_type option;
    (*

    Specifies an authentication credential for the external key store proxy (XKS proxy). This parameter is required for all custom key stores with a CustomKeyStoreType of EXTERNAL_KEY_STORE.

    The XksProxyAuthenticationCredential has two required elements: RawSecretAccessKey, a secret key, and AccessKeyId, a unique identifier for the RawSecretAccessKey. For character requirements, see XksProxyAuthenticationCredentialType.

    KMS uses this authentication credential to sign requests to the external key store proxy on your behalf. This credential is unrelated to Identity and Access Management (IAM) and Amazon Web Services credentials.

    This parameter doesn't set or change the authentication credentials on the XKS proxy. It just tells KMS the credential that you established on your external key store proxy. If you rotate your proxy authentication credential, use the UpdateCustomKeyStore operation to provide the new credential to KMS.

    *)
  3. xks_proxy_vpc_endpoint_service_name : string option;
    (*

    Specifies the name of the Amazon VPC endpoint service for interface endpoints that is used to communicate with your external key store proxy (XKS proxy). This parameter is required when the value of CustomKeyStoreType is EXTERNAL_KEY_STORE and the value of XksProxyConnectivity is VPC_ENDPOINT_SERVICE.

    The Amazon VPC endpoint service must fulfill all requirements for use with an external key store.

    Uniqueness requirements:

    • External key stores with VPC_ENDPOINT_SERVICE connectivity can share an Amazon VPC, but each external key store must have its own VPC endpoint service and private DNS name.
    *)
  4. xks_proxy_uri_path : string option;
    (*

    Specifies the base path to the proxy APIs for this external key store. To find this value, see the documentation for your external key store proxy. This parameter is required for all custom key stores with a CustomKeyStoreType of EXTERNAL_KEY_STORE.

    The value must start with / and must end with /kms/xks/v1 where v1 represents the version of the KMS external key store proxy API. This path can include an optional prefix between the required elements such as

    /{i prefix}/kms/xks/v1

    .

    Uniqueness requirements:

    • The combined XksProxyUriEndpoint and XksProxyUriPath values must be unique in the Amazon Web Services account and Region.
    *)
  5. xks_proxy_uri_endpoint : string option;
    (*

    Specifies the endpoint that KMS uses to send requests to the external key store proxy (XKS proxy). This parameter is required for custom key stores with a CustomKeyStoreType of EXTERNAL_KEY_STORE.

    The protocol must be HTTPS. KMS communicates on port 443. Do not specify the port in the XksProxyUriEndpoint value.

    For external key stores with XksProxyConnectivity value of VPC_ENDPOINT_SERVICE, specify https:// followed by the private DNS name of the VPC endpoint service.

    For external key stores with PUBLIC_ENDPOINT connectivity, this endpoint must be reachable before you create the custom key store. KMS connects to the external key store proxy while creating the custom key store. For external key stores with VPC_ENDPOINT_SERVICE connectivity, KMS connects when you call the ConnectCustomKeyStore operation.

    The value of this parameter must begin with https://. The remainder can contain upper and lower case letters (A-Z and a-z), numbers (0-9), dots (.), and hyphens (-). Additional slashes (/ and ]) are not permitted. {b Uniqueness requirements:} {ul {- The combined [XksProxyUriEndpoint] and [XksProxyUriPath] values must be unique in the Amazon Web Services account and Region. } {- An external key store with [PUBLIC_ENDPOINT] connectivity cannot use the same [XksProxyUriEndpoint] value as an external key store with [VPC_ENDPOINT_SERVICE] connectivity in this Amazon Web Services Region. } {- Each external key store with [VPC_ENDPOINT_SERVICE] connectivity must have its own private DNS name. The [XksProxyUriEndpoint] value for external key stores with [VPC_ENDPOINT_SERVICE] connectivity (private DNS name) must be unique in the Amazon Web Services account and Region. } }

    *)
  6. custom_key_store_type : custom_key_store_type option;
    (*

    Specifies the type of custom key store. The default value is AWS_CLOUDHSM.

    For a custom key store backed by an CloudHSM cluster, omit the parameter or enter AWS_CLOUDHSM. For a custom key store backed by an external key manager outside of Amazon Web Services, enter EXTERNAL_KEY_STORE. You cannot change this property after the key store is created.

    *)
  7. key_store_password : string option;
    (*

    Specifies the kmsuser password for an CloudHSM key store. This parameter is required for custom key stores with a CustomKeyStoreType of AWS_CLOUDHSM.

    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.

    *)
  8. trust_anchor_certificate : string option;
    (*

    Specifies the certificate for an CloudHSM key store. This parameter is required for custom key stores with a CustomKeyStoreType of AWS_CLOUDHSM.

    Enter the content of the trust anchor certificate for the CloudHSM cluster. This is the content of the customerCA.crt file that you created when you initialized the cluster.

    *)
  9. cloud_hsm_cluster_id : string option;
    (*

    Identifies the CloudHSM cluster for an CloudHSM key store. This parameter is required for custom key stores with CustomKeyStoreType of AWS_CLOUDHSM.

    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.

    *)
  10. custom_key_store_name : string;
    (*

    Specifies a friendly name for the custom key store. The name must be unique in your Amazon Web Services account and Region. This parameter is required for all custom key stores.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    *)
}
type invalid_alias_name_exception = {
  1. message : string option;
}

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

type create_alias_request = {
  1. target_key_id : string;
    (*

    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:

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

    *)
  2. alias_name : string;
    (*

    Specifies the alias name. This value must begin with alias/ followed by a name, such as alias/ExampleAlias.

    Do not include confidential or sensitive information in this field. This field may be displayed in plaintext in CloudTrail logs and other output.

    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.

    *)
}
type connect_custom_key_store_response = unit
type connect_custom_key_store_request = {
  1. custom_key_store_id : string;
    (*

    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.

    *)
}
type cancel_key_deletion_response = {
  1. key_id : string option;
    (*

    The Amazon Resource Name (key ARN) of the KMS key whose deletion is canceled.

    *)
}
type cancel_key_deletion_request = {
  1. key_id : string;
    (*

    Identifies the KMS key whose deletion is being canceled.

    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.

    *)
}

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

If you need to use FIPS 140-2 validated cryptographic modules when communicating with Amazon Web Services, use the FIPS endpoint in your preferred Amazon Web Services Region. For more information about the available FIPS endpoints, see Service endpoints in the Key Management Service topic of the Amazon Web Services General Reference.

All KMS API calls must be signed and be transmitted using Transport Layer Security (TLS). KMS recommends you always use the latest supported TLS version. 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 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 access key for everyday work. You can use the access key ID and secret access key for an IAM user or you can use the Security Token Service (STS) to generate temporary security credentials and use those to sign requests.

All KMS requests must be signed with 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.

type base_document = Smaws_Lib.Json.t

Builders

val make_xks_proxy_configuration_type : ?vpc_endpoint_service_name:string -> ?uri_path:string -> ?uri_endpoint:string -> ?access_key_id:string -> ?connectivity:xks_proxy_connectivity_type -> unit -> xks_proxy_configuration_type
val make_xks_proxy_authentication_credential_type : raw_secret_access_key:string -> access_key_id:string -> unit -> xks_proxy_authentication_credential_type
val make_xks_key_configuration_type : ?id:string -> unit -> xks_key_configuration_type
val make_verify_response : ?signing_algorithm:signing_algorithm_spec -> ?signature_valid:bool -> ?key_id:string -> unit -> verify_response

Create a verify_response type

val make_verify_request : ?dry_run:bool -> ?grant_tokens:string list -> ?message_type:message_type -> signing_algorithm:signing_algorithm_spec -> signature:bytes -> message:bytes -> key_id:string -> unit -> verify_request

Create a verify_request type

val make_verify_mac_response : ?mac_algorithm:mac_algorithm_spec -> ?mac_valid:bool -> ?key_id:string -> unit -> verify_mac_response

Create a verify_mac_response type

val make_verify_mac_request : ?dry_run:bool -> ?grant_tokens:string list -> mac:bytes -> mac_algorithm:mac_algorithm_spec -> key_id:string -> message:bytes -> unit -> verify_mac_request

Create a verify_mac_request type

val make_update_primary_region_request : primary_region:string -> key_id:string -> unit -> update_primary_region_request
val make_update_key_description_request : description:string -> key_id:string -> unit -> update_key_description_request
val make_update_custom_key_store_response : unit -> update_custom_key_store_response
val make_update_custom_key_store_request : ?xks_proxy_connectivity:xks_proxy_connectivity_type -> ?xks_proxy_authentication_credential:xks_proxy_authentication_credential_type -> ?xks_proxy_vpc_endpoint_service_name:string -> ?xks_proxy_uri_path:string -> ?xks_proxy_uri_endpoint:string -> ?cloud_hsm_cluster_id:string -> ?key_store_password:string -> ?new_custom_key_store_name:string -> custom_key_store_id:string -> unit -> update_custom_key_store_request
val make_update_alias_request : target_key_id:string -> alias_name:string -> unit -> update_alias_request

Create a update_alias_request type

val make_untag_resource_request : tag_keys:string list -> key_id:string -> unit -> untag_resource_request
val make_tag : tag_value:string -> tag_key:string -> unit -> tag

Create a tag type

val make_tag_resource_request : tags:tag list -> key_id:string -> unit -> tag_resource_request

Create a tag_resource_request type

val make_sign_response : ?signing_algorithm:signing_algorithm_spec -> ?signature:bytes -> ?key_id:string -> unit -> sign_response

Create a sign_response type

val make_sign_request : ?dry_run:bool -> ?grant_tokens:string list -> ?message_type:message_type -> signing_algorithm:signing_algorithm_spec -> message:bytes -> key_id:string -> unit -> sign_request

Create a sign_request type

val make_schedule_key_deletion_response : ?pending_window_in_days:int -> ?key_state:key_state -> ?deletion_date:float -> ?key_id:string -> unit -> schedule_key_deletion_response
val make_schedule_key_deletion_request : ?pending_window_in_days:int -> key_id:string -> unit -> schedule_key_deletion_request
val make_rotate_key_on_demand_response : ?key_id:string -> unit -> rotate_key_on_demand_response
val make_rotate_key_on_demand_request : key_id:string -> unit -> rotate_key_on_demand_request
val make_revoke_grant_request : ?dry_run:bool -> grant_id:string -> key_id:string -> unit -> revoke_grant_request

Create a revoke_grant_request type

val make_retire_grant_request : ?dry_run:bool -> ?grant_id:string -> ?key_id:string -> ?grant_token:string -> unit -> retire_grant_request

Create a retire_grant_request type

val make_multi_region_key : ?region:string -> ?arn:string -> unit -> multi_region_key

Create a multi_region_key type

val make_multi_region_configuration : ?replica_keys:multi_region_key list -> ?primary_key:multi_region_key -> ?multi_region_key_type:multi_region_key_type -> unit -> multi_region_configuration
val make_key_metadata : ?xks_key_configuration:xks_key_configuration_type -> ?mac_algorithms:mac_algorithm_spec list -> ?pending_deletion_window_in_days:int -> ?multi_region_configuration:multi_region_configuration -> ?multi_region:bool -> ?key_agreement_algorithms:key_agreement_algorithm_spec list -> ?signing_algorithms:signing_algorithm_spec list -> ?encryption_algorithms:encryption_algorithm_spec list -> ?key_spec:key_spec -> ?customer_master_key_spec:customer_master_key_spec -> ?key_manager:key_manager_type -> ?expiration_model:expiration_model_type -> ?cloud_hsm_cluster_id:string -> ?custom_key_store_id:string -> ?origin:origin_type -> ?valid_to:float -> ?deletion_date:float -> ?key_state:key_state -> ?key_usage:key_usage_type -> ?description:string -> ?enabled:bool -> ?creation_date:float -> ?arn:string -> ?aws_account_id:string -> key_id:string -> unit -> key_metadata

Create a key_metadata type

val make_replicate_key_response : ?replica_tags:tag list -> ?replica_policy:string -> ?replica_key_metadata:key_metadata -> unit -> replicate_key_response
val make_replicate_key_request : ?tags:tag list -> ?description:string -> ?bypass_policy_lockout_safety_check:bool -> ?policy:string -> replica_region:string -> key_id:string -> unit -> replicate_key_request

Create a replicate_key_request type

val make_re_encrypt_response : ?destination_encryption_algorithm:encryption_algorithm_spec -> ?source_encryption_algorithm:encryption_algorithm_spec -> ?key_id:string -> ?source_key_id:string -> ?ciphertext_blob:bytes -> unit -> re_encrypt_response

Create a re_encrypt_response type

val make_re_encrypt_request : ?dry_run:bool -> ?grant_tokens:string list -> ?destination_encryption_algorithm:encryption_algorithm_spec -> ?source_encryption_algorithm:encryption_algorithm_spec -> ?destination_encryption_context:(string * string) list -> ?source_key_id:string -> ?source_encryption_context:(string * string) list -> destination_key_id:string -> ciphertext_blob:bytes -> unit -> re_encrypt_request

Create a re_encrypt_request type

val make_put_key_policy_request : ?bypass_policy_lockout_safety_check:bool -> ?policy_name:string -> policy:string -> key_id:string -> unit -> put_key_policy_request
val make_grant_constraints : ?encryption_context_equals:(string * string) list -> ?encryption_context_subset:(string * string) list -> unit -> grant_constraints

Create a grant_constraints type

val make_grant_list_entry : ?constraints:grant_constraints -> ?operations:grant_operation list -> ?issuing_account:string -> ?retiring_principal:string -> ?grantee_principal:string -> ?creation_date:float -> ?name:string -> ?grant_id:string -> ?key_id:string -> unit -> grant_list_entry

Create a grant_list_entry type

val make_list_grants_response : ?truncated:bool -> ?next_marker:string -> ?grants:grant_list_entry list -> unit -> list_grants_response

Create a list_grants_response type

val make_list_retirable_grants_request : ?marker:string -> ?limit:int -> retiring_principal:string -> unit -> list_retirable_grants_request
val make_list_resource_tags_response : ?truncated:bool -> ?next_marker:string -> ?tags:tag list -> unit -> list_resource_tags_response
val make_list_resource_tags_request : ?marker:string -> ?limit:int -> key_id:string -> unit -> list_resource_tags_request
val make_key_list_entry : ?key_arn:string -> ?key_id:string -> unit -> key_list_entry

Create a key_list_entry type

val make_list_keys_response : ?truncated:bool -> ?next_marker:string -> ?keys:key_list_entry list -> unit -> list_keys_response

Create a list_keys_response type

val make_list_keys_request : ?marker:string -> ?limit:int -> unit -> list_keys_request

Create a list_keys_request type

val make_rotations_list_entry : ?rotation_type:rotation_type -> ?rotation_date:float -> ?key_id:string -> unit -> rotations_list_entry

Create a rotations_list_entry type

val make_list_key_rotations_response : ?truncated:bool -> ?next_marker:string -> ?rotations:rotations_list_entry list -> unit -> list_key_rotations_response
val make_list_key_rotations_request : ?marker:string -> ?limit:int -> key_id:string -> unit -> list_key_rotations_request
val make_list_key_policies_response : ?truncated:bool -> ?next_marker:string -> ?policy_names:string list -> unit -> list_key_policies_response
val make_list_key_policies_request : ?marker:string -> ?limit:int -> key_id:string -> unit -> list_key_policies_request
val make_list_grants_request : ?grantee_principal:string -> ?grant_id:string -> ?marker:string -> ?limit:int -> key_id:string -> unit -> list_grants_request

Create a list_grants_request type

val make_alias_list_entry : ?last_updated_date:float -> ?creation_date:float -> ?target_key_id:string -> ?alias_arn:string -> ?alias_name:string -> unit -> alias_list_entry

Create a alias_list_entry type

val make_list_aliases_response : ?truncated:bool -> ?next_marker:string -> ?aliases:alias_list_entry list -> unit -> list_aliases_response

Create a list_aliases_response type

val make_list_aliases_request : ?marker:string -> ?limit:int -> ?key_id:string -> unit -> list_aliases_request

Create a list_aliases_request type

val make_import_key_material_response : unit -> import_key_material_response
val make_import_key_material_request : ?expiration_model:expiration_model_type -> ?valid_to:float -> encrypted_key_material:bytes -> import_token:bytes -> key_id:string -> unit -> import_key_material_request
val make_get_public_key_response : ?key_agreement_algorithms:key_agreement_algorithm_spec list -> ?signing_algorithms:signing_algorithm_spec list -> ?encryption_algorithms:encryption_algorithm_spec list -> ?key_usage:key_usage_type -> ?key_spec:key_spec -> ?customer_master_key_spec:customer_master_key_spec -> ?public_key:bytes -> ?key_id:string -> unit -> get_public_key_response
val make_get_public_key_request : ?grant_tokens:string list -> key_id:string -> unit -> get_public_key_request
val make_get_parameters_for_import_response : ?parameters_valid_to:float -> ?public_key:bytes -> ?import_token:bytes -> ?key_id:string -> unit -> get_parameters_for_import_response
val make_get_parameters_for_import_request : wrapping_key_spec:wrapping_key_spec -> wrapping_algorithm:algorithm_spec -> key_id:string -> unit -> get_parameters_for_import_request
val make_get_key_rotation_status_response : ?on_demand_rotation_start_date:float -> ?next_rotation_date:float -> ?rotation_period_in_days:int -> ?key_id:string -> ?key_rotation_enabled:bool -> unit -> get_key_rotation_status_response
val make_get_key_rotation_status_request : key_id:string -> unit -> get_key_rotation_status_request
val make_get_key_policy_response : ?policy_name:string -> ?policy:string -> unit -> get_key_policy_response
val make_get_key_policy_request : ?policy_name:string -> key_id:string -> unit -> get_key_policy_request
val make_generate_random_response : ?ciphertext_for_recipient:bytes -> ?plaintext:bytes -> unit -> generate_random_response
val make_recipient_info : ?attestation_document:bytes -> ?key_encryption_algorithm:key_encryption_mechanism -> unit -> recipient_info

Create a recipient_info type

val make_generate_random_request : ?recipient:recipient_info -> ?custom_key_store_id:string -> ?number_of_bytes:int -> unit -> generate_random_request
val make_generate_mac_response : ?key_id:string -> ?mac_algorithm:mac_algorithm_spec -> ?mac:bytes -> unit -> generate_mac_response

Create a generate_mac_response type

val make_generate_mac_request : ?dry_run:bool -> ?grant_tokens:string list -> mac_algorithm:mac_algorithm_spec -> key_id:string -> message:bytes -> unit -> generate_mac_request

Create a generate_mac_request type

val make_generate_data_key_without_plaintext_response : ?key_id:string -> ?ciphertext_blob:bytes -> unit -> generate_data_key_without_plaintext_response
val make_generate_data_key_without_plaintext_request : ?dry_run:bool -> ?grant_tokens:string list -> ?number_of_bytes:int -> ?key_spec:data_key_spec -> ?encryption_context:(string * string) list -> key_id:string -> unit -> generate_data_key_without_plaintext_request
val make_generate_data_key_pair_without_plaintext_response : ?key_pair_spec:data_key_pair_spec -> ?key_id:string -> ?public_key:bytes -> ?private_key_ciphertext_blob:bytes -> unit -> generate_data_key_pair_without_plaintext_response
val make_generate_data_key_pair_without_plaintext_request : ?dry_run:bool -> ?grant_tokens:string list -> ?encryption_context:(string * string) list -> key_pair_spec:data_key_pair_spec -> key_id:string -> unit -> generate_data_key_pair_without_plaintext_request
val make_generate_data_key_pair_response : ?ciphertext_for_recipient:bytes -> ?key_pair_spec:data_key_pair_spec -> ?key_id:string -> ?public_key:bytes -> ?private_key_plaintext:bytes -> ?private_key_ciphertext_blob:bytes -> unit -> generate_data_key_pair_response
val make_generate_data_key_pair_request : ?dry_run:bool -> ?recipient:recipient_info -> ?grant_tokens:string list -> ?encryption_context:(string * string) list -> key_pair_spec:data_key_pair_spec -> key_id:string -> unit -> generate_data_key_pair_request
val make_generate_data_key_response : ?ciphertext_for_recipient:bytes -> ?key_id:string -> ?plaintext:bytes -> ?ciphertext_blob:bytes -> unit -> generate_data_key_response
val make_generate_data_key_request : ?dry_run:bool -> ?recipient:recipient_info -> ?grant_tokens:string list -> ?key_spec:data_key_spec -> ?number_of_bytes:int -> ?encryption_context:(string * string) list -> key_id:string -> unit -> generate_data_key_request
val make_encrypt_response : ?encryption_algorithm:encryption_algorithm_spec -> ?key_id:string -> ?ciphertext_blob:bytes -> unit -> encrypt_response

Create a encrypt_response type

val make_encrypt_request : ?dry_run:bool -> ?encryption_algorithm:encryption_algorithm_spec -> ?grant_tokens:string list -> ?encryption_context:(string * string) list -> plaintext:bytes -> key_id:string -> unit -> encrypt_request

Create a encrypt_request type

val make_enable_key_rotation_request : ?rotation_period_in_days:int -> key_id:string -> unit -> enable_key_rotation_request
val make_enable_key_request : key_id:string -> unit -> enable_key_request

Create a enable_key_request type

val make_disconnect_custom_key_store_response : unit -> disconnect_custom_key_store_response
val make_disconnect_custom_key_store_request : custom_key_store_id:string -> unit -> disconnect_custom_key_store_request
val make_disable_key_rotation_request : key_id:string -> unit -> disable_key_rotation_request
val make_disable_key_request : key_id:string -> unit -> disable_key_request

Create a disable_key_request type

val make_describe_key_response : ?key_metadata:key_metadata -> unit -> describe_key_response

Create a describe_key_response type

val make_describe_key_request : ?grant_tokens:string list -> key_id:string -> unit -> describe_key_request

Create a describe_key_request type

val make_custom_key_stores_list_entry : ?xks_proxy_configuration:xks_proxy_configuration_type -> ?custom_key_store_type:custom_key_store_type -> ?creation_date:float -> ?connection_error_code:connection_error_code_type -> ?connection_state:connection_state_type -> ?trust_anchor_certificate:string -> ?cloud_hsm_cluster_id:string -> ?custom_key_store_name:string -> ?custom_key_store_id:string -> unit -> custom_key_stores_list_entry
val make_describe_custom_key_stores_response : ?truncated:bool -> ?next_marker:string -> ?custom_key_stores:custom_key_stores_list_entry list -> unit -> describe_custom_key_stores_response
val make_describe_custom_key_stores_request : ?marker:string -> ?limit:int -> ?custom_key_store_name:string -> ?custom_key_store_id:string -> unit -> describe_custom_key_stores_request
val make_derive_shared_secret_response : ?key_origin:origin_type -> ?key_agreement_algorithm:key_agreement_algorithm_spec -> ?ciphertext_for_recipient:bytes -> ?shared_secret:bytes -> ?key_id:string -> unit -> derive_shared_secret_response
val make_derive_shared_secret_request : ?recipient:recipient_info -> ?dry_run:bool -> ?grant_tokens:string list -> public_key:bytes -> key_agreement_algorithm:key_agreement_algorithm_spec -> key_id:string -> unit -> derive_shared_secret_request
val make_delete_imported_key_material_request : key_id:string -> unit -> delete_imported_key_material_request
val make_delete_custom_key_store_response : unit -> delete_custom_key_store_response
val make_delete_custom_key_store_request : custom_key_store_id:string -> unit -> delete_custom_key_store_request
val make_delete_alias_request : alias_name:string -> unit -> delete_alias_request

Create a delete_alias_request type

val make_decrypt_response : ?ciphertext_for_recipient:bytes -> ?encryption_algorithm:encryption_algorithm_spec -> ?plaintext:bytes -> ?key_id:string -> unit -> decrypt_response

Create a decrypt_response type

val make_decrypt_request : ?dry_run:bool -> ?recipient:recipient_info -> ?encryption_algorithm:encryption_algorithm_spec -> ?key_id:string -> ?grant_tokens:string list -> ?encryption_context:(string * string) list -> ciphertext_blob:bytes -> unit -> decrypt_request

Create a decrypt_request type

val make_create_key_response : ?key_metadata:key_metadata -> unit -> create_key_response

Create a create_key_response type

val make_create_key_request : ?xks_key_id:string -> ?multi_region:bool -> ?tags:tag list -> ?bypass_policy_lockout_safety_check:bool -> ?custom_key_store_id:string -> ?origin:origin_type -> ?key_spec:key_spec -> ?customer_master_key_spec:customer_master_key_spec -> ?key_usage:key_usage_type -> ?description:string -> ?policy:string -> unit -> create_key_request

Create a create_key_request type

val make_create_grant_response : ?grant_id:string -> ?grant_token:string -> unit -> create_grant_response

Create a create_grant_response type

val make_create_grant_request : ?dry_run:bool -> ?name:string -> ?grant_tokens:string list -> ?constraints:grant_constraints -> ?retiring_principal:string -> operations:grant_operation list -> grantee_principal:string -> key_id:string -> unit -> create_grant_request

Create a create_grant_request type

val make_create_custom_key_store_response : ?custom_key_store_id:string -> unit -> create_custom_key_store_response
val make_create_custom_key_store_request : ?xks_proxy_connectivity:xks_proxy_connectivity_type -> ?xks_proxy_authentication_credential:xks_proxy_authentication_credential_type -> ?xks_proxy_vpc_endpoint_service_name:string -> ?xks_proxy_uri_path:string -> ?xks_proxy_uri_endpoint:string -> ?custom_key_store_type:custom_key_store_type -> ?key_store_password:string -> ?trust_anchor_certificate:string -> ?cloud_hsm_cluster_id:string -> custom_key_store_name:string -> unit -> create_custom_key_store_request
val make_create_alias_request : target_key_id:string -> alias_name:string -> unit -> create_alias_request

Create a create_alias_request type

val make_connect_custom_key_store_response : unit -> connect_custom_key_store_response
val make_connect_custom_key_store_request : custom_key_store_id:string -> unit -> connect_custom_key_store_request
val make_cancel_key_deletion_response : ?key_id:string -> unit -> cancel_key_deletion_response
val make_cancel_key_deletion_request : key_id:string -> unit -> cancel_key_deletion_request

Operations

module CancelKeyDeletion : sig ... end
module ConnectCustomKeyStore : sig ... end
module CreateAlias : sig ... end
module CreateCustomKeyStore : sig ... end
module CreateGrant : sig ... end
module CreateKey : sig ... end
module Decrypt : sig ... end
module DeleteAlias : sig ... end
module DeleteCustomKeyStore : sig ... end
module DeleteImportedKeyMaterial : sig ... end
module DeriveSharedSecret : sig ... end
module DescribeCustomKeyStores : sig ... end
module DescribeKey : sig ... end
module DisableKey : sig ... end
module DisableKeyRotation : sig ... end
module DisconnectCustomKeyStore : sig ... end
module EnableKey : sig ... end
module EnableKeyRotation : sig ... end
module Encrypt : sig ... end
module GenerateDataKey : sig ... end
module GenerateDataKeyPair : sig ... end
module GenerateDataKeyWithoutPlaintext : sig ... end
module GenerateMac : sig ... end
module GenerateRandom : sig ... end
module GetKeyPolicy : sig ... end
module GetKeyRotationStatus : sig ... end
module GetParametersForImport : sig ... end
module GetPublicKey : sig ... end
module ImportKeyMaterial : sig ... end
module ListAliases : sig ... end
module ListGrants : sig ... end
module ListKeyPolicies : sig ... end
module ListKeyRotations : sig ... end
module ListKeys : sig ... end
module ListResourceTags : sig ... end
module ListRetirableGrants : sig ... end
module PutKeyPolicy : sig ... end
module ReEncrypt : sig ... end
module ReplicateKey : sig ... end
module RetireGrant : sig ... end
module RevokeGrant : sig ... end
module RotateKeyOnDemand : sig ... end
module ScheduleKeyDeletion : sig ... end
module Sign : sig ... end
module TagResource : sig ... end
module UntagResource : sig ... end
module UpdateAlias : sig ... end
module UpdateCustomKeyStore : sig ... end
module UpdateKeyDescription : sig ... end
module UpdatePrimaryRegion : sig ... end
module Verify : sig ... end
module VerifyMac : sig ... end