Skip to content

Commit 9153579

Browse files
ldecarvalho-docldecarvalho-doc
committed
fix(mdb): vpc pt 2
1 parent d3f7bf7 commit 9153579

File tree

5 files changed

+43
-23
lines changed

5 files changed

+43
-23
lines changed

‎menu/navigation.json‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2576,6 +2576,10 @@
25762576
"label": "Create a Database Instance",
25772577
"slug": "create-a-database-instance"
25782578
},
2579+
{
2580+
"label": "Connect a Database Instance to a Private Network",
2581+
"slug": "connect-database-private-network"
2582+
},
25792583
{
25802584
"label": "Connect to a Database Instance",
25812585
"slug": "connect-database-instance"

‎pages/managed-databases-for-postgresql-and-mysql/how-to/create-a-database.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Compared to traditional database management, which requires customers to provide
5050
- Choose your storage type and capacity. Two types of storage are available:
5151
- **Block Storage Legacy** - With this type, your storage is decoupled from your compute resources. You can increase your storage space without changing your node type. You can define your storage capacity by entering the desired amount in the box. The volume can be increased up to 10 TB.
5252

53-
- **Block Storage**: This storage type works like the [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy), while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB.
53+
- **Block Storage**: This storage type works like Block Storage Legacy, while providing lower latency and high resiliency through 5k or 15k IOPS. You can increase your volume to up to 10 TB.
5454

5555
- **Local SSD Storage** - Your storage is fixed and tied to your compute resource.
5656
<Message type="note">

‎pages/managed-databases-for-redis/how-to/create-a-database-for-redis.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Managed Database for Redis™<sup>*</sup> is a low-latency caching solution base
3838
- Select a node type.
3939
4. Configure your Network. You can select either:
4040

41-
- **Private Network**: allows your databases to communicate in an isolated and secure network without requiring a public IP address. If you select this option, you must either:
41+
- **Attach to Private Network**: allows your databases to communicate in an isolated and secure network without requiring a public IP address. If you select this option, you must either:
4242
- select an existing Private Network to attach from the drop-down or
4343
- create and attach a new one
4444

@@ -48,7 +48,7 @@ Managed Database for Redis™<sup>*</sup> is a low-latency caching solution base
4848
- Managed Databases for Redis™ are currently not compatible with the [Static NAT](/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/public-gateways/concepts/#public-gateway). You can use Public Gateways in [SSH bastion](/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding.
4949
</Message>
5050

51-
- **Public network**: resources in a public network are publicly visible by default. The default Access Control List (ACL) settings allow anybody to connect to resources in your network. You can restrict access by configuring ACLs.
51+
- **Set up public connectivity**: resources in a public network are publicly visible by default. The default Access Control List (ACL) settings allow anybody to connect to resources in your network. You can restrict access by configuring ACLs.
5252
5. Complete the remaining steps in the creation wizard:
5353
- Create credentials: add a name and set a password for your user.
5454
<Message type="important">

‎pages/managed-mongodb-databases/how-to/connect-database-private-network.mdx‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
meta:
3-
title: How to connect a Managed MongoDB® Database Instance to a Private Network
3+
title: How to connect an existing MongoDB® Database Instance to a Private Network
44
description: Instructions for connecting your MongoDB® Database Instance over a Private Network.
55
content:
6-
h1: How to connect a Managed MongoDB® Database Instance to a Private Network
6+
h1: How to connect an existing MongoDB® Database Instance to a Private Network
77
paragraph: Instructions for connecting your MongoDB® Database Instance over a Private Network.
88
tags: managed-mongodb mongodb private-network database-instance
99
dates:
@@ -18,7 +18,7 @@ categories:
1818

1919
Using Private Networks improves performance by reducing the latency between your application and your database nodes. It also increases the security of your databases, as Instances in your Private Network can directly communicate with your Database Instance, without passing through the public internet.
2020

21-
You can create new Database Instances to attach to your Private Network, or attach existing ones.
21+
You can [create new Database Instances](/managed-mongodb-databases/how-to/create-a-database-instance) to attach to your Private Network, or attach existing ones.
2222

2323
<Macro id="requirements" />
2424

@@ -29,15 +29,15 @@ You can create new Database Instances to attach to your Private Network, or atta
2929

3030
## How to attach a Database Instance to a Private Network
3131

32-
<Message type="note">
33-
You can only attach your Database Instance to one Private Network at a time.
34-
</Message>
32+
<Message type="note">
33+
You can only attach your Database Instance to one Private Network at a time.
34+
</Message>
3535

3636
1. Click **MongoDB®** under **Managed Databases** on the side menu. A list of your Database Instances displays.
3737
2. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
3838
3. Scroll to the **Network** section.
3939
4. Click **Attach Private Network** next to **Private endpoint**. A pop-up appears.
40-
5. Choose whether to:
40+
5. Choose one or both of the options below:
4141
- Select and attach an existing Private Network and select the network from the drop-down list.
4242
<Message type="important">
4343
The Database Instance must be attached to a Private Network in the same region.
@@ -48,7 +48,7 @@ You can create new Database Instances to attach to your Private Network, or atta
4848
</Message>
4949
6. Click **Attach to Private Network** to conclude.
5050

51-
<Message type="important">
51+
<Message type="note">
5252
Managed MongoDB® is currently not compatible with the [Static NAT](/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/public-gateways/concepts/#public-gateway). You can use Public Gateways in [SSH bastion](/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding.
5353
</Message>
5454

@@ -61,8 +61,8 @@ Once you have attached your Database Instance to a Private Network, you can [con
6161
1. Click **MongoDB®** under **Managed Databases** on the side menu. A list of your Database Instances displays.
6262
2. Click the database name or <Icon name="more" /> > **More info** to access the Database Instance information page.
6363
3. Scroll to the **Network** section.
64-
4. Click <Icon name="unlink" /> next to the static IP that you want to unlink from your Database Instance.
65-
5. Click **Detach Private Network** to remove the Instance from your Private Network.
64+
4. Click **Detach Private Network**. A pop-up appears.
65+
5. Click **Detach resource** to confirm.
6666

6767
<Message type="note">
6868
This action takes a few moments to complete. During this time, your Database Instance:

‎pages/managed-mongodb-databases/how-to/create-a-database-instance.mdx‎

Lines changed: 26 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -38,16 +38,32 @@ Document databases enable users to store and retrieve data in a document format,
3838
- **Replica-set 1-node** - an instance of MongoDB® that runs as a single server and does not provide redundancy or high availability.
3939
- **Replica-set 3-nodes** - a group of 3 MongoDB® servers (1 primary and 2 standby nodes) that maintain the same data set. Replica sets provide redundancy and high availability and are the basis for all production deployments. If the main node fails for any reason, one of the remaining standby nodes is assigned and can take over requests, reducing downtime.
4040
- Select a node type.
41-
- Define the size of your Block Storage volume. You can increase your storage space without changing your node type, with no downtime. You can increase your volume size to up to 10 TB.
42-
- Add a name and set a password for your user.
43-
<Message type="important">
44-
Your username must adhere to specific criteria.
45-
- Length must be between 1 and 63 characters
46-
- First character must be an alphabetic character (**a-Za-Z**)
47-
- It can not start with **_rdb**
48-
- Only **a-zA-Z0-9_$-** characters are accepted
49-
</Message>
41+
- Configure storage settings. You can:
42+
- Choose the [IOPS](/block-storage/concepts/#iops) setting, between **5k** and **15k**.
43+
- Define your volume size. Block Storage volumes can increase up to 10 TB.
44+
- Review the snapshot configuration. During the private beta, only manual snapshots are available.
45+
4. Configure your Network. Choose one or both of the options below:
46+
- **Attach to Private Network**: allows your databases to communicate in an isolated and secure network without requiring a public IP address. If you select this option, you must either:
47+
- Select and attach an existing Private Network and select the network from the drop-down list.
48+
<Message type="important">
49+
The Database Instance must be attached to a Private Network in the same region.
50+
</Message>
51+
- Create and attach a new Private Network and enter the name of the network in the form.
52+
<Message type="important">
53+
If you select this option, a Private Network with default settings will be created in the same region as your Database Instance. Do not use a TLD (e.g. dev, cloud) as a name, to avoid conflicts.
54+
</Message>
55+
- **Set up public connectivity**: resources in a public network are publicly visible by default. The default Access Control List (ACL) settings allow anybody to connect to resources in your network. You can restrict access by configuring ACLs.
56+
5. Complete the remaining steps in the creation wizard:
57+
- Create credentials: add a name and set a password for your user.
58+
<Message type="important">
59+
Your username must adhere to specific criteria.
60+
- Length must be between 1 and 63 characters
61+
- First character must be an alphabetic character (**a-Za-Z**)
62+
- It can not start with **_rdb**
63+
- Only **a-zA-Z0-9_$-** characters are accepted
64+
</Message>
5065
- Enter a name for your Database Instance.
51-
4. Click **Create a Database Instance** to confirm your choices and launch creation.
66+
- Review the estimated cost.
67+
4. Click **Create Database Instance** to confirm your choices and launch creation.
5268

5369
You are taken to the **Overview** tab for your Database Instance.

0 commit comments

Comments
 (0)