Appearance
Forward data to S3 / OSS
Object storage forwarding saves batches of point records as JSON files. The connection uses the S3 API, so the destination needs a compatible endpoint, bucket, and write credentials.
Configure the bucket
A Manager or Owner can create an S3/OSS profile under Organization → Data → Data Forwarding.
| Field | Value |
|---|---|
| Endpoint | Object storage service address; use its S3-compatible endpoint |
| Bucket | An existing writable bucket |
| Object key prefix | Path prefix, such as site-a/data |
| Region | Region required by the service and bucket |
| Access key | Access Key ID |
| Secret key | Corresponding Secret Access Key |
Use dedicated write credentials restricted to the required bucket and paths. Services such as OSS need a matching S3-compatible endpoint and authentication method. A web console address is not a service endpoint.
Files and paths
Each batch becomes a .json object containing an array of point records. Its key includes the configured prefix, processing date, and batch information. The path date does not replace each record's measurement time.
These files archive data, not point settings. Use point configuration export to back up channel parameters.
Verify storage
- Save and enable the profile, then have a device report new data.
- Look for a new JSON object under the selected bucket prefix.
- Download a file and check point identifiers, times, and values.
- Check platform counts and object storage logs.
No files appear
Check the endpoint, region, bucket, credentials, and write policy. Access to the storage web console does not prove that the cloud forwarding connection can write. Configure destination retention or lifecycle rules separately for long-term archives.