This guide explains the process for withdrawing and restoring assets when a Public Cloud product is terminated.

Withdrawing and Restoring Assets on Public Cloud

When a voluntary termination is performed, the resources associated with the Public Cloud are gradually deactivated and then deleted.

DNS resources of the DNSaaS (Designate) type are immediately deleted upon termination.

Other resources are deactivated across all Public Cloud regions:

• users and projects are deactivated;
• access to the remaining resources is no longer possible;
• resources that are still exposed are deactivated:
  • S3 buckets and Swift containers (Object Storage);
  • stopped Compute instances (power-off);
  • automatic exit from pause mode before instance shutdown;
  • automatic exit from rescue mode before instance shutdown;
  • deactivation of Load Balancers (LBaaS);
  • deactivation of orchestrations and alarms (Heat).

Resources that are not exposed are not immediately modified, including:

• volumes;
• images;
• backups;
• snapshots;
• public keys;
• private networks;
• secrets.

Asset Retention Period

With the exception of DNS resources, assets are retained for a period of 7 days after termination.

On the 7th day at 3:00 AM, all remaining resources are permanently deleted, with no possibility of restoration.

Restoring Assets After Termination

After the product is terminated, a request for restoration can be made within a maximum period of 3 calendar days.

This request requires:

• an active subscription to a Public Cloud product;
• an up-to-date billing status;
• compliance with the applicable contractual terms.

Provided that the data is still available on the storage infrastructure, suspended services can be reactivated within a maximum period of 4 days after the request is approved.

Stopped instances are not restarted automatically. However, they can be restarted manually if necessary.

Exporting assets remains your responsibility.