Internxt's Object Storage provides native Rclone support. To connect to Rclone, simply follow these steps:
Run “rclone config”, Input “n” for “New Remote”, press “Enter”, input a name for the remote “internxt-us-central-1”, then press “Enter”
# rclone config
No remotes found - make a new one
1. n) New remote
2. s) Set configuration password
3. q) Quit config
n/s/q> n
name> internxt-us-central-1
Choose the Storage Type. Input “5” for “S3 Compliant”, press “Enter”, input “18” for “Any other S3 compatible provider”, then press “Enter”
Type of storage to configure.
Enter a string value. Press Enter for the default ("").
Choose a number from below, or type in your own value
5 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, Ceph, China Mobile, Digital Ocean, Dreamhost, IBM COS, Lyve Cloud, Minio, Netease, RackCorp, Scaleway, SeaweedFS, StackPath, Storj, Tencent COS and Wasabi
Storage> 5
Option provider.
Choose your S3 provider.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
18 / Any other S3 compatible provider
\ (Other)
provider> 18
Configure the Authentication. Input “1”, press “Enter” and Input your Internxt Access and Secret key when prompted. See our article about generating these credentials to obtain them
Option env_auth.
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
Only applies if access_key_id and secret_access_key is blank.
Choose a number from below, or type in your own boolean value (true or false).
Press Enter for the default (false).
1 / Enter AWS credentials in the next step.
\ (false)
2 / Get AWS credentials from the environment (env vars or IAM).
\ (true)
env_auth> 1
Option access_key_id.
AWS Access Key ID.
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
access_key_id> some_access_key_id
Option secret_access_key.
AWS Secret Access Key (password).
Leave blank for anonymous access or runtime credentials.
Enter a value. Press Enter to leave empty.
secret_access_key> some_secret_access_key
Configure the ACL. Input “1” to set uploaded objects to private, then press “Enter”
Option acl.
Canned ACL used when creating buckets and storing or copying objects.
This ACL is used for creating objects and if bucket_acl isn't set, for creating buckets too.
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
Note that this ACL is applied when server-side copying objects as S3
doesn't copy the ACL from the source but rather writes a fresh one.
Choose a number from below, or type in your own value.
Press Enter to leave empty.
/ Owner gets FULL_CONTROL.
1 | No one else has access rights (default).
\ (private)
/ Owner gets FULL_CONTROL.
2 | The AllUsers group gets READ access.
\ (public-read)
/ Owner gets FULL_CONTROL.
3 | The AllUsers group gets READ and WRITE access.
| Granting this on a bucket is generally not recommended.
\ (public-read-write)
/ Owner gets FULL_CONTROL.
4 | The AuthenticatedUsers group gets READ access.
\ (authenticated-read)
/ Object owner gets FULL_CONTROL.
5 | Bucket owner gets READ access.
| If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
\ (bucket-owner-read)
/ Both the object owner and the bucket owner get FULL_CONTROL over the object.
6 | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
\ (bucket-owner-full-control)
acl> 1
Finalize Configuration. Input “n” to decline editing advanced config, press “Enter”, then confirm choices. Input “y”, then press “Enter” to finalize the configuration. Finally, input “q”, then press “Enter” to quit the configuration
Edit advanced config?
y) Yes
n) No (default)
y/n> n
--------------------
[internxt-us-central-1]
type = s3
provider = Other
access_key_id = some_access_key
secret_access_key = some_secret_access_key
endpoint = s3.us-central-1.internxt.com
acl = private
--------------------
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d> y
Current remotes:
Name Type
==== ====
internxt-us-central-1 s3
e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q>
If you run into any problems or concerns, please don’t hesitate to contact us for support at [email protected]