- Newest
- Most votes
- Most comments
Hi Pawan. It seems to me that the error message you're reporting is not so likely if the status is "In sync". Maybe that error didn't occur at the same time as "In sync".
Is your Kepware OPC server in the same VPC and subnet as the SiteWise gateway? Perhaps you can tell us a little about your network architecture.
- I think Kepware OPC requires it, but you need to determine that. As for where to find the cert on the gateway, please retrace your steps. Have you found the
sitewise-COLLECTOR-config.json
file? If not, perhaps trysudo find / -name sitewise-COLLECTOR-config.json
. - It will depend on your network architecture.
By the way, you said in one of your other questions that you're following this blog: https://aws.amazon.com/blogs/iot/collecting-organizing-monitoring-and-analyzing-industrial-data-at-scale-using-aws-iot-sitewise-part-1/. Please be aware that that blog is more than 4 years old and was written for Greengrass V1.
The SiteWise workshop might also be a valuable reference: https://catalog.us-east-1.prod.workshops.aws/workshops/2de8cd26-ae40-4b09-ad19-7b1eff358f5f/en-US/30-aws-iot-sitewise-setup/create-sitewise-gateway
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
Thank you Greg. I found the issue on Network end and rectified..
Thank you Greg. I found the issue on Network end and rectified..