Initial setup
FPT MongoDB Enterprise builds on resources that already exist in your tenant. Four 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. |
For the same prerequisites written from the relational-engine side, see Prerequisites.
What is specific to MongoDB Enterprise
Two points that the general guides above do not make for you:
- Activating the service is a separate, one-time step per VPC. Having an account and permissions is not enough — until FPT Database Engine is activated in the VPC, the console offers no way to create a cluster. See Activate FPT Database Engine service.
- 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.
note
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 four prerequisites are in place
- Features and architecture if you have not yet chosen between Single Node and Replica Set