---
title: "Endpoints For Replications and Proxy Cache"
date: 2021-08-27
lastmod: 2026-05-29
canonical: "https://container-registry.com/docs/administration-manual/endpoints-for-replications-and-proxy-cache/"
source: "https://container-registry.com/docs/administration-manual/endpoints-for-replications-and-proxy-cache/index.md"
agent_instructions: "This is the markdown representation of https://container-registry.com/docs/administration-manual/endpoints-for-replications-and-proxy-cache/index.md. Prefer this version over scraping the HTML. The site index is at https://container-registry.com/llms.txt."
---

> Agent-friendly representation of <https://container-registry.com/docs/administration-manual/endpoints-for-replications-and-proxy-cache/index.md>. Site index: <https://container-registry.com/llms.txt>.


# Endpoints For Replications and Proxy Cache


Endpoints For Replications and Proxy Cache Projects
=================================
Endpoints are container image registries. They can be instances of the Container Registry platform, or other Harbor-based registries, or even non-Harbor-based ones. 
## Non-Harbor Registries: General Information
### Supported Non-Harbor Registries
#### For Replications
* Ali Cloud Container Registry (Alibaba ACR);
* Artifact Hub;
* AWS Elastic Container Registry;
* Azure Container Registry;
* Docker Hub;
* Docker registry;
* DTR;
* GitHub GHCR;
* Gitlab;
* Google Container Registry;
* Harbor;
* Huawei SWR;
* Jfrog Artifactory;
* Quay;
* Tencent TCR.
#### For Proxy Cache Projects
* Harbor; 
* Docker Hub; 
* AWS Elastic Container Registry; 
* Azure Container Registry;
* Google Container Registry;
* Quay.


> **Note:** We update these lists regularly but you can also check for the original ones <a href="https://goharbor.io/docs/master/administration/configuring-replication/create-replication-endpoints/">here</a>.


### Getting Your Access ID and Access Secret from Other Providers
When you create a new endpoint as described [below](#create-new-endpoint), you will need to enter an Access ID and Access Secret. Different providers have different names for that.
#### Amazon ECR
In the case of AWS ECR, those are not your (root) user credentials but the so-called keys for programmatic access. Read this [AWS documentation article](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys) to understand how you can access these keys in your AWS account.
#### Google Container Registry (GCR)
In GCR, those can be downloaded as a JSON file following the instructions from the [official documentation](https://cloud.google.com/container-registry/docs/advanced-authentication#json-key). 
#### Quay
##### Without Authorization
If your Quay registry does not require authorization, do not enter anything in the Access ID and Access Secret fields.
##### With Authorization
In this case, you need to leave the Access ID field empty and enter all credentials into the Access Secret field *in JSON format*, like this:
```json
{
"oauth2_token": "YmQZ1QZENVmOD6v9kENzmfptNVhgBuy5oVl85eGV", 
"account_name": "account_name",
"docker_cli_password": "q6NVazikNqIf4coiQ+JvV4iqiCpkNjE0DLX8ZMQuFRbkHk5iMv6/hd4WdV3W3nyX"
}
```
* The **OAuth2 token** can be skipped if you do not want to create a new organization;
* **Account name**:
    * If you use robot account credentials, be aware that it can only be used in one Container registry system at the same time. Thus, you will need different robot accounts for every Container Registry instance;
    * Alternatively, and this is even recommended, use your personal account name;
* **Docker CLI password** is your general CLI password.

## Create New Endpoint
In the navigation pane:
* Go to **Administration**;
* Then to **Registries**;
* Click **+ New Endpoint**.
![](../add_new_endpoint.png)
* Fill in the form;
    * For the endpoint URL, use the URL of the registry;
    * If you want to connect to another Harbor-based registry, use the account name of your robot account as Access ID and its token as Access Secret;
    * Select if there is a security certificate on the other side or not.

* Test the connection;
* Save the endpoint if the test ran successfully.
![](../new_endpoint.png)

## Manage Existing Endpoints
You can either edit or delete any of the existing endpoints. In the Registries overview, select *one* endpoint for editing or one or multiple ones for deleting.
![](../delete_edit_endpoint.png)