Skip to main content
This page describes how S3 Glacier maps to services in the environment where the application runs, including backend choices, supported operations and service-specific behavior.

​
Supported environments

  • Scaleway
Check the operation and capability tables for the behavior your application depends on. A supported environment does not imply that every operation of the origin service is available.

​
How the targets compare

Each row compares a capability of S3 Glacier with its adaptation on each target. A dash means this profile does not state the capability for that target.

​
Cloud Adapter

​
On Scaleway

​
Scaleway Object Storage

​
Service level agreements

These tables show Tensor9’s standard service levels and adapters whose standard terms are still being defined. Your signed agreement determines the SLAs, covered adapters and operations, limits, remedies and support terms that apply to your deployment.
Listed terms cover requests sent through this service adapter. They do not cover direct connections to the target service or replace the cloud provider’s own SLA. Each origin-to-target pair has its own terms or an explicit pending status. See the SLA tables, measurement rules, and scaling conditions.

​
S3 Glacier to Scaleway Object Storage

SLA status: Not applicable This maps archive storage classes and lifecycle configuration. It is not a Glacier request-serving adapter or a promise about archive retrieval time.

​
Install and run

The documentation and SLAs are public. Downloading and running the Cloud Adapter binary requires an entitled customer account. Set T9_API_KEY as described in Install and Authenticate, then list the adapters your account may use with this origin:
The result is limited to directed mappings for this origin that your account is entitled to use. Use a returned target identifier when configuring the adapter or investigating a request. Request binary access from [email protected] if your account does not yet include this direction.

​
Existing data and credentials

Selecting a backend does not copy existing data, credentials or access policies. Plan and verify migration separately before changing an application’s endpoint. Do not assume an identifier, credential or encrypted value from the origin service works unchanged on the target.

​
Configure, tune and debug

Start with setup and configuration. Use tuning to understand supported request tags, debugging to investigate a request, and High Fidelity Cloud Emulators to validate a bounded reproduction. For requests that go through an entitled service adapter, use tensor9 explain and x-t9-explain to inspect the selected mapping.