Dual JIRA/Confluence/etc installation on a single Linux server

NB - this is an alternative proposal to an existing project request providing this solution using Docker. This variation will NOT use Docker.. It should use the correct Atlassian techniques to run two sets of applications on the same server. Summary: Move an existing JIRA* installation to a new server. Add a second JIRA* installation to this server. Configure a HTTPS proxy with LetsEncrypt certificates to provide access. JIRA* means the suite of applications. We have an existing JIRA self hosted installation with Confluence using Crowd local authentication. There was also a connected Bamboo, Fisheye and Crucible installation when this was installed on a previous server - it was not yet restored from backups. We wish to move this all to a new high capacity server which is planned to run two separate installations of the full suite for two different companies. This will also need a local HTTPS proxy installed with LetsEncrypt self-renewing certificates. This HTTPS must be configured and working for each service. Firewall configuration should secure the server behind the proxy. We will provide URLs and DNS support. Each installation will also have JIRA Service Desk but it is not currently configured on the first one. The existing installation had Bamboo, Crucible and Fisheye but has not been re-installed on the current server. It needs to be restored from backup and re-activated on the new server. The second installation will also need Bamboo, Crucible and Fisheye installed. Both Bamboo installations will talk to BitBucket hosted and need to build to a Windows IIS server (no Active Directory or auth is currently configured). A single machine can run multiple JIRA etal instances via these provisos. We expect it to be done along these lines. [login to view URL] The final configuration should do nightly automated full backups to an S3 bucket via S3 CLI (will be installed). The base server will be Centos 7 64 bit with 16Gb of RAM running on KVM. The current setup is using Postgres for the database. We'd like to continue with Postgres. Each set of applications will have no relation to each other, other than sharing a production web server to build to. There is no Active Directory configured for either setup but they could share a common Crowd server to make life easier. Maybe even in a federated setup? Please confirm. [login to view URL] Documentation of the configuration with instructions on how to restore the backups to a new server should be supplied. Some support assistance maybe required in configuring Service Desk, Bamboo etc. Our staff will use SourceTree - assistance maybe required in ensuring this is configured correctly for up to 3 developers. The data size and user count is quite small and is only using the small teams licences. If you know your JIRA admin, this should be fairly simple. Please confirm if you have experience with JIRA etc and how you would execute the above and any concerns. Any questions, let us know.