- 最新
- 最多得票
- 最多評論
You should be able to login to the Test instance using the Local credentials of your source server which is replicating into AWS MGN service.
Once you are logged into the instance, I would suggest running "ssm-cli" diagnostic tool (1) and reviewing the SSM agent logs to identify the reason for SSM issue on the Test instance
SSM-CLI Tool:
(-) Windows : & 'C:\Program Files\Amazon\SSM\ssm-cli.exe' get-diagnostics --output table
(-) Linux : ssm-cli get-diagnostics --output table
SSM Agent logs:
(-) Windows : %PROGRAMDATA%\Amazon\SSM\Logs\
(-) Linux : /var/log/amazon/ssm/
Additionally, please also check article (2) to troubleshoot SSM issue.
References:
(1) https://docs.aws.amazon.com/systems-manager/latest/userguide/ssm-cli.html
(2) Troubleshoot "ConnectionLost" status - https://repost.aws/knowledge-center/systems-manager-ec2-instance-not-appear
相關內容
- AWS 官方已更新 1 年前
Also, you need to either have VPC endpoint created for SSM service if you want to connect via private link or have Internet connectivity to reach SSM public endpoint.