Importing the Anjuna Docker images to AWS

In the previous section, you created an AWS EKS cluster. For the preferred way to specify the docker images that should be loaded in the AWS cluster, you will use ECR (or Amazon Elastic Container Registry).

In this section, you will upload the Anjuna Nitro Kubernetes tools to AWS ECR so that the EKS cluster can use those tools.

From the directory to which you extracted the downloaded package, run the build-anjuna-docker-images.sh script:

$ ./build-anjuna-docker-images.sh

This script builds the docker images from their sources (located in ./docker/specs) - allowing you to control the base image, if needed, to align it to your organization standards.

Confirm that the docker images were correctly imported by running the following command:

$ docker images

This should show the following images:

REPOSITORY              TAG           IMAGE ID         CREATED           SIZE
anjuna-device-manager   1.29.0001     ecf3ca0f45b0     41 seconds ago    19.4MB
anjuna-nitro-launcher   1.29.0001     62b682bd707a     44 seconds ago    832MB
anjuna-nitro-webhook    1.29.0001     dbfaa3fb38b5     15 seconds ago    85.5MB

You can now push the images to ECR:

$ ./anjuna-k8s.sh --push-images-ecr

This command will automatically create the ECR repositories for the Anjuna Nitro Kubernetes containers (anjuna-nitro-webhook and anjuna-nitro-launcher).

Congratulations! Now that the Anjuna Nitro Kubernetes containers have been pushed to AWS ECR, your AWS EKS cluster can be configured to deploy those containers, which are responsible for automatically identifying and configuring Pods that are supposed to run in an AWS Nitro Enclave.