-
Notifications
You must be signed in to change notification settings - Fork 65
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
Create FAQ for common errors on encrypt/decrypt #305
Comments
"unencryptedDataKey has not been set" and "Noop keyring is not allowed: Set a keyId or discovery" are the two that have been giving me trouble so far. |
Definitely backing @holmser on those clearer error messages - also in related business when the IAM permissions aren't quite right it would be nice to get a message that says insufficient IAM privileges rather than the cryptic null parameter not allowed which I think you tend to get at the moment. |
I get following error: Following example here: https://github.com/aws/aws-encryption-sdk-javascript/blob/master/modules/example-node/src/aes_simple.ts using Raw AES keyring in example here. Only difference being I split up encryption and decryption steps into separate functions. What am I missing? Is KMS required even if explicitly want to avoid it, for example using Hashicorp Vault for storing secrets? |
Errors can bubble up from the encrypt/decrypt functions.
It would be nice to have clear explanations for common errors.
In creating this documentation,
the error messages can also be re-evaluated for clarity.
See #152 as an example.
The text was updated successfully, but these errors were encountered: