Cherry-pick #23469 to 7.x: Rename s3 input to aws-s3 input #23573
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.
Cherry-pick of PR #23469 to 7.x branch. Original message:
What does this PR do?
This PR is to rename Filebeat
s3
input toaws-s3
input.Closes elastic/integrations#488
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
aws-s3
input:This should start
aws-s3
input with no error.aws-s3
input:and change
modules.d/aws.yml
to enable a fileset inaws
module. For example:Then run Filebeat and you should see no error. If there are new logs going into the S3 which generates new SQS messages in
test-fb-ks
, you should also see the events in Elasticsearch.