We entered in the AWS IoT Client the ClientID, Endpoint, port and topics. We uploaded the (3) certificates that AWS broker creates into the core, see attachment.
The AWS client FB remains on a TCP_READ_ERROR. It seems that we cannot/should not connect to AWS. This could be due to the certificates. See attachment.
Now, if we are to follow the approach in this Codesys documentation with the necessary adjustments following changes to the AWS console, we would be generating a certificate signing request (CSR) (steps 37-41). We have generated the signed certificate based on the CSR using Amazon as the certificate authority. The certificate file along with the root CA files are attached to this email. These files are needed in steps 61-66.
We do not have a privite key (belonging to the CSR file of steps 37-41) in our hands. Based on Codesys' documentation, one must assume that the private key is available somewhere within the Codesys environment.
Hello,
We are using the CodeSyS IIOT package. Specifically the AWS IoT Core Client library. Online there is a roadmap what you can follow to connect to AWS, see: https://faq.codesys.com/pages/viewpage.action?pageId=119504904 We followed this roadmap.
We entered in the AWS IoT Client the ClientID, Endpoint, port and topics. We uploaded the (3) certificates that AWS broker creates into the core, see attachment.
The AWS client FB remains on a TCP_READ_ERROR. It seems that we cannot/should not connect to AWS. This could be due to the certificates. See attachment.
Now, if we are to follow the approach in this Codesys documentation with the necessary adjustments following changes to the AWS console, we would be generating a certificate signing request (CSR) (steps 37-41). We have generated the signed certificate based on the CSR using Amazon as the certificate authority. The certificate file along with the root CA files are attached to this email. These files are needed in steps 61-66.
We do not have a privite key (belonging to the CSR file of steps 37-41) in our hands. Based on Codesys' documentation, one must assume that the private key is available somewhere within the Codesys environment.
Can this be verified?
Kind Regards