You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our setup, we need to set VPC endpoints for aws ssm agent, and not pass all the communication via proxy. It will be nice, when there will be possible to set vpc endpointf for ssm agent / push own content of amazon-ssm-agent.json using bottlerocket settings.
The text was updated successfully, but these errors were encountered:
Hey @rubroboletus - interesting challenge here. This may take some research to figure out a good way to support this use case.
The SSM agent runs in the control host container. There would need to be a setting that could be provided in the user data that could be passed through to this host container, and something there that would need to read that value and get it written into the SSM agent config file. And if it can't do that before the agent starts, it would also need to restart the control container.
Technically all possible, but unfortunately not something I can just give you a script to get working for you right away.
Image I'm using:
Issue or Feature Request:
In our setup, we need to set VPC endpoints for aws ssm agent, and not pass all the communication via proxy. It will be nice, when there will be possible to set vpc endpointf for ssm agent / push own content of amazon-ssm-agent.json using bottlerocket settings.
The text was updated successfully, but these errors were encountered: