Conversation
lucabelluccini
left a comment
There was a problem hiding this comment.
Hello @alaudazzi
I would involve the owners / developer of the aws_logs integration for a double check.
To me, the pointers to the Filebeat aws-s3 doc and cloudwatch doc make sense, but I would have expected that the whole Requirement section of https://www.elastic.co/docs/current/integrations/aws#requirements would have been ported to https://www.elastic.co/docs/current/integrations/aws_logs.
IIUC, the permissions should be similar (just the AWS integration Requirement section mixes up both the permissions required for S3 and Cloudwatch).
Obviously the "cost" of this is we're duplicating the content.
If instead we want to tackle this problem properly in the follow up issue #11793, then this PR should be ok to allow users to understand which permissions are required.
I would ask @octavioranieri to review.
|
+1 to @lucabelluccini suggestions above. It's better to have it within the page (and product) instead of referencing to an external page. |
|
Duplicating content often leads to maintenance issues that are difficult to track. |
|
@alaudazzi I agree with Luca on |
|
@kaiyan-sheng @octavioranieri
Yes, let's do that. Please note that one of the points highlighted in the follow-up issue is |
💚 Build Succeeded
History
cc @alaudazzi |
|
|
Package aws_logs - 1.5.1 containing this change is available at https://epr.elastic.co/package/aws_logs/1.5.1/ |
* Add required permissions for AWS custom logs * Update changelog and manifest
* Add required permissions for AWS custom logs * Update changelog and manifest
This PR adds the specific permissions required to use the Custom AWS Logs integration, both for
aws-s3input andaws-cloudwatchinput.Closes #11603.