-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Describe the feature you'd like
In CreateFeatureGroup, the parameter "KmsKeyId" expects KMS Key ID ARN, instead of the KmsKeyId value. This behavior is different from other API calls. This is not just a documentation issue. This inconsistency becomes a serious problem when someone tries to pass KMS Key to all SageMaker API calls either via either AWS Systems Manager Parameter Store or by encapsulating KMS Key in a SageMaker SuperSession object.
How would this feature be used? Please describe.
To preserve backwards compatibility, modify CreateFeatureGroup API call to accept both KmsKeyId and KmsKeyId_ARN.
Describe alternatives you've considered
This seems to be the best solution
Additional context
https://t.corp.amazon.com/V408655442/communication