fix(backend): Refactor S3 bucket management by replacing MinIO client code with AWS SDK v2 and improving configuration validation #12512
+448
−50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The API server required
OBJECTSTORECONFIG_ACCESSKEYandOBJECTSTORECONFIG_SECRETACCESSKEYto be non-empty, which broke AWS IRSA (IAM Roles for Service Accounts) authentication where credentials are obtained from the environment.Solution
AccessKeyandSecretAccessKeyoptional in validationBucketAlreadyOwnedByYouerrors;BucketAlreadyExistsnow surfaces as a warning to help detect misconfigurationChanges
validateRequiredConfig: No longer requires credentials; only validates both are set or both emptyloadAWSConfig: Uses default credential chain when credentials are emptyensureBucketExists: Refactored to use AWS SDK v2 instead of minio-goisBucketAlreadyOwnedByUs: Only suppressesBucketAlreadyOwnedByYou(concurrent creation race), surfacesBucketAlreadyExistsas warningFixes:
Checklist: