-
Notifications
You must be signed in to change notification settings - Fork 392
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
[Cloudflare Logpush] Add non_aws_bucket_name option to AWS S3 input #8278
[Cloudflare Logpush] Add non_aws_bucket_name option to AWS S3 input #8278
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
🌐 Coverage report
|
multi: false | ||
required: false | ||
show_user: true | ||
description: "This can replace Bucket ARN with a Bucket Name for collecting logs from a 3rd party S3 compatible service. It will override the global Non AWS Bucket Name if provided." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be helpful to have a brief section in the global docs about this. Probably something similar to the text in the docs that you link to in the PR description. Though maybe what you have in the package manifest is enough.
{{/each}} | ||
{{#contains "forwarded" tags}} | ||
publisher_pipeline.disable_host: true | ||
{{/contains}} | ||
{{#if processors}} | ||
processors: | ||
{{processors}} | ||
{{/if}} | ||
{{/if}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Final new line (and below).
multi: false | ||
required: false | ||
show_user: true | ||
description: "This can replace Bucket ARN with a Bucket Name for collecting logs from a 3rd party S3 compatible service. This is a global setting which can be overriden by specific local bucket names for each data stream if required. \nUsing non-AWS S3 compatible buckets requires the use of Access Key ID and Secret Access Key for authentication. To specify the S3 bucket name, use the non_aws_bucket_name config and the endpoint must be set to replace the default API endpoint." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: "This can replace Bucket ARN with a Bucket Name for collecting logs from a 3rd party S3 compatible service. This is a global setting which can be overriden by specific local bucket names for each data stream if required. \nUsing non-AWS S3 compatible buckets requires the use of Access Key ID and Secret Access Key for authentication. To specify the S3 bucket name, use the non_aws_bucket_name config and the endpoint must be set to replace the default API endpoint." | |
description: |- | |
This can replace Bucket ARN with a Bucket Name for collecting logs from a 3rd party S3 compatible service. This is a global setting which can be overriden by specific local bucket names for each data stream if required. | |
Using non-AWS S3 compatible buckets requires the use of Access Key ID and Secret Access Key for authentication. To specify the S3 bucket name, use the non_aws_bucket_name config and the endpoint must be set to replace the default API endpoint. |
multi: false | ||
required: false | ||
show_user: true | ||
description: "This can replace Bucket ARN with a Bucket Name for collecting logs from a 3rd party S3 compatible service. This is a global setting which can be overriden by specific local bucket names for each data stream if required. \nUsing non-AWS S3 compatible buckets requires the use of Access Key ID and Secret Access Key for authentication. To specify the S3 bucket name, use the non_aws_bucket_name config and the endpoint must be set to replace the default API endpoint." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably the wording should be To specify the non-AWS S3 bucket name, use the Non AWS Bucket Name config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍🏼
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add system test to run on CI. Probably, Localstack as a Non-AWS service?
@chemamartinez should we considering renaming the |
I think the system tests can be added in #7034 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.. You can proceed to merge after @jamiehynds approval
655cf3f
to
da179ed
Compare
@jamiehynds sure! Looks like more user-friendly this way. Here you have the requested changes: da179ed. |
Package cloudflare_logpush - 1.16.0 containing this change is available at https://epr.elastic.co/search?package=cloudflare_logpush |
Proposed commit message
It exposes the
non_aws_bucket_name
of the AWS S3 input for the Cloudflare Logpush integration so users are able to collect logs from a 3rd party S3 bucket. Apart from the global setting, a local one for each data stream has been added so a different bucket can be set for each data stream.See more about how to use the
non_aws_bucket_name
here.The new parameter is called
Cloudflare R2 bucket name
, as Cloudflare R2 is the S3-compatible storage service that Cloudflare provides by default, so it is assumed to be the one used by its users. Nevertheless, it is also noted that the parameter can be used to specify any other S3-compliant service.Checklist
changelog.yml
file.Screenshots