AWS Greengrass Proxy Issues

Question

I am attempting to connect and manage a Greengrass v2 device, nucleus version 2.12.1, on ubuntu 22, that is running remotely.

The device is now offline (and effectively unreachable) since we incorrectly configured a proxy via the cloud-based deployment.

The proxies set on the host device are:
```
https_proxy=:9480
http_proxy=:9480
```

Do these also need to be set in uppercase?

The networkProxy object set in the cloud deployment (and verified to be present in the local effectiveConfig.yaml) is:
```
"networkProxy": {
      "proxy": {
        "url": ":9400"  <------- Note the incorrect port here, set from the cloud.
      }
    }
```

I have read the documentation at: https://docs.aws.amazon.com/greengrass/v2/developerguide/configure-greengrass-core-v2.html#configure-alpn-network-proxy, specifically, 'Connection through a network proxy'.

So I have two questions:
 - How can I recover/remove/overwrite the incorrect config on the local device? I can gain local access through a screen share
 - Once that is recovered/reset - could you please clarify the process for working with a proxy normally? I presume it is not enough that there is a system-wide proxy set through `etc/environment` - I must also match that with the 'networkProxy' object, and cat the proxy cert onto the rootCA.pem cert?

Answer

Recipe directory is the only required param for the CLI deployment create command. You need to create a directory on your device and provide its absolute path as the value to this param.

You can skip every other param except the `--update-config` in which you need to merge in the correct network config for the component `aws.greengrass.Nucleus`. For more info on the config for Nucleus, please take a look at [1].

Greengrass will not inherit the values set in `/etc/environment`, you need to set the `networkProxy` object explicitly.

I hope this helps! Happy to help if there are further questions!

[1] https://docs.aws.amazon.com/greengrass/v2/developerguide/greengrass-nucleus-component.html#greengrass-nucleus-component-configuration

Answer

Hi

Do you have the Greengrass CLI deployed on your device? If yes, you can deploy the correct proxy settings using the CLI. Please take a look at [1].

If not, then you need to uninstall Greengrass from that device and re-install with the correct configuration provided as a yaml file with the `--init-config` param. Please take a look at [2].

It is recommended to have `http_proxy` in all caps.

could you please clarify the process for working with a proxy normally?
Did you read through [3]? Your device should able to operate in a network proxy properly if this doc is followed.

Please reach out if there are other concerns/questions.
Thanks!

[1] https://docs.aws.amazon.com/greengrass/v2/developerguide/gg-cli-deployment.html#deployment-create

[2] https://docs.aws.amazon.com/greengrass/v2/developerguide/configure-installer.html

[3] https://docs.aws.amazon.com/greengrass/v2/developerguide/configure-greengrass-core-v2.html#configure-mqtt-port-443

AWS Greengrass Proxy Issues

Relevant content