Hi man2002, Might not be the answer to your issue, but the screenshot of the certificates shows all three in the same folder. The AWS Device certificate should be in the "Own Certificates" folder in the Device Security Manager and the AWS ones in the "Trusted Certificates Folder". The other thing to check would be the Policies in the AWS Security settings section as this can cause hours of head aches! As a basic test policy - not to be used for day-to-day as it could pose a security risk - you could...
Hi man2002, Might not be the answer to your issue, but the screenshot of the certificates shows all three in the same folder. The AWS Device certificate should be in the "Own Certificates" folder in the Device Security Manager and the AWS ones in the "Trusted Certificates Folder". The other thing to check would be the Policies in the AWS Security settings section as this can cause hours of head aches! As a basic test policy - not to be used for day-to-day as it could pose a security risk - you could...
Hi Jere, We have also been having similar issues with the IOT library's on IFM PLC's. I have traced the issue as you have to be to do with DNS resolution. For a work around we have to set the PLC to get it's IP address via DHCP which also sets the DNS server address on the PLC. As far as we have been able to find, there is no way to set the DNS server address for the ethernet stack on these when using them with a manually set / static IP Address. I previously discussed the issue with IFM support...