如果在AWS上有舊的機器要使用SSM Session Manager的話,就必須要自行安裝套件。

所以稍微研究了一下怎麼安裝,這邊僅列出CentOS7以及Ubuntu

CentOS 7

    #Download Package
    $sudo yum install -y https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/linux_amd64/amazon-ssm-agent.rpm

    #Check Status 
    systemctl status amazon-ssm-agent

Ubuntu

Solution One From Package

    #Download Package
    $wget https://s3.amazonaws.com/ec2-downloads-windows/SSMAgent/latest/debian_amd64/amazon-ssm-agent.deb

    #Install Package
    $dpkg -i amazon-ssm-agent.deb

    #Check Running Status On Ubuntu 18.04
    $systemctl status amazon-ssm-agent

    #Start SSM Process On Ubuntu 18.04
    $systemctl start amazon-ssm-agent

    #Check Running Status On Ubuntu 16.04 & 14.04
    $status amazon-ssm-agent

    #Start SSM Process On Ubuntu 16.04 & 14.04
    $start amazon-ssm-agent

Solution Two From Snap

    #Install SSM-Agent
    $snap install amazon-ssm-agent --classic

    #Check Running 
    $snap list amazon-ssm-agent

    #Start SSM-Agent Process
    $snap start amazon-ssm-agent

    #Check Status
    $snap services amazon-ssm-agent

Use Proxy With SSM Session

Upstar

    $vim /etc/init.d/amazon-ssm-agent.override

    #Put These In Line:

    env http_proxy=http://hostname:port
    env https_proxy=http(s)://hostname:port
    env no_proxy=169.254.169.254

Restart Service

    $stop amazon-ssm-agent
    $start amazon-ssm-agent

systemd

    $systemctl edit amazon-ssm-agent

    #Add These
    $env http_proxy=http://hostname:port
    $env https_proxy=http(s)://hostname:port
    $env no_proxy=169.254.169.254

Restart Service

    systemctl stop amazon-ssm-agent
    systemctl start amazon-ssm-agent

After few mins, you can see instance on SSM Start Session Console

Caution:

–==Must Assign SSM Role to Instance==–

–==Must Assign SSM Role to Instance==–

–==Must Assign SSM Role to Instance==–

參考網址