Expand description

Data structures used by operation inputs/outputs.

Modules§

  • Builders
  • Error types that Payment Cryptography Control Plane can respond with.

Structs§

  • Contains information about an alias.

  • The attributes for IPEK generation during export.

  • Parameter information for IPEK generation during export.

  • Parameter information for key material export using asymmetric RSA wrap and unwrap key exchange method.

  • Parameter information for key material export using symmetric TR-31 key exchange method.

  • Parameter information for key material export using the asymmetric TR-34 key exchange method.

  • Parameter information for key material import using asymmetric RSA wrap and unwrap key exchange method.

  • Parameter information for key material import using symmetric TR-31 key exchange method.

  • Parameter information for key material import using the asymmetric TR-34 key exchange method.

  • Metadata about an Amazon Web Services Payment Cryptography key.

  • The role of the key, the algorithm it supports, and the cryptographic operations allowed with the key. This data is immutable after the key is created.

  • The list of cryptographic operations that you can perform using the key. The modes of use are defined in section A.5.3 of the TR-31 spec.

  • Metadata about an Amazon Web Services Payment Cryptography key.

  • Parameter information for root public key certificate import.

  • A structure that contains information about a tag.

  • Parameter information for trusted public key certificate import.

  • Parameter information for generating a WrappedKeyBlock for key exchange.

Enums§

  • Parameter information for key material export from Amazon Web Services Payment Cryptography using TR-31 or TR-34 or RSA wrap and unwrap key exchange method.

  • Parameter information for key material import into Amazon Web Services Payment Cryptography using TR-31 or TR-34 or RSA wrap and unwrap key exchange method.

  • When writing a match expression against KeyAlgorithm, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against KeyCheckValueAlgorithm, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against KeyClass, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against KeyMaterialType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against KeyOrigin, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against KeyState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against KeyUsage, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against Tr34KeyBlockFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against WrappedKeyMaterialFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against WrappingKeySpec, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.