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 a static IP address that we own to perform all downloads:
Static IP Address: 54.245.27.223
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.
Do you have an agent that can be installed instead?
We currently do not support having an installable agent into the environment, but this is a planned improvement on our roadmap.