From 9060775ce1c5c4f8e751f8f7e3268fbd279c12aa Mon Sep 17 00:00:00 2001 From: julianleonard123 Date: Wed, 15 Jan 2025 10:42:39 +0100 Subject: [PATCH] Update AWS private networking instructions due to changes in AWS Console. Signed-off-by: julianleonard123 --- pages/authzed/guides/setting-up-private-networking.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/authzed/guides/setting-up-private-networking.mdx b/pages/authzed/guides/setting-up-private-networking.mdx index fa709140..cd22adf0 100644 --- a/pages/authzed/guides/setting-up-private-networking.mdx +++ b/pages/authzed/guides/setting-up-private-networking.mdx @@ -31,7 +31,7 @@ Navigate to `VPC` → `Endpoints` → `Create Endpoint` and input the following | Option | Selection | | :-------------------:| :-------------------:| | Name tag | Choose whatever you want | -| Service category | Select “Other endpoint services” | +| Service category | Select “Endpoint services that use NLBs and GWLBs” | | Service name | Enter the "service name" provided to you by the AuthZed team | | VPC | Choose the VPC from where you will deploy your SpiceDB client. DNS resolution for your SpiceDB cluster endpoint address will only be available from this VPC. | | Subnets | You can deploy your VPC endpoint in one subnet per AZ. We recommend choosing all AZs where SpiceDB clients will exist. |