-
Notifications
You must be signed in to change notification settings - Fork 1
Installation Guide: Step 4
Rohit Rathi edited this page Sep 17, 2018
·
1 revision
Note: You must be an admin IAM user for writing roles and pushing it to AWS.
For writing rules on the platform you need to do additional setup on AWS.
- For creating rules that interact with other services such as SNS, DynamoDB, AWS IoT & AWS Lambda. This is required for writing rules for storing data in DynamoDB, sending notifications with SNS, invoking lambda functions, actuators to AWS IoT etc.
- Create an IAM role for AWS IoT. A role grants a service like IoT, the right to access other services.
- Give permissions to the roles by attaching policies (AWS IoTFullAccess policy, SNS Full Access policy, DynamoDB policy).
- Put the ARN of this role into configset table as
IoTRoleARN
.
- Create three DynamoDB tables to hold corresponding data
-
NotificationDetail
- primaryPartitionKey: ruleName (String)
-
ThingDB
- primarySortKey: timestamp (Number)
-
actuatorStates
- primarySortKey: ruleName (String)
-
NotificationDetail
- For creating CRON rules
- Create a Lambda function and put it's ARN into configset as a value to the key
lambdaCronArn
. - Assign it a role with policies that give it access to AWS IoT, DynamoDB and SNS.
- Create a Lambda function and put it's ARN into configset as a value to the key
- For using notification service
- Create a Lambda function and put it's ARN into configset as a value to the key
lambdaNotificationArn
. - Assign it a role with policies that give it access to AWS IoT, DynamoDB and SNS.
- Create a Lambda function and put it's ARN into configset as a value to the key
- For using actuators
- Create a Lambda function and put it's ARN into configset as a value to the key
lambdaActuatorArn
. - Assign it a role with policies that give it access to AWS IoT, DynamoDB and SNS.
- Create a Lambda function and put it's ARN into configset as a value to the key