search

scylladb / scylladb-cloud-doc-issues

A repo for Scylla Cloud docs issues
https://cloud.docs.scylladb.com/stable/
1 stars 1 forks source link

docs: Issue in page Configure Virtual Private Cloud (VPC) Peering with AWS #15

Open tarzanek opened 6 months ago

tarzanek commented 6 months ago

I would like to report an issue in page https://cloud.docs.scylladb.com/master/cluster-connections/aws-vpc-peering

Problem

172.31.0.0/16 is still mentioned there, which is too big

Suggest a fix

I think CIDR is now smaller should be 172.31.0.0/24

but someone from cloud team should clarify

annastuchlik commented 4 months ago

@gmizrahi Could you assign this issue to somebody who could verify the above?

gmizrahi commented 4 months ago

@charconstpointer - this is under the 'networking domain' - can you ACK ?

charconstpointer commented 4 months ago

@charconstpointer - this is under the 'networking domain' - can you ACK ?

yup, we will take care of that

carlosms commented 4 months ago

The customer's VPC network block should not intersect with the network of the scylla DC block.

The network for the scylla DC is configured during creation, so we can't know for sure the exact value. I just checked in production, and indeed by default we are using 172.31.0.0/24. But this can be changed by the customer.

image

charconstpointer commented 4 months ago

Just to add $0.02 here /16 is still a valid cluster CIDR in Scylla Cloud as of today - that means the Configure Virtual Private Cloud (VPC) Peering with AWS page contains valid information, what I would suggest to reduce potential confusion is to add a comment at the beginning of the article that mentions "this document assumes your cluster was created with a CIDR of X.X.X.X/YY - you may need to adjust following commands to suite your setup" or something along these lines