Skip to content

Commit 3556183

Browse files
authored
update intro and examples (#19633)
1 parent 78255c1 commit 3556183

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

content/security/for-admins/registry-access-management.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,19 @@ aliases:
1010

1111
> **Note**
1212
>
13-
> Registry Access Management is available to [Docker Business](../../subscription/core-subscription/details.md) customers only.
13+
> Registry Access Management is available to [Docker Business](../../subscription/core-subscription/details.md) customers only.
1414
1515
With Registry Access Management (RAM), administrators can ensure that their developers using Docker Desktop only access allowed registries. This is done through the Registry Access Management dashboard in Docker Hub or the Docker Admin Console.
1616

17-
Registry Access Management supports both cloud and on-prem registries. Example registries administrators can allow include:
17+
Registry Access Management supports both cloud and on-prem registries. This feature operates at the DNS level and therefore is compatible with all registries. You can add any hostname or domain name you’d like to include in the list of allowed registries. However, if the registry redirects to other domains such as `s3.amazon.com`, then you must add those domains to the list.
18+
19+
Example registries administrators can allow include:
20+
1821
- Docker Hub. This is enabled by default.
1922
- Amazon ECR
2023
- GitHub Container Registry
2124
- Google Container Registry
25+
- GitLab Container Registry
2226
- Nexus
2327
- Artifactory
2428

0 commit comments

Comments
 (0)