proxy: nginx config is out of date, doesn't launch

[cameronattard]

Describe the bug

nginx currently can't start in the access proxy stack as the config provided in the user data uses the ssl directive, which is removed in the nginx version on the latest AMI.

Apr 09 03:34:58 xxx.us-west-2.compute.internal systemd[1]: Starting The nginx HTTP and reverse proxy server...
Apr 09 03:34:58 xxxus-west-2.compute.internal nginx[2564]: nginx: [emerg] unknown directive "ssl" in /etc/nginx/conf.d/default.conf:8
Apr 09 03:34:58 xxx.us-west-2.compute.internal nginx[2564]: nginx: configuration file /etc/nginx/nginx.conf test failed
Apr 09 03:34:59 xxx.us-west-2.compute.internal systemd[1]: nginx.service: control process exited, code=exited status=1
Apr 09 03:34:59 xxx.us-west-2.compute.internal systemd[1]: Failed to start The nginx HTTP and reverse proxy server.
Apr 09 03:34:59 xxx.us-west-2.compute.internal systemd[1]: Unit nginx.service entered failed state.
Apr 09 03:34:59 xxx.us-west-2.compute.internal systemd[1]: nginx.service failed.

Expected Behavior

nginx should launch successfully.

Current Behavior

nginx doesn't launch due to invalid config.

Reproduction Steps

Launch the stack.

Possible Solution

Update the config to configure ssl according to current conventions.

Additional Information/Context

No response

Solution Version

v2.3.2

AWS Region. e.g., us-east-1

No response

Other information

No response

[jangidms]

Hi @cameronattard
Thanks for reporting this issue.
We are aware of this issue and are planning to fix in next release

[jangidms]

Hi @cameronattard
This has been fixed in latest release v2.3.3

Thanks