Archiving to the cloud through the S3 API

Configuring connection settings for the S3 API
If you are connecting to an Archive Node using the S3 interface, you must configure the connection settings for the S3 API. Until these settings are configured, the ARC service remains in a Major alarm state as it is unable to communicate with the external archival storage system.

Modifying connection settings for S3 API
After the Archive Node is configured to connect to an external archival storage system through the S3 API, you can modify some settings should the connection change.

Modifying the Cloud Tiering Service state
You can control the Archive Node's ability read and write to the targeted external archival storage system that connects through the S3 API by changing the state of the Cloud Tiering Service.

Resetting the Store Failure Count for S3 API connection
If your Archive Node connects to an archival storage system through the S3 API, you can reset the Store Failure Count, which can be used to clear the ARVF (Store Failures) alarm.

Migrating objects from Cloud Tiering - S3 to a Cloud Storage Pool
If you are currently using the Cloud Tiering - Simple Storage Service (S3) feature to tier object data to an S3 bucket, consider migrating your objects to a Cloud Storage Pool instead. Cloud Storage Pools provide a scalable approach that takes advantage of all of the Storage Nodes in your StorageGRID system.

Archiving to the cloud through the S3 API

More information