Initial setup
FPT MongoDB Enterprise builds on resources that already exist in your tenant. Five things must be in place before you can provision a cluster.
None of this is MongoDB-specific — it is the same FPT Cloud onboarding every Database Engine service uses, so each row below links to the authoritative guide rather than repeating it here.
What you need
| Requirement | Where to set it up |
|---|---|
| A service agreement with a Project or Tenant, a VPC, and a Network | Contact the FPT Smart Cloud sales team via the FPT Smart Cloud contact page. This has the longest lead time — start here. |
| An active FPT Console Portal account | Register at https://fptcloud.com/, then verify the email you receive. Sign in with an FPT ID or your organization account. |
| RBAC permissions for Database Engine | Configure IAM — roles, user groups, the permission reference, and the FDE:hide_admin_password inversion. |
| A Subnet in the VPC | Create a Subnet. See also Subnet overview. |
| FPT Database Engine activated in the VPC | Activate FPT Database Engine service. Once per VPC, and it takes 8–10 minutes — see the section below. |
For the same prerequisites written from the relational-engine side, see Prerequisites.
Activating the service
This is the prerequisite people miss. An account and permissions are not enough on their own: until FPT Database Engine is activated in the VPC, the console offers no way to create a cluster. Activation works the same for MongoDB Enterprise as for every other engine, and the procedure is documented once in Activate FPT Database Engine service.
Two things the general guide does not spell out:
- Activation needs a permission most roles do not carry.
manageDatabase:ProvisionBackendis usually held only by a Tenant Admin or Cloud Platform Admin, because activating or deactivating the service affects database availability for the whole VPC. - Allow 8 to 10 minutes. Activation initializes the backend components clusters run on, so it is not instant. Deactivation takes about as long, and only works once the VPC holds no database resources at all.
The subnet must exist before you provision. The creation wizard asks you to select one and offers no way to create a subnet inline.
Next steps
- Create your first database once all five prerequisites are in place
- Features and architecture if you have not yet chosen between Standalone, Replica Set, and Sharded Cluster