The S3 (Compatible) endpoint enables Automate MFT to connect to storage services that implement the Amazon S3 API, but are not hosted on Amazon Web Services.

This endpoint type allows integration with third-party S3-compatible providers, such as Backblaze and MinIO, enabling Automate MFT to perform file transfer operations using a consistent S3-based interface.

Because S3-compatible providers may require configuration that differs from native Amazon S3, Automate MFT includes a dedicated S3 (Compatible) endpoint type for non-AWS services. This ensures that the S3 (AWS) endpoint is kept as simple as possible for use with native Amazon S3 services.

Create an S3 (Compatible) endpoint

To add a new S3 (AWS) endpoint:
  1. Click the Libraries drop-down menu and select Endpoints.
  2. Click the Add Endpoints drop-down menu and select S3 (Compatible).
  3. The New S3 (Compatible) Endpoint dialog appears.

General

Enter basic endpoint details:
  • Name: Provide a unique name for the endpoint.
  • Description: Optionally, enter a description to help identify the purpose or scope of this endpoint.
  • Service URL: The base URL of the S3-compatible service. This value is provided by your storage provider and identifies the endpoint used for all API requests.

    The Service URL must begin with https://.

  • Bucket: Enter the name of the bucket that Automate MFT will access for file transfer operations.
  • Authentication Method: Select a valid Authentication Method from the authentication method library, or to add a new Authentication Method, click Add New. For more information, see S3 (Compatible) authentication method.

Compatibility

The Compatibility tab provides settings that allow you to adjust howAutomate MFT interacts with different S3-compatible providers. Some providers implement the S3 protocol with variations, and these settings ensure compatibility in those environments.

  • Force Path Style: Enables path-style addressing for S3 requests. When enabled, the bucket name is included in the request path instead of the hostname.

    Use this option for providers that do not support virtual-host-style addressing.

  • Disable Payload Signing: Disables request payload signing. Some S3-compatible providers do not support payload signing, and enabling this option allows requests to succeed in those environments.

  • Disable Checksums: Disables checksum validation for requests. This option may be required when connecting to providers that do not support checksum validation or where checksum handling differs from the standard S3 implementation.

Retry

Define retry behavior:
  • Retry Count: Number of extra times that a transfer is retried.
  • Retry Delay: The time between each retry.
  • Use the time unit drop-down menu to select a time measurement for the retry delay.

Save the endpoint

Click Save to create the endpoint