Setting Up Access to Portal Content Using the S3 API: CTERA Fusion
  • 3 Minutes to read
  • Dark
    Light
  • PDF

Setting Up Access to Portal Content Using the S3 API: CTERA Fusion

  • Dark
    Light
  • PDF

Article summary

CTERA Fusion enables the content of cloud folders to be accessed using the S3 API, either using supported S3 operations in programs or using an S3 browser application like FileZilla, WinSCP, Cyberduck, CloudBerry, and S3 Browser.

Note

CTERA Fusion supports S3 browsers that use multipart uploads.

The capabilities of CTERA Fusion include:
In-Place Read/Write – Enables reading and writing directly to a global file system using the S3 protocol eliminating expensive and time-consuming processes of copying data to external S3 buckets.
Single Namespace Across File and Object – Interact with data generated at the edge using standard object storage S3 protocols, or access cloud-generated data from the edge using NAS protocols. Data is available where you need it, when you need it.
Support for Multipart Uploads – Benefit from multipart uploads, making ingestion and sharing of large files even more efficient.
Robust Security – All data is secured in transit via TLS and encrypted at rest, providing an added layer of protection.
NT-ACL support – File ACLs are preserved.

To set up access to a cloud folder using the S3 API, you need to do the following:

After these steps, you can access the cloud folder content using the S3 API by providing the following:

Setting Up the CTERA Portal Server

The global administrator must specify at least one portal server as an S3 endpoint. For details, see the description of the S3 Endpoint field in Editing Server Settings:General Settings.

Note

Checking the S3 Endpoint is required on only one server. For high availability, the global administrator can set the S3 Endpoint on more than one server.

Creating an S3 Bucket

To access content you must set up the required cloud folders as buckets, one bucket for each cloud folder.

To create an S3 bucket:

  1. Select Folders > Buckets in the navigation pane.
    The Buckets page opens, displaying all cloud folders linked as S3 buckets.
    image.png
  2. Click New Bucket.
    The New Bucket window is displayed.
    image.png
  3. Complete the fields:
    Name – A name for the bucket. The name cannot include uppercase letters. CTERA recommends a name between 3 and 63 characters. Valid characters are lowercase letters, numbers, and special characters.
    Description (Optional) – A description for the bucket.
    Cloud Folder Owner – The user who owns the bucket. The owner controls access to the bucket using the Access Key ID and Secret Access Key pair created for that user.
    Linked Cloud Folder – A folder from the list of folders associated with the folder owner.
  4. Click Save.

image.png
To access the bucket content using the S3 API, you need the endpoint.

To get the bucket endpoint:

  1. Select Folders > Buckets in the navigation pane.
    The Buckets page opens, displaying all cloud folders linked as S3 buckets.
    image.png
  2. Click the bucket.
    The bucket window is displayed with the name of the bucket as the window title.
    image.png
  3. Copy the Bucket Address to use as the endpoint.
    Note

    The endpoint includes the DNS name and not the IP address. You cannot access the bucket using an endpoint with an IP address.

  4. Optionally, edit the Description (Optional) field.
  5. Click Save or Cancel.

You can delete a bucket by selecting the bucket row and clicking Delete.
image.png

Creating Access Key IDs and Secret Access Keys

A single Access Key ID and Secret Access Key pair can be used to access all the buckets assigned for a specific user. Each user can have more than one pair of Access Key IDs and Secret Access Keys, up to a maximum of 100.

Both the administrator can create the Access Key ID and Secret Access Key pair for a user as described in Setting Up API Keys to Access S3 Buckets, or the end user can create the Access Key ID and Secret Access Key pair in the end user portal, as described in Using an S3 Browser.

Accessing Portal Content Using the S3 API

Access to portal content using the S3 API can be done using an S3 browser or in code.

Access via an S3 Browser

You require the following information:

  • The endpoint for the bucket
  • The Access Key ID
  • The Secret Access Key

You enter this information in the S3 browser to access the content, for example using S3 Browser:
image.png

Access via Code Using the S3 Protocol

The following S3 operations are supported:

  • GetObject
  • HeadObject
  • DeleteObject
  • S3 PutObject
  • S3 ListObject
  • Copy
  • Get Byte Range
  • CreateMultipartUpload
  • ListMultipartUploads
  • UploadPart
  • ListParts
  • AbortMultipartUpload
  • CompleteMultipartUpload
Note

The following operations are not supported:

  • Create a bucket
  • Versioning
  • SignedURLs

Was this article helpful?

What's Next