-
Notifications
You must be signed in to change notification settings - Fork 133
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
Init doesn't work in GovCloud #617
Comments
The SDK even has a library specifically for parsing ARNs, which is used in that very same file: https://github.com/aws/aws-for-fluent-bit/blob/mainline/init/fluent_bit_init_process.go#L91-L94 |
Thanks/Sorry! We will work on fixing this. Definitely should use the ARN parsing library. |
Signed-off-by: Wesley Pettit <[email protected]>
Signed-off-by: Wesley Pettit <[email protected]>
Testing the fix with this image, which can be pulled by any AWS account if you want to test/use as well:
|
Confirmed, this fixes the issue for me running in GovCloud environment :) |
Signed-off-by: Wesley Pettit <[email protected]>
Thank you @PettitWesley on the super fast turnaround on this, I really appreciate it! |
@PettitWesley just wondering - what's the release cadence like for this repo? Just waiting on a new image to be available for us to consume :) |
@dalgibbard probably next week I hope (no guarantee)... we're working out some issues in our build pipeline right now... Also we needs to do a CVE release first: |
This reverts commit 35f563b.
This reverts commit 760bfed.
This reverts commit 760bfed.
This reverts commit 760bfed.
Describe the question/issue
When using aws-for-fluentbit in the AWS GovCloud environment, loading from S3 using the
init
tagged images is not possible because of this line: https://github.com/aws/aws-for-fluent-bit/blob/mainline/init/fluent_bit_init_process.go#L205Which assumes that the ARN prefix is always
arn:aws:*
(13 chars to the bucket name start), whereas, in GovCloud environments, this is actuallyarn:aws-us-gov:*
(20 chars to the bucket name start)This results in truncation on the wrong part, resulting in a target bucket/path of:
Configuration
Using envvars in ECS Fargate to load from S3; eg:
Fluent Bit Log Output
Note the Bucket name starting with
v:s3:::
due to misaligned truncationFluent Bit Version Info
2.31.5
Cluster Details
ECS Fargate
Application Details
N/A
Steps to reproduce issue
See above
Related Issues
N/A
The text was updated successfully, but these errors were encountered: