amazon-ssm-agent
amazon-ssm-agent copied to clipboard
An agent to enable remote management of your EC2 instances, on-premises servers, or virtual machines (VMs).
Add build option for FreeBSD 386 os/architecture combination Update the README.md accordingly By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under...
*Issue #, if available:* *Description of changes:* When a proxy server is specified in Windows without a scheme restriction SSM agent should use it for both http and https calls....
## *Issue #, if available:* None ## *Description of changes:* ### Fixing Bounds Checking Logic There is a small bug in the AgentMessage. As exampled below, when checking bounds on...
*Issue #, if available:* *Description of changes:* The Amazon SSM Agent should be started after networking and dns available and should not start until after cloud-init has finished to prevent...
Hi Team, I am using the official Ubuntu 24.04 AMI with ssm agent 3.3.131.0 pre-installed with snap. But it comes with an error: ``` snap.amazon-ssm-agent.amazon-ssm-agent.service - Service for snap application...
In some cases, our on-premise hosts boot up without internet connectivity. And once the SSM agent enters hibernate mode, it becomes increasingly harder to make it resume back to active...
fixes #604 *Description of changes:* refactor start and stop agent to not rely on $PSCulture en-US By submitting this pull request, I confirm that you can use, modify, copy, and...
When booting an OnPremise system, Ubuntu 22.04 + Raspberry Pi4, after having been offline for atleast 30 minutes I get the following error in the Agent log: Agent version: 3.3.1611.0,...
I setup Amazon SSM connection on a Greengrass Device using a WiFi connection. When disabled WiFi and enabled a cellular connection, I get the error: `ERROR [ssm-agent-worker] [HealthCheck] error when...
When using start-session, the connection will fail with a broken pipe if there is no input or output for 60 seconds. ```bash Cannot perform start session: write tcp 1.2.3.4:45678->100.99.98.97:443: write:...