Response other than 200 - scanning API

[lee2]

Hey everyone. I was following the CMX AWS lambda guide - https://github.com/dexterlabora/cmxreceiver-lambda-inline

It looks like everything is all good on the AWS end. If I copy my post URL into the browser, it returns the correct meraki validation key. However, the URL will not validate. I receive a "Response other than 200". If I check the AWS logs, it looks like the request is never making it to the API gateway. I checked the event logs for my MX64 and OpenDNS to see if the URL was somehow being blocked.

Any recommendations or ideas would really be beneficial.

[DexterLabora]

1. When I was building this integration, I got tripped up on the permissions also, so you are not alone!

2. The purpose is to capture the raw data (i.e MAC addresses) to use as desired. The Meraki built-it reporting anonymizes the data and has a limited amount of reports. By collecting this data, you can trigger workflows for known clients, aggregate the data with other sources and analyze multiple networks as needed.

(Glad you liked the tutorial 😉 We hope to build many more tutorials like this for our developers and integrators.

3. As an alternative to Elasticsearch and AWS, I have also written a basic Google Firebase Database version.

It will provide a Firebase Function to run the CMX/Scanning API receiver. That data is then stored in the Firebase Database, by MAC address. The service is FREE. To get a solution similar to Elasticsearch, you could integrate Google Big Query, but there is a cost associated with that.

https://github.com/dexterlabora/MerakiLocationFirebase

[Lawrence2]

No worries~ Thanks for sharing your experience~