Cloud connector 9.3 updates #4284
Conversation
✅ Vale Linting ResultsNo issues found on modified lines! |
|
Keeping this as a draft for now until Smriti is back from PTO Dec 16 and can review |
| ::::{important} | ||
| In order to use cloud connector for an AWS integration, your {{kib}} instance must be hosted on AWS. In other words, you must have chosen AWS hosting during {{kib}} setup. | ||
| :::: | ||
| * To use a pre-existing cloud connector for this deployment, select **Existing connection** then the cloud connector's name. |
There was a problem hiding this comment.
Maybe we need to elaborate here what to expect under name for existing cloud connector. Since Cloud Connector name will be introduced in 9.3, for any cloud connector which was created before 9.3 in case of AWS the name will be Cloud Connector RoleARN and in case of Azure it will be Cloud Connector ID. If user wishes to rename the cloud connector to a more user friendly name they can do so by clicking edit button next to the selected cloud connector in the drop down, it leads to opening a flyout with cloud connector details and one can rename the cloud connector there.
There was a problem hiding this comment.
I'm going to add some of this info to the Cloud connector general page, and link to it from here, but not include the info here so the instructions don't get too long.
[DO NOT MERGE BEFORE FEATURE IS RELEASED IN SERVERLESS]
Fixes #4205 —
@smriti0321, does the limitation in point 2 above still apply to version 9.2?
Generative AI disclosure