Skip to content

Commit

Permalink
Adjust heading levels on amazon-ecr page (#770)
Browse files Browse the repository at this point in the history
adjust heading levels on amazon-ecr page
  • Loading branch information
bgonp authored Jun 24, 2024
1 parent 48b5b95 commit cd53d63
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions src/content/admin/registry-credentials/amazon-ecr.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,15 +11,15 @@ It's recommended that you have the [AWS CLI installed](https://docs.aws.amazon.c

ECR credentials can be configured with either static credentials belonging to an IAM user or using OIDC federation to assume an IAM Role via Web Identity.

# Using IAM User credentials
## Using IAM User credentials

The steps to configure your private ECR with Okteto are:

- Create a user with access to your private ECR
- Retrieve the user credentials
- Configure the credentials in Okteto

## Step 1: Create a user with access to your private ECR
### Step 1: Create a user with access to your private ECR

Create IAM user with the [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/iam/create-user.html) by executing:

Expand All @@ -33,7 +33,7 @@ aws iam attach-user-policy \
--user-name private-registry-user
```

## Step 2: Retrieve the user credentials
### Step 2: Retrieve the user credentials

Once we have the `User` created, we need to retrieve their credentials.
Create IAM user access key with the [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/iam/create-access-key.html) by executing:
Expand All @@ -56,7 +56,7 @@ aws iam create-access-key --user-name private-registry-user

Remember the value of `AccessKeyId` and `SecretAccessKey`. You will need them in the next step.

## Step 3: Configure the credentials in Okteto
### Step 3: Configure the credentials in Okteto

Add the following registry credentials to the [Admin Registry Credentials view](index.mdx#add-registry-credentials):

Expand All @@ -65,9 +65,9 @@ Add the following registry credentials to the [Admin Registry Credentials view](
- **Username**: `AccessKeyId` from the previous step
- **Password**: `SecretAccessKey` from the previous step

# Using OIDC Federation
## Using OIDC Federation

## Step 1: Create the Identity Provider
### Step 1: Create the Identity Provider

```bash
OIDC_ENDPOINT=https://container.googleapis.com/v1/projects/my-project-12345/locations/us-central1/clusters/development
Expand Down Expand Up @@ -102,7 +102,7 @@ your-okteto-instance.com/your-region
```


## Step 2: Create the Role
### Step 2: Create the Role


First create the role and allow it to access EC2:
Expand Down Expand Up @@ -166,7 +166,7 @@ aws iam attach-role-policy --role-name my-private-registry --policy-arn arn:aws:
If you only need read access you can use `AmazonEC2ContainerRegistryReadOnly` instead.


## Step 3: Configure the credentials in Okteto
### Step 3: Configure the credentials in Okteto

Add the following registry credentials to the [Admin Registry Credentials view](index.mdx#add-registry-credentials):

Expand Down

0 comments on commit cd53d63

Please sign in to comment.