Particle to S3

This page provides you with instructions on how to extract data from Particle and load it into Amazon S3. (If this manual process sounds onerous, check out Stitch, which can do all the heavy lifting for you in just a few clicks.)

What is Particle?

Particle allows businesses to bring their Internet of Things (IoT) products to market faster. It provides a secure, easy-to-use, full-stack IoT cloud platform and low-cost connected hardware.

What is S3?

Amazon S3 (Simple Storage Service) provides cloud-based object storage through a web service interface. You can use S3 to store and retrieve any amount of data, at any time, from anywhere on the web. S3 objects, which may be structured in any way, are stored in resources called buckets.

Getting data out of Particle

Particle exposes events through webhooks. To use webhooks, log into your Particle console and click on the Integrations tab, then click New Integration > Webhook. Set the event name to the item you want to track; it's good practice to specify the name of the field where you want the data to live in your data warehouse. Set the URL to the key or token that you'll use to accept the data. Leave the request type as POST. In the device field, select the device you want to trigger the webhook. Finally, click Create Webhook.

Sample Particle data

Particle sends data in JSON format via webhook through a POST request whenever an event triggers it to do so. The JSON fields and endpoints will match the data collected by your form. For instance:

{
    "event": [event-name],
    "data": [event-data],
    "published_at": [timestamp],
    "coreid": [device-id]
}

Loading data into Amazon S3

To upload files you must first create an S3 bucket. Once you have a bucket you can add an object to it. An object can be any kind of file: a text file, data file, photo, or anything else. You can optionally compress or encrypt the files before you load them.

Keeping Particle data up to date

Once you've coded up a script or written a program to get the data you want and move it into your data warehouse, you're going to have to maintain it. If Particle modifies its API, or sends a field with a datatype your code doesn't recognize, you may have to modify the script. If your users want slightly different information, you definitely will have to.

Other data warehouse options

S3 is great, but sometimes you want a more structured repository that can serve as a basis for BI reports and data analytics — in short, a data warehouse. Some folks choose to go with Amazon Redshift, Google BigQuery, PostgreSQL, Snowflake, Microsoft Azure SQL Data Warehouse, or Panoply, which are RDBMSes that use similar SQL syntax. If you're interested in seeing the relevant steps for loading data into one of these platforms, check out To Redshift, To BigQuery, To Postgres, To Snowflake, To Azure SQL Data Warehouse, and To Panoply.

Easier and faster alternatives

If all this sounds a bit overwhelming, don’t be alarmed. If you have all the skills necessary to go through this process, chances are building and maintaining a script like this isn’t a very high-leverage use of your time.

Thankfully, products like Stitch were built to move data from Particle to Amazon S3 automatically. With just a few clicks, Stitch starts extracting your Particle data via the API, structuring it in a way that is optimized for analysis, and inserting that data into your Amazon S3 data warehouse.