You must have an AWS account with the Required IAM permissions:<\/p>\n
- \n
- SSM<\/strong> (Systems Manager), EC2, and IAM permissions with “AmazonSSMManagedInstanceCore” Policy.<\/li>\n
- AWS SSM Agent<\/strong> must be installed and operational on Azure VMs.<\/li>\n<\/ul>\n
Solution Architecture Diagram:<\/strong><\/p>\n
The below diagram illustrates the architecture of this configuration.<\/p>\n
![\"Architecture-Diagram\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/08\/Architecture-Diagram-1-1024x686.png\")
Architecture-Diagram<\/p><\/div>\n
Step-by-Step Procedure:<\/strong><\/p>\n
Step 1:<\/strong> Log in to the AWS and navigate to the AWS System Manager service<\/p>\n
https:\/\/console.aws.amazon.com\/systems-manager\/home<\/p>\n
Step 2:<\/strong> Click the Hybrid Activations option under Node Tools<\/p>\n
![\"Click-on-Hybrid-Activations\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/08\/Click-on-Hybrid-Activations.png\")
Click-on-Hybrid-Activations<\/p><\/div>\n
Step 3:<\/strong> Click on “Create activation” and provide the mandatory fields-<\/p>\n
![\"Create-activation\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/08\/Create-activation-1-1024x484.png\")
Create-activation<\/p><\/div>\n
Note:<\/strong> Note: In the “Activation Expiry Date” field, you are instructing AWS that the hybrid activation code should expire within the number of days you enter here. The highest value you can use is 30 days. Once this time limit is reached, if you need to add more VMs (servers), you will have to create a new activation code.<\/p>\n
Step 4:<\/strong> Once you filled in the details, when you press Create Activation, you will be provided with the\u00a0 Activation-Code and Activation-ID. Please note these points somewhere you will require them later.<\/p>\n
![\"Activation_Details\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/08\/Activation_Details-1024x127.png\")
Activation_Details<\/p><\/div>\n
Step 5:<\/strong> SSH the server on your Azure cloud that you want to integrate with the AWS SSM.<\/p>\n
Step 6:<\/strong> Install SSM agent if not already installed. Below are the installation commands for SSM agent.<\/p>\n
![\"Commands\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/09\/Screenshot-from-2025-09-01-12-56-50.png\")
Commands<\/p><\/div>\n
Step 7:<\/strong> Now, run the below commands in order to set up the connectivity between AWS SSM and the Azure VM.
\nNote-<\/strong> Replace activation-code and activation-id with the ones you copied in Step 4.<\/p>\n![\"Commands\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/09\/Screenshot-from-2025-09-01-12-58-32.png\")
Commands<\/p><\/div>\n
Step 8:<\/strong> Now you can confirm that your server is registered in Fleet Manager.<\/p>\n
![\"Server_Registered\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/08\/Server_Registered-1024x249.png\")
Server_Registered.<\/p><\/div>\n
Step 9<\/strong>: If you click the Node ID, you can validate your server information-<\/p>\n
![\"Server_Details\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/08\/Server_Details-1024x378.png\")
Server_Details<\/p><\/div>\n
Step 10:<\/strong> Once you’ve verified the information, you access your server.<\/p>\n
![\"Start_Terminal_Session\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/08\/Start_Terminal_Session-1024x141.png\")
Start_Terminal_Session<\/p><\/div>\n
![\"Server\"](\"https:\/\/www.tothenew.com\/blog\/wp-ttn-blog\/uploads\/2025\/08\/Server-1024x189.png\")
Server<\/p><\/div>\n
Conclusion:<\/h2>\n
Whenever we have multiple cloud architecture and want to manage servers from one place, we can enable Hybrid Activation across servers. We can perform operations on many servers from a single point using this feature, and it is supportive of security, simplifies access control, and makes processes more efficient.<\/p>\n
If you have any questions for this article, you may comment below.<\/p>\n
Thank You.<\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction AWS System Manager (SSM) is a secure, end-to-end process to be used for managing servers on AWS, on-premises, and on any other cloud platform. We can manage our servers from one central point using the SSM. Prerequisites: You must have an AWS account with the Required IAM permissions: SSM (Systems Manager), EC2, and IAM […]<\/p>\n","protected":false},"author":1199,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":91,"footnotes":""},"categories":[5877],"tags":[1711,1586,7475,7895,7894],"class_list":["post-74503","post","type-post","status-publish","format-standard","hentry","category-msp","tag-audit","tag-ec2","tag-multicloud","tag-patching","tag-ssm"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
- AWS SSM Agent<\/strong> must be installed and operational on Azure VMs.<\/li>\n<\/ul>\n