# Cannot connect an HTTP Monitor to AWS API Gateway
**URL:** https://forums.digi.com/t/cannot-connect-an-http-monitor-to-aws-api-gateway/19009
**Category:** Web Services (API)
**Tags:** aws, connect-sensor, remote-manager
**Created:** [December 22, 2017, 11:18am UTC](https://forums.digi.com/t/cannot-connect-an-http-monitor-to-aws-api-gateway/19009 "2017-12-22T11:18:17Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@mpfluger](https://forums.digi.com/u/mpfluger)
#### Post date: [December 22, 2017, 11:18am UTC](https://forums.digi.com/t/cannot-connect-an-http-monitor-to-aws-api-gateway/19009/1 "2017-12-22T11:18:17Z")
I’m having issues with an HTTP monitor I’ve created to push notifications to an API endpoint. I’ve followed the documentation located here ([http://bit.ly/2BsUf8O](http://bit.ly/2BsUf8O)). I’ve also been able to follow this tutorial ([http://bit.ly/2yGnzDv](http://bit.ly/2yGnzDv)).
Using the API Explorer under the Documentation tab of the Remote Manager, I submitted the following request:
URL: /ws/Monitor
Method: POST
Response Time: 1.311s
Time Sent: Wed Dec 13 14:47:20 CST 2017
DataStream/00010000-00000000-03566100-70211723/\*/val
http
[https://xye9z679wg.execute-api.us-east-1.amazonaws.com/dev/logData](https://xye9z679wg.execute-api.us-east-1.amazonaws.com/dev/logData)
POST
json
none
1
1
When the device connects to report its state, it seems that it tries to fire this push notification. Each time, I’m receiving the following alarm:
Monitor disconnected: transport channel was closed
You can test accessing my API Endpoint by running the following curl statement (no authentication needed):
curl -H “Content-Type: application/json” -X POST [https://xye9z679wg.execute-api.us-east-1.amazonaws.com/dev/logData](https://xye9z679wg.execute-api.us-east-1.amazonaws.com/dev/logData) -d “”
It should respond with:
{“status”:“success”}
Can someone tell me what this alarm means? Alternatively, is there another way I should go about this?
---
### Author:  [@pabloariasmora](https://forums.digi.com/u/pabloariasmora)
#### Post date: [February 15, 2018, 3:03pm UTC](https://forums.digi.com/t/cannot-connect-an-http-monitor-to-aws-api-gateway/19009/2 "2018-02-15T15:03:25Z")
Hi @mpfluger, Were you able to solve the problem?
---
### Author:  [@pabloariasmora](https://forums.digi.com/u/pabloariasmora)
#### Post date: [February 16, 2018, 12:23pm UTC](https://forums.digi.com/t/cannot-connect-an-http-monitor-to-aws-api-gateway/19009/3 "2018-02-16T12:23:09Z")
Hi @mpfluger, Were you able to solve the problem?
---
### Author:  [@ralexjbr](https://forums.digi.com/u/ralexjbr)
#### Post date: [February 15, 2018, 3:03pm UTC](https://forums.digi.com/t/cannot-connect-an-http-monitor-to-aws-api-gateway/19009/4 "2018-02-15T15:03:34Z")
Hello, i have the same problem, hope somebody from digi can help us.
Regards.
---
### Author:  [@mpfluger](https://forums.digi.com/u/mpfluger)
#### Post date: [February 21, 2018, 3:58pm UTC](https://forums.digi.com/t/cannot-connect-an-http-monitor-to-aws-api-gateway/19009/5 "2018-02-21T15:58:20Z")
Hi everyone,
I eventually received a follow-up email from Digi saying the following:
“The HTTP library which DRM uses for delivering events doesn’t support the SNI TLS extension API Gateway uses to know which TLS certificate to hand out. That’s why it seems that authentication is failing, even though you said your API call doesn’t require authentication.”
At this time, I worked around the problem by building an API Gateway entry point, a Lambda function to poll the Digi RESTful web services, and a CloudWatch even to trigger the API Gateway every 5 minutes to invoke the lambda function. It’s not ideal, but it works.
Thanks,
Matthew