Class GetParametersForImportRequest
- All Implemented Interfaces:
- SdkPojo,- ToCopyableBuilder<GetParametersForImportRequest.Builder,- GetParametersForImportRequest> 
- 
Nested Class SummaryNested Classes
- 
Method SummaryModifier and TypeMethodDescriptionbuilder()final booleanfinal booleanequalsBySdkFields(Object obj) Indicates whether some other object is "equal to" this one by SDK fields.final <T> Optional<T> getValueForField(String fieldName, Class<T> clazz) Used to retrieve the value of a field from any class that extendsSdkRequest.final inthashCode()final StringkeyId()The identifier of the KMS key that will be associated with the imported key material.static Class<? extends GetParametersForImportRequest.Builder> Take this object and create a builder that contains all of the current property values of this object.final StringtoString()Returns a string representation of this object.final AlgorithmSpecThe algorithm you will use with the RSA public key (PublicKey) in the response to protect your key material during import.final StringThe algorithm you will use with the RSA public key (PublicKey) in the response to protect your key material during import.final WrappingKeySpecThe type of RSA public key to return in the response.final StringThe type of RSA public key to return in the response.Methods inherited from class software.amazon.awssdk.awscore.AwsRequestoverrideConfigurationMethods inherited from interface software.amazon.awssdk.utils.builder.ToCopyableBuildercopy
- 
Method Details- 
keyIdThe identifier of the KMS key that will be associated with the imported key material. The Originof the KMS key must beEXTERNAL.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. - Returns:
- The identifier of the KMS key that will be associated with the imported key material. The
         Originof the KMS key must beEXTERNAL.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. 
- 
         
 
- 
 
- 
wrappingAlgorithmThe 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. 
 If the service returns an enum value that is not available in the current SDK version, wrappingAlgorithmwill returnAlgorithmSpec.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available fromwrappingAlgorithmAsString().- Returns:
- 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. 
 
- 
         
- See Also:
 
- 
 
- 
wrappingAlgorithmAsStringThe 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. 
 If the service returns an enum value that is not available in the current SDK version, wrappingAlgorithmwill returnAlgorithmSpec.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available fromwrappingAlgorithmAsString().- Returns:
- 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. 
 
- 
         
- See Also:
 
- 
 
- 
wrappingKeySpecThe 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. If the service returns an enum value that is not available in the current SDK version, wrappingKeySpecwill returnWrappingKeySpec.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available fromwrappingKeySpecAsString().- Returns:
- 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. 
- See Also:
 
- 
wrappingKeySpecAsStringThe 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. If the service returns an enum value that is not available in the current SDK version, wrappingKeySpecwill returnWrappingKeySpec.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available fromwrappingKeySpecAsString().- Returns:
- 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. 
- See Also:
 
- 
toBuilderDescription copied from interface:ToCopyableBuilderTake this object and create a builder that contains all of the current property values of this object.- Specified by:
- toBuilderin interface- ToCopyableBuilder<GetParametersForImportRequest.Builder,- GetParametersForImportRequest> 
- Specified by:
- toBuilderin class- KmsRequest
- Returns:
- a builder for type T
 
- 
builder
- 
serializableBuilderClass
- 
hashCodepublic final int hashCode()- Overrides:
- hashCodein class- AwsRequest
 
- 
equals- Overrides:
- equalsin class- AwsRequest
 
- 
equalsBySdkFieldsDescription copied from interface:SdkPojoIndicates whether some other object is "equal to" this one by SDK fields. An SDK field is a modeled, non-inherited field in anSdkPojoclass, and is generated based on a service model.If an SdkPojoclass does not have any inherited fields,equalsBySdkFieldsandequalsare essentially the same.- Specified by:
- equalsBySdkFieldsin interface- SdkPojo
- Parameters:
- obj- the object to be compared with
- Returns:
- true if the other object equals to this object by sdk fields, false otherwise.
 
- 
toString
- 
getValueForFieldDescription copied from class:SdkRequestUsed to retrieve the value of a field from any class that extendsSdkRequest. The field name specified should match the member name from the corresponding service-2.json model specified in the codegen-resources folder for a given service. The class specifies what class to cast the returned value to. If the returned value is also a modeled class, theSdkRequest.getValueForField(String, Class)method will again be available.- Overrides:
- getValueForFieldin class- SdkRequest
- Parameters:
- fieldName- The name of the member to be retrieved.
- clazz- The class to cast the returned object to.
- Returns:
- Optional containing the casted return value
 
- 
sdkFields
- 
sdkFieldNameToField- Specified by:
- sdkFieldNameToFieldin interface- SdkPojo
- Returns:
- The mapping between the field name and its corresponding field.
 
 
-