[PR #141] Fix S3/Backblaze upload failure by enabling path-style addressing #161

Open
opened 2026-02-26 21:34:47 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/eduardolat/pgbackweb/pull/141
Author: @possebon
Created: 10/3/2025
Status: 🔄 Open

Base: mainHead: bugfix/issue-140-s3-upload-failure


📝 Commits (1)

  • 310733a Fix S3/Backblaze upload failure by enabling path-style addressing

📊 Changes

1 file changed (+5 additions, -1 deletions)

View changed files

📝 internal/integration/storage/s3.go (+5 -1)

📄 Description

  • Add UsePathStyle option to S3 client configuration
  • Required for S3-compatible services like Backblaze B2
  • Restores functionality lost in AWS SDK v1 to v2 migration
  • Compatible with Amazon S3, Backblaze, and arm64 architecture

Fixes #140

Summary by CodeRabbit

  • Bug Fixes
    • Improved compatibility with S3-compatible storage by switching to path-style addressing, reducing access and listing errors with certain buckets, regions, and VPC/private endpoints.
    • Enhances reliability when connecting to providers like MinIO or Ceph and legacy S3 setups.
    • No action required; existing configurations continue to work with more consistent connectivity and fewer endpoint-related issues.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/eduardolat/pgbackweb/pull/141 **Author:** [@possebon](https://github.com/possebon) **Created:** 10/3/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `bugfix/issue-140-s3-upload-failure` --- ### 📝 Commits (1) - [`310733a`](https://github.com/eduardolat/pgbackweb/commit/310733a123f486074fb0b1eb28c24b896b26d3eb) Fix S3/Backblaze upload failure by enabling path-style addressing ### 📊 Changes **1 file changed** (+5 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `internal/integration/storage/s3.go` (+5 -1) </details> ### 📄 Description - Add UsePathStyle option to S3 client configuration - Required for S3-compatible services like Backblaze B2 - Restores functionality lost in AWS SDK v1 to v2 migration - Compatible with Amazon S3, Backblaze, and arm64 architecture Fixes #140 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Improved compatibility with S3-compatible storage by switching to path-style addressing, reducing access and listing errors with certain buckets, regions, and VPC/private endpoints. * Enhances reliability when connecting to providers like MinIO or Ceph and legacy S3 setups. * No action required; existing configurations continue to work with more consistent connectivity and fewer endpoint-related issues. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pgbackweb#161
No description provided.