Added public ip doc. #13
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # Pipes' Public IP Addresses | ||
|
There was a problem hiding this comment. If we're already in the Pipes docs, do we need There was a problem hiding this comment. Yeah it wasn't necessary, removed |
||
|
|
||
| ## **Overview** | ||
| This document provides a list of public IPs used by Pipes for outbound requests. These IPs are intended for end-users to configure whitelisting, firewall rules, and integrations with external services. | ||
|
There was a problem hiding this comment. Are these for inbound, outbound or both? Also, would just be There was a problem hiding this comment. Yes, the ips are for both inbound and outbound requests, fixed it. Also changed |
||
|
|
||
| ## **Public IPs** | ||
| #### **1. Load Balancer IPs** | ||
| The following IPs are used by Pipes' load balancers. Please ensure these are whitelisted for access to our services: | ||
|
|
||
| | **Load Balancer Name** | **Static IP Address** | **Ports** | | ||
|
There was a problem hiding this comment. General comments:
There was a problem hiding this comment. General practice is to use /32 so updated the doc with the same. |
||
| |------------------------------|---------------------------|---------------| | ||
| | Main Service | 34.86.218.179 | 80, 443 | | ||
|
There was a problem hiding this comment. What is There was a problem hiding this comment. Yeah! This is the main load balancer that redirects traffic from our application url to our services. There was a problem hiding this comment. Is there a better name than |
||
| | Database Proxy | 34.145.175.31 | 9193 | | ||
|
There was a problem hiding this comment. Probably best to be more Pipe-specific? There was a problem hiding this comment. Makes sense. Updated to There was a problem hiding this comment. The DB and dashboard IPs are really per hive; we just happen to only have one hive at present. It may be more accurate to look them up for your individual workspace. For example, you can get your database host from the Steampipe query tab by clicking the info button, eg, There was a problem hiding this comment. I would not call these "load balancer IPs" - that's not really relevant to the end user. Note that the scope is different - what you call Application Endpoint is the pipes.turbot.com console and API endpoint, and it's global for everyone. Steampipe Database and Powerpipe Dashboard are for your workspace and could vary from one workspace to the next (eventually). There was a problem hiding this comment. @prithage perhaps have a chat with @johnsmyth on this to get the required path for updates? There was a problem hiding this comment. replace application endpoint to turbot pipes ui (pipes.turbot.com) - add in description about custom tenant replace load balancer (inbound to us not them) and nat gateway (outbound to us) to connect to pipes and connect pipes to your services |
||
| | Dashboard | 34.85.232.246 | 80, 443 | | ||
|
There was a problem hiding this comment. As above - There was a problem hiding this comment. Updated to |
||
|
|
||
| These IPs are static and will not change. | ||
|
|
||
| #### **2. NAT Gateway IPs** | ||
| The following IPs are used for outbound traffic from Pipes to external services: | ||
|
|
||
| | **Static IP Address** | | ||
| |---------------------------| | ||
| | 35.194.64.40 | | ||
| | 34.150.247.248 | | ||
| | 34.150.238.109 | | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's try moving this to
Reference->Public IP Addresses?@johnsmyth thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree @MichaelBurgess - I would put it in the reference section somewhere