We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The policy given here https://milvus.io/docs/s3.md#Associate-an-IAM-role-with-a-Kubernetes-service-account is not correct - there is no reason to apply a s3:ListBucket statement to a resource named arn:aws:s3:::<bucket-name>/* - the s3:ListBucket only needs to be applied to a bucket itself. The current policy is shown below:
s3:ListBucket
arn:aws:s3:::<bucket-name>/*
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:GetObject", "s3:PutObject", "s3:ListBucket", "s3:DeleteObject" ], "Resource": [ "arn:aws:s3:::cloudavail-milvus", "arn:aws:s3:::cloudavail-milvus/*" ] } ] }
The policy below is actually the correct policy:
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:DeleteObject", "s3:GetObject", "s3:PutObject" ], "Resource": [ "arn:aws:s3:::cloudavail-milvus/*" ] }, { "Effect": "Allow", "Action": [ "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::cloudavail-milvus" ] } ] }
I'll submit a PR with the corrected policy.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing issue for this?
Issue
The policy given here https://milvus.io/docs/s3.md#Associate-an-IAM-role-with-a-Kubernetes-service-account is not correct - there is no reason to apply a
s3:ListBucket
statement to a resource namedarn:aws:s3:::<bucket-name>/*
- thes3:ListBucket
only needs to be applied to a bucket itself. The current policy is shown below:Suggestion
The policy below is actually the correct policy:
Anything else?
I'll submit a PR with the corrected policy.
The text was updated successfully, but these errors were encountered: