Skip to content

Specify v4 s3 signatures to allow buckets with KMS encryption#82

Merged
tarekio merged 7 commits intomainfrom
s3-sig-v4
Jun 19, 2025
Merged

Specify v4 s3 signatures to allow buckets with KMS encryption#82
tarekio merged 7 commits intomainfrom
s3-sig-v4

Conversation

@tarekio
Copy link
Contributor

@tarekio tarekio commented Feb 23, 2025

Jira Issue

  1. [Add links to jira issues]

Description

[Brief description of changes]

Checklist

  • Tests added/updated
  • Documentation updated (if needed)
  • New strings prepared for translations

API Changes (if applicable)

  • Permissions checked
  • Endpoint tests added

Additional Notes

[Any other relevant information]

@tarekio tarekio self-assigned this Feb 23, 2025
Base automatically changed from fix-arabic-filenames to main February 24, 2025 12:42
@tarekio tarekio requested review from Copilot and level09 May 31, 2025 14:34
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the S3 client configuration by specifying the v4 signature version, which is necessary for supporting buckets with KMS encryption.

  • Introduces a new import for BotoConfig from botocore.config
  • Instantiates s3_config with signature_version='s3v4' and passes it to the S3 client
  • Updates the S3 client initialization to include the new configuration

@sjacorg sjacorg deleted a comment from Copilot AI Jun 12, 2025
@tarekio tarekio merged commit 15d0291 into main Jun 19, 2025
6 of 7 checks passed
@tarekio tarekio deleted the s3-sig-v4 branch June 19, 2025 19:33
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.

3 participants