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

object_storage: remove access denied warning for s3 buckets #162

Merged
merged 1 commit into from
Dec 21, 2023

Conversation

tkren
Copy link
Contributor

@tkren tkren commented Dec 7, 2023

About this change - What it does

The Access denied on bucket check warning messages do not add value, at least they are confusing. A missing s3:ListBucket permission does not prohibit writing to a bucket.

The `Access denied on bucket check` warning messages do not add value,
at least they are confusing. A missing `s3:ListBucket` permission does
not prohibit writing to a bucket.
@@ -553,7 +553,8 @@ def check_or_create_bucket(self) -> None:
if status_code == HTTPStatus.MOVED_PERMANENTLY:
raise InvalidConfigurationError(f"Wrong region for bucket {self.bucket_name}, check configuration")
elif status_code == HTTPStatus.FORBIDDEN:
self.log.warning("Access denied on bucket check, assuming write permissions")
# Access denied on bucket check, most likely due to missing s3:ListBucket, assuming write permissions

Choose a reason for hiding this comment

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

Suggested change
# Access denied on bucket check, most likely due to missing s3:ListBucket, assuming write permissions
# Access denied on bucket check, most likely due to missing s3:ListBucket, assuming we have write permissions

@rominf rominf merged commit e7d8d4a into Aiven-Open:main Dec 21, 2023
8 checks passed
@tkren tkren deleted the teakay-remove-bucket-check-warning branch January 2, 2024 19:16
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