Package de.taimos.pipeline.aws

Class AbstractS3Step.S3ClientOptions

java.lang.Object
de.taimos.pipeline.aws.AbstractS3Step.S3ClientOptions
All Implemented Interfaces:
Serializable
Enclosing class:
AbstractS3Step
public static class AbstractS3Step.S3ClientOptions extends Object implements Serializable
See Also:

  • Constructor Details

    • S3ClientOptions

      public S3ClientOptions()

  • Method Details

    • isPathStyleAccessEnabled

      public boolean isPathStyleAccessEnabled()

    • setPathStyleAccessEnabled

      public void setPathStyleAccessEnabled(boolean pathStyleAccessEnabled)

    • isPayloadSigningEnabled

      public boolean isPayloadSigningEnabled()

    • setPayloadSigningEnabled

      public void setPayloadSigningEnabled(boolean payloadSigningEnabled)

    • createS3ClientBuilder

      public software.amazon.awssdk.services.s3.S3ClientBuilder createS3ClientBuilder()

    • createS3AsyncClientBuilderForCopy

      public software.amazon.awssdk.services.s3.S3AsyncClientBuilder createS3AsyncClientBuilderForCopy()
      multipartEnabled is not the SDK default, and without it the transfer manager issues a single CopyObject, which S3 rejects above 5 GiB - so copies that worked under v1 would start failing.

    • createS3AsyncClientBuilderForUpload

      public software.amazon.awssdk.services.s3.S3AsyncClientBuilder createS3AsyncClientBuilderForUpload()
      As for copies: without multipartEnabled a single PutObject is issued, which S3 rejects above 5 GiB.

    • createS3AsyncClientBuilderForDownload

      public software.amazon.awssdk.services.s3.S3AsyncClientBuilder createS3AsyncClientBuilderForDownload()

    • createS3Configuration

      public software.amazon.awssdk.services.s3.S3Configuration createS3Configuration()
      v1 had pathStyleAccessEnabled and payloadSigningEnabled directly on the client builder; v2 moves both under S3Configuration. pathStyleAccessEnabled maps across unchanged. payloadSigningEnabled has no exact v2 equivalent: v1 used it to sign the request body in one piece instead of relying on aws-chunked signing, so the closest v2 expression is to turn chunked encoding off. Left at the SDK default when the option is off, which is v1's default too.