-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: update docs with info about multiple CIDR blocks and changes t… #3479
Conversation
Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-3478-content-bug-documentation-on-vpc-peering-configuration-needs-updating-as-it-was-not-accurate-for-their-setup |
…ing-configuration-needs-updating-as-it-was-not-accurate-for-their-setup
Hello @miqrc, @esclymeTS , just double-checking before I publish. I had another ticket (#3478) saying that they had issues with the VPC procedure. Did you have time to check that the procedure is correct? |
@billy-the-fish I reviewed the doc, and everything seems okay. |
#3479) * chore: update docs with info about multiple CIDR blocks, changes to pricing, and revalidate the procedure.
#3479) * chore: update docs with info about multiple CIDR blocks, changes to pricing, and revalidate the procedure.
Please review VPC Peering and AWS PrivateLink for updates about the pricing plans and CIDR block. If you could ask someone to do a quick validation of the procedure please. A customer said that they had issues: https://docs-dev.timescale.com/docs-3478-content-bug-documentation-on-vpc-peering-configuration-needs-updating-as-it-was-not-accurate-for-their-setup/use-timescale/3478-content-bug-documentation-on-vpc-peering-configuration-needs-updating-as-it-was-not-accurate-for-their-setup/vpc/