AWS Fleet Deployment: Cloudamize Agent Installation via SSM Run Command

Overview

This Knowledge Base article provides a step-by-step guide on how to perform mass, non-interactive installations of the Cloudamize Agent across your EC2 fleet using AWS Systems Manager (SSM) Run Command.

AWS Systems Manager Run Command allows you to remotely and securely manage the configuration of your managed instances without requiring direct SSH/RDP access, bastion hosts, or open inbound ports. By utilizing SSM Run Command alongside Cloudamize's silent installation scripts, administrators can rapidly deploy the Cloudamize inventory agent across hundreds of Linux and Windows EC2 instances simultaneously.

Note: The AWS Systems Manager Run Command steps in this article are provided as guidance for using third-party deployment tooling with the Cloudamize Agent. Cloudamize has not validated or tested these AWS deployment workflows end to end. Review and test the process in your own AWS environment before using it for production deployments.

Prerequisites

Before deploying the Cloudamize Agent across your AWS fleet, verify that all target nodes comply with the official Cloudamize Agent Installation Prerequisites and meet the following AWS-specific requirements:

Official Cloudamize Prerequisites: Review OS compatibility, system resource requirements, and regional proxy/endpoint settings in the Agent Installation Prerequisites KB.
Network & Outbound Access: Target instances must have outbound access on TCP Port 443 directly or via proxy to your assigned Cloudamize regional endpoint:
- US Region: am.cloudamize.com
- EU Region: am-de.cloudamize.com
- UAE Region: am-ae.cloudamize.com

SSM Agent: Target EC2 instances must have amazon-ssm-agent installed and running (pre-installed on most standard AWS AMIs).
IAM Permissions: Target EC2 instances must have an IAM role attached with the AmazonSSMManagedInstanceCore policy attached.
Network Access: Target instances must have outbound HTTPS access on TCP Port 443 to am.cloudamize.com (or your regional Cloudamize endpoint).
Customer Key: Ensure you have your unique Cloudamize Customer Key from the Cloudamize Console.

Step-by-Step Installation Instructions

Step 1: Open AWS Systems Manager Run Command

Log in to the AWS Management Console.
Search for and select Systems Manager.
In the left navigation menu under Node Management, choose Run Command.
Click the Run command button at the top right of the page.

Step 2: Select the Execution Document

In the Command document search box:

For Linux instances, search and select: AWS-RunShellScript
For Windows instances, search and select: AWS-RunPowerShellScript

Step 3: Configure Command Parameters

Important Note on Region Endpoints & Customer Keys:
The installer URL domain and custkey / customerkey parameters depend on the specific region where your Cloudamize assessment is provisioned (e.g., US, EU, or UAE) and your unique account credentials. Always copy the exact command and key directly from your Cloudamize Console.

In the Command parameters box, paste the non-interactive installation script matching your target operating system. Replace <YOUR_CLOUDAMIZE_CUSTOMER_KEY> with your actual key.

For Linux Fleet (`AWS-RunShellScript`):

#!/bin/bash
# Download and execute official Cloudamize Agent Installer
sh <(curl 'https://am.cloudamize.com/cxf/downloadFileV3?custkey=<YOUR_CUSTOMER_KEY>&filename=installCloudamizeAgentV2.sh' -L)

(Replace am.cloudamize.com with your regional endpoint domain if using EU or UAE, and replace YOUR_CUSTOMER_KEY with your actual Customer Key).

For Windows Fleet (`AWS-RunPowerShellScript`):

#PowerShel
# Download and silently install Cloudamize Agent MSI
$msiPath = "$env:TEMP\cloudamizeAgent.msi"
Invoke-WebRequest -Uri "https://am.cloudamize.com/cxf/downloadFileV3?custkey=<YOUR_CUSTOMER_KEY>&filename=cloudamizeAgent.msi" -OutFile $msiPath
msiexec /i $msiPath customerkey=YOUR_CUSTOMER_KEY /

(Replace am.cloudamize.com with your regional endpoint domain if using EU or UAE, and replace YOUR_CUSTOMER_KEY with your actual Customer Key).

Step 4: Target Instances

Under the Targets section, select how you want to target your EC2 fleet:

Specify instance tags: (Recommended for scale) Target instances using tag key-value pairs (e.g., Key: Environment, Value: Production).
Choose instances manually: Manually select specific EC2 instances from the list.
Choose a resource group: Target instances belonging to a specific AWS Resource Group.

Step 5: Output Options & Execution

(Optional) Under Output options, choose to write standard output and error logs to an S3 Bucket or CloudWatch Logs group for auditing.
Click Run to initiate deployment across the selected fleet.

Verification & Monitoring

Once execution completes, verify the installation status across your targets:

In the SSM Console, navigate to Run Command and select the command execution ID to view the per-instance execution status (Success or Failed).
Verify agent services on target nodes:
- Linux: Run systemctl status cloudamize-agent
- Windows: Check services for Cloudamize Agent Service
Log in to the Cloudamize Console and confirm that the newly registered instances appear in your node list.

Frequently Asked Questions

Why are some instances not showing up in the target list?

Instances must have the SSM Agent active and possess an IAM role with AmazonSSMManagedInstanceCore attached. If offline or missing permissions, they will not appear as SSM managed nodes.

Can I automate this for newly launched EC2 instances?

Yes. To automatically enforce Cloudamize Agent installation on new or auto-scaled instances, use AWS SSM State Manager instead of Run Command to apply the policy on an automated schedule or event trigger.

Do I need SSH/RDP ports open for this installation?

No. AWS SSM communicates over outbound HTTPS (Port 443) to AWS SSM endpoints. No inbound SSH or RDP ports need to be open on your security groups.

If you have any queries, please get in touch with the helpdesk via our Helpdesk Portal or by email at helpdesk@cloudamize.com.