Could not run multiple chromeless on same AWS account and region

[kch-agnitio]

Hi, was just wondering, if we run multiple chromeless on same AWS account and region (and all chromeless uses the same AWS_IOT_HOST), would it cause problems?

Currently I'm trying to run two chromeless at the same time, because I need to separate them for different environments (development and production). I'm running into some issues where i get an error which says 'Timing out. No requests received for 30 seconds.', after it connects to the AWS IoT broker. This is what I see on CloudWatch:

START RequestId: bc0acdbc-748f-11e8-90e3-899f4a601055 Version: $LATEST
2018-06-20T13:43:53.666Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Spawning headless shell
2018-06-20T13:43:53.667Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: ChromeLauncher No debugging port found on port 9222, launching a new Chrome.
2018-06-20T13:43:53.683Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Launcher Chrome running with pid 47 on port 9222.
2018-06-20T13:43:53.683Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Waiting for Chrome 0
2018-06-20T13:43:54.185Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Waiting for Chrome 1
2018-06-20T13:43:54.186Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Started Chrome
2018-06-20T13:43:54.186Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: It took 520ms to spawn chrome.
2018-06-20T13:43:54.186Z bc0acdbc-748f-11e8-90e3-899f4a601055 Invoked with data: cjin62tkb004i01qs5dqe0bgi
{.......................}
2018-06-20T13:43:54.319Z bc0acdbc-748f-11e8-90e3-899f4a601055 Subscribed to chrome/cjin62tkb004i01qs5dqe0bgi/request
2018-06-20T13:44:24.319Z bc0acdbc-748f-11e8-90e3-899f4a601055 Timing out. No requests received for 30 seconds.
2018-06-20T13:44:24.346Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Trying to terminate Chrome instance
2018-06-20T13:44:24.349Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Waiting for Chrome to terminate..
2018-06-20T13:44:24.350Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Confirmed Chrome killed
2018-06-20T13:44:24.351Z bc0acdbc-748f-11e8-90e3-899f4a601055 @serverless-chrome/lambda: Chrome successfully terminated.
END RequestId: bc0acdbc-748f-11e8-90e3-899f4a601055
REPORT RequestId: bc0acdbc-748f-11e8-90e3-899f4a601055 Duration: 30685.19 ms Billed Duration: 30700 ms Memory Size: 1536 MB Max Memory Used: 191 MB 

It works fine for me if I use a single chromeless deployment only. I'm experiencing this on both chromeless deployment.

---

Update: I have Chromeless A & Chromeless B as remote proxy, setup on the same AWS account. There is a bug where when I call Chromeless A endpoint, sometimes the request gets sent to Chromeless B. Maybe this is caused by using the same AWS_IOT_HOST?