-
Notifications
You must be signed in to change notification settings - Fork 460
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
Add support for AWS Access Point ARN in compatible integrations #12154
Add support for AWS Access Point ARN in compatible integrations #12154
Conversation
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
/test |
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.
I mostly focused on the elastic/obs-ds-hosted-services
integration packages (aws
, aws_logs
) and data streams, but the PR looks good.
So, LGTM.
multi: false | ||
required: false | ||
show_user: true | ||
description: This is an alternative to the Bucket ARN, one of them is required for collecting logs via the AWS S3 Bucket. |
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.
nits: Suggestion to rephrase the description to clearly conveying the relationship with BucketARN
Mandatory if the "Collect logs via S3 Bucket" switch is on. It is a required parameter for collecting logs via the AWS S3 Bucket unless you set a Bucket ARN.
Not sure, how important it is to mention - what happens if both BucketARN and AccessPoint ARNs are set, which one is be given higher preference? Would it be an important point to mention in the README ?
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.
Thanks for the suggestions.
Not sure, how important it is to mention - what happens if both BucketARN and AccessPoint ARNs are set, which one is be given higher preference? Would it be an important point to mention in the README ?
I think it is nice to have it. I added it at the description of Bucket ARN
setting, as Readme don't talk about these particular settings in most of the integrations.
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.
Added a suggestion for improving the description. Other changes LGTM!
/test |
💚 Build Succeeded
History
|
Quality Gate passedIssues Measures |
Package amazon_security_lake - 2.3.0 containing this change is available at https://epr.elastic.co/package/amazon_security_lake/2.3.0/ |
Package aws - 2.38.0 containing this change is available at https://epr.elastic.co/package/aws/2.38.0/ |
Package aws_bedrock - 0.18.0 containing this change is available at https://epr.elastic.co/package/aws_bedrock/0.18.0/ |
Package aws_logs - 1.6.0 containing this change is available at https://epr.elastic.co/package/aws_logs/1.6.0/ |
Package canva - 0.4.0 containing this change is available at https://epr.elastic.co/package/canva/0.4.0/ |
Package carbon_black_cloud - 2.8.0 containing this change is available at https://epr.elastic.co/package/carbon_black_cloud/2.8.0/ |
Package cisco_umbrella - 1.28.0 containing this change is available at https://epr.elastic.co/package/cisco_umbrella/1.28.0/ |
Package cloudflare_logpush - 1.29.0 containing this change is available at https://epr.elastic.co/package/cloudflare_logpush/1.29.0/ |
Package f5_bigip - 1.23.0 containing this change is available at https://epr.elastic.co/package/f5_bigip/1.23.0/ |
Package imperva_cloud_waf - 1.5.0 containing this change is available at https://epr.elastic.co/package/imperva_cloud_waf/1.5.0/ |
Package jamf_protect - 2.9.0 containing this change is available at https://epr.elastic.co/package/jamf_protect/2.9.0/ |
Package sentinel_one_cloud_funnel - 1.8.0 containing this change is available at https://epr.elastic.co/package/sentinel_one_cloud_funnel/1.8.0/ |
Package servicenow - 0.8.0 containing this change is available at https://epr.elastic.co/package/servicenow/0.8.0/ |
Package sublime_security - 1.4.0 containing this change is available at https://epr.elastic.co/package/sublime_security/1.4.0/ |
Package symantec_endpoint_security - 1.6.0 containing this change is available at https://epr.elastic.co/package/symantec_endpoint_security/1.6.0/ |
Package tanium - 1.14.0 containing this change is available at https://epr.elastic.co/package/tanium/1.14.0/ |
Package trellix_edr_cloud - 1.6.0 containing this change is available at https://epr.elastic.co/package/trellix_edr_cloud/1.6.0/ |
Proposed commit message
Add support for the new setting
access_point_arn
for the AWS S3 input added at elastic/beats#41495 for 8.16.2 and 8.17.0.Checklist
changelog.yml
file.Related issues