Skip to main content

Create your first database

This is the path from an empty VPC to a MongoDB Enterprise cluster in Running status. It takes roughly 15 minutes, most of it waiting on the platform.

Two things happen here: the FPT Database Engine service is activated in your VPC (once per VPC, ever), then you provision a cluster into it.

Prerequisites​

Step 1. Activate the service in your VPC​

Until the service is activated, the console offers no way to create a database. Activation initializes the backend components and is needed once per VPC.

  1. Log in to FPT Cloud Portal.

  2. From the main menu, select Database Platform → All Databases.

    Database Engine Management page with the Activate Service button

  3. Click Activate Service.

Activation takes about 8–10 minutes. When the status reaches Active, you can provision clusters.

note

If the service is already Active in this VPC, skip to Step 2. Someone else on your team may have activated it.

Step 2. Open the provisioning wizard​

From the Database cluster list page, select Create a Database Engine (or Create). The wizard has three steps: database configuration, additional services, then review.

Step 3. Define the cluster​

Create new database cluster, step 1 — engine, network, and node configuration

General information

FieldWhat to enter
Engine TypeMongoDB
EditionEnterprise
Architecture TypeStandalone for one node, ReplicaSet for a replicated cluster, Sharded Cluster to partition data across shards
Engine VersionA supported version — see Database Engine Versions
warning

Architecture Type cannot be changed after creation. Choose ReplicaSet if this cluster might ever carry production data — moving later means provisioning a new cluster and migrating. Pick Sharded Cluster only when you already know one replica set will not hold the data; it starts at 11 nodes. See Choosing an architecture.

Network information

FieldWhat to enter
Edge GatewayThe gateway routing traffic between the cluster and other systems
NetworkThe Network/Subnet the cluster deploys into. This sets access scope and isolation.

Engine information

FieldRules
Cluster Name8–25 characters, starts with a letter, letters/numbers/hyphens only
Database Name8–25 characters, starts with a lowercase letter, lowercase letters/numbers/underscores only
Password / Confirm Password12–20 characters with uppercase, lowercase, a number, and a special character

Spaces and these characters are rejected in the password: / \ " ' < > ? % ; : $ ! [ ] { } ( ) , & +

Node configuration

FieldWhat to enter
Storage PolicyDefines IOPS. Use ≥ 4,000 IOPS for production.
Number Of NodesNode count matching the chosen architecture
FlavorvCPU and RAM per node
Data Disk Size (GB)Minimum 20 GB

On Sharded Cluster this section splits into three groups — Mongos, Shard, and ConfigServer — each sized on its own. Provision a database cluster has the field-by-field reference.

Click Next Step.

Step 4. Configure additional services​

Backup and PITR are enabled by default for MongoDB Enterprise clusters. What you set here is the maintenance window and who gets notified.

  • Enable Additional Service — turns add-on services on or off as a group. You can enable them later.
  • Maintenance Window — day of week and start time. Maintenance runs for 1 hour from that time.
  • Notification Recipients List — email addresses for backup and scaling events. Add more with the + button.

Click Next Step.

Step 5. Review and create​

Check the configuration. Back returns you to edit; Create confirms.

The system validates resources, then starts deploying. You are returned to the Database cluster list with the new cluster at the top in Processing status.

Creation typically takes 5–7 minutes. On success the cluster reaches Running.

note

If creation fails, delete the failed cluster and create it again. A failed cluster cannot be repaired in place.

Next steps​