Skip to content
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

x-pack/filebeat/input/awss3: support for Access Point ARN #41495

Merged
merged 11 commits into from
Nov 19, 2024

Conversation

chemamartinez
Copy link
Contributor

@chemamartinez chemamartinez commented Oct 31, 2024

Proposed commit message

Added a new option access_point_arn to the AWS S3 input as an alternative to the bucket ARN to access S3 buckets.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@chemamartinez chemamartinez added enhancement Filebeat Filebeat Team:Security-Service Integrations Security Service Integrations Team labels Oct 31, 2024
@chemamartinez chemamartinez self-assigned this Oct 31, 2024
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Oct 31, 2024
Copy link
Contributor

mergify bot commented Oct 31, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @chemamartinez? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

Copy link
Contributor

mergify bot commented Oct 31, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Oct 31, 2024
Copy link
Contributor

mergify bot commented Nov 6, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b 41494-awss3-access_point upstream/41494-awss3-access_point
git merge upstream/main
git push upstream 41494-awss3-access_point

@chemamartinez chemamartinez force-pushed the 41494-awss3-access_point branch from d3b8e50 to 827c92e Compare November 13, 2024 17:40
@chemamartinez chemamartinez force-pushed the 41494-awss3-access_point branch from 827c92e to 148d6c6 Compare November 13, 2024 17:41
@chemamartinez chemamartinez added backport-8.15 Automated backport to the 8.15 branch with mergify backport-8.16 Automated backport with mergify labels Nov 13, 2024
@chemamartinez chemamartinez force-pushed the 41494-awss3-access_point branch from c501329 to dfb0fdb Compare November 13, 2024 18:09
@chemamartinez chemamartinez marked this pull request as ready for review November 14, 2024 09:00
@chemamartinez chemamartinez requested review from a team as code owners November 14, 2024 09:00
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

Copy link
Contributor

@belimawr belimawr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not an expert in the AWS S3 input, but LGTM.

Copy link
Contributor

@ShourieG ShourieG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AndersonQ
Copy link
Member

LGTM, just make sure to do not merge the 8.16 backport until 8.16.1 is released.

Copy link
Contributor

mergify bot commented Nov 18, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b 41494-awss3-access_point upstream/41494-awss3-access_point
git merge upstream/main
git push upstream 41494-awss3-access_point

@kaiyan-sheng
Copy link
Contributor

Looks good to me. Can we create an issue in the integrations repo to add this new parameter later in related data streams please? Thanks!

@strawgate
Copy link
Contributor

Does setting the Access Point ARN work when using SQS?

@chemamartinez
Copy link
Contributor Author

Looks good to me. Can we create an issue in the integrations repo to add this new parameter later in related data streams please? Thanks!

Thank you for the review. The issue for updating the integrations is elastic/integrations#11737.

@chemamartinez chemamartinez removed the backport-8.15 Automated backport to the 8.15 branch with mergify label Nov 19, 2024
@chemamartinez chemamartinez merged commit 301988d into elastic:main Nov 19, 2024
20 of 22 checks passed
mergify bot pushed a commit that referenced this pull request Nov 19, 2024
Added a new option access_point_arn to the AWS S3 input as an alternative to the bucket ARN to access S3 buckets.

(cherry picked from commit 301988d)
mergify bot pushed a commit that referenced this pull request Nov 19, 2024
Added a new option access_point_arn to the AWS S3 input as an alternative to the bucket ARN to access S3 buckets.

(cherry picked from commit 301988d)
chemamartinez pushed a commit that referenced this pull request Nov 19, 2024
…s Point ARN (#41689)

Added a new option access_point_arn to the AWS S3 input as an alternative to the bucket ARN to access S3 buckets.
chemamartinez pushed a commit that referenced this pull request Nov 22, 2024
…ss Point ARN (#41688)

* x-pack/filebeat/input/awss3: support for Access Point ARN (#41495)

Backport: Added a new option access_point_arn to the AWS S3 input as an alternative to the bucket ARN to access S3 buckets.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify backport-8.16 Automated backport with mergify enhancement Filebeat Filebeat Team:Security-Service Integrations Security Service Integrations Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[aws]Add support for access point in aws integration
7 participants