On-premises installationOverview | Software architecture | Download | Deployment | Configuration | Troubleshooting | FAQ | EULA
Authentication | LDAP | SAML 2.0 | Authorisation and role-based access | HTTPS | Amazon Web Services S3 | Elasticsearch
There are several options for running the on-premises installation over HTTPS, including:
- Configure HTTPS in the web/application server hosting the on-premises installation; for example SSL/TLS Configuration How-To for Apache Tomcat.
- Configure HTTPS upstream; for example Load Balancing Apache Tomcat Servers with NGINX Open Source and NGINX Plus, Create an HTTPS listener for your Application Load Balancer, etc.
If, after configuring HTTPS, you find that the on-premises installation is still trying to use some HTTP URLs
or the web pages don't look right (e.g. styles are not loading correctly, images are oversize, etc),
you will likely need to configure the
structurizr.url property - see On-premises installation - Configuration for details.