> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/getting-started/quick-start-guide/fcp-client-installation-and-environment-configuration.md).

# FCP Client Installation and Environment Configuration

Access the FCP client installation guide and configure your local environment for Rhino FCP.

Use this page to install the FCP client and prepare your local environment.

## Install the required dependencies

{% stepper %}
{% step %}
Install these dependencies in your local development environment before you push code to ECR:

* [Docker](https://docs.docker.com/engine/install/)
* [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
* [AWS ECR Credential Helper](https://github.com/awslabs/amazon-ecr-credential-helper)
  {% endstep %}

{% step %}
Make sure the ECR Credential Helper is installed and configured correctly.
{% endstep %}

{% step %}
Run this command and confirm the version is at least `0.7.0`.

```bash
docker-credential-ecr-login -v
```

{% endstep %}

{% step %}
If the version is too old, the command fails, or nothing happens, reinstall the helper.
{% endstep %}

{% step %}
Download the latest executable for your platform from [the GitHub releases page](https://github.com/awslabs/amazon-ecr-credential-helper/releases).
{% endstep %}

{% step %}
Make the executable runnable.

```bash
chmod +x ./docker-credential-ecr-login
```

{% endstep %}

{% step %}
Copy it to a location on your `PATH`, such as `/usr/local/bin/`.
{% endstep %}

{% step %}
If needed, change the owner.

```bash
sudo chown root:root /usr/local/bin/docker-credential-ecr-login
```

{% endstep %}

{% step %}
Edit `~/.docker/config.json` and add `"credsStore": "ecr-login"` at the top level.

If the file does not exist or is empty, create it with this content:

```json
{
  "credsStore": "ecr-login"
}
```

{% endstep %}
{% endstepper %}

For more detail, see [Amazon ECR Docker Credential Helper configuration](https://github.com/awslabs/amazon-ecr-credential-helper#configuration).

## Open your user profile

{% stepper %}
{% step %}
Log in to Rhino FCP. For instructions, see [Log in to Rhino FCP](/getting-started/quick-start-guide/log-in-to-rhino-fcp.md)**.** 
{% endstep %}

{% step %}
In the bottom-left corner, select the circle with your initials or profile image.
{% endstep %}

{% step %}
This opens your user profile.
{% endstep %}
{% endstepper %}

## Retrieve your SFTP and ECR credentials

In your user profile, you can find:

* **Rhino Client IP Address** — use this as your SFTP server name or IP address.
* **SFTP credentials** — select **Reveal Credentials** to view your SFTP username and password.
* **ECR credentials** — select **Reveal Credentials** to view your ECR access key ID and secret access key.
* **Workgroup ECR repository** — use this as your ECR workgroup.

If any credentials are missing, contact <support@rhinofcp.com>.

## Configure AWS CLI for ECR access

{% stepper %}
{% step %}
Open a terminal and run:

```bash
aws configure
```

{% endstep %}

{% step %}
Enter these values when prompted:

```bash
aws configure
AWS Access Key ID [None]: YOUR_AWS_ACCESS_KEY_ID
AWS Secret Access Key [None]: YOUR_AWS_SECRET_ACCESS_KEY
Default region name [None]: us-east-1
Default output format [None]: json
```

Use these values:

* **AWS Access Key ID** — the access key ID from your FCP profile
* **AWS Secret Access Key** — the secret access key from your FCP profile
* **Default region name** — `us-east-1`
* **Default output format** — `json`
  {% endstep %}
  {% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rhinofcp.com/getting-started/quick-start-guide/fcp-client-installation-and-environment-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.