Sanya proxy na SSM Agent a kan ainihin sabis ɗin systemd ɗinsa
Yi amfani da drop-in na agent da kewaye metadata, sannan ka bambanta haɗinsa da buƙatar curl ta ɓangaren Image Builder.
Da farko gano mai aikawa da ya kasa: sadarwar SSM Agent ko saukarwa cikin ɓangaren Image Builder. Fitarwa ta harsashin SSH ba ya sabunta agent ɗin da ke gudana.
Don rukunin systemd na yau da kullum amazon-ssm-agent, haɗa drop-in ɗin da aka rubuta a /etc/systemd/system/amazon-ssm-agent.service.d/override.conf:
[Service]
Environment="http_proxy=http://proxy.example:8080"
Environment="https_proxy=http://proxy.example:8080"
Environment="no_proxy=169.254.169.254"Ƙarshen HTTP na iya ɗaukar wuraren HTTPS. Lokacin da agent zai iya amfani da mai shiga tsakani na jama'a don ƙarshen ayyukan AWS na jama'a, jerin proxy na HTTP yana ba da 'yan takara don waɗannan URL; kiyaye kewaye metadata. Ka riƙe 169.254.169.254 kai tsaye don metadata na instance; AWS kuma yana rubuta [fd00:ec2::254] don ƙarshen metadata na IPv6.
Sake loda systemd kuma sake kunna ainihin rukunin agent bayan canjin. Marufi na snap na Ubuntu yana amfani da wani wuri na rukuni/drop-in, don haka daidaita da shigarwar.
Idan agent ɗin yana aiki amma curl na ɓangaren ya kasa, ka ba da muhallin wannan umarnin. Ƙananan haruffa http_proxy suna da mahimmanci ga curl; ciniki mai nasara na agent ba ya tabbatar da waɗannan shigarwar buƙatar yaro.