User guidesIT services in ColombiaeCloud help and resources

ECLOUD / 04

Delete instances and environments carefully

Two different operations in one guide: identify the scope, review confirmation and verify the result.

Version 4.0 · review proposal · 28 Oct 2026

eCloud manuals

Arrows point to real controls. Enlarge any detail. Names and options may vary by version and account permissions.

01

First: identify what you will delete

Authorised administrators only. These actions can stop services and cause data loss. Do not delete production resources for practice.

An environment

For example, Testing or Production within an application. In the example, the notice preserves the instance, other environments and persistent volumes. Read the current notice: this does not guarantee complete recovery.

An instance

May affect every application it hosts.

A persistent volume is storage that may retain data independently of the running application. Keeping it is not equivalent to having a backup or keeping the service operational.

02

Required checks before continuing

  • I identified the exact instance, application and environment.
  • I have authorisation and a maintenance window if required.
  • I verified a recoverable backup, its coverage and a recovery plan.
  • I checked users, integrations and dependent services.
  • I confirmed whether this is Testing or Production.
  • I read current retention, recovery and billing conditions.

If a check is missing, stop and consult the responsible person. Never use screenshot names as confirmation: verify your actual resource.

03

Delete an environment: select and review

  1. Open AppCloud → Aplicaciones and enter the correct instance and application.
  2. Select the environment and verify its name and Testing or Production label.
  3. Open Configuración (Settings) and locate Zona de riesgo (Danger zone).
  4. Read what will stop and which data the current console says will be retained.
  5. Select Eliminar entorno (Delete environment) to review the confirmation dialog.
  6. Check the identifier and scope again. Cancel if they do not match.
  7. Only after completing all checks, type the exact requested name and confirm Eliminar entorno.

Afterwards: verify the target environment changed as stated and that environments and services meant to remain available still work. Deleting Production may immediately affect real users.

Reference capture · Spanish interface

Configuración

Configuración
Select 1 to highlight the instruction.

01Confirm the environment in the heading before entering. Do not switch environments during deletion.

Reference capture · Spanish interface

Eliminar entorno

Eliminar entorno
Select 1 to highlight the instruction.

01Opens confirmation. Before continuing, check the name, authorisation and recoverable backup.

Reference capture · Spanish interface

Cancelar

Cancelar
Select 1 to highlight the instruction.

01Closes the dialog without deleting. Use it if the name or scope does not match the authorised operation.

04

Delete an instance: review its full scope

  1. In Applications, identify the exact instance and review all hosted applications.
  2. Open Eliminar instancia (Delete instance) on that instance’s card.
  3. Read the shutdown, retention and permanent deletion notice. Check current conditions before confirming.
  4. Type the requested identifier only if it matches the authorised resource.
  5. Select Enviar a la papelera (Move to trash) only with approval and a verified backup.
  6. Observe the status.Apagando (Shutting down), then En papelera (In trash).
Check the recovery period shown by your console before confirming. Do not assume a three-day retention period. After permanent deletion, recovery through the trash may be unavailable.
Reference capture · Spanish interface

Enviar a la papelera

Enviar a la papelera
Select 1 to highlight the instruction.

01Affects the instance and its applications. Read the current recovery period and billing conditions in the dialog.

05

Trash, recovery and final verification

The example offers Restaurar (Restore) while the instance remains recoverable in trash. Do not assume it will be available after permanent deletion.

  1. If recovery is needed, contact the responsible person immediately and confirm the correct instance is still within the current retention period.
  2. With authorisation, review Restore and current notices.
  3. Wait for completion and verify application access, data and dependencies. An Active status does not replace this check.
  4. Record the date, responsible person, resource and result.

Check your contract and current billing; this guide does not guarantee billing terms.

If something does not match: do not repeat deletions or create resources with the same name to try to recover data. Contact support with the identifier, time, action and visible status, without secrets.

Help and references

Available options depend on the service, version and your account permissions.

Request support ↗