Skip to main content

How to connect Internxt's object storage to Rclone

Internxt's Object Storage features a direct, native support for Rclone, follow the steps from this article to set up Rclone.

Configure Internxt S3 Storage with rclone

This guide explains how to configure an Internxt S3-compatible remote using rclone.

1. Start the configuration

Run:

rclone config

If no remotes are configured, select:

n) New remote

2. Name the remote

Enter a name for the remote.

Example:

name> internxt-us-central-1

You can choose any name.

3. Select the storage type

When prompted for the storage type, select:

4) Amazon S3 Compliant Storage Providers (s3)

4. Select the provider

Choose:

51) Other

Internxt provides an S3-compatible API, so the Other provider should be used.

5. Configure authentication

When prompted for environment authentication, select:

1

This configures rclone to use the AWS credentials entered in the next steps instead of obtaining them from environment variables or EC2/ECS metadata.

Enter your credentials:

access_key_id> <your_access_key>  secret_access_key> <your_secret_key>

6. Configure the region

When prompted for the region, select:

1

This configures rclone to use Signature Version 4 with an empty region, which is recommended for Internxt's S3-compatible API.

7. Enter the endpoint

Enter the endpoint for your storage region.

Example:

endpoint> s3.us-central-1.internxt.com

8. Configure the location constraint

Leave this field empty unless you are creating buckets and have been instructed to use a specific location constraint.

location_constraint>

The location constraint must match the configured region when creating new buckets. It is not required for normal uploads or downloads.

9. Configure the ACL

When prompted, select:

1) private

The ACL (Access Control List) determines the permissions applied when creating buckets and storing or copying objects.

The private canned ACL gives only the bucket owner FULL_CONTROL. No other users are granted access by default.

This ACL is used when:

  • Creating buckets

  • Storing objects

  • Copying objects

If bucket_acl is not configured separately, this ACL is also used when creating buckets.

Important: This ACL is applied when performing server-side copies. Amazon S3 does not copy the ACL from the source object. Instead, it writes a new ACL using the value configured here.

For more information about canned ACLs, refer to the Amazon S3 documentation:

10. Configure Object Lock

When prompted, leave the default value:

bucket_object_lock_enabled> false

Object Lock is used to prevent objects from being deleted or overwritten for a defined retention period. Enable this only if you require Object Lock for newly created buckets.

11. Advanced configuration

When asked:

Edit advanced config?

Select:

n

The default settings are sufficient for most users.

12. Save the configuration

Review the configuration. It should look similar to the following:

type: s3 provider: Other access_key_id: <your_access_key> secret_access_key: <your_secret_key> endpoint: s3.us-central-1.internxt.com acl: private

If everything is correct, save the remote by selecting:

y

Your Internxt S3 remote is now configured and ready to use.

Example configuration

Name: internxt-us-central-1 Type: s3 Provider: Other Endpoint: s3.us-central-1.internxt.com ACL: private
Did this answer your question?