Configuring your Environment

Installing the Dependencies

1. The following dependencies must be installed into your local development environment in order to be able to push code to the ECR:
   • Docker
   • AWS CLI
   • AWS ECR Credential Helper
2. Additionally, you will need to follow the steps below to ensure the ECR Credential Helper is properly installed and configured:
3. Ensure that the following command can run and its version is at least 0.7.0.

> docker-credential-ecr-login -v

4. If the version is too old, an error is displayed, or nothing at all you will need to follow steps 4 - 9 to uninstall the AWS ECR Credentials Helper and install the latest version:
5. Download the most recent executable for your platform from the GitHub releases page
6. Make it executable:

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

7. Copy it to an appropriate location on your PATH (e.g. /usr/local/bin/)
8. If needed, change its owner:

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

9. Edit the ~/.docker/config.json file and add "credsStore": "ecr-login" to the top-level JSON, as shown below.  If ~/.docker/config.json does not exist or is empty, create the file and add the following:

{
    "credsStore": "ecr-login"
}

For more details, refer to this section of the Amazon ECR Docker Credential Helper GitHub documentation.

Logging into the Rhino FCP

To log into the Rhino FCP, navigate to https://dashboard.rhinohealth.com/login in your web browser.  There are currently three different ways to login to the FCP:

1. Username & Password
   • If this is your first time logging into the platform, you will be required to change your password from the temporary one sent to you during onboarding
   • Note: If you have not received your credentials or are not prompted to change your password, please contact support@rhinohealth.com.
2. Google Single Sign-on (SSO)
   • Click the button and follow the prompts to log in with your Google credentials
3. Azure Single Sign-on (SSO)
   • Click the button and follow the prompts to log in with your Azure credentials

If you encounter any issues while attempting to log in, please contact support@rhinohealth.com.

Navigating to your User Profile

1. Log into the Rhino Health Federated Computing Platform, https://dashboard.rhinohealth.com/login
2. In the bottom left corner, you will see a circle with either your initials or your picture in it, click it to take you to your user profile.

Retrieving your SFTP & ECR Credentials

1. Within your user profile, you will find:
   • Rhino Client IP Address which is your SFTP Server Name/IP Address
   • SFTP Section, click Reveal Credentials to find your:
     • SFTP Username:
       • Your SFTP Username will be in the top box, you can either copy it from the box or press the copy button to the left of the credential
     • SFTP Password:
       • Your SFTP Password will be in the bottom box, you can either copy it from the box or press the copy button to the left of the credential
   • ECR Section, click Reveal Credentials to find your:
     • ECR Access Key ID:
       • Your ECR Access Key ID will be in the top box, you can either copy it from the box or press the copy button to the left of the credential
     • ECR Secret Access Key:
       • Click the Reveal Credentials button next to the ECR label
       • Your ECR Secret Access Key will be in the bottom box, you can either copy it from the box or press the copy button to the left of the credential
   • Workgroup ECR repository which is your ECR Workgroup

If any of your credentials are missing, please contact support@rhinohealth.com.

Configuring your AWS CLI to be able to Push to your ECR

1. Open a terminal or command prompt on your respective operating system. Type in the command 

aws configure

1. The code block below shows what you will need to enter at each step of the prompt.

> 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 

• As a reminder of what each value should be:
  • AWS Access Key ID - The AWS Access Key ID from your FCP profile
  • AWS Secret Access Key - The AWS Secret Access Key from your FCP profile
  • Default region name - us-east-1
  • Default output format - json