Skip to content

Commit 9b4cb7b

Browse files
authored
Docs Cloud Section Styling Batch #3 - Keep Original File Names (#312)
* Revert "Revert "Docs Cloud Section Styling Batch #3 (#309)" (#311)" This reverts commit 82481ff. * do not redirect in vercel.json * revert file names * revert file names x02 * fix links
1 parent 82481ff commit 9b4cb7b

File tree

11 files changed

+356
-206
lines changed

11 files changed

+356
-206
lines changed

docs/cloud/backups.md

Lines changed: 39 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,21 @@ sidebar_position: 6
66

77
## Overview
88

9-
- Dragonfly Cloud supports [manual on-demand](#manual-on-demand-backups) and recurring [scheduled backups](#scheduled-backups).
10-
- Dragonfly Cloud supports [importing Redis backups (RDB files)](#importing-redis-backups-rdb) from a remote storage system.
11-
- Existing backups can be [restored](#restoring-from-backup) to an existing data store.
9+
Dragonfly Cloud supports [manual on-demand backups](#manual-on-demand-backups) and
10+
recurring [scheduled backups](#scheduled-backups).
11+
To ease the process of migrating data, [importing Redis backups (RDB files)](#importing-redis-backups-rdb)
12+
from a remote storage system is also supported.
13+
14+
Existing backups in your Dragonfly Cloud account can be [restored to an active data store](#restoring-from-backup)
15+
at any time.
1216

1317
## Manual On-Demand Backups
1418

1519
To create a manual on-demand backup, follow the steps below:
1620

17-
- Click the three-dot menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>) in the data store row.
21+
- Click the three-dot
22+
menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>)
23+
in the data store row.
1824
- Expand the **Backups** menu and select **Manual**, the backup drawer will open on the right.
1925
- Enter a meaningful **Description** that will help you identify the backup later for restoration.
2026
- Set the **Retention** period to the number of days after which the backup will be deleted automatically.
@@ -26,49 +32,61 @@ View created backups under the [Account > Backups](https://dragonflydb.cloud/acc
2632

2733
To set a recurring scheduled backup, follow the steps below:
2834

29-
- Click the three-dot menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>) in the data store row.
35+
- Click the three-dot
36+
menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>)
37+
in the data store row.
3038
- Expand the **Backups** menu and select **Schedule**, the backup drawer will open on the right.
3139
- Set the **Backup Policy** to **Enabled**, the **Schedule** options will appear.
32-
- Select the day(s) of the week (or **Every Day**) and hours of the day (or **Every Hour**) to set when the scheduled backup should be created.
40+
- Select the day(s) of the week (or **Every Day**) and hours of the day (or **Every Hour**) to set when
41+
the scheduled backup should be created.
3342
- Set the **Retention** period to the number of days after which the backup will be deleted automatically.
3443
- Click **Apply**.
3544

36-
You can edit the backup schedule anytime.
45+
You can edit the backup schedule anytime.
3746

38-
## Restoring from Backup
47+
## Restoring from Backup
3948

40-
To restore a backup in an existing data store, follow the steps below:
49+
To restore a backup in an existing data store, follow the steps below, **with caution**:
4150

42-
- Click the three-dot menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>) in the row of the data store you would like to restore to.
43-
- The restore backup drawer will open on the right.
44-
- Select the backup you want to restore and click **Restore**.
45-
- ***CAUTION: This operation cannot be undone. It will clear all data in the data store and replace it with the backup.***
51+
- ***CAUTION: This cannot be undone. It will clear all data in the data store and replace it with the backup.***
52+
- Click the three-dot
53+
menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>)
54+
in the row of the data store you would like to restore to.
55+
- The **Restore Backup** drawer will open on the right.
56+
- Make **100% sure you select the correct backup** from the dropdown.
57+
- Click **Restore**.
4658

47-
## Viewing and Deleting Backups
59+
## Viewing and Deleting Backups
4860

4961
- You can view all backups under the [Account > Backups](https://dragonflydb.cloud/account/backups) tab.
50-
- To delete a backup, click the three-dot menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>) in the backup row and click **Delete**.
62+
- To delete a backup, click the three-dot
63+
menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>)
64+
in the backup row and click **Delete**.
5165

5266
## Importing Redis Backups (RDB)
5367

5468
You can import Redis backups (RDB files) to Dragonfly Cloud from a remote storage system.
55-
Once imported, the backup will be visible under the [Account > Backups](https://dragonflydb.cloud/account/backups) tab and will be available for restoration as described above.
69+
Once imported, the backup will be visible under the [Account > Backups](https://dragonflydb.cloud/account/backups)
70+
tab and will be available for restoration.
5671

5772
To import a Redis backup, follow the steps below:
5873

5974
- Navigate to the [Account > Backups](https://dragonflydb.cloud/account/backups) tab.
60-
- Click on the **+ Import RDB** button.
75+
- Click on the **+Import RDB** button.
6176
- Enter a meaningful **Description** that will help you identify the backup later for restoration.
6277
- Set the **Retention** period to the number of days after which the imported backup will be deleted automatically.
63-
- Enter the HTTP **Source URL** of the RDB file to import.
78+
- Enter the HTTP **Source URL** of the RDB file to import.
6479
- Chose the **Target Cloud** to import to, must match the cloud of the data store you want to restore to.
6580
- Chose the **Target Region** to import to, preferably match the region of the data store you want to restore to.
6681
- Click **Import**.
67-
- Once the backup is visible in status **Ready** you can restore it to a data store as described in [Restoring from Backup](#restoring-from-backup).
82+
- Once the backup is visible in status **Ready**, you can restore it to a data store as
83+
described [above](#restoring-from-backup).
6884

6985
### RDB File Accessibility
7086

7187
- The imported RDB file URL must be publicly accessible via HTTP(S) over the internet.
7288
- It is most secure to use a signed URL with a short expiration time to import the RDB file.
73-
- See [AWS S3 pre-signed URLs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html) or [Google Cloud Storage signed URLs](https://cloud.google.com/storage/docs/access-control/signed-urls) for more information.
74-
- Otherwise, you can generate a long random URL and delete the file after import to ensure security.
89+
- See [AWS S3 presigned URLs](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html)
90+
or [Google Cloud Storage signed URLs](https://cloud.google.com/storage/docs/access-control/signed-urls)
91+
for more information.
92+
- Otherwise, you can generate a long random URL and delete the file after import to ensure security.

docs/cloud/bandwidth.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ sidebar_position: 9
66

77
## Overview
88

9-
- For heavy network traffic workloads, please refer to the following tables to understand the network bandwidth available for each data store size and compute tier in various cloud providers.
10-
- For more customized network bandwidth requirements, please contact support.
9+
For heavy network traffic workloads, please refer to the following tables to understand the network bandwidth available for each data store size and compute tier in various cloud providers.
10+
If you have more customized network bandwidth requirements, please contact support.
1111

12-
## AWS
12+
## Amazon Web Services (AWS)
1313

1414
- AWS provides burstable network bandwidth for certain data store sizes.
1515
- Burst bandwidth can be used for short periods of time but is not guaranteed.
@@ -38,7 +38,7 @@ sidebar_position: 9
3838
| Extreme | 100 | 20 | - |
3939
| Extreme | 200 | 25 | - |
4040

41-
## GCP
41+
## Google Cloud Platform (GCP)
4242

4343
| Compute Tier | Size (GB) | Bandwidth (Gbps) |
4444
|--------------|-----------|-------------------|

docs/cloud/cloud.md

Lines changed: 31 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,40 @@
11
---
22
title: Dragonfly Cloud
3-
description: Dragonfly is a modern in-memory datastore, fully compatible with Redis & Memcached APIs. Learn how to use Dragonfly with our comprehensive documentation.
3+
description: Dragonfly is a modern in-memory data store, fully compatible with Redis & Memcached APIs. Learn how to use Dragonfly with our comprehensive documentation.
44
sidebar_position: 0
55
slug: /cloud
66
---
77

88
# Dragonfly Cloud
99

10-
Dragonfly Cloud is an in-memory data store service fully managed by the Dragonfly team.
11-
Dragonfly Cloud deploys Dragonfly instances providing full API compatibility with Redis, ValKey and Memcached.
12-
Hosted on AWS and GCP, Dragonfly Cloud is designed to be cost efficient, highly available, secure and simple to operate.
10+
## Overview
1311

14-
To create a Dragonfly Cloud data store visit [Data Stores](/docs/cloud/datastores.md).
12+
Dragonfly Cloud is an in-memory data store service fully managed by the Dragonfly team.
13+
14+
Dragonfly Cloud deploys [Dragonfly](https://github.com/dragonflydb/dragonfly) instances (the exact same
15+
technology without gated features), providing full API compatibility
16+
with [Redis](https://github.com/redis/redis), [Valkey](https://github.com/valkey-io/valkey),
17+
and [Memcached](https://github.com/memcached/memcached).
18+
19+
Hosted on Amazon Web Services (AWS), Google Cloud Platform (GCP), and other cloud providers, Dragonfly Cloud is designed
20+
to be cost-efficient, highly available, secure, and simple to operate.
21+
22+
## Managing Data Stores & Networks
23+
24+
- [Getting Started](getting-started.md)
25+
- [Managing Data Stores](datastores.md)
26+
- [Managing Private Networks](networks.md)
27+
- [Managing Peering Connections](connections.md)
28+
29+
## Monitoring & Backups
30+
31+
- [Monitoring Data Stores](monitoring.md)
32+
- [Creating & Managing Backups](backups.md)
33+
34+
## Other Dragonfly Cloud Features
35+
36+
- [Managing Dragonfly Cloud Users](users.md)
37+
- [Dragonfly Cloud Pricing](pricing.md)
38+
- [Dragonfly Cloud Support Plans](support.md)
39+
- [Dragonfly Cloud Data Retention Policy](data-retention.md)
40+
- [Data Store Network Bandwidth Limits](connections.md)

docs/cloud/connections.md

Lines changed: 55 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -4,36 +4,58 @@ sidebar_position: 4
44

55
# Peering Connections
66

7-
*Peering connections* are used to connect a Dragonfly Cloud private network with a VPC in your cloud account to establish communication between the two networks over private IP space.
8-
9-
Private IP space communication is more secure, performant and reduces data transfer costs incurred by cloud providers.
10-
11-
Once you create a *private network* as described in [Networks](./networks), click the network three dots menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>) and click *+ Connect*
12-
13-
Continue to [AWS](#aws) or [GCP](#gcp) based on your cloud provider.
14-
15-
16-
## AWS
17-
Specify the *region*, *CIDR*, *account ID* (also called owner ID in AWS) and *VPC ID* of your AWS VPC from where you want to connect and click *Create*.
18-
19-
The connection will be created in an **Inactive** state.
20-
21-
Following, you should accept the peering connection in your AWS account console (VPC > Peering Connections).
22-
Create a route in your AWS VPC, set the destination to the CIDR of the Dragonfly Cloud private network, set the target to the AWS peering connection ID.
23-
More information about AWS peering connection [here](https://docs.aws.amazon.com/vpc/latest/peering/create-vpc-peering-connection.html).
24-
25-
Modify your relevant security groups to allow traffic from the Dragonfly cloud Private Network CIDR.
26-
27-
At this point you should see the connection in state **Active** in the Dragonfly Cloud console.
28-
29-
If you haven’t done so already, create a data store with a private endpoint. See [Data Stores](./datastores#private-endpoint) for more information.
30-
31-
32-
## GCP
33-
Specify the *CIDR*, GCP *project ID* and *VPC ID* of your GCP VPC from where you want to connect and click Create.
34-
35-
The connection will be created in an **Inactive** state. Follow the Google Cloud guide <a href="https://cloud.google.com/sdk/gcloud/reference/compute/networks/peerings/create">here</a> , specify `--peer-network` and `--peer-project` with the VPC ID and account ID values from the Dragonfly Cloud private network you wish to connect. Observe the connection becomes **Active** after a few moments.
36-
37-
Don't forget to modify your firewall to allow traffic from the Dragonfly cloud Private Network CIDR.
38-
39-
If you haven’t done so already, create a data store with a private endpoint.
7+
## Overview
8+
9+
**Peering connections** are used to connect a Dragonfly Cloud private network with a VPC in your
10+
cloud provider account to establish communication between the two networks over private IP space.
11+
Private IP space communication is **more secure, more performant,
12+
and reduces data transfer costs** incurred by cloud providers.
13+
14+
Once you have a private network created, as described in the [networks](./networks) section,
15+
you can create a peering connection by clicking the three-dot
16+
menu (<svg xmlns="http://www.w3.org/2000/svg" height="24px" viewBox="0 -960 960 960" width="24px" fill="#e8eaed"><path d="M480-160q-33 0-56.5-23.5T400-240q0-33 23.5-56.5T480-320q33 0 56.5 23.5T560-240q0 33-23.5 56.5T480-160Zm0-240q-33 0-56.5-23.5T400-480q0-33 23.5-56.5T480-560q33 0 56.5 23.5T560-480q0 33-23.5 56.5T480-400Zm0-240q-33 0-56.5-23.5T400-720q0-33 23.5-56.5T480-800q33 0 56.5 23.5T560-720q0 33-23.5 56.5T480-640Z"/></svg>)
17+
on the right side of the network and then clicking the **+Connect** button,
18+
or simply by clicking the **+Add Connection** button under the network itself.
19+
20+
Continue to the next sections for instructions on how to create a peering connection with your cloud provider.
21+
22+
## Amazon Web Services (AWS)
23+
24+
Follow the steps below to create a peering connection within the Dragonfly Cloud console,
25+
and then accept the peering connection in your AWS account console:
26+
27+
- In the **Networks** tab of the Dragonfly Cloud console, click the **+Add Connection** button,
28+
and a dialog will appear.
29+
- Specify a **Name**, the **Acceptor Region**, the **Acceptor Account ID** (also called owner ID in AWS),
30+
and the **Acceptor VPC ID** of your AWS VPC from where you want to connect, and click **Create**.
31+
- The connection will be created in the **Inactive** status.
32+
- Next, you should accept the peering connection in your AWS account console (**VPC > Peering Connections**).
33+
- Create a route in your AWS VPC, set the destination to the CIDR of the Dragonfly Cloud private network,
34+
and set the target to the AWS peering connection ID.
35+
- You can read more about AWS peering
36+
connections [here](https://docs.aws.amazon.com/vpc/latest/peering/create-vpc-peering-connection.html).
37+
- Modify your relevant security groups to allow traffic from the Dragonfly Cloud private network CIDR.
38+
- Observe the connection becoming **Active** after a few moments in the Dragonfly Cloud console.
39+
40+
If you haven't done so already, create a data store with a private endpoint and start building your applications with
41+
it. Read more about creating a data store with a private endpoint [here](./datastores#private-endpoint).
42+
43+
## Google Cloud Platform (GCP)
44+
45+
Follow the steps below to create a peering connection within the Dragonfly Cloud console,
46+
and then accept the peering connection in your GCP account console:
47+
48+
- In the **Networks** tab of the Dragonfly Cloud console, click the **+Add Connection** button
49+
and a dialog will appear.
50+
- Specify a **Name**, the **Acceptor Account ID** (the GCP project ID),
51+
and the **Acceptor VPC ID** of your GCP VPC from where you want to connect, and click **Create**.
52+
- The connection will be created in the **Inactive** status.
53+
- Next, you should accept the peering connection using your GCP account.
54+
- Follow the Google Cloud guide [here](https://cloud.google.com/sdk/gcloud/reference/compute/networks/peerings/create),
55+
specify `--peer-network` and `--peer-project` with the **VPC ID** and **Account ID** values from the Dragonfly Cloud
56+
private network you wish to connect.
57+
- Observe the connection becoming **Active** after a few moments in the Dragonfly Cloud console.
58+
- Don't forget to modify your firewall to allow traffic from the Dragonfly Cloud private network CIDR.
59+
60+
If you haven't done so already, create a data store with a private endpoint and start building your applications with
61+
it. Read more about creating a data store with a private endpoint [here](./datastores#private-endpoint).

docs/cloud/data-retention.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,4 @@ sidebar_position: 9
1818
## Dragonfly Cloud Operations
1919

2020
- If the Dragonfly Cloud operations team takes a backup of a data store, the backup is deleted as soon as possible and is never retained for more than 60 days.
21-
- For details regarding the processing of Dragonfly Cloud users' data, please refer to the [Privacy Policy](https://www.dragonflydb.io/privacy).
21+
- For details regarding the processing of Dragonfly Cloud users' data, please refer to our [Privacy Policy](https://www.dragonflydb.io/privacy).

0 commit comments

Comments
 (0)