# Switching and Portability Annex

**Effective date:** 28 July 2026
**Version:** 1.0

This Annex is the Switching and Portability Annex referred to in Section 12.2 of the [Terms of Service](https://docs.aur.lu/docs/legal/terms) and forms part of the Terms. It exhaustively specifies, for each Service, the categories of Exportable Data and digital assets, their formats, the export methods, the register of applicable data structures, standards, and open interoperability specifications, the exempted categories, the step-by-step switching procedure, known restrictions, known risks to service continuity, and the switching assistance contact. Capitalized terms have the meaning given in the Terms.

Information on switching charges (there are none), early-termination charges (there are none), and standard Fees is published on the [Data Act information page](https://docs.aur.lu/docs/legal/data-act).

## a. Exportable Data per Service

### Object Storage (Aurora S3)

| Category | Format | Export method |
|---|---|---|
| Objects | Native object bytes, exactly as stored | S3 API `GetObject` (including ranged reads and multipart-assisted download) |
| Object metadata | S3 system metadata and user-defined metadata (`x-amz-meta-*`), as HTTP headers / JSON | S3 API `GetObject` / `HeadObject` |
| Version metadata | Version identifiers, delete markers, timestamps | S3 API `ListObjectVersions` |
| Object Lock metadata | Retention mode, retain-until dates, legal holds | S3 API `GetObjectRetention`, `GetObjectLegalHold`, `GetObjectLockConfiguration` |
| Bucket configuration | Versioning state, Object Lock configuration, encryption setting | S3 API `GetBucketVersioning`, `GetObjectLockConfiguration`, and the Portal |

### Compute (Aurora Compute)

| Category | Format | Export method |
|---|---|---|
| Volume images | Standard disk-image formats (raw / qcow2) | On request via [support@aurorainfra.ai](mailto:support@aurorainfra.ai): we extract the volume on the underlying platform and provide a time-limited download link |
| Snapshot images | Standard disk-image formats (raw / qcow2) | On request via [support@aurorainfra.ai](mailto:support@aurorainfra.ai): we extract the snapshot on the underlying platform and provide a time-limited download link |
| Instance configuration | JSON (service offering, attached volumes, network attachments) | Portal API |
| Network configuration | JSON (VPCs, private networks, public IP allocations, static NAT assignments) | Portal API |
| SSH-key configuration | JSON (key names and public keys) | Portal API |

### Inference (Aurora Inference)

| Category | Format | Export method |
|---|---|---|
| Usage and billing records | CSV / JSON (per-model token counts, request counts, timestamps, billing line items) | Portal (billing section) and Portal API |
| Stored configuration | JSON (API token metadata, quota and limit settings) | Portal API |

Prompt and Output content is not stored by the Inference Service (Terms Section 6.2) and therefore does not exist to be exported.

## b. Register of data structures, formats, standards, and open interoperability specifications

| Specification | Used for | Reference |
|---|---|---|
| S3-compatible API (HTTP/REST) | Object Storage export: objects, metadata, versions, Object Lock, bucket configuration | [S3 documentation](https://docs.aur.lu/docs/s3/getting-started) |
| OpenAI-compatible API (HTTP/REST, JSON) | Inference Service interoperability (chat and text completions, including streaming) | [Inference documentation](https://docs.aur.lu/docs/inference) |
| JSON | Configuration exports; usage and billing record export | RFC 8259 |
| CSV | Usage and billing record export | RFC 4180 |
| raw / qcow2 disk images | Compute volume and snapshot images | Open, commonly used disk-image formats (QEMU project specifications) |

## c. Exempted categories (trade secrets)

The following are exempted from Exportable Data to the extent necessary to protect Aurora's trade secrets (Terms Section 12.2):

- internal scheduler and placement logs; and
- infrastructure-level diagnostics.

This exemption does not impede switching. **Your usage and billing records remain exportable** (section a above).

## d. Step-by-step switching procedure

The following procedure mirrors Terms Sections 12.3–12.4:

1. **Notice.** Initiate switching (or elect erasure) by notice to [support@aurorainfra.ai](mailto:support@aurorainfra.ai) (or via the Portal, where a dedicated option is available), stating whether you will (i) switch to another provider (naming it where applicable), (ii) move to your own on-premises ICT infrastructure, or (iii) erase your Exportable Data. The maximum notice period is **30 days**.
2. **Transitional period.** After the notice period, a transitional period of **30 calendar days** begins, during which Aurora, you, and any destination provider cooperate in good faith. Aurora provides reasonable assistance, maintains service continuity, supports your exit strategy (including by providing all relevant information), and maintains a high level of security throughout the switching process and the retrieval period.
3. **Unfeasibility notice.** If completing switching within 30 days is technically unfeasible, Aurora notifies you **within 14 working days of your switching request**, duly justifying the unfeasibility and indicating an alternative transitional period **not exceeding 7 months**.
4. **Customer extension.** You may in any event extend the transitional period **once**, for a period you consider more appropriate for your purposes.
5. **Retrieval period.** After the end of the transitional period, you have a data-retrieval period of **at least 30 calendar days** during which your Exportable Data remains retrievable through the Service APIs.
6. **Erasure and confirmation.** Following successful completion of switching and expiry of the retrieval period (or a later date agreed with you), Aurora **fully erases** all of your Exportable Data and digital assets from its primary systems — including destruction of bucket encryption keys, which is irreversible, logged, and renders encrypted Filecoin-resident ciphertext permanently unreadable — and **confirms the erasure**, except only where Union or Member State law requires retention. Residual copies on Aurora-operated storage providers are removed within the period stated in Terms Section 4.4(d); where such copies remain at the time of the confirmation, the confirmation states this, and a further confirmation is issued once removal completes. For encrypted buckets, erasure is effective upon key destruction.

The contract remains applicable throughout the transitional period; the contract for the affected Service terminates upon successful completion of switching, or at the end of the notice period where you elected erasure. Fees for the affected Service cease to accrue upon termination, except charges permitted under Terms Section 12.5.

## e. Known restrictions

- **S3 compatibility deltas.** "S3-compatible" does not mean full parity with Amazon S3; specific operations, headers, consistency behaviors, and error semantics may differ. The supported operations and current limits are set out in the [S3 documentation](https://docs.aur.lu/docs/s3/getting-started) and [Limits & Quotas](https://docs.aur.lu/docs/s3/reference/limits-quotas).
- **Public Filecoin network copies.** Copies of unencrypted data that third parties have already retrieved from the public Filecoin network cannot be recalled by Aurora (Terms Section 4.4(d)). Erasure under this Annex covers Aurora-operated infrastructure and Aurora-managed keys.
- **Object Lock retention.** Objects under Object Lock (especially Compliance mode) cannot be deleted before the configured retention expires, even at your request; they remain exportable, and storage Fees continue to accrue for locked objects (Terms Section 4.5).

## f. Known risks to continuity of services

- **Transfer duration.** Exporting large datasets is constrained by network throughput; plan the transitional period (and any extension) accordingly.
- **Cutover.** Repointing your applications, endpoints, and DNS to a destination provider or your own infrastructure is under your control; parallel use of the Services alongside the destination during the transition (which the Data Act permits) reduces cutover risk.
- **Destination capabilities.** Feature differences at the destination (for example S3 API deltas or different disk-image import formats) may require adaptation of your applications or images.
- **Early Access Compute.** The Compute Service is an Early Access Service without an availability commitment (Terms Sections 5.2 and 8); volume and snapshot exports are provided on request via support (section a above).

## g. Switching assistance contact

For assistance with switching, portability, and export: [support@aurorainfra.ai](mailto:support@aurorainfra.ai).