Skip to content

modify CreateFeatureGroup API call to accept _both_ KmsKeyId and KmsKeyId_ARN.  #3057

@sermolin

Description

@sermolin

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions