E2E CloudS3 compatibility
E2E Object Storage implements the same S3 API that Amazon S3 does, so any S3-compliant tool or SDK can read and write your buckets, once it is pointed at E2E’s endpoint instead of Amazon’s. E2E recommends the MinIO SDKs for the smoothest experience, and writes its own examples against them.
The endpoint for each region
Section titled “The endpoint for each region”Point a tool at the endpoint for the region your bucket is in:
| Region | Endpoint |
|---|---|
| Delhi | objectstore.e2enetworks.net |
| Chennai | in-south1-objectstore.e2enetworks.net |
Every tool needs three things to connect: this endpoint, an access key, and its secret key. See Generate an access key. The other pages on connecting a tool link back here for the endpoint, rather than repeating it.
Creating and listing buckets
Section titled “Creating and listing buckets”An access key works with the objects inside whichever bucket it has been given a role on: uploading, downloading, copying, versioning, deleting, all the everyday work an S3-compatible tool does, the same way it would against Amazon S3. Creating a new bucket, or listing every bucket in your account, happens in the dashboard or through the MyAccount API.
The MyAccount API uses your account API key, which works with the same account credentials as the dashboard. An Object Storage access key reaches only the objects in the buckets it is attached to. Keep the two apart: an app that only needs a bucket gets an access key.
If a tool warns that your key lacks permission to list all buckets, that is expected: it is testing for a permission E2E Object Storage keeps at the account level, and your key still works on its own buckets.
A GUI instead of the command line
Section titled “A GUI instead of the command line”CS Browser, formerly S3 Browser, is a free Windows application that connects the same way any other S3-compatible tool does, so you can browse, upload, and download through a window instead of a terminal; see Connect with CS Browser (formerly S3 Browser).