Configure KMS Key Policies for Kinesis Video Streams Encryption

[kgopelom]

Issue #, if available:

Description of changes: This pull request addresses an issue encountered when using a customer-managed KMS key for encryption in Kinesis Video Streams (KVS). While the default KMS key works without any problems, using a customer-managed key leads to certain complications.

Changes made in this pull request:

• Implemented KMS key policies specifically tailored for the encryption key used in Kinesis Video Streams.
• Ensured that the necessary permissions are in place for the customer-managed KMS key.
• Tested the implementation to verify that encryption and decryption operations function correctly with the configured key policies.

By applying these changes, we can now successfully utilize customer-managed KMS keys for encryption in Kinesis Video Streams, providing enhanced security and control over the encryption process.

Please review the modifications and provide any feedback or suggestions for improvement.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[kgopelom]

Hello,

Not sure if the responsibility is delegated to user for them to add lambda permissions in their key policy when using customer managed keys. In that case, it would be beneficial to update the documentation to clearly communicate this expectation to users.