-
Notifications
You must be signed in to change notification settings - Fork 63
Decrypting AWS DB Activity Stream #151
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
Comments
I looked into the code and I figured but in |
It looks like the As a side note, for every record you are making an AWS KMS decrypt call. Why not use a KMS keyring? |
Looking deeper at the
The raw keyrings are tricky as these values must exactly match or the keyring will not even attempt to decrypt. I have opened #152 to track this error message. |
Thanks @seebees, that solved my issue. I could decrypt the activityStreamEvent. Maybe we should add the Node example in docs. |
Hi @amirsaber, Need help, Requirement: lambda function to Decrypting AWS Aurora Mysql DB Activity Stream. Do the Above script will works now? I follow the code but endup with Configuration conflict. Am I missing something or wrong? INFO Error: Configuration conflict. Cannot process message with ID c62bdfgfd43543sdf due to CommitmentPolicy REQUIRE_ENCRYPT_REQUIRE_DECRYPT requiring only committed messages. Algorithm ID was ALG_AES256_GCM_IV12_TAG16_HKDF_SHA384_ECDSA_P384. See: https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/troubleshooting-migration.html Could some one please help? Do we have any clear reference or doc with working example? |
I get the following error
while running a lambda function to decrypt DB activity streams.
with Test Data
I followed https://github.com/awslabs/aws-encryption-sdk-javascript/blob/master/modules/example-node/src/aes_simple.ts and https://docs.amazonaws.cn/en_us/AmazonRDS/latest/AuroraUserGuide/DBActivityStreams.html#DBActivityStreams.CodeExample
Not sure if this is a bug or I did something wrong. Any help would be much appreciated
The text was updated successfully, but these errors were encountered: