Author Topic: HTTPS interface to AWS hosted PCS + keystore server  (Read 2606 times)

Ron Beernink

  • EA User
  • **
  • Posts: 24
  • Karma: +1/-0
    • View Profile
HTTPS interface to AWS hosted PCS + keystore server
« on: December 13, 2022, 07:43:11 am »
Anyone hosting their own ProCloud server on an AWS EC2 instance, and able to tell me how to configure the HTTPS port 1805 for the instance security group?

We are implementing PCS on AWS and all is running fine, except the Sparx Enterprise Architect connection which can't connect to Sparx keystore server; returning an "the operation timed out" error.   When I connect with a local EA client installed on the PCS instance everything works ok.  So I am guessing that it is a problem with the HTTPS port.   AWS does not allow you to change the port from 443 to 1805 for the HTTPS rule.  So instead I have a "Custom TCP" type of rule with 1805 as the port range.   I found another discussion on using a different port number with HTTPS in AWS and the advise was that "Custom TCP" is the right type.

The other cause of the problem could be the SSL certificate.  I used Open-SSL on the EC2 PCS instance to generate the certificate.   But when I created the EC2 server instance, it created its own key pair.   I'm not sure which one to use and how you would turn the EC2 key pair into a server.pem file that PCS needs.

« Last Edit: December 13, 2022, 11:35:21 am by Ron Beernink »