-
Notifications
You must be signed in to change notification settings - Fork 1.9k
out_s3: Add SSE support + validation tests #11409
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
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
0384477 to
26a7ccd
Compare
Summary
Adds server-side encryption support for S3 uploads with SSE-KMS and DSSE-KMS.
Changes
sseconfiguration option:AES256,aws:kms,aws:kms:dssesse_kms_key_idoption to specify a custom KMS key ARNEnter
[N/A]in the box, if an item is not applicable to your change.Testing
Before we can approve your change; please submit the following in a comment:
Configuration Example
[OUTPUT] Name s3 Match * bucket my-bucket region us-east-1 sse aws:kms sse_kms_key_id arn:aws:kms:us-east-1:123456789:key/my-key-idTesting
Click to expand test results
No SSE
[OUTPUT] Name s3 Match valid_no_sse bucket <BUCKET-NAME> region eu-west-1 upload_timeout 5s use_put_object true total_file_size 1M s3_key_format /flb-test/valid_no_sse.logSSE-KMS (single layer)
[OUTPUT] Name s3 Match valid_sse_kms bucket <BUCKET-NAME> region eu-west-1 upload_timeout 5s use_put_object true total_file_size 1M sse aws:kms s3_key_format /flb-test/valid_sse_kms.logTrying to upload without SSE headers (bucket requires SSE-KMS):
With SSE header:
SSE-S3 (AES256)
[OUTPUT] Name s3 Match valid_sse_aes256 bucket <BUCKET-NAME> region eu-west-1 upload_timeout 5s use_put_object true total_file_size 1M sse AES256 s3_key_format /flb-test/valid_sse_aes256.logDSSE-KMS (dual layer)
[OUTPUT] Name s3 Match valid_sse_kms_dsse bucket <BUCKET-NAME> region eu-west-1 upload_timeout 5s use_put_object true total_file_size 1M sse aws:kms:dsse s3_key_format /flb-test/valid_sse_kms_dsse.logSSE-KMS with specific key ID
[OUTPUT] Name s3 Match valid_sse_kms_with_key bucket <BUCKET-NAME> region eu-west-1 upload_timeout 5s use_put_object true total_file_size 1M sse aws:kms sse_kms_key_id arn:aws:kms:eu-west-1:<ACCOUNT-NUMBER>:key/<KEY-ID> s3_key_format /flb-test/valid_sse_kms_with_key.logDSSE-KMS with specific key ID
[OUTPUT] Name s3 Match valid_sse_kms_dsse_with_key bucket <BUCKET-NAME> region eu-west-1 upload_timeout 5s use_put_object true total_file_size 1M sse aws:kms:dsse sse_kms_key_id arn:aws:kms:eu-west-1:<ACCOUNT-NUMBER>:key/<KEY-ID> s3_key_format /flb-test/valid_sse_kms_dsse_with_key.logInvalid SSE value rejected
[OUTPUT] Name s3 Match invalid_sse_value bucket <BUCKET-NAME> region eu-west-1 upload_timeout 5s use_put_object true total_file_size 1M sse invalid_encryption s3_key_format /flb-test/invalid_sse_value.logValgrind report
Click to expand valgrind report
If this is a change to packaging of containers or native binaries then please confirm it works for all targets.
ok-package-testlabel to test for all targets (requires maintainer to do).Documentation
Backporting
Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.