Skip to content

AWS: Apply service configurations to S3AsyncClient#16030

Open
yadavay-amzn wants to merge 1 commit into
apache:mainfrom
yadavay-amzn:fix/14575-s3async-service-config
Open

AWS: Apply service configurations to S3AsyncClient#16030
yadavay-amzn wants to merge 1 commit into
apache:mainfrom
yadavay-amzn:fix/14575-s3async-service-config

Conversation

@yadavay-amzn
Copy link
Copy Markdown
Contributor

This fixes a bug where DefaultAwsClientFactory applies S3FileIOProperties.applyServiceConfigurations() to the synchronous S3Client but not to the S3AsyncClient. This means settings like s3.path-style-access, s3.dualstack-enabled, s3.accelerate-enabled, and s3.use-arn-region-enabled silently do not take effect for async S3 operations.

Changes

  1. Widened type bound of S3FileIOProperties.applyServiceConfigurations() from S3ClientBuilder to S3BaseClientBuilder<T, ?> so it accepts both sync and async builders.
  2. Added applyServiceConfigurations call to the S3AsyncClient.builder() path in DefaultAwsClientFactory.s3Async().
  3. Added test testApplyS3AsyncServiceConfigurations verifying that path-style access, ARN region, and acceleration settings are correctly applied to the async client builder.

Closes #14575

Apply S3FileIOProperties.applyServiceConfigurations() to the
S3AsyncClient builder, matching the existing sync S3Client
configuration. Without this, settings like s3.path-style-access
and s3.dualstack-enabled silently do not apply to async operations.
@yadavay-amzn yadavay-amzn changed the title AWS: Apply service configurations to S3AsyncClient (#14575) AWS: Apply service configurations to S3AsyncClient May 12, 2026
@yadavay-amzn
Copy link
Copy Markdown
Contributor Author

@jackye1995 @nastra Could you take a look when you get a chance? This fixes a bug where S3 service configurations (path-style-access, dualstack, acceleration, use-arn-region) are not applied to the async client. CI is green.

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.

AWS: DefaultAwsClientFactory s3 / s3Async serviceConfiguration are not equivalent

1 participant