Whaleal Platform is now listed on AWS Marketplace and delivered as an AMI. Subscribe, launch an EC2 instance, open its address in a browser, and you have MongoDB deployment, monitoring, backup and diagnostics at your fingertips. This post walks the whole path: how to launch, which instance to pick, what you get once it's up, and how billing and support work.
Details are taken from the WAP listing on AWS Marketplace · the page itself is authoritative
Deploying a management platform yourself usually starts with dependencies, environments and versions. Delivering it as an AMI folds that groundwork into the image.
The image already contains the platform. Start the instance, wait for it to come up, and open it in a browser — no step-by-step installation.
The platform runs on an EC2 instance in your account, so networking, security groups and allowed sources are all under your own AWS configuration.
The subscription goes through AWS Marketplace and lands on your existing AWS bill — no separate procurement process to set up.
Everything happens in the AWS console — there's no installer to download.
Open the Whaleal Platform listing and choose to subscribe. You'll be asked to accept the vendor's end-user license agreement (EULA).
Launch an instance from the AMI you subscribed to. The listing names a recommended instance type (see the next section). Keep the disk at 500GB or more.
Once the instance is running, open http://instance-IP:80/ in a browser. If it doesn't load, first check that the security group allows your network to reach port 80.
After logging in you can deploy and manage clusters, view monitoring and configure backups. Make sure the WAP instance can reach the MongoDB deployments it will manage over the network.
The listing names the supported EC2 instance types. Unless you have a specific reason, start with the recommended one and adjust after watching real load.
Instance types come from the Marketplace listing; vCPU and memory are the standard AWS specs for those types. The "rough guidance" column is general sizing reasoning, not an official capacity commitment — evaluate against how many clusters you manage and how often you collect metrics.
These are the main capabilities named on the AWS Marketplace listing. Each one has a matching module in WAP.
Track query response time, connection counts and read/write throughput, and see trends before they hit the business.
Configure backup frequency and retention to fit your needs, and restore when you have to.
Deploy MongoDB clusters and resize them when needed, with fewer manual steps and fewer chances for error.
Manage database users, roles and permissions, with data-encryption-related capabilities.
Charts that show running state, supporting query tuning and routine inspection.
Get notified when something goes wrong, along with diagnostic leads. A user review on the listing also praises the timely, accurate alert diagnostics.
The following is compiled from the listing. Prices and terms can change at any time — before subscribing, go by what the Marketplace page shows.
This is general deployment advice, not a product requirement: restrict port 80 to your office network or a bastion host; confirm the disk is at least 500GB; confirm the WAP subnet can reach the MongoDB deployments it will manage; and plan a snapshot policy for this instance's data volume.
Want the full details from the listing first, or have a custom requirement? Get in touch with us directly.