Is it possible to setup SG with it's GW-Nodes so that you can reach "mgmt.s3.hosting.com" for the Tennant WEB Login, and "s3.hosting.com" for the data traffic, but all on the same VIP ?
Also... it is possible to change the logo yo your own in the Tennant login spash and at the top when logged it?
#Hosting experience?
dire bison
lofty frost
mgmt.s3.hosting.com and s3.hosting.com can be served from the same VIP but need to use different TCP ports
- The VIP needs to defined in an HA group consisting of admin node(s) as the admin portal is only available on admin nodes
- Using the name mgmt.s3 for management makes it confusing if you are also using virtual-hosted-style addressing - mgmt would then be a bucket name. Realise the names given here are probably only examples but a name like mgmt-s3.hosting.com would probably make more sense
I know that in the past, we have had approved FPVRs to replace the logo in the GUI. Not sure of the current status as none of "my" customer are using it. Check with the account team as for any FPVR related question.
dire bison
So I guess if you want to use the standard ports 443 for management and S3 data. You will need something like HAProxy to seperate this and "proxy" it to the correct ports?
lofty frost
Yes, I don't see why not but also don't really see the benefit of one endpoint/hostname and the same TCP port service both admin and S3.
In theory you can have 2 VIPs in 2 different HA groups then bind one admin endpoint to port 443 on one of the VIPs and an S3 endpoint to port 443 on the other VIP.
But currently there is some issue with the code so the admin service will mess up the use of port 443 "everywhere else" on the same node. Once that is resolved (in a hotfix or so, fingers crossed) you should be able to implement this.
In a larger grid where you have separate admin nodes and gateway nodes, this is of course less of an issue.