> For the complete documentation index, see [llms.txt](https://docs.akamas.io/akamas-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akamas.io/akamas-docs/3.2.0/installing-akamas/docker/install-the-akamas-server/online-installation-mode/online-installation-behind-a-proxy-server.md).

# Online installation behind a Proxy server

This section describes how to setup an Akamas Server behind a proxy server and to allow Docker to connect to the Akamas repository on AWS ECR.

### Configure Docker daemon <a href="#proxysetup-dockerdaemon" id="proxysetup-dockerdaemon"></a>

First, create the `/etc/systemd/system/docker.service.d` directory if it does not already exists. Then create or update the `/etc/systemd/system/docker.service.d/http-proxy.conf` file with the variables listed below, taking care of replacing `<PROXY>` with the address and port (and credentials if needed) of your target proxy server:

{% code lineNumbers="true" %}

```
[Service]
Environment="HTTP_PROXY=<PROXY>"
Environment="HTTPS_PROXY=<PROXY>"
```

{% endcode %}

Once configured, flush the changes and restart Docker with the following commands:

```bash
sudo systemctl daemon-reload
sudo systemctl restart docker
```

For more details, refer to the official documentation page: [Control Docker with systemd](https://docs.docker.com/config/daemon/systemd/#httphttps-proxy).

### Configure the Akamas containers <a href="#proxysetup-configurethecontainers" id="proxysetup-configurethecontainers"></a>

To allow the Akamas services to connect to addresses outside your intranet, the Docker instance needs to be configured to forward the proxy configuration to the Akamas containers.

Update the `~/.docker/config.json` file adding the following field to the JSON, taking care to replace `<PROXY>` with the address (and credentials if needed) of your target proxy server:

{% code lineNumbers="true" %}

```json
{
  ...
  "proxies": {
    "default": {
      "httpProxy": "<PROXY>",
      "httpsProxy": "<PROXY>",
      "ftpProxy": "<PROXY>",
      "noProxy": "localhost,127.0.0.1,/var/run/docker.sock,database,optimizer,campaign,analyzer,telemetry,log,elasticsearch,metrics,system,license,store,orchestrator,airflow-db,airflow-webserver,kong-database,kong,user-service,keycloak,logstash,kibana,akamas-ui,grafana,prometheus,node-exporter,cadvisor,konga,benchmark"
    }
  }
}
```

{% endcode %}

For more details, refer to the official documentation page: [Configure Docker to use a proxy server](https://docs.docker.com/network/proxy/).

## Run Akamas <a href="#proxysetup-runakamas" id="proxysetup-runakamas"></a>

Set the following variables to configure your working environment, taking care to replace `<PROXY>` with the address (and credentials if needed) of your target proxy server:

```bash
export HTTP_PROXY='<PROXY>'
export HTTPS_PROXY='<PROXY>'
```

Once configured, you can log into the ECR repository through the AWS CLI and start the Akamas services manually.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akamas.io/akamas-docs/3.2.0/installing-akamas/docker/install-the-akamas-server/online-installation-mode/online-installation-behind-a-proxy-server.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.