JSM Ops - JEC Proxy Configuration

Tom Russell

We've just moved our Opsgenie Sandbox to JSM, but can't seem to get a JEC working. We have HTTP_PROXY configured in the jecService64.json file. In our OECs, this is used by the OEC to connect to AWS SQS.

Unfortunately, the JEC, on startup, is trying to make a connection to "https://api.atlassian.com/jsm/ops/jec/v1/credentials" without using the proxy, and is getting blocked by our corporate firewall.

How do I configure things so that the credentials API call uses the proxy?

Tom Russell

Problem solved.

Our company only uses an HTTP proxy; this worked fine with the Opsgenie OEC (and the JEC) for connecting to SQS.

The credentials API call apparently requires the HTTPS proxy to be in the environment.

I added an HTTPS_PROXY line to the jecService64.json file (pointed to our standard HTTP proxy) and the service started up.