This article explains how to deploy the Flexera Kubernetes Resource Monitor (KRM) Agent using the public AWS Elastic Container Registry (ECR) image. This approach allows you to pull container images directly from AWS rather than relying on a private container registry.
It is intended for system administrators or DevOps engineers who are installing the KRM Agent in a Kubernetes environment using either the install.sh script or a Helm chart.
The steps below will guide you through:
- Meeting the necessary prerequisites (AWS CLI setup and IAM access)
- Authenticating to Flexera’s public AWS ECR registry
- Running the KRM Agent installer using the public image
- Notes on using Helm as an alternative installation method
For general installation instructions, see the KRM Agent Installation Guide
Prerequisites
Before deploying the agent, ensure the following:
- AWS CLI is installed on the system managing your Kubernetes cluster.
How to install AWS CLI - An IAM user is configured with the following permission:
AmazonElasticContainerRegistryPublicReadOnly
- On the server where you're deploying the KRM Agent, run the following command to configure your AWS credentials:
aws configure
You will be prompted to enter your Access Key ID and Secret Access Key. For example:
$ aws configure
AWS Access Key ID [None]: YOUR_ACCESS_KEY_ID
AWS Secret Access Key [None]: YOUR_SECRET_ACCESS_KEY
Install the KRM Agent using the public ECR image
- Authenticate to the public AWS ECR registry:
aws ecr-public get-login-password --region us-east-1 | \
docker login --username AWS --password-stdin public.ecr.aws
- After successfully authenticating to the public AWS ECR registry, run the install script and specify the registry domain:
./install.sh --registry public.ecr.aws
This instructs the script to pull the KRM Agent image from Flexera’s public repository at
public.ecr.aws/flexera/krm.
Using Helm instead of install.sh
If you're using Helm to install the KRM Agent:
- Follow the same prerequisites listed above (AWS CLI installed and IAM permissions configured).
- Refer to the Helm-specific installation guide here:
KRM Helm Configuration Options
Related Articles
Install the Flexera KRM Agent using a custom namespace 9Number of Views Deploy SVM Agent with VDI Images safely 15Number of Views Prevent FlexNet inventory agent AgentID collisions when cloning virtual machines 11Number of Views Fix "ndtrack.exe is not marked for installation" error when installing the FlexNet Inventory Agent on Windows 41Number of Views Configure CheckCertificateRevocation and CheckServerCertificate during Flexera Kubernetes Agent Helm chart installation 92Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago