Beka i-proxy ye-SSM Agent kusivisi sayo sangempela se-systemd
Sebenzisa i-drop-in ye-agent kanye nokweqa i-metadata, bese uhlukanisa ukuxhumana kwayo nesicelo se-curl sesigaba se-Image Builder.
Qala ukuhlonza umthumeli ohlulekayo: ukuxhumana kwe-SSM Agent noma ukulandwa ngaphakathi kwesigaba se-Image Builder. Ukukhipha nge-SSH shell akukubuyekezi i-agent esebenzayo.
Kuyunithi evamile ye-amazon-ssm-agent systemd, hlanganisa i-drop-in ebhaliwe ku-/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"Indawo yokugcina ye-HTTP ingathwala izindawo ze-HTTPS. Uma i-agent ivunyelwe ukusebenzisa umlamuli womphakathi ezindaweni zayo zokugcina ze-AWS zomphakathi, uhlu lwe-proxy ye-HTTP lunikeza abazongenela kulezi zinhlelo zokuxhumana; gcina ukweqa kwe-metadata. Gcina i-169.254.169.254 iqondile kwi-metadata ye-instance; i-AWS ibhala futhi i-[fd00:ec2::254] endaweni yokugcina ye-metadata ye-IPv6.
Layisha kabusha i-systemd bese uqala kabusha iyunithi yangempela ye-agent ngemuva koshintsho. Ukupakisha kwe-snap kwe-Ubuntu kusebenzisa enye indawo yeyunithi/drop-in, ngakho hambisana nokufakwa.
Uma i-agent isebenza kodwa i-curl yesigaba ihluleka, nikeza indawo yezemvelo yalowo myalo. Izinhlamvu ezincane i-http_proxy zibalulekile ku-curl; ukuthengiselana okuphumelelayo kwe-agent akufakazeli lezo zokufaka zesicelo sengane.