Research & data integration

Amazon Web Services

Explore how ThingsCommute could securely deliver agricultural sensor data to your own Amazon S3 storage environment.

Illustrative future workflow

From farm sensor data to your own data lake

Illustration of sensor data flowing from farm devices through ThingsCommute to Amazon S3.
Illustrative future integration. AWS authorization and automated sensor data exports are not yet available.

Why connect farm data?

More context for practical decisions and research.

For farmers

  • Review historical sensor readings from different fields and seasons.
  • Bring agricultural telemetry together with farm records and other relevant information.
  • Work with chosen analysts to build reports that support practical farm decisions.

For researchers

  • Prepare sensor data from field trials and longitudinal studies.
  • Combine agricultural telemetry with study and environmental context.
  • Use research tools to analyze, document and share approved data.

Two possible approaches

Choose a future integration path.

Both options are marked Coming Soon. Select a card to read what may be needed before secure data delivery can be set up.

These workflows are not available yet. This page does not generate bucket policies, authorize AWS accounts, upload sensor data or deploy CloudFormation stacks.

Standard · Coming Soon

Connect Your S3 Data Lake

A possible approach for teams with an existing Amazon S3 bucket. Any future sensor data transfer would require an agreed purpose, limited access and a reviewed bucket policy.

Prerequisites to plan for

  • An AWS account and a customer-owned S3 bucket in an agreed region.
  • A bucket owner or administrator authorized to review and manage its bucket policy.
  • Agreement on which sensor data to share, its file format, destination folder and how long it should be kept.
  • A security review to define any transfer identity and the access it would need.

Potential future setup steps

  1. Confirm which sensor data should be shared, when it should be sent and where it should go.
  2. Review planned access and written setup instructions before changing permissions.
  3. Have the authorized bucket owner apply approved access settings in AWS.
  4. Test a limited data transfer and agree how to monitor and stop access.

Advanced · Coming Soon

Automated AWS Integration

A potential guided setup using AWS CloudFormation. No template is currently offered, and this website does not create stacks.

Prerequisites to plan for

  • An AWS account with authority to review and deploy CloudFormation stacks.
  • An agreed S3 destination, AWS region and data-retention approach.
  • Organizational approval for any IAM roles, policies and resources a future template may request.
  • A technical owner available to review the proposed architecture, costs and security impact.

Potential future setup steps

  1. Agree the integration scope and document every resource a proposed stack would create.
  2. Review the template, permissions, costs and removal procedure before deployment.
  3. Have an authorized customer administrator deploy the approved stack in their AWS account.
  4. Verify the configured destination and test the agreed data flow before broader use.

Planning a research or data project?

Talk with us about a future integration.

Contact ThingsCommute