AnsweredAssumed Answered

Configuring S3 Compatible connections in ports different than 80?

Question asked by Alejandro Lineiro Employee on Dec 14, 2017
Latest reply on Dec 18, 2017 by Alejandro Lineiro

Hello everyone!

 

We are having some trouble configuring an S3 Compatible data connection: the S3 endpoint host is an Atmos, which exports its endpoints on port 8080.

When trying to configure a new S3 data connection in HCI, I haven't seen any way to configure the port for the endpoint. By default, it seems to connect to port 80 for http and 443 for https, which is a problem in our situation.

 

If I try to add a port to the IP address, like 192.168.0.1:8080, it detects it as a hostname and throws an error saying that the hostname couldn't be solved. We have been unable to try configuring the hostname instead of the IP because we get a "hostname can't be null" error (we suspect it's due to the fact that the hostname has an "_" character). Would using the hostname instead of the IP allow us to specify a different port?

 

Can we fix this problem on our end, or will it require a new DNS name for the endpoint/exporting the endpoint on port 80/both?

 

Thanks a lot for your help!

Outcomes