Configure Systems Manager proxy using Greengrass

Hello,

Thank you for reaching out on re:Post. My name is Tom from AWS Support. I see that we would like to configure Systems Manager proxy from Greengrass programmatically.

After further research, the reason that http_proxy / https_proxy environment variables are not being read from the Greengrass configuration is that these environment variables are not Greegrass variables. These are general Linux environment variables for devices. For a list of supported environment variables from Greengrass, please see the reference here [1].

Reading through your use case, it is possible to create a customized component [2] to pull the http_proxy / https_proxy environment variables details from a source (such as a text file from a S3 bucket) and then use code to run the commands for deployment.

Alternatively, if the http_proxy / https_proxy environment variables are static, it can be hard coded into the component's config and use code to pull config for updating http/https_proxy environment.

If the devices are accessible through System Manager, once the System Manager Agent is installed, it could be possible to use run command [3] to update on its proxy settings and restart the device.

I hope the above information helps. Have a nice day.

Links and References

[1] Component environment variable reference - https://docs.aws.amazon.com/greengrass/v2/developerguide/component-environment-variables.html

[2] Create AWS IoT Greengrass components - https://docs.aws.amazon.com/greengrass/v2/developerguide/create-components.html

[3] AWS System Manager Run Command - https://docs.aws.amazon.com/systems-manager/latest/userguide/run-command.html