I do not understand how CSRs work. Will a self-signed CSR function on a public AWS EC2 instance?
If I need to use a certificate-issuing authority, I'll probably use Let's Encrypt as it is a free Certificate Authority. I'm planning to use this for TLS for SECT on AWS unless anyone forsees any problem with it.
In reply to JB:
JB, thanks for your help. I progressed a bit more. Right now, I'm using a self-signed CSR. When I go to my SECT Dashboard on AWS, I get the response below.
If I click on ADVANCED, I then get the option to go to my test server.
At this point, I can access my SECT Dashboard on AWS.
I can also log in.
At this point, I'm still trying to figure out how to point my S5D9 to my new SECT dashboard server.
This code in HTTPClientSample.h looks promising
/* Staging server */#ifdef STAGING_SERVER#define BOOT_URI "sect.k2-inc.com/.../bootstrap"#define BOOT_CONFIRM_URI "sect.k2-inc.com/.../confirm"#else#define BOOT_URI "cloud.renesassynergy.com/.../bootstrap"#define BOOT_CONFIRM_URI "cloud.renesassynergy.com/.../confirm"#endif
Is anyone using the AE-CLOUD1 kit with their own deployment of the SECT Dashboard? If so, can you give me some hints how I can configure the S5D9 to go to the new server.
In reply to codetricity: