https://github.com/t04glovern/traffic-cop
WiFi Beacon & Client sniffing pipeline for analysing the movements of Human Traffickers.
https://github.com/t04glovern/traffic-cop
aws-cloudformation aws-dynamodb aws-iot aws-serverless esp8266 espressif wifi-scanner
Last synced: 3 months ago
JSON representation
WiFi Beacon & Client sniffing pipeline for analysing the movements of Human Traffickers.
- Host: GitHub
- URL: https://github.com/t04glovern/traffic-cop
- Owner: t04glovern
- Created: 2018-10-07T14:41:25.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2018-10-09T16:51:29.000Z (about 7 years ago)
- Last Synced: 2025-07-19T15:44:44.935Z (3 months ago)
- Topics: aws-cloudformation, aws-dynamodb, aws-iot, aws-serverless, esp8266, espressif, wifi-scanner
- Language: C++
- Homepage: http://traffic-cop.s3-website-us-east-1.amazonaws.com/
- Size: 3.54 MB
- Stars: 13
- Watchers: 3
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Traffic Cop
[http://traffic-cop.s3-website-us-east-1.amazonaws.com/](http://traffic-cop.s3-website-us-east-1.amazonaws.com/)
WiFi Beacon & Client sniffing pipeline for analysing the movements of Human Traffickers.
## Authors
* Nathan Glover [@nathangloverAUS (Twitter)](https://twitter.com/nathangloverAUS), [@t04glovern (Github)](https://github.com/t04glovern)
* Stephen Mott [@SrzStephen (Github)](https://github.com/SrzStephen)
* Rico Beti [@SilentyByte (Github)](https://github.com/SilentByte)
## Proof of Concept
## Circuit Diagram
### BOM
* [2x NodeMCU 1.0 (ESP 12 E Module)](https://www.amazon.com/NodeMCU-ESP8266-Microcontroller-Arduino-Makerdo/dp/B07BGCF3NY)
* [1x U-blox NEO-6M GPS Module](https://core-electronics.com.au/u-blox-neo-6m-gps-module.html)
* 1x ~200kΩ+ Resistor
* 5x M2M Jumper Wires
## Architecture
## Deploying CF
### IoT Vending Machine
Deploys a IoT Vending machine instances that can be used to generate certificates for new devices
```bash
aws cloudformation create-stack --stack-name "TrafficCop-IoT-Vending-Machine" \
--template-body file://aws/Iot-Certificate-Vending-Machine.json \
--parameters file://aws/Iot-Certificate-Vending-Machine-Params.json \
--capabilities CAPABILITY_IAM
```
#### Create Device
Check the outputs from your cloudformation stack and retrieve the *RequestUrlExample*, It'll look like the following:
```bash
https://.execute-api.us-east-1.amazonaws.com/LATEST/getcert?serialNumber=value1&deviceToken=value2
```
Create a new item in the DynamoDB instance that was created by the previous CloudFormation script (the DB is called deviceInfo)
* **serialNumber**: This should be something unique and will be the identifier for the IoT device you are onboarding (*e.g. gps-glover-01*)
* **deviceToken**: This should be a private hash/secret that you will use to generate certificates for your new device securely (*e.g. 572589798725*)
Substitute these two into your API Gateway query
```bash
https://.execute-api.us-east-1.amazonaws.com/LATEST/getcert?serialNumber=gps-glover-01&deviceToken=572589798725
```
You'll be returned a json response:
```json
{
"certificateArn": "arn:aws:iot:us-east-1::cert/009ff6ee0.........",
"certificateId": "009ff6ee092e......",
"certificatePem": "-----BEGIN CERTIFICATE-----\nMIIDWTCCAkGgAwIBAgIUZiIgLi......-----END CERTIFICATE-----\n",
"keyPair": {
"PublicKey": "-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAO.......-----END PUBLIC KEY-----\n",
"PrivateKey": "-----BEGIN RSA PRIVATE KEY-----\nMIIEpAIBAAKCAQ........-----END RSA PRIVATE KEY-----\n"
},
"RootCA": "-----BEGIN CERTIFICATE-----\r\nMIIE0zCCA7ugAwIBAgIQGNrRniZ96Lt........-----END CERTIFICATE-----"
}
```
Place the outputs for each of the three fields below into new files in [esp8266-gps/certs](esp8266-gps/certs)
* **esp8266-gps/certs/certificate.pem.crt**: certificatePem
* **esp8266-gps/certs/private.pem.key**: keyPair.PrivateKey
* **esp8266-gps/certs/root-CA.pem**: RootCA
Follow the instructions in [esp8266-gps/README.md](esp8266-gps/README.md) on how to convert and upload these certificates to the ESP8266
### DynamoDB Instance
Deploys the DynamoDB table + an action rule to push data from a topic into said Dynamo instance
```bash
aws cloudformation create-stack --stack-name "TrafficCop-IoT-TopicRule" \
--template-body file://aws/IoT-TopicRule.json \
--parameters file://aws/IoT-TopicRule-Params.json \
--capabilities CAPABILITY_IAM
```
### DynamoDB API
Build the API zip
```bash
cd api
./package-lambda.sh
```
Upload the API to S3 bucket (this same S3 bucket should be used in the Parameters of the `aws/DynamoDB-Frontend-Params.json` file)
```bash
cd api
aws s3 cp dynamodb-api.zip s3://waanimals-deployment-scripts/traffic-cop/dynamodb-api.zip
```
Deploy the API to CloudFormation
```bash
aws cloudformation deploy --template-file aws/DynamoDB-Frontend.json \
--stack-name "TrafficCop-DynamoDB-API" \
--capabilities CAPABILITY_IAM
```
Retrieve the stacks API endpoint
```bash
aws cloudformation describe-stacks --stack-name "TrafficCop-DynamoDB-API" --query Stacks[].Outputs[].OutputValue[] --output text
```
Place the output from this command into the `frontend/index.html` file under replacing the `api_gateway_url` variable.
```html
var api_gateway_url = 'https://.execute-api.us-east-1.amazonaws.com/prod';
```
### Frontend
Deploy the frontend HTML to an S3 bucket with site capability
The bucket policy should be the following for public access
```json
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PublicReadGetObject",
"Effect": "Allow",
"Principal": "*",
"Action": [
"s3:GetObject"
],
"Resource": [
"arn:aws:s3:::traffic-cop/*"
]
}
]
}
```
Push the frontend to the bucket.
```bash
aws s3 sync frontend/ s3://traffic-cop/
```
### Extras
The `db_tools` can be used in order to add new entries to the DynamoDB instance manually while testing. To use it simply run `npm install` then `npm run test`. You will need to also change the DynamoDB instance name in `db_tools/test.js` first.
### Deploy to SAM
#### Create a bucket
```bash
aws s3 mb s3://traffic-cop-api --region us-east-1
```
#### Package
```bash
sam package --template-file aws/DynamoDB-Frontend.json \
--s3-bucket traffic-cop-api \
--output-template-file aws/packaged.yaml
```
#### Deploy
```bash
sam deploy --template-file ./aws/packaged.yaml \
--stack-name "traffic-cop-query-engine" \
--capabilities CAPABILITY_IAM
```