Manage Data Storage Locations

Users save data to files, which are stored as objects in buckets. Buckets are stored in locations, which correspond to a service and a region, such as AWS us-east-1, or GCP europe-west1.

Note

  • ARTESCA cannot operate more than 10 data storage locations on a platform.

  • The default location for ARTESCA is called us-east-1 and should not be changed.

Requirements

  • Before you can establish a location, you must have an account with at least one cloud storage service. This can be:

    • A public cloud, such as Amazon S3 or Google Cloud Platform

    • Scality’s private cloud, the RING, with an S3 Connector

  • When using the CLI, you need to have access tokens. To retrieve these tokens, follow this procedure.

Cross-Region Replication Location

Cross-Region Replication (CRR) is a feature designed to automatically copy your data across different instances of ARTESCA.

Add a Cross-Region Replication Location to ensure your information is safely stored in multiple locations and to achieve higher data durability and accessibility.

CRR Considerations

Types

  • Uni-directional Replication: Data flows from a source site to a destination site.

  • Bi-directional Replication: Data replicates in both directions between two sites, allowing updates on either site to be synchronized to the other.

Principles

  • Replication Only: CRR locations cannot be used for primary data storage, as a storage backend for buckets, or in transition workflows.

  • Metadata Preserved: CRR mirrors essential metadata (like versionID and object lock) to avoid version order mismatch issues.

  • Asynchronous Delay: Replication is asynchronous and event-driven, meaning objects appear on the destination with a delay after being written to the source site.

  • Deletes: Soft deletes (delete markers) are replicated, but hard (permanent) deletions are not.

  • Conflict Rule: In bi-directional setups, conflicts are resolved using a last-writer-wins rule.

  • Encryption: Source object encryption settings are preserved on the destination.

  • Required Roles: A source role (arn:aws:iam::root:role/s3-replication-role) and a destination IAM role.

Limitations

  • One Destination Per Configuration: Each replication configuration can only target a single CRR location (one destination site).

  • No Chaining: Replication is not supported across three or more sites (e.g., A → B → C).

  • Destination Policies: Bucket policies on the destination must explicitly allow the s3:ReplicateObject action, or replication will be denied.

  • Access Control Lists (ACLs): Object ACLs are replicated, but cross-account permissions can require additional configuration on the destination site.

Public Clouds

If you do not have a cloud storage account already configured, here are some useful links to get started. These may change without notice.

Scality RING

RING provides resilient, reliable object storage, and S3 Connector provides an Amazon S3-compatible command set and namespace.

In most cases, you will access the RING through the S3 Connector. However, if you are not using the S3 Connector, you can access the RING directly through the sproxyd REST API.

Scality RING with S3 Connector

S3 Connector provides an Amazon S3-compliant front end for the Scality RING private cloud storage solution.

Except as noted, you can integrate to S3 Connector exactly as you would integrate to any of the other S3-based cloud services, such as AWS, DigitalOcean Spaces, Wasabi Hot Cloud, Orange Naos, or Jaguar Networks. Refer to the S3 Connector and RING documentation for more details on deploying and configuring S3 Connector with the RING.

Scality RING with sproxyd

sproxyd presents a RING-native REST API providing direct object-store access to the RING. If you are integrating to a RING that does not have an S3 Connector installed, use this API to access the RING.

Truststore for Storage Location

The Truststore feature is used when configuring a remote location whose endpoint presents a non-public or privately signed TLS certificate. The truststore allows ARTESCA to validate the server’s certificate and establish a trusted TLS connection.

Operations