1 回答
- 最新
- 投票最多
- 评论最多
0
It seems the data is not being saved to S3 or Timestream as expected when running the demo.sh script.
- Verify the IAM role used has the necessary permissions to write to S3 and Timestream in the specified region.
- Check that the S3 bucket and Timestream database specified in the campaign file exist and the region matches where the script is run.
- Review the logs for any errors when the SDK attempts to write to S3 or Timestream. Invalid credentials, missing resources etc could cause failures.
- As a test, try saving a simple test object/record manually using the AWS CLI or SDK to check connectivity to the resources.
aws s3 cp test.txt s3://bucket/path/
aws timestream write-records --database-name db --records file://records.json
- Compare the data format and names used in the script versus what Timestream and S3 expect. Make sure fields line up properly.
相关内容
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
Thank you for your kind answer! I used <campaign-break-event.json> collection rule to create and deploy e a campaign to save to s3 together. However, I found that [Vehicle.ECM.DemoEngineTorque] and [Vehicle.ABS.DemoBrakePedalPressure] data were saved really well in s3! Also, when I checked the IAM credentials, they were all authorized as AdministratorAccess! What did I miss? I guess OBD data is a problem. Is there any other log to see OBD data occurring other than cansim@0.service? I would like to know the answer! Thank you always!
Thank you. After troubleshooting, I had to modify some variable values in the config.json file from 0 to 1. The variable values to change are as follows: obdInterface:pidRequestIntervalSeconds or obdInterface:dtcRequestIntervalSeconds. Thank you for your kind reply.