This guide explains the procedures for withdrawal (deletion) and return of assets upon termination of a Public Cloud product.

Withdrawal and return of assets on Public Cloud

When a voluntary termination is performed, the resources associated with the Public Cloud are progressively 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:

• deactivation of users and projects;
• inability to access remaining resources;
• deactivation of still exposed resources:
  • 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).

Non-exposed resources 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 AM, all remaining resources are permanently deleted, with no possibility of restoration.

Return of assets after termination

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

This request requires:

• an active subscription to a Public Cloud product;
• an up-to-date billing situation;
• compliance with applicable contractual conditions.

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

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

The export of assets remains your responsibility.