In this example I will send data from my device to the Hologram cloud router and then onto AWS S3 for archiving and analysis. I assume you are already familiar with sending data to the Hologram Cloud from your device. If you haven’t yet sent data to Hologram’s Cloud, check out Hologram Python SDK Quick Start Guide. Once you have data flowing to the Hologram Cloud you will be able to set up routing to AWS S3.
You will, obviously, need a Amazon Web Services account. You can signup for one here if you don’t.
Once you have your account set up, navigate to the S3 Console and click the “+ Create bucket” button to create a new bucket for your data.
I created one named
Use the default properties and permissions.
Next, you need to go to Identity and Access Management and create a user that will be used for your cloud route.Click on Users in the menu and then the Add User button to add a user. I added a user named
routecloud. And choose the Programmatic access as the Access type.
Choose to Attach existing policies directly and filter on S3. You should then find, and add, AmazonS3FullAccess and click Next.
Finally, click Create user.
On the next page you will need to copy the Access key ID and the Secret access key. You will use these when you set up the route in Hologram’s Cloud.
Now it is time to move over to the Hologram Cloud and start setting up a cloud route.
+ New Route and provide a nickname for the route. Pick the topics you wish to filter on. And then select Amazon S3 as your output.
This is where you enter your AWS KEY and AWS SECRET for the user you created earlier. Match the AWS REGION and enter the name of the S3 BUCKET.
When your device sends a message to the Hologram Cloud that meets the topic requirements, you should see your route triggered.
Now go to your S3 Bucket (using your tool of choice) and look for the file representation of your message.
Its contents should be the same as what you saw in the Hologram Cloud console.
If you followed along, you should be seeing your bucket fill up with data.