-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KMS: Fix method for specifying custom key material #1482
Conversation
⚡️ Deploying PR Preview... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing this out 🙌 🚀 I have requested some changes regarding the custom key material we use to create a key, once thats fixed we can merge the PR.
super secret key | ||
</disable-copy> | ||
$ awslocal kms create-key --tags '[{"TagKey":"_custom_key_material_","TagValue":"c3VwZXIgc2VjcmV0IGtleQo="}]' | ||
$ CUSTOM_KEY_MATERIAL=$(openssl rand -base64 32) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather keep the format intact and change the string to thisisasecurekey
which would give me dGhpc2lzYXNlY3VyZWtleQ==
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sannya-singal Apologies for the delayed response. I've made the correction as you suggested.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @ainoya, let me know if something is not clear or you need help, happy to assist :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing the reviews, changes LGTM 🎉
In the previous documentation, it was possible to create a key, but when running
kms encrypt
, the errorInvalid key size (136) for AES.
would occur. I've updated the documentation to ensure that the key is generated with a size of 32 bytes.Example: