Using SSL/TLS when Zabbix is on AWS behind an Application Load Balancer
Hi all,
I'm not sure this is directly related to Zabbix but any advice is very welcome. I need to make Zabbix securely available via a domain name, without "/zabbix" when the whole lot is installed on AWS. I can get the apache welcome page to display via HTTPS but not Zabbix. i.e. https://mydomain.com is fine but https://mydomain.com/zabbix is "not secure" according to Firefox / Chrome.
I guess there are 2 things here :
Environment:
I've created the AWS Application load balancer, created a Route 53 domain and generated an AWS Certificate. All seems good there.
When I go to "https://<domain name> I see the Apache "123 Testing" page as expected.
When I go to "https://<domain name>/zabbix, the browser reverts to HTTP and displays "not secure" in the URL.
In the past, when I've set this up on-premise I've set up the cert using LetsEncrypt and created a virtual host in Apache so that I no longer need the "/zabbix" part. When I do the same thing in an AWS environment, with the cert on the load balancer, I get browser errors about "Too many redirects".
Has anyone encountered this and can point me in the right direction for a solution please?
All advice is gratefully received.
Dave
I'm not sure this is directly related to Zabbix but any advice is very welcome. I need to make Zabbix securely available via a domain name, without "/zabbix" when the whole lot is installed on AWS. I can get the apache welcome page to display via HTTPS but not Zabbix. i.e. https://mydomain.com is fine but https://mydomain.com/zabbix is "not secure" according to Firefox / Chrome.
I guess there are 2 things here :
- Make Zabbix accessible without using "/zabbix"
- Add the SSL/TLS Cert into the mix.
- Do all the above within AWS !!
Environment:
- Zabbix 5.0 LTS installed on AWS.
- Separate front-end (apache), server and database.
- Domain name registered on AWS Route 53
- AWS Certificate Manager SSL/TLS Cert generated.
I've created the AWS Application load balancer, created a Route 53 domain and generated an AWS Certificate. All seems good there.
When I go to "https://<domain name> I see the Apache "123 Testing" page as expected.
When I go to "https://<domain name>/zabbix, the browser reverts to HTTP and displays "not secure" in the URL.
In the past, when I've set this up on-premise I've set up the cert using LetsEncrypt and created a virtual host in Apache so that I no longer need the "/zabbix" part. When I do the same thing in an AWS environment, with the cert on the load balancer, I get browser errors about "Too many redirects".
Has anyone encountered this and can point me in the right direction for a solution please?
All advice is gratefully received.
Dave