On-Prem Tools Connection
- Jeremy Freeman
- Chad Girard (Unlicensed)
- Hersh Tapadia
Guide for Cloud setup, where servers are located in a private cloud or on-premises.
When to use this guide?
If all services you wish to connect to are available outside of your organization's VPN or internal network, you should be able to connect normally without this guide. This typically applies if you're using "Cloud" versions of services like Jira or Github. A quick test is to look at the URL you access the tool from. If it's a domain that belongs to the tool [atlassian.net or github.com], this is most likely a cloud tool. If the URL contains either an IP address or contains your company's URL [192.168.1.234 or jira.allstacks.com], you will most likely need this guide.
How do we connect to on-premises or private cloud tools?
We connect by using a whitelisted IP address that has access to the correct tools. This generally requires someone from our IT department to establish the connection. We use the following static IP addresses for our shared instances to perform all downloads. You should select the appropriate static IP for whitelisting based on your relevant instance hosted either in the US or EU region.
[US] app.allstacks.com: 54.245.27.223
[EU] app-eu.allstacks.com: 108.128.171.181
*Note: If your organization is set up in a dedicated single tenant environment, please reach out to your Allstacks representative for IP address information.
Which ports need to be opened?
Ports:
80 [Only allow port 80 if you have a service that's not communicating over HTTPS]
443
Please note that if you establish a connection with a tool that doesn't support SSL encryption, your data will be transferred unencrypted in flight. We strongly recommend that you enable this feature (SSL Encryption) of all services before connecting Allstacks. Internally, all data is encrypted at rest and in transit at Allstacks.