Last updated: 2025-06-24

Setup On-Premise or Non-AWS Target Servers

To manage non-AWS servers with ServerSage, you must first register them as managed instances using AWS Systems Manager Hybrid Activation.

These servers can include:
- On-premise Linux servers
- Cloud-hosted VMs (e.g., GCP, Azure, DigitalOcean)

---

Prerequisites

• Your ServerSage Bastion must already be deployed Set up the Bastion first
• You must have access to an AWS IAM role with AmazonSSMManagedInstanceCore permissions
• Your AWS CLI must be installed and configured locally

---

Steps to Register On-Premise Targets

Create a Hybrid Activation

To register non-AWS servers, you need to create a Hybrid Activation in AWS Systems Manager.
This will generate an activation code and ID that you will use to register your on-premise instances.

To create a hybrid activation, and generate the activation code and ID you can follow the step same as on Bastion setup:

• Create a Hybrid Activation
• Generate the Activation Code and ID
• Activate the Instance

✅ Now your on-premise server has managed instance capabilities through AWS Systems Manager.

Register the On-Premise Target in ServerSage

1. Log in to your ServerSage dashboard.
2. Navigate to the Sidebar section.
3. Choose Bastion.
4. Click on Add Target.
5. Enter the Instance ID and Region you retrieved earlier.

🎉 Your on-premise server is now ready to receive AI-powered instructions from ServerSage.