View source: R/kms_operations.R
kms_create_custom_key_store | R Documentation |
Creates a custom key store backed by a key store that you own and manage. When you use a KMS key in a custom key store for a cryptographic operation, the cryptographic operation is actually performed in your key store using your keys. KMS supports CloudHSM key stores backed by an CloudHSM cluster and external key stores backed by an external key store proxy and external key manager outside of Amazon Web Services.
See https://www.paws-r-sdk.com/docs/kms_create_custom_key_store/ for full documentation.
kms_create_custom_key_store(
CustomKeyStoreName,
CloudHsmClusterId = NULL,
TrustAnchorCertificate = NULL,
KeyStorePassword = NULL,
CustomKeyStoreType = NULL,
XksProxyUriEndpoint = NULL,
XksProxyUriPath = NULL,
XksProxyVpcEndpointServiceName = NULL,
XksProxyAuthenticationCredential = NULL,
XksProxyConnectivity = NULL
)
CustomKeyStoreName |
[required] 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. |
CloudHsmClusterId |
Identifies the CloudHSM cluster for an CloudHSM key store. This
parameter is required for custom key stores with 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. |
TrustAnchorCertificate |
Specifies the certificate for an CloudHSM key store. This parameter is
required for custom key stores with a Enter the content of the trust anchor certificate for the CloudHSM
cluster. This is the content of the |
KeyStorePassword |
Specifies the Enter the password of the The password must be a string of 7 to 32 characters. Its value is case sensitive. This parameter tells KMS the |
CustomKeyStoreType |
Specifies the type of custom key store. The default value is
For a custom key store backed by an CloudHSM cluster, omit the parameter
or enter |
XksProxyUriEndpoint |
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 The protocol must be HTTPS. KMS communicates on port 443. Do not specify
the port in the For external key stores with For external key stores with The value of this parameter must begin with Uniqueness requirements:
|
XksProxyUriPath |
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
The value must start with Uniqueness requirements:
|
XksProxyVpcEndpointServiceName |
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
The Amazon VPC endpoint service must fulfill all requirements for use with an external key store. Uniqueness requirements:
|
XksProxyAuthenticationCredential |
Specifies an authentication credential for the external key store proxy
(XKS proxy). This parameter is required for all custom key stores with a
The 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
|
XksProxyConnectivity |
Indicates how KMS communicates with the external key store proxy. This
parameter is required for custom key stores with a If the external key store proxy uses a public endpoint, specify
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. |
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.