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

[Docs] Required permissions under AWS custom logs #11603

Open
octavioranieri opened this issue Oct 31, 2024 · 3 comments
Open

[Docs] Required permissions under AWS custom logs #11603

octavioranieri opened this issue Oct 31, 2024 · 3 comments
Assignees
Labels

Comments

@octavioranieri
Copy link

Currently we only mention the required permissions under the parent AWS integration, which would cover all the AWS integrations:
https://www.elastic.co/docs/current/integrations/aws#aws-permissions

Users may need more granular of what’s required for the specifics instead of having all the permissions.

AWS custom logs docs should have the specific required permissions, similar to the Filebeat module:
https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-aws-s3.html#_aws_permissions_2

@lucabelluccini
Copy link
Contributor

The request here could be expanded further, where we should have a way to include the documentation associated to a specific input in all integrations using it.

E.g. aws-s3 input is used in several integrations (O11y & Security owned) and in all of them generally the settings and prerequisites are similar.

@lucabelluccini
Copy link
Contributor

FYI @alaudazzi / @eedugon do you know what might be the best way to put this under the radar?

@alaudazzi
Copy link
Contributor

@lucabelluccini Thanks for raising this! It makes sense to provide more granular info where needed and consolidate similar settings to facilitate discoverability. I can follow up on this ticket.

@alaudazzi alaudazzi self-assigned this Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants