We are trying to run the SCIM container on ECS behind a loadbalancer.
- We are able to bring the container up and access the setup. The setup starts on 3002 port and as we login to 1password and install scimsession file, the setup server stops and restarts on some other port (8443). How to avoid that?
- As this is behind the load-balancer and we terminate TLS, we would not require to run LetsEncrypt setup within the container. How do we disable that?
- We were also wanting to generate the scimsession file and start the container with setting up
OP_SESSION environment variable (cat scimsession | base64 | tr -d "\n"). But when we do that, the setup server does not seem to start on 3002.
Can we have more details instructions on running the SCIM container behind the loadbalancer?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided