Skip to content

Commit 2918a06

Browse files
authored
Update getting-started.md to clarify AI Assistant usage for cloud instances (#3070)
1 parent 3e50ae2 commit 2918a06

2 files changed

Lines changed: 6 additions & 2 deletions

File tree

329 KB
Loading

src/pages/docs/octopus-ai/assistant/getting-started.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ navOrder: 3
99

1010
## Prerequisites
1111

12-
- An Octopus instance (cloud or on-premises with [public accessibility](#using-with-on-premises-instances))
12+
- An Octopus instance (cloud or on-premises with [public accessibility](#using-with-on-premises-instances-or-cloud-instance-allow-lists))
1313
- A Chromium-based browser (Chrome, Brave, Edge, etc.) that supports Chrome Web Store extensions
1414

1515
## Installation
@@ -18,10 +18,14 @@ navOrder: 3
1818
2. Navigate to your Octopus Deploy instance. You will see a new icon in the bottom right corner of your Chrome browser
1919
3. Click the AI Assistant icon in your browser to start using the assistant
2020

21-
## Using with on-premises instances
21+
## Using with on-premises instances or cloud instance allow lists
2222

2323
For on-premises Octopus instances, ensure your server accepts HTTPS requests from IP address `51.8.40.170` to enable AI Assistant functionality. The DNS entry of your Octopus Server will also need to be resolvable over the Internet for the IP address to be able to communicate with it.
2424

25+
Cloud instances with the `IP address allow list` feature activated will need to add `51.8.40.170` to the allow list to enable AI Assistant functionality:
26+
27+
![Control Centre](/docs/img/octopus-ai/assistant/cloud-portal.png)
28+
2529
:::div{.warning}
2630
It is not possible to integrate Octopus AI Assistant with an on-premises Octopus instance that cannot accept HTTP requests from this public IP address.
2731
:::

0 commit comments

Comments
 (0)