Create and manage deployments

Find and create a design #

1. Choose the organisation, then Deployments. Use Search deployments and Sort deployments to find a name; an empty search result is different from a failed deployment list.
2. Owners and Editors can select New deployment. Enter a non-empty Deployment name of up to 200 characters, then Create deployment. Cancel closes the draft; leaving a non-empty draft asks for confirmation.
3. Select Open deployment. A direct editor link can open only a deployment in your current accessible list. For Deployment unavailable or conflicting links, return to Deployments and select an authorized design.

Edit details and enter or leave the editor #

Above the editor, Deployment details has Deployment name (up to 200 characters) and Deployment description (up to 4000). These fields save automatically after a brief pause when you have save permission. Wait for Deployment details saved. An error means they were not saved; edit the fields to retry. This metadata save is separate from the editor’s design Save.

Full screen expands the editor; Exit full screen or Escape returns to the page. If the browser refuses native fullscreen, the product can use its viewport layout. Back to deployments leaves the editor and asks before discarding unsaved design changes. Browser reload/closing can lose unsaved work; save first.

The catalogue has no archive or snapshot-history selector. To remove a saved design, see Delete a saved deployment.

Delete a saved deployment #

An active organisation Owner or Editor, or a user with an active explicit deployment Editor grant, can delete that deployment. Viewer access alone cannot delete a design.

Delete deployment removes the saved design and its version history from Atlas. It cannot be undone in Atlas. Stored snapshots follow the existing retention and cleanup policy; they may remain in storage until cleanup runs.

This deletes an Atlas design only. It never deletes AWS infrastructure, other deployments, users or organisation memberships.

1. Choose the correct Active organisation, then open Deployments. Find the deployment and choose Delete deployment in its row.
2. If an unsaved-change prompt appears, Cancel keeps your current work. Return to the editor and Save first if you want to keep it. Choose Discard changes only if you intend to lose unsaved edits; deletion does not save them.
3. Review Delete deployment? and the named target and consequences. Cancel leaves the saved deployment unchanged. Choose Delete deployment only when you intend to remove that design.
4. After confirmed success, the deployment disappears from your list and any current selection of that deployment is cleared. Other deployments remain available.
5. If Atlas cannot confirm deletion or shows an error, refresh the deployment list before retrying. A stale or repeated request may find that the deployment is already gone; do not assume an error means deletion succeeded.

Manage explicit deployment access #

1. For a deployment you can administer, choose Manage access. Search deployment grants and use paging to find an existing grant.
2. An Owner can select an Organisation member for Add explicit access. Choose Viewer or Editor and Save deployment access, then confirm. Editors can manage eligible existing grants; the UI controls which additions are available.
3. Use Edit grant to change an active eligible grant. Save deployment access and confirm. Cancel grant edit discards the draft after any required confirmation.
4. Revoke grant removes the explicit grant after confirmation. It does not remove organisation membership or inherited access. Organisation Viewer remains organisation-wide, so a narrower grant cannot restrict it.