Connector Name

destination-s3

Connector Version

1.9.10

What step the error happened?

None

Relevant information

Problem

The S3 destination currently forces path-style requests and does not let users select virtual-hosted-style addressing. Some S3-compatible endpoints require the bucket name in the hostname, so configuring only a custom endpoint is insufficient.

For the same bucket and object, the two URL shapes are:

• Path style: https://s3.example.com/my-bucket/object.json
• Virtual-hosted style: https://my-bucket.s3.example.com/object.json

Requested behavior

Add an optional s3_addressing_style setting with these values:

• path_style: keep forcePathStyle = true.
• virtual_hosted_style: use forcePathStyle = false to enable the AWS SDK's virtual-hosted-style behavior.

Keep path_style as the default, including when the setting is omitted, to preserve existing configurations. The option should be available in the S3 destination UI and configuration specification.

Current upstream evidence

Checked public master on October 12, 2026 at commit af60507ae6d46f1b30c7eb31f963cd7477b2bec8. The current connector version is 1.9.10, using Bulk Load CDK 1.1.1. The current version and behavior were verified through source inspection; runtime reproduction against this release has not been performed.

• S3 client construction still hard-codes forcePathStyle = true.
• The connector specification has no addressing-style option.

Previous request

This revisits #19426, which requested the same destination capability and was closed by the stale bot on May 9, 2024. Its associated PR #19427 was closed without being merged. The option is still absent in the current implementation. Please advise whether to track the renewed contribution here or reopen the earlier issue.

Contribution

Yes, I am willing to contribute. I have prepared a backward-compatible implementation and focused tests locally. The proposed contribution is a Bulk CDK change followed by a destination-s3 update after the new CDK version is published.

I plan to submit from our company fork, HudHud-Maps/data-airbyte-fork. Please advise whether an organization-fork exception is available or which contribution workflow you prefer.

Relevant log output

Contribute

• Yes, I want to contribute