-
Notifications
You must be signed in to change notification settings - Fork 467
DOC-2994: Connectivity Section - Transit Gateway branch #2968
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
base: master
Are you sure you want to change the base?
Conversation
* copied greg's transit gateway docs * Text * Images * title cap * Change step to account for automatic acceptance
|
aliases: | ||
--- | ||
|
||
Redis offers a few ways you can securely connect your application and your database without exposing your application's [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Redis offers a few ways you can securely connect your application and your database without exposing your application's [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud). | |
Redis offers a few ways to securely connect your application and your database without exposing your application's [virtual private cloud](https://en.wikipedia.org/wiki/Virtual_private_cloud). |
|
||
## [Transit Gateway]({{<relref "/rc/subscriptions/connectivity/aws-transit-gateway">}}) | ||
|
||
[Amazon Web Services (AWS) Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/how-transit-gateways-work.html) acts as a regional virtual router for traffic flowing between your virtual private cloud(s) (VPCs) and on-premises networks. You can attach multiple different resources to a transit gateway, including your Redis Cloud and application VPCs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Amazon Web Services (AWS) Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/how-transit-gateways-work.html) acts as a regional virtual router for traffic flowing between your virtual private cloud(s) (VPCs) and on-premises networks. You can attach multiple different resources to a transit gateway, including your Redis Cloud and application VPCs. | |
[Amazon Web Services (AWS) Transit Gateway](https://docs.aws.amazon.com/vpc/latest/tgw/how-transit-gateways-work.html) acts as a regional virtual router for traffic flowing between your virtual private cloud (VPC) and on-premises networks. You can attach multiple different resources to a transit gateway, including your Redis Cloud and application VPCs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We try to avoid the "(s)" if we can. You state below this that multiple VPCs can be supported, so it's unnecessary here.
|
||
If you want to try out Redis 7.2, turn on the **Redis 7.2 preview** toggle: | ||
If you want to try out Redis 7.2, turn on the **Redis 7.2 regions** toggle to show the regions where it is available: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to try out Redis 7.2, turn on the **Redis 7.2 regions** toggle to show the regions where it is available: | |
If you want to try out Redis 7.2, turn on the **Redis 7.2 regions** toggle to show the available regions: |
|
||
### Proxy policies | ||
|
||
Redis Enterprise Software uses [proxies]({{<relref "/rs/references/terminology#proxy">}}) to manage and optimize access to database shards. Each node in the cluster runs a single proxy process, which can be active (receives incoming traffic) or passive (waits for failovers). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Redis Enterprise Software uses [proxies]({{<relref "/rs/references/terminology#proxy">}}) to manage and optimize access to database shards. Each node in the cluster runs a single proxy process, which can be active (receives incoming traffic) or passive (waits for failovers). | |
Redis Enterprise Software uses [proxies]({{<relref "/rs/references/terminology#proxy">}}) to manage and optimize access to database shards. Each node in the cluster runs a single proxy process, which can be active (receiving incoming traffic) or passive (waiting for failovers). |
|
||
Redis Enterprise Software uses [proxies]({{<relref "/rs/references/terminology#proxy">}}) to manage and optimize access to database shards. Each node in the cluster runs a single proxy process, which can be active (receives incoming traffic) or passive (waits for failovers). | ||
|
||
Configure the following default [proxy policies]({{<relref "/rs/databases/configure/proxy-policy">}}) to determine which nodes' proxies are active and bound to new databases by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Configure the following default [proxy policies]({{<relref "/rs/databases/configure/proxy-policy">}}) to determine which nodes' proxies are active and bound to new databases by default. | |
Configure the following default [proxy policies]({{<relref "/rs/databases/configure/proxy-policy">}}) to determine which proxies are active and bound to new databases by default. |
aliases: | ||
--- | ||
|
||
Downloads a support package, which includes logs and information about the cluster, nodes, databases, and shards, as a tar file called `filename.tar.gz`. Extract the files from the tar file to access the debug info. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Downloads a support package, which includes logs and information about the cluster, nodes, databases, and shards, as a tar file called `filename.tar.gz`. Extract the files from the tar file to access the debug info. | |
Download a support package, which includes logs and information about the cluster, nodes, databases, and shards, as a tar file called `filename.tar.gz`. Extract the files from the tar file to access the debug info. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason this needs to be passive "downloads" instead of active "download"?
Correct preview link |
Holding off on this until the site merge. |
Staging link: https://docs.redis.com/staging/DOC-2994-tgw/subscriptions/connectivity
Similar to #2908, but with the Transit Gateway page moved.