Private traffic edit (#564)

neo4j · Dec 18, 2024 · 7f24bfc · 7f24bfc
1 parent c15d8ba
commit 7f24bfc
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/modules/ROOT/pages/platform/security/secure-connections.adoc b/modules/ROOT/pages/platform/security/secure-connections.adoc
@@ -15,7 +15,7 @@ The Aura console resides in a separate VPC, isolated from the rest of the Aura s
 
 An Aura instance can be publicly available, completely private, or allow both public and private access.
 
-If private traffic is enabled, your Aura instances are public and traffic to them is allowed to traverse the public internet and they are accessible with the correct username and password.
+If public traffic is enabled, your Aura instances are public and traffic to them is allowed to traverse the public internet and they are accessible with the correct username and password.
 
 To make your instance completely private, you need to disable public traffic, use the cloud provider's network, and create a private endpoint inside your VPC, which gives you a private connection to Aura.
 The only way to connect to your database is from inside your network (your VPC in your AWS/Azure/GCP account) using an internal IP address you choose and DNS records you create.