[aws] Fix s3access ingest pipeline#17748
Merged
kaiyan-sheng merged 4 commits intomainfrom Mar 16, 2026
Merged
Conversation
packages/aws/data_stream/s3access/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
vpcflow |
7874.02 | 5586.59 | -2287.43 (-29.05%) | 💔 |
cloudwatch_logs |
1e+06 | 500000 | -500000 (-50%) | 💔 |
To see the full report comment with /test benchmark fullreport
Contributor
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Kavindu-Dodan
approved these changes
Mar 13, 2026
💚 Build Succeeded
History
|
|
Package aws - 6.3.2 containing this change is available at https://epr.elastic.co/package/aws/6.3.2/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
This PR fixes the s3access data stream ingest pipeline by:
Host header with port: Extended
S3IDpattern to allow:so host headers likebucket.s3.region.amazonaws.com:80are matched.Trailing
aclrequiredfield: IntroducedS3ACLREQUIREDpattern [a-zA-Z0-9_-]+ and use it for the last optional field so values such asus-east-1(and other hyphenated tokens) are parsed instead of failing the grok.Checklist
changelog.ymlfile.How to test this PR locally
Sample log is already added and
elastic-package test pipeline -d s3access --generateis used to update the expected.json file.