Skip to content
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.

Commit

Permalink
fix
Browse files Browse the repository at this point in the history
  • Loading branch information
wojcik-dorota committed Sep 29, 2023
1 parent 7d932b8 commit 8f2996a
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 1 deletion.
2 changes: 2 additions & 0 deletions .github/vale/dicts/aiven.dic
Original file line number Diff line number Diff line change
Expand Up @@ -273,6 +273,8 @@ untrusted
unaggregated
UpCloud
upsert
UUID
UUIDs
vectorizing
virtualized
VM
Expand Down
2 changes: 2 additions & 0 deletions .github/vale/styles/Aiven/capitalization_headings.yml
Original file line number Diff line number Diff line change
Expand Up @@ -132,6 +132,8 @@ exceptions:
- Transport Layer Security
- United States
- UpCloud
- UUID
- UUIDs
- Virtual Private Cloud
- VNet
- Workbench
Expand Down
2 changes: 1 addition & 1 deletion docs/platform/howto/vpc-peering-upcloud.rst
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ This article shows how to establish a network peering connection between Aiven a
About establishing Aiven-Upcloud peering
----------------------------------------

To set up a peering connection between Aiven and UpCloud, you need a VPC created for your Aiven project in `Aiven Console <https://console.aiven.io/>`_. On the UpCloud side, you can set up the peering connection via API. Since the API takes UUIDs of both networks as attrbutes, you need to identify the network UUIDs before calling the API.
To set up a peering connection between Aiven and UpCloud, you need a VPC created for your Aiven project in `Aiven Console <https://console.aiven.io/>`_. On the UpCloud side, you can set up the peering connection via API. Since the API takes UUIDs of both networks as attributes, you need to identify the network UUIDs before calling the API.

Limitations
-----------
Expand Down

0 comments on commit 8f2996a

Please sign in to comment.