> ## Documentation Index
> Fetch the complete documentation index at: https://www.qovery.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Container Registry
> Manage container registries for your organization
## Overview
This section allows you to define the container registries available within your organization. Once configured, only images stored in these registered container registries will be allowed to be deployed on your clusters.
By connecting container registries to your organization, you can deploy applications using images from these registries across all your projects and environments.
Container registries configured here apply to the entire organization and are available for all projects.
## Accessing Container Registry Settings
To manage container registries:
1. Navigate to **Organization Settings** → **Container Registries**
2. You'll see a list of all configured registries
## Supported Registry Types
Qovery supports the following container registry providers:
* **ECR** (AWS Elastic Container Registry)
* **GCP Artifact Registry** (Google Cloud Artifact Registry)
* **Scaleway Container Registry**
* **Docker Hub**
* **GitHub Container Registry (GHCR)**
* **GitHub Enterprise Container Registry**
* **GitLab Container Registry**
* **Public ECR** (AWS Public Elastic Container Registry)
* **Generic Container Registry** (any Docker-compatible registry accessible via `docker login`)
## Create a Container Registry
Press the **Add Registry** button to create a new container registry connection
Choose your registry provider from the dropdown menu
Enter the necessary authentication details based on your registry type.
**Example for AWS ECR:**
* **Registry URL**: `https://.dkr.ecr..amazonaws.com`
* **Region**: AWS region where your ECR is located (e.g., `us-east-1`, `eu-west-1`)
* **Access Key ID**: AWS IAM access key with ECR permissions
* **Secret Access Key**: AWS IAM secret access key
Each registry type requires different configuration fields. The form will adapt based on your selection.
Qovery will automatically test the connection to verify credentials
Click **Save** to add the registry to your organization
Once added, the container registry will be available for all projects and environments in your organization.
## Modify an Existing Registry
To edit a container registry:
1. Locate the registry in the Container Registry list
2. Click the **wheel button** (edit icon) next to the registry
3. Update the registry configuration as needed
4. Click **Save** to apply changes
Updating registry credentials will affect all applications using images from this registry. Ensure new credentials are valid before saving.
## Delete a Container Registry
To remove a container registry:
1. Locate the registry in the Container Registry list
2. Click the **trash button** (delete icon) next to the registry
3. Confirm the deletion
Before deleting a registry, make sure that there are no applications within your organization using images stored in this registry. Deleting a registry may prevent deployments from succeeding.
## Best Practices
Consider creating separate registry connections for different environments (development, staging, production) for better security and access management.
Name registries clearly to indicate their purpose:
* `aws-ecr-production-us-east-1`
* `docker-hub-public-images`
* `gcr-staging-europe`
Periodically rotate registry credentials for security:
1. Create new credentials in your registry provider
2. Update the registry configuration in Qovery
3. Test with a deployment
4. Remove old credentials from the provider
## Related Resources
Manage cloud provider credentials
Deploy applications using container images
Configure Git repository access
Manage Helm chart repositories