Class: Aws::PaymentCryptography::Client
- Inherits:
-
Seahorse::Client::Base
- Object
- Seahorse::Client::Base
- Aws::PaymentCryptography::Client
- Includes:
- ClientStubs
- Defined in:
- lib/aws-sdk-paymentcryptography/client.rb
Overview
An API client for PaymentCryptography. To construct a client, you need to configure a ‘:region` and `:credentials`.
client = Aws::PaymentCryptography::Client.new(
region: region_name,
credentials: credentials,
# ...
)
For details on configuring region and credentials see the [developer guide](/sdk-for-ruby/v3/developer-guide/setup-config.html).
See #initialize for a full list of supported configuration options.
Class Attribute Summary collapse
- .identifier ⇒ Object readonly private
API Operations collapse
-
#add_key_replication_regions(params = {}) ⇒ Types::AddKeyReplicationRegionsOutput
Adds replication Amazon Web Services Regions to an existing Amazon Web Services Payment Cryptography key, enabling the key to be used for cryptographic operations in additional Amazon Web Services Regions.
-
#associate_mpa_team(params = {}) ⇒ Types::AssociateMpaTeamOutput
Associates a Multi-Party Approval (MPA) team with a protected operation.
-
#create_alias(params = {}) ⇒ Types::CreateAliasOutput
Creates an alias, or a friendly name, for an Amazon Web Services Payment Cryptography key.
-
#create_key(params = {}) ⇒ Types::CreateKeyOutput
Creates an Amazon Web Services Payment Cryptography key, a logical representation of a cryptographic key, that is unique in your account and Amazon Web Services Region.
-
#delete_alias(params = {}) ⇒ Struct
Deletes the alias, but doesn’t affect the underlying key.
-
#delete_key(params = {}) ⇒ Types::DeleteKeyOutput
Deletes the key material and metadata associated with Amazon Web Services Payment Cryptography key.
-
#delete_resource_policy(params = {}) ⇒ Struct
Removes the resource-based policy attached to an Amazon Web Services Payment Cryptography key.
-
#disable_default_key_replication_regions(params = {}) ⇒ Types::DisableDefaultKeyReplicationRegionsOutput
Disables [Multi-Region key replication] settings for the specified Amazon Web Services Regions in your Amazon Web Services account, preventing new keys from being automatically replicated to those regions.
-
#disassociate_mpa_team(params = {}) ⇒ Types::DisassociateMpaTeamOutput
Removes the association between a Multi-Party Approval (MPA) team and a protected operation.
-
#enable_default_key_replication_regions(params = {}) ⇒ Types::EnableDefaultKeyReplicationRegionsOutput
Enables [Multi-Region key replication] settings for your Amazon Web Services account, causing new keys to be automatically replicated to the specified Amazon Web Services Regions when created.
-
#export_key(params = {}) ⇒ Types::ExportKeyOutput
Exports a key from Amazon Web Services Payment Cryptography.
-
#get_alias(params = {}) ⇒ Types::GetAliasOutput
Gets the Amazon Web Services Payment Cryptography key associated with the alias.
-
#get_certificate_signing_request(params = {}) ⇒ Types::GetCertificateSigningRequestOutput
Creates a certificate signing request (CSR) from a key pair.
-
#get_default_key_replication_regions(params = {}) ⇒ Types::GetDefaultKeyReplicationRegionsOutput
Retrieves the list of Amazon Web Services Regions where [Multi-Region key replication] is currently enabled for your Amazon Web Services account.
-
#get_key(params = {}) ⇒ Types::GetKeyOutput
Gets the key metadata for an Amazon Web Services Payment Cryptography key, including the immutable and mutable attributes specified when the key was created.
-
#get_mpa_team_association(params = {}) ⇒ Types::GetMpaTeamAssociationOutput
Returns the Multi-Party Approval (MPA) team association for a protected operation.
-
#get_parameters_for_export(params = {}) ⇒ Types::GetParametersForExportOutput
Gets the export token and the signing key certificate to initiate a TR-34 key export from Amazon Web Services Payment Cryptography.
-
#get_parameters_for_import(params = {}) ⇒ Types::GetParametersForImportOutput
Gets the import token and the wrapping key certificate in PEM format (base64 encoded) to initiate a TR-34 WrappedKeyBlock or a RSA WrappedKeyCryptogram import into Amazon Web Services Payment Cryptography.
-
#get_public_key_certificate(params = {}) ⇒ Types::GetPublicKeyCertificateOutput
Gets the public key certificate of the asymmetric key pair that exists within Amazon Web Services Payment Cryptography.
-
#get_resource_policy(params = {}) ⇒ Types::GetResourcePolicyOutput
Returns the resource-based policy attached to an Amazon Web Services Payment Cryptography key.
-
#import_key(params = {}) ⇒ Types::ImportKeyOutput
Imports symmetric keys and public key certificates in PEM format (base64 encoded) into Amazon Web Services Payment Cryptography.
-
#list_aliases(params = {}) ⇒ Types::ListAliasesOutput
Lists the aliases for all keys in the caller’s Amazon Web Services account and Amazon Web Services Region.
-
#list_keys(params = {}) ⇒ Types::ListKeysOutput
Lists the keys in the caller’s Amazon Web Services account and Amazon Web Services Region.
-
#list_tags_for_resource(params = {}) ⇒ Types::ListTagsForResourceOutput
Lists the tags for an Amazon Web Services resource.
-
#put_resource_policy(params = {}) ⇒ Types::PutResourcePolicyOutput
Attaches or replaces a resource-based policy on an Amazon Web Services Payment Cryptography key.
-
#remove_key_replication_regions(params = {}) ⇒ Types::RemoveKeyReplicationRegionsOutput
Removes Replication Regions from an existing Amazon Web Services Payment Cryptography key, disabling the key’s availability for cryptographic operations in the specified Amazon Web Services Regions.
-
#restore_key(params = {}) ⇒ Types::RestoreKeyOutput
Cancels a scheduled key deletion during the waiting period.
-
#start_key_usage(params = {}) ⇒ Types::StartKeyUsageOutput
Enables an Amazon Web Services Payment Cryptography key, which makes it active for cryptographic operations within Amazon Web Services Payment Cryptography.
-
#stop_key_usage(params = {}) ⇒ Types::StopKeyUsageOutput
Disables an Amazon Web Services Payment Cryptography key, which makes it inactive within Amazon Web Services Payment Cryptography.
-
#tag_resource(params = {}) ⇒ Struct
Adds or edits tags on an Amazon Web Services Payment Cryptography key.
-
#untag_resource(params = {}) ⇒ Struct
Deletes a tag from an Amazon Web Services Payment Cryptography key.
-
#update_alias(params = {}) ⇒ Types::UpdateAliasOutput
Associates an existing Amazon Web Services Payment Cryptography alias with a different key.
Class Method Summary collapse
- .errors_module ⇒ Object private
Instance Method Summary collapse
- #build_request(operation_name, params = {}) ⇒ Object private
-
#initialize(options) ⇒ Client
constructor
A new instance of Client.
- #waiter_names ⇒ Object deprecated private Deprecated.
Constructor Details
#initialize(options) ⇒ Client
Returns a new instance of Client.
480 481 482 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 480 def initialize(*args) super end |
Class Attribute Details
.identifier ⇒ Object (readonly)
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
3526 3527 3528 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3526 def identifier @identifier end |
Class Method Details
.errors_module ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
3529 3530 3531 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3529 def errors_module Errors end |
Instance Method Details
#add_key_replication_regions(params = {}) ⇒ Types::AddKeyReplicationRegionsOutput
Adds replication Amazon Web Services Regions to an existing Amazon Web Services Payment Cryptography key, enabling the key to be used for cryptographic operations in additional Amazon Web Services Regions.
- Multi-Region key replication][1
-
allow you to use the same key
material across multiple Amazon Web Services Regions, providing lower latency for applications distributed across regions. When you add Replication Regions, Amazon Web Services Payment Cryptography securely replicates the key material to the specified Amazon Web Services Regions.
The key must be in an active state to add Replication Regions. You can add multiple regions in a single operation, and the key will be available for use in those regions once replication is complete.
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- RemoveKeyReplicationRegions][3
- EnableDefaultKeyReplicationRegions][4
- GetDefaultKeyReplicationRegions][5
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_RemoveKeyReplicationRegions.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_EnableDefaultKeyReplicationRegions.html [5]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetDefaultKeyReplicationRegions.html
590 591 592 593 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 590 def add_key_replication_regions(params = {}, = {}) req = build_request(:add_key_replication_regions, params) req.send_request() end |
#associate_mpa_team(params = {}) ⇒ Types::AssociateMpaTeamOutput
Associates a Multi-Party Approval (MPA) team with a protected operation. For more information, see [Multi-Party Approval] in the *Amazon Web Services Payment Cryptography User Guide.*
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- DisassociateMpaTeam][2
- GetMpaTeamAssociation][3
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/mpa.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DisassociateMpaTeam.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetMpaTeamAssociation.html
655 656 657 658 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 655 def associate_mpa_team(params = {}, = {}) req = build_request(:associate_mpa_team, params) req.send_request() end |
#build_request(operation_name, params = {}) ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3499 def build_request(operation_name, params = {}) handlers = @handlers.for(operation_name) tracer = config.telemetry_provider.tracer_provider.tracer( Aws::Telemetry.module_to_tracer_name('Aws::PaymentCryptography') ) context = Seahorse::Client::RequestContext.new( operation_name: operation_name, operation: config.api.operation(operation_name), client: self, params: params, config: config, tracer: tracer ) context[:gem_name] = 'aws-sdk-paymentcryptography' context[:gem_version] = '1.54.0' Seahorse::Client::Request.new(handlers, context) end |
#create_alias(params = {}) ⇒ Types::CreateAliasOutput
Creates an alias, or a friendly name, for an Amazon Web Services Payment Cryptography key. You can use an alias to identify a key in the console and when you call cryptographic operations such as
- EncryptData][1
-
or [DecryptData].
You can associate the alias with any key in the same Amazon Web Services Region. Each alias is associated with only one key at a time, but a key can have multiple aliases. You can’t create an alias without a key. The alias must be unique in the account and Amazon Web Services Region, but you can create another alias with the same name in a different Amazon Web Services Region.
To change the key that’s associated with the alias, call [UpdateAlias]. To delete the alias, call [DeleteAlias]. These operations don’t affect the underlying key. To get the alias that you created, call [ListAliases].
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- DeleteAlias][4
- GetAlias][6
- ListAliases][5
- UpdateAlias][3
[1]: docs.aws.amazon.com/payment-cryptography/latest/DataAPIReference/API_EncryptData.html [2]: docs.aws.amazon.com/payment-cryptography/latest/DataAPIReference/API_DecryptData.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html [5]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html [6]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetAlias.html
732 733 734 735 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 732 def create_alias(params = {}, = {}) req = build_request(:create_alias, params) req.send_request() end |
#create_key(params = {}) ⇒ Types::CreateKeyOutput
Creates an Amazon Web Services Payment Cryptography key, a logical representation of a cryptographic key, that is unique in your account and Amazon Web Services Region. You use keys for cryptographic functions such as encryption and decryption.
In addition to the key material used in cryptographic operations, an Amazon Web Services Payment Cryptography key includes metadata such as the key ARN, key usage, key origin, creation date, description, and key state.
When you create a key, you specify both immutable and mutable data about the key. The immutable data contains key attributes that define the scope and cryptographic operations that you can perform using the key, for example key class (example: ‘SYMMETRIC_KEY`), key algorithm (example: `TDES_2KEY`), key usage (example: `TR31_P0_PIN_ENCRYPTION_KEY`) and key modes of use (example: `Encrypt`). Amazon Web Services Payment Cryptography binds key attributes to keys using key blocks when you store or export them. Amazon Web Services Payment Cryptography stores the key contents wrapped and never stores or transmits them in the clear.
For information about valid combinations of key attributes, see
- Understanding key attributes][1
-
in the *Amazon Web Services Payment
Cryptography User Guide*. The mutable data contained within a key includes usage timestamp and key deletion timestamp and can be modified after creation.
You can use the ‘CreateKey` operation to generate an ECC (Elliptic Curve Cryptography) key pair used for establishing an ECDH (Elliptic Curve Diffie-Hellman) key agreement between two parties. In the ECDH key agreement process, both parties generate their own ECC key pair with key usage K3 and exchange the public keys. Each party then use their private key, the received public key from the other party, and the key derivation parameters including key derivation function, hash algorithm, derivation data, and key algorithm to derive a shared key.
To maintain the single-use principle of cryptographic keys in payments, ECDH derived keys should not be used for multiple purposes, such as a ‘TR31_P0_PIN_ENCRYPTION_KEY` and `TR31_K1_KEY_BLOCK_PROTECTION_KEY`. When creating ECC key pairs in Amazon Web Services Payment Cryptography you can optionally set the `DeriveKeyUsage` parameter, which defines the key usage bound to the symmetric key that will be derived using the ECC key pair.
**Cross-account use**: This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- DeleteKey][2
- GetKey][3
- ListKeys][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetKey.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListKeys.html
940 941 942 943 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 940 def create_key(params = {}, = {}) req = build_request(:create_key, params) req.send_request() end |
#delete_alias(params = {}) ⇒ Struct
Deletes the alias, but doesn’t affect the underlying key.
Each key can have multiple aliases. To get the aliases of all keys, use the [UpdateAlias] operation. To change the alias of a key, first use [DeleteAlias] to delete the current alias and then use
- CreateAlias][3
-
to create a new alias. To associate an existing alias
with a different key, call [UpdateAlias].
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- CreateAlias][3
- GetAlias][4
- ListAliases][5
- UpdateAlias][1
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetAlias.html [5]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html
991 992 993 994 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 991 def delete_alias(params = {}, = {}) req = build_request(:delete_alias, params) req.send_request() end |
#delete_key(params = {}) ⇒ Types::DeleteKeyOutput
Deletes the key material and metadata associated with Amazon Web Services Payment Cryptography key.
Key deletion is irreversible. After a key is deleted, you can’t perform cryptographic operations using the key. For example, you can’t decrypt data that was encrypted by a deleted Amazon Web Services Payment Cryptography key, and the data may become unrecoverable. Because key deletion is destructive, Amazon Web Services Payment Cryptography has a safety mechanism to prevent accidental deletion of a key. When you call this operation, Amazon Web Services Payment Cryptography disables the specified key but doesn’t delete it until after a waiting period set using ‘DeleteKeyInDays`. The default waiting period is 7 days. During the waiting period, the `KeyState` is `DELETE_PENDING`. After the key is deleted, the `KeyState` is `DELETE_COMPLETE`.
You should delete a key only when you are sure that you don’t need to use it anymore and no other parties are utilizing this key. If you aren’t sure, consider deactivating it instead by calling [StopKeyUsage].
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- RestoreKey][3
- StartKeyUsage][4
- StopKeyUsage][1
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StopKeyUsage.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_RestoreKey.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StartKeyUsage.html
1095 1096 1097 1098 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1095 def delete_key(params = {}, = {}) req = build_request(:delete_key, params) req.send_request() end |
#delete_resource_policy(params = {}) ⇒ Struct
Removes the resource-based policy attached to an Amazon Web Services Payment Cryptography key.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- PutResourcePolicy][1
- GetResourcePolicy][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_PutResourcePolicy.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetResourcePolicy.html
1133 1134 1135 1136 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1133 def delete_resource_policy(params = {}, = {}) req = build_request(:delete_resource_policy, params) req.send_request() end |
#disable_default_key_replication_regions(params = {}) ⇒ Types::DisableDefaultKeyReplicationRegionsOutput
Disables [Multi-Region key replication] settings for the specified Amazon Web Services Regions in your Amazon Web Services account, preventing new keys from being automatically replicated to those regions.
After disabling Multi-Region key replication for specific regions, new keys created in your account will not be automatically replicated to those regions. You can still manually add replication to those regions for individual keys using the [AddKeyReplicationRegions] operation.
This operation does not affect existing keys or their current replication configuration.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- EnableDefaultKeyReplicationRegions][3
- GetDefaultKeyReplicationRegions][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_AddKeyReplicationRegions.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_EnableDefaultKeyReplicationRegions.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetDefaultKeyReplicationRegions.html
1194 1195 1196 1197 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1194 def disable_default_key_replication_regions(params = {}, = {}) req = build_request(:disable_default_key_replication_regions, params) req.send_request() end |
#disassociate_mpa_team(params = {}) ⇒ Types::DisassociateMpaTeamOutput
Removes the association between a Multi-Party Approval (MPA) team and a protected operation.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- AssociateMpaTeam][1
- GetMpaTeamAssociation][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_AssociateMpaTeam.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetMpaTeamAssociation.html
1253 1254 1255 1256 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1253 def disassociate_mpa_team(params = {}, = {}) req = build_request(:disassociate_mpa_team, params) req.send_request() end |
#enable_default_key_replication_regions(params = {}) ⇒ Types::EnableDefaultKeyReplicationRegionsOutput
Enables [Multi-Region key replication] settings for your Amazon Web Services account, causing new keys to be automatically replicated to the specified Amazon Web Services Regions when created.
When Multi-Region key replication are enabled, any new keys created in your account will automatically be replicated to these regions unless you explicitly override this behavior during key creation. This simplifies key management for applications that operate across multiple regions.
Existing keys are not affected by this operation - only keys created after enabling default replication will be automatically replicated.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- DisableDefaultKeyReplicationRegions][2
- GetDefaultKeyReplicationRegions][3
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DisableDefaultKeyReplicationRegions.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetDefaultKeyReplicationRegions.html
1317 1318 1319 1320 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1317 def enable_default_key_replication_regions(params = {}, = {}) req = build_request(:enable_default_key_replication_regions, params) req.send_request() end |
#export_key(params = {}) ⇒ Types::ExportKeyOutput
Exports a key from Amazon Web Services Payment Cryptography.
Amazon Web Services Payment Cryptography simplifies key exchange by replacing the existing paper-based approach with a modern electronic approach. With ‘ExportKey` you can export symmetric keys using either symmetric and asymmetric key exchange mechanisms. Using this operation, you can share your Amazon Web Services Payment Cryptography generated keys with other service partners to perform cryptographic operations outside of Amazon Web Services Payment Cryptography
For symmetric key exchange, Amazon Web Services Payment Cryptography uses the ANSI X9 TR-31 norm in accordance with PCI PIN guidelines. And for asymmetric key exchange, Amazon Web Services Payment Cryptography supports ANSI X9 TR-34 norm, RSA unwrap, and ECDH (Elliptic Curve Diffie-Hellman) key exchange mechanisms. Asymmetric key exchange methods are typically used to establish bi-directional trust between the two parties exhanging keys and are used for initial key exchange such as Key Encryption Key (KEK). After which you can export working keys using symmetric method to perform various cryptographic operations within Amazon Web Services Payment Cryptography.
PCI requires specific minimum key strength of wrapping keys used to protect the keys being exchanged electronically. These requirements can change when PCI standards are revised. The rules specify that wrapping keys used for transport must be at least as strong as the key being protected. For more information on recommended key strength of wrapping keys and key exchange mechanism, see [Importing and exporting keys] in the *Amazon Web Services Payment Cryptography User Guide*.
You can also use ‘ExportKey` functionality to generate and export an IPEK (Initial Pin Encryption Key) from Amazon Web Services Payment Cryptography using either TR-31 or TR-34 export key exchange. IPEK is generated from BDK (Base Derivation Key) and `ExportDukptInitialKey` attribute KSN (`KeySerialNumber`). The generated IPEK does not persist within Amazon Web Services Payment Cryptography and has to be re-generated each time during export.
For key exchange using TR-31 or TR-34 key blocks, you can also export optional blocks within the key block header which contain additional attribute information about the key. The ‘KeyVersion` within `KeyBlockHeaders` indicates the version of the key within the key block. Furthermore, `KeyExportability` within `KeyBlockHeaders` can be used to further restrict exportability of the key after export from Amazon Web Services Payment Cryptography.
The ‘OptionalBlocks` contain the additional data related to the key. For information on data type that can be included within optional blocks, refer to [ASC X9.143-2022].
<note markdown=“1”> Data included in key block headers is signed but transmitted in clear text. Sensitive or confidential information should not be included in optional blocks. Refer to ASC X9.143-2022 standard for information on allowed data type.
</note>
**To export initial keys (KEK) or IPEK using TR-34**
Using this operation, you can export initial key using TR-34 asymmetric key exchange. You can only export KEK generated within Amazon Web Services Payment Cryptography. In TR-34 terminology, the sending party of the key is called Key Distribution Host (KDH) and the receiving party of the key is called Key Receiving Device (KRD). During key export process, KDH is Amazon Web Services Payment Cryptography which initiates key export and KRD is the user receiving the key.
To initiate TR-34 key export, the KRD must obtain an export token by calling [GetParametersForExport]. This operation also generates a key pair for the purpose of key export, signs the key and returns back the signing public key certificate (also known as KDH signing certificate) and root certificate chain. The KDH uses the private key to sign the the export payload and the signing public key certificate is provided to KRD to verify the signature. The KRD can import the root certificate into its Hardware Security Module (HSM), as required. The export token and the associated KDH signing certificate expires after 30 days.
Next the KRD generates a key pair for the the purpose of encrypting the KDH key and provides the public key cerificate (also known as KRD wrapping certificate) back to KDH. The KRD will also import the root cerificate chain into Amazon Web Services Payment Cryptography by calling [ImportKey] for ‘RootCertificatePublicKey`. The KDH, Amazon Web Services Payment Cryptography, will use the KRD wrapping cerificate to encrypt (wrap) the key under export and signs it with signing private key to generate a TR-34 WrappedKeyBlock. For more information on TR-34 key export, see section [Exporting symmetric keys] in the *Amazon Web Services Payment Cryptography User Guide*.
Set the following parameters:
-
‘ExportAttributes`: Specify export attributes in case of IPEK export. This parameter is optional for KEK export.
-
‘ExportKeyIdentifier`: The `KeyARN` of the KEK or BDK (in case of IPEK) under export.
-
‘KeyMaterial`: Use `Tr34KeyBlock` parameters.
-
‘CertificateAuthorityPublicKeyIdentifier`: The `KeyARN` of the certificate chain that signed the KRD wrapping key certificate.
-
‘ExportToken`: Obtained from KDH by calling [GetParametersForImport].
-
‘WrappingKeyCertificate`: The public key certificate in PEM format (base64 encoded) of the KRD wrapping key Amazon Web Services Payment Cryptography uses for encryption of the TR-34 export payload. This certificate must be signed by the root certificate (CertificateAuthorityPublicKeyIdentifier) imported into Amazon Web Services Payment Cryptography.
When this operation is successful, Amazon Web Services Payment Cryptography returns the KEK or IPEK as a TR-34 WrappedKeyBlock.
**To export initial keys (KEK) or IPEK using RSA Wrap and Unwrap**
Using this operation, you can export initial key using asymmetric RSA wrap and unwrap key exchange method. To initiate export, generate an asymmetric key pair on the receiving HSM and obtain the public key certificate in PEM format (base64 encoded) for the purpose of wrapping and the root certifiate chain. Import the root certificate into Amazon Web Services Payment Cryptography by calling [ImportKey] for ‘RootCertificatePublicKey`.
Next call ‘ExportKey` and set the following parameters:
-
‘CertificateAuthorityPublicKeyIdentifier`: The `KeyARN` of the certificate chain that signed wrapping key certificate.
-
‘KeyMaterial`: Set to `KeyCryptogram`.
-
‘WrappingKeyCertificate`: The public key certificate in PEM format (base64 encoded) obtained by the receiving HSM and signed by the root certificate (CertificateAuthorityPublicKeyIdentifier) imported into Amazon Web Services Payment Cryptography. The receiving HSM uses its private key component to unwrap the WrappedKeyCryptogram.
When this operation is successful, Amazon Web Services Payment Cryptography returns the WrappedKeyCryptogram.
**To export working keys or IPEK using TR-31**
Using this operation, you can export working keys or IPEK using TR-31 symmetric key exchange. In TR-31, you must use an initial key such as KEK to encrypt or wrap the key under export. To establish a KEK, you can use [CreateKey] or [ImportKey].
Set the following parameters:
-
‘ExportAttributes`: Specify export attributes in case of IPEK export. This parameter is optional for KEK export.
-
‘ExportKeyIdentifier`: The `KeyARN` of the KEK or BDK (in case of IPEK) under export.
-
‘KeyMaterial`: Use `Tr31KeyBlock` parameters.
**To export working keys using ECDH**
You can also use ECDH key agreement to export working keys in a TR-31 keyblock, where the wrapping key is an ECDH derived key.
To initiate a TR-31 key export using ECDH, both sides must create an ECC key pair with key usage K3 and exchange public key certificates. In Amazon Web Services Payment Cryptography, you can do this by calling ‘CreateKey`. If you have not already done so, you must import the CA chain that issued the receiving public key certificate by calling `ImportKey` with input `RootCertificatePublicKey` for root CA or `TrustedPublicKey` for intermediate CA. You can then complete a TR-31 key export by deriving a shared wrapping key using the service ECC key pair, public certificate of your ECC key pair outside of Amazon Web Services Payment Cryptography, and the key derivation parameters including key derivation function, hash algorithm, derivation data, key algorithm.
-
‘KeyMaterial`: Use `DiffieHellmanTr31KeyBlock` parameters.
-
‘PrivateKeyIdentifier`: The `KeyArn` of the ECC key pair created within Amazon Web Services Payment Cryptography to derive a shared KEK.
-
‘PublicKeyCertificate`: The public key certificate of the receiving ECC key pair in PEM format (base64 encoded) to derive a shared KEK.
-
‘CertificateAuthorityPublicKeyIdentifier`: The `keyARN` of the CA that signed the public key certificate of the receiving ECC key pair.
When this operation is successful, Amazon Web Services Payment Cryptography returns the working key as a TR-31 WrappedKeyBlock, where the wrapping key is the ECDH derived key.
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- GetParametersForExport][3
- ImportKey][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-importexport.html [2]: webstore.ansi.org/standards/ascx9/ansix91432022 [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForExport.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-export.html [6]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html [7]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [8]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html
1663 1664 1665 1666 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1663 def export_key(params = {}, = {}) req = build_request(:export_key, params) req.send_request() end |
#get_alias(params = {}) ⇒ Types::GetAliasOutput
Gets the Amazon Web Services Payment Cryptography key associated with the alias.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- CreateAlias][1
- DeleteAlias][2
- ListAliases][3
- UpdateAlias][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html
1713 1714 1715 1716 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1713 def get_alias(params = {}, = {}) req = build_request(:get_alias, params) req.send_request() end |
#get_certificate_signing_request(params = {}) ⇒ Types::GetCertificateSigningRequestOutput
Creates a certificate signing request (CSR) from a key pair.
1757 1758 1759 1760 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1757 def get_certificate_signing_request(params = {}, = {}) req = build_request(:get_certificate_signing_request, params) req.send_request() end |
#get_default_key_replication_regions(params = {}) ⇒ Types::GetDefaultKeyReplicationRegionsOutput
Retrieves the list of Amazon Web Services Regions where [Multi-Region key replication] is currently enabled for your Amazon Web Services account.
This operation returns the current Multi-Region key replication configuration. New keys created in your account will be automatically replicated to these regions unless explicitly overridden during key creation.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- EnableDefaultKeyReplicationRegions][2
- DisableDefaultKeyReplicationRegions][3
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_EnableDefaultKeyReplicationRegions.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DisableDefaultKeyReplicationRegions.html
1799 1800 1801 1802 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1799 def get_default_key_replication_regions(params = {}, = {}) req = build_request(:get_default_key_replication_regions, params) req.send_request() end |
#get_key(params = {}) ⇒ Types::GetKeyOutput
Gets the key metadata for an Amazon Web Services Payment Cryptography key, including the immutable and mutable attributes specified when the key was created. Returns key metadata including attributes, state, and timestamps, but does not return the actual cryptographic key material.
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- CreateKey][2
- DeleteKey][3
- ListKeys][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListKeys.html
1883 1884 1885 1886 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1883 def get_key(params = {}, = {}) req = build_request(:get_key, params) req.send_request() end |
#get_mpa_team_association(params = {}) ⇒ Types::GetMpaTeamAssociationOutput
Returns the Multi-Party Approval (MPA) team association for a protected operation.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- AssociateMpaTeam][1
- DisassociateMpaTeam][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_AssociateMpaTeam.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DisassociateMpaTeam.html
1934 1935 1936 1937 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 1934 def get_mpa_team_association(params = {}, = {}) req = build_request(:get_mpa_team_association, params) req.send_request() end |
#get_parameters_for_export(params = {}) ⇒ Types::GetParametersForExportOutput
Gets the export token and the signing key certificate to initiate a TR-34 key export from Amazon Web Services Payment Cryptography.
The signing key certificate signs the wrapped key under export within the TR-34 key payload. The export token and signing key certificate must be in place and operational before calling [ExportKey]. The export token expires in 30 days. You can use the same export token to export multiple keys from your service account.
To return a previously generated export token and signing key certificate instead of generating new ones, set ‘ReuseLastGeneratedToken` to `true`.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- ExportKey][1
- GetParametersForImport][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ExportKey.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html
2015 2016 2017 2018 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2015 def get_parameters_for_export(params = {}, = {}) req = build_request(:get_parameters_for_export, params) req.send_request() end |
#get_parameters_for_import(params = {}) ⇒ Types::GetParametersForImportOutput
Gets the import token and the wrapping key certificate in PEM format (base64 encoded) to initiate a TR-34 WrappedKeyBlock or a RSA WrappedKeyCryptogram import into Amazon Web Services Payment Cryptography.
The wrapping key certificate wraps the key under import. The import token and wrapping key certificate must be in place and operational before calling [ImportKey]. The import token expires in 30 days. You can use the same import token to import multiple keys into your service account.
To return a previously generated import token and wrapping key certificate instead of generating new ones, set ‘ReuseLastGeneratedToken` to `true`.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- GetParametersForExport][2
- ImportKey][1
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ImportKey.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForExport.html
2104 2105 2106 2107 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2104 def get_parameters_for_import(params = {}, = {}) req = build_request(:get_parameters_for_import, params) req.send_request() end |
#get_public_key_certificate(params = {}) ⇒ Types::GetPublicKeyCertificateOutput
Gets the public key certificate of the asymmetric key pair that exists within Amazon Web Services Payment Cryptography.
Unlike the private key of an asymmetric key, which never leaves Amazon Web Services Payment Cryptography unencrypted, callers with ‘GetPublicKeyCertificate` permission can download the public key certificate of the asymmetric key. You can share the public key certificate to allow others to encrypt messages and verify signatures outside of Amazon Web Services Payment Cryptography
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html
2150 2151 2152 2153 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2150 def get_public_key_certificate(params = {}, = {}) req = build_request(:get_public_key_certificate, params) req.send_request() end |
#get_resource_policy(params = {}) ⇒ Types::GetResourcePolicyOutput
Returns the resource-based policy attached to an Amazon Web Services Payment Cryptography key.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- PutResourcePolicy][1
- DeleteResourcePolicy][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_PutResourcePolicy.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteResourcePolicy.html
2196 2197 2198 2199 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2196 def get_resource_policy(params = {}, = {}) req = build_request(:get_resource_policy, params) req.send_request() end |
#import_key(params = {}) ⇒ Types::ImportKeyOutput
Imports symmetric keys and public key certificates in PEM format (base64 encoded) into Amazon Web Services Payment Cryptography.
Amazon Web Services Payment Cryptography simplifies key exchange by replacing the existing paper-based approach with a modern electronic approach. With ‘ImportKey` you can import symmetric keys using either symmetric and asymmetric key exchange mechanisms.
For symmetric key exchange, Amazon Web Services Payment Cryptography uses the ANSI X9 TR-31 norm in accordance with PCI PIN guidelines. And for asymmetric key exchange, Amazon Web Services Payment Cryptography supports ANSI X9 TR-34 norm, RSA unwrap, and ECDH (Elliptic Curve Diffie-Hellman) key exchange mechanisms. Asymmetric key exchange methods are typically used to establish bi-directional trust between the two parties exhanging keys and are used for initial key exchange such as Key Encryption Key (KEK) or Zone Master Key (ZMK). After which you can import working keys using symmetric method to perform various cryptographic operations within Amazon Web Services Payment Cryptography.
PCI requires specific minimum key strength of wrapping keys used to protect the keys being exchanged electronically. These requirements can change when PCI standards are revised. The rules specify that wrapping keys used for transport must be at least as strong as the key being protected. For more information on recommended key strength of wrapping keys and key exchange mechanism, see [Importing and exporting keys] in the *Amazon Web Services Payment Cryptography User Guide*.
You can also import a *root public key certificate*, used to sign other public key certificates, or a *trusted public key certificate* under an already established root public key certificate.
**To import a public root key certificate**
Using this operation, you can import the public component (in PEM cerificate format) of your private root key. You can use the imported public root key certificate for digital signatures, for example signing wrapping key or signing key in TR-34, within your Amazon Web Services Payment Cryptography account.
Set the following parameters:
-
‘KeyMaterial`: `RootCertificatePublicKey`
-
‘KeyClass`: `PUBLIC_KEY`
-
‘KeyModesOfUse`: `Verify`
-
‘KeyUsage`: `TR31_S0_ASYMMETRIC_KEY_FOR_DIGITAL_SIGNATURE`
-
‘PublicKeyCertificate`: The public key certificate in PEM format (base64 encoded) of the private root key under import.
**To import a trusted public key certificate**
The root public key certificate must be in place and operational before you import a trusted public key certificate. Set the following parameters:
-
‘KeyMaterial`: `TrustedCertificatePublicKey`
-
‘CertificateAuthorityPublicKeyIdentifier`: `KeyArn` of the `RootCertificatePublicKey`.
-
‘KeyModesOfUse` and `KeyUsage`: Corresponding to the cryptographic operations such as wrap, sign, or encrypt that you will allow the trusted public key certificate to perform.
-
‘PublicKeyCertificate`: The trusted public key certificate in PEM format (base64 encoded) under import.
**To import initial keys (KEK or ZMK or similar) using TR-34**
Using this operation, you can import initial key using TR-34 asymmetric key exchange. In TR-34 terminology, the sending party of the key is called Key Distribution Host (KDH) and the receiving party of the key is called Key Receiving Device (KRD). During the key import process, KDH is the user who initiates the key import and KRD is Amazon Web Services Payment Cryptography who receives the key.
To initiate TR-34 key import, the KDH must obtain an import token by calling [GetParametersForImport]. This operation generates an encryption keypair for the purpose of key import, signs the key and returns back the wrapping key certificate (also known as KRD wrapping certificate) and the root certificate chain. The KDH must trust and install the KRD wrapping certificate on its HSM and use it to encrypt (wrap) the KDH key during TR-34 WrappedKeyBlock generation. The import token and associated KRD wrapping certificate expires after 30 days.
Next the KDH generates a key pair for the purpose of signing the encrypted KDH key and provides the public certificate of the signing key to Amazon Web Services Payment Cryptography. The KDH will also need to import the root certificate chain of the KDH signing certificate by calling ‘ImportKey` for `RootCertificatePublicKey`. For more information on TR-34 key import, see section [Importing symmetric keys] in the *Amazon Web Services Payment Cryptography User Guide*.
Set the following parameters:
-
‘KeyMaterial`: Use `Tr34KeyBlock` parameters.
-
‘CertificateAuthorityPublicKeyIdentifier`: The `KeyARN` of the certificate chain that signed the KDH signing key certificate.
-
‘ImportToken`: Obtained from KRD by calling [GetParametersForImport].
-
‘WrappedKeyBlock`: The TR-34 wrapped key material from KDH. It contains the KDH key under import, wrapped with KRD wrapping certificate and signed by KDH signing private key. This TR-34 key block is typically generated by the KDH Hardware Security Module (HSM) outside of Amazon Web Services Payment Cryptography.
-
‘SigningKeyCertificate`: The public key certificate in PEM format (base64 encoded) of the KDH signing key generated under the root certificate (CertificateAuthorityPublicKeyIdentifier) imported in Amazon Web Services Payment Cryptography.
**To import initial keys (KEK or ZMK or similar) using RSA Wrap and Unwrap**
Using this operation, you can import initial key using asymmetric RSA wrap and unwrap key exchange method. To initiate import, call
- GetParametersForImport][2
-
with ‘KeyMaterial` set to `KEY_CRYPTOGRAM`
to generate an import token. This operation also generates an encryption keypair for the purpose of key import, signs the key and returns back the wrapping key certificate in PEM format (base64 encoded) and its root certificate chain. The import token and associated KRD wrapping certificate expires after 30 days.
You must trust and install the wrapping certificate and its certificate chain on the sending HSM and use it to wrap the key under export for WrappedKeyCryptogram generation. Next call ‘ImportKey` with `KeyMaterial` set to `KEY_CRYPTOGRAM` and provide the `ImportToken` and `KeyAttributes` for the key under import.
**To import working keys using TR-31**
Amazon Web Services Payment Cryptography uses TR-31 symmetric key exchange norm to import working keys. A KEK must be established within Amazon Web Services Payment Cryptography by using TR-34 key import or by using [CreateKey]. To initiate a TR-31 key import, set the following parameters:
-
‘KeyMaterial`: Use `Tr31KeyBlock` parameters.
-
‘WrappedKeyBlock`: The TR-31 wrapped key material. It contains the key under import, encrypted using KEK. The TR-31 key block is typically generated by a HSM outside of Amazon Web Services Payment Cryptography.
-
‘WrappingKeyIdentifier`: The `KeyArn` of the KEK that Amazon Web Services Payment Cryptography uses to decrypt or unwrap the key under import.
**To import working keys using ECDH**
You can also use ECDH key agreement to import working keys as a TR-31 keyblock, where the wrapping key is an ECDH derived key.
To initiate a TR-31 key import using ECDH, both sides must create an ECC key pair with key usage K3 and exchange public key certificates. In Amazon Web Services Payment Cryptography, you can do this by calling ‘CreateKey` and then `GetPublicKeyCertificate` to retrieve its public key certificate. Next, you can then generate a TR-31 WrappedKeyBlock using your own ECC key pair, the public certificate of the service’s ECC key pair, and the key derivation parameters including key derivation function, hash algorithm, derivation data, and key algorithm. If you have not already done so, you must import the CA chain that issued the receiving public key certificate by calling ‘ImportKey` with input `RootCertificatePublicKey` for root CA or `TrustedPublicKey` for intermediate CA. To complete the TR-31 key import, you can use the following parameters. It is important that the ECDH key derivation parameters you use should match those used during import to derive the same shared wrapping key within Amazon Web Services Payment Cryptography.
-
‘KeyMaterial`: Use `DiffieHellmanTr31KeyBlock` parameters.
-
‘PrivateKeyIdentifier`: The `KeyArn` of the ECC key pair created within Amazon Web Services Payment Cryptography to derive a shared KEK.
-
‘PublicKeyCertificate`: The public key certificate of the receiving ECC key pair in PEM format (base64 encoded) to derive a shared KEK.
-
‘CertificateAuthorityPublicKeyIdentifier`: The `keyARN` of the CA that signed the public key certificate of the receiving ECC key pair.
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- ExportKey][6
- GetParametersForImport][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-importexport.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetParametersForImport.html [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-import.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [5]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [6]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ExportKey.html
2638 2639 2640 2641 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2638 def import_key(params = {}, = {}) req = build_request(:import_key, params) req.send_request() end |
#list_aliases(params = {}) ⇒ Types::ListAliasesOutput
Lists the aliases for all keys in the caller’s Amazon Web Services account and Amazon Web Services Region. You can filter the aliases by ‘keyARN`. For more information, see [Using aliases] in the *Amazon Web Services Payment Cryptography User Guide*.
This is a paginated operation, which means that each response might contain only a subset of all the aliases. When the response contains only a subset of aliases, it includes a ‘NextToken` value. Use this value in a subsequent `ListAliases` request to get more aliases. When you receive a response with no NextToken (or an empty or null value), that means there are no more aliases to get.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- CreateAlias][2
- DeleteAlias][3
- GetAlias][4
- UpdateAlias][5
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-managealias.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetAlias.html [5]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UpdateAlias.html
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
2719 2720 2721 2722 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2719 def list_aliases(params = {}, = {}) req = build_request(:list_aliases, params) req.send_request() end |
#list_keys(params = {}) ⇒ Types::ListKeysOutput
Lists the keys in the caller’s Amazon Web Services account and Amazon Web Services Region. You can filter the list of keys.
This is a paginated operation, which means that each response might contain only a subset of all the keys. When the response contains only a subset of keys, it includes a ‘NextToken` value. Use this value in a subsequent `ListKeys` request to get more keys. When you receive a response with no NextToken (or an empty or null value), that means there are no more keys to get.
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- CreateKey][1
- DeleteKey][2
- GetKey][3
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetKey.html
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
2811 2812 2813 2814 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2811 def list_keys(params = {}, = {}) req = build_request(:list_keys, params) req.send_request() end |
#list_tags_for_resource(params = {}) ⇒ Types::ListTagsForResourceOutput
Lists the tags for an Amazon Web Services resource.
This is a paginated operation, which means that each response might contain only a subset of all the tags. When the response contains only a subset of tags, it includes a ‘NextToken` value. Use this value in a subsequent `ListTagsForResource` request to get more tags. When you receive a response with no NextToken (or an empty or null value), that means there are no more tags to get.
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- TagResource][2
- UntagResource][3
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_TagResource.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UntagResource.html
The returned response is a pageable response and is Enumerable. For details on usage see PageableResponse.
2884 2885 2886 2887 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2884 def (params = {}, = {}) req = build_request(:list_tags_for_resource, params) req.send_request() end |
#put_resource_policy(params = {}) ⇒ Types::PutResourcePolicyOutput
Attaches or replaces a resource-based policy on an Amazon Web Services Payment Cryptography key. A resource-based policy can grant cross-account access to your key.
If the policy would grant public access, the request fails with a ‘PublicPolicyException`.
To remove a resource-based policy from a key, use [DeleteResourcePolicy].
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- GetResourcePolicy][2
- DeleteResourcePolicy][1
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteResourcePolicy.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetResourcePolicy.html
2940 2941 2942 2943 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 2940 def put_resource_policy(params = {}, = {}) req = build_request(:put_resource_policy, params) req.send_request() end |
#remove_key_replication_regions(params = {}) ⇒ Types::RemoveKeyReplicationRegionsOutput
Removes Replication Regions from an existing Amazon Web Services Payment Cryptography key, disabling the key’s availability for cryptographic operations in the specified Amazon Web Services Regions.
When you remove Replication Regions, the key material is securely deleted from those regions and can no longer be used for cryptographic operations there. This operation is irreversible for the specified Amazon Web Services Regions. For more information, see [Multi-Region key replication].
Ensure that no active cryptographic operations or applications depend on the key in the regions you’re removing before performing this operation.
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- AddKeyReplicationRegions][3
- DisableDefaultKeyReplicationRegions][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-multi-region-replication.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_AddKeyReplicationRegions.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DisableDefaultKeyReplicationRegions.html
3044 3045 3046 3047 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3044 def remove_key_replication_regions(params = {}, = {}) req = build_request(:remove_key_replication_regions, params) req.send_request() end |
#restore_key(params = {}) ⇒ Types::RestoreKeyOutput
Cancels a scheduled key deletion during the waiting period. Use this operation to restore a ‘Key` that is scheduled for deletion.
During the waiting period, the ‘KeyState` is `DELETE_PENDING` and `deletePendingTimestamp` contains the date and time after which the `Key` will be deleted. After `Key` is restored, the `KeyState` is `CREATE_COMPLETE`, and the value for `deletePendingTimestamp` is removed.
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- DeleteKey][2
- StartKeyUsage][3
- StopKeyUsage][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StartKeyUsage.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StopKeyUsage.html
3133 3134 3135 3136 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3133 def restore_key(params = {}, = {}) req = build_request(:restore_key, params) req.send_request() end |
#start_key_usage(params = {}) ⇒ Types::StartKeyUsageOutput
Enables an Amazon Web Services Payment Cryptography key, which makes it active for cryptographic operations within Amazon Web Services Payment Cryptography
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- StopKeyUsage][2
^
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StopKeyUsage.html
3212 3213 3214 3215 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3212 def start_key_usage(params = {}, = {}) req = build_request(:start_key_usage, params) req.send_request() end |
#stop_key_usage(params = {}) ⇒ Types::StopKeyUsageOutput
Disables an Amazon Web Services Payment Cryptography key, which makes it inactive within Amazon Web Services Payment Cryptography.
You can use this operation instead of [DeleteKey] to deactivate a key. You can enable the key in the future by calling [StartKeyUsage].
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- DeleteKey][1
- StartKeyUsage][2
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_StartKeyUsage.html [3]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html
3295 3296 3297 3298 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3295 def stop_key_usage(params = {}, = {}) req = build_request(:stop_key_usage, params) req.send_request() end |
#tag_resource(params = {}) ⇒ Struct
Adds or edits tags on an Amazon Web Services Payment Cryptography key.
<note markdown=“1”> Tagging or untagging an Amazon Web Services Payment Cryptography key can allow or deny permission to the key.
</note>
Each tag consists of a tag key and a tag value, both of which are case-sensitive strings. The tag value can be an empty (null) string. To add a tag, specify a new tag key and a tag value. To edit a tag, specify an existing tag key and a new tag value. You can also add tags to an Amazon Web Services Payment Cryptography key when you create it with [CreateKey].
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- ListTagsForResource][3
- UntagResource][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateKey.html [2]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListTagsForResource.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_UntagResource.html
3375 3376 3377 3378 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3375 def tag_resource(params = {}, = {}) req = build_request(:tag_resource, params) req.send_request() end |
#untag_resource(params = {}) ⇒ Struct
Deletes a tag from an Amazon Web Services Payment Cryptography key.
<note markdown=“1”> Tagging or untagging an Amazon Web Services Payment Cryptography key can allow or deny permission to the key.
</note>
**Cross-account use:** This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see [Resource-based policies].
**Related operations:**
- ListTagsForResource][2
- TagResource][3
[1]: docs.aws.amazon.com/payment-cryptography/latest/userguide/security_iam_resource-based-policies.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListTagsForResource.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_TagResource.html
3431 3432 3433 3434 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3431 def untag_resource(params = {}, = {}) req = build_request(:untag_resource, params) req.send_request() end |
#update_alias(params = {}) ⇒ Types::UpdateAliasOutput
Associates an existing Amazon Web Services Payment Cryptography alias with a different key. Each alias is associated with only one Amazon Web Services Payment Cryptography key at a time, although a key can have multiple aliases. The alias and the Amazon Web Services Payment Cryptography key must be in the same Amazon Web Services account and Amazon Web Services Region
**Cross-account use:** This operation can’t be used across different Amazon Web Services accounts.
**Related operations:**
- CreateAlias][1
- DeleteAlias][2
- GetAlias][3
- ListAliases][4
[1]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_CreateAlias.html [2]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteAlias.html [3]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetAlias.html [4]: docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListAliases.html
3490 3491 3492 3493 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3490 def update_alias(params = {}, = {}) req = build_request(:update_alias, params) req.send_request() end |
#waiter_names ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
3519 3520 3521 |
# File 'lib/aws-sdk-paymentcryptography/client.rb', line 3519 def waiter_names [] end |