Amazon CodeCatalyst is no longer open to new customers. Existing customers can continue to use the service as normal. For more information, see [How to migrate from CodeCatalyst](migration.md).
# Administering Dev Environments for a space
All Dev Environments are created as part of a project within a space. Space members can create their own Dev Environments within a project at the source repository level. Space administrators can then use the Amazon CodeCatalyst console to view, edit, delete, and stop Dev Environments on behalf of space members. In short, space administrators maintain Dev Environments at the space level.
**Considerations for administering Dev Environments**
+ You must have the **Space administrator** role to view the **Dev Environments** page under **Settings** and to manage Dev Environments at the space level.
+ Space members manage the Dev Environments that they create in projects through their CodeCatalyst accounts. When administering Dev Environments as a space administrator, you are maintaining these resources on behalf of space members.
+ Dev Environments default to a specific compute and storage configuration. For information about billing and rates for upgrading your configuration, see the [Amazon CodeCatalyst pricing page](https://codecatalyst.aws/explore/pricing).
**Important**
Dev Environments aren't available for users in spaces where Active Directory is used as the identity provider. For more information, see [I can't create a Dev Environment when I'm signed into CodeCatalyst using a single sign-on account](devenvironments-troubleshooting.md#troubleshoot-create-dev-env-idprovider).
For other considerations about Dev Environments, including stopping running instances, default compute configuration, upgrading your compute, incurring costs, and configuring timeouts, see [Write and modify code with Dev Environments in CodeCatalystWrite and modify code with Dev Environments](devenvironment.md).
**Topics**
+ [Viewing Dev Environments for your space](spaces-devenv-view.md)
+ [Editing a Dev Environment for your space](spaces-devenv-edit.md)
+ [Stopping a Dev Environment for your space](spaces-devenv-stop.md)
+ [Deleting a Dev Environment for your space](spaces-devenv-delete.md)
# Viewing Dev Environments for your space
You can view the type, status, and details for all Dev Environments in your space. For more information about creating and running Dev Environments, see [Creating a Dev Environment](devenvironment-create.md).
You must have the **Space administrator** role to view this page and to manage Dev Environments at the space level.
**To view Dev Environments in your space**
1. Open the CodeCatalyst console at [https://codecatalyst.aws/](https://codecatalyst.aws/).
1. Navigate to your CodeCatalyst space.
**Tip**
If you belong to more than one space, choose a space in the top navigation bar.
1. Choose **Settings**, and then choose **Dev Environments**.
The page lists all Dev Environments in your space. You can view the **Resource** name, the resource **alias** if applicable, the type of **IDE**, the default or configured **Compute** and **Storage**, and the configured **Timeout** for each Dev Environment.
# Editing a Dev Environment for your space
You can edit the configuration for a Dev Environment, such as the configured length of timeout, if any, for an idle Dev Environment to stop running. For more information about editing a Dev Environment, see [Editing a Dev Environment](devenvironment-edit.md).
You must have the **Space administrator** role to view this page and to manage Dev Environments at the space level.
**To edit Dev Environments in your space**
1. Open the CodeCatalyst console at [https://codecatalyst.aws/](https://codecatalyst.aws/).
1. Navigate to your CodeCatalyst space.
**Tip**
If you belong to more than one space, choose a space in the top navigation bar.
1. Choose **Settings**, and then choose **Dev Environments**.
1. Choose the selector next to the Dev Environment you want to manage. Choose **Edit**.
1. Make the changes you want to the compute or inactivity timeout for the Dev Environment.
1. Choose **Save**.
# Stopping a Dev Environment for your space
You can stop a running Dev Environment before it becomes idle if the Dev Environment is configured to have a timeout. Otherwise, a Dev Environment with an elapsed timeout will already be stopped. For more information about stopping a Dev Environment, see [Stopping a Dev Environment](devenvironment-stop.md).
You must have the **Space administrator** role to view this page and to manage Dev Environments at the space level.
**To stop a Dev Environments in your space**
1. Open the CodeCatalyst console at [https://codecatalyst.aws/](https://codecatalyst.aws/).
1. Navigate to your CodeCatalyst space.
**Tip**
If you belong to more than one space, choose a space in the top navigation bar.
1. Choose **Settings**, and then choose **Dev Environments**.
1. Choose the selector next to the Dev Environment you want to manage. Choose **Stop**.
# Deleting a Dev Environment for your space
You can delete a Dev Environment that is no longer needed or that no longer has an owner. For more information about considerations for deleting a Dev Environment, see [Deleting a Dev Environment](devenvironment-delete.md).
You must have the **Space administrator** role to view this page and to manage Dev Environments at the space level.
**To delete Dev Environments in your space**
1. Open the CodeCatalyst console at [https://codecatalyst.aws/](https://codecatalyst.aws/).
1. Navigate to your CodeCatalyst space.
**Tip**
If you belong to more than one space, choose a space in the top navigation bar.
1. Choose **Settings**, and then choose **Dev Environments**.
1. Choose the selector next to the Dev Environment you want to manage. Choose **Delete**. To confirm, type `delete`, and then choose **Delete**.