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] s3:ListObjects does not exist #3198

Merged
merged 2 commits into from
Dec 1, 2023

Conversation

joe-elliott
Copy link
Member

According to this thread the s3:ListObjects permission does not actually exist. Removing!

#2489

cc @knylander-grafana

@joe-elliott joe-elliott merged commit ed1d975 into grafana:main Dec 1, 2023
14 checks passed
Copy link

@shayal01 shayal01 left a comment

Choose a reason for hiding this comment

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

this doesn't work.even if we give full access to an iam user, with iam policy for full access of s3 ,s3accesspoint policy with all the actions and and bucket policy delegating the access to the s3accesspoint .the following error throws up when i am using in the rosa classic clustermsg="error running Tempo" err="failed to init module services: error initialising module: store: failed to create store: unexpected error from ListObjects on tempo-openshift: The specified method is not allowed against this .and i think there is no more listobject action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants