Overview
QMCLOUD is a No Code platform for composing and deploying cloud infrastructure. QMCLOUD supports common infrastructure resources including Virtual Network, Virtual Machines (VM) and modern resources such as Containers and Serverless. The AWS marketplace product supports AWS and Azure platform.
Highlights
- Compose and deploy cloud infrastructure using a canvas, with a deployment wizard or predefined templates
- Visualize, edit and track changes of the deployed cloud infrastructure
Details
Typical total price
$0.846/hour
Features and programs
Financing for AWS Marketplace purchases
Pricing
Instance type | Product cost/hour | EC2 cost/hour | Total/hour |
|---|---|---|---|
t3.large | $0.117 | $0.083 | $0.20 |
m5.large Recommended | $0.75 | $0.096 | $0.846 |
Additional AWS infrastructure costs
Type | Cost |
|---|---|
EBS General Purpose SSD (gp2) volumes | $0.10/per GB/month of provisioned storage |
Vendor refund policy
No refunds are typically offered. Please contact us at support@appmodz.net for details.
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
updated 05/04/2023
The developer edition version is limited to one organization, one user, and one workspace.
This version includes cloud infrastructure deployment capabilities for many AWS and Azure platform components including AWS VPC, Subnets, Gateway, Routing, EC2, RDS, EKS, Azure Resource Groups, Virtual Networks, Virtual Machines etc.
Updates:
-
Updated startup script to set auto password to the aws ec2 instance id to minimize user interaction. Use the "start_the_containers.sh" to start qmcloud containers instead of the gather script
-
QMCLOUD now supports multiple platforms and the instance now is pre-loaded with all AWS, Azure, K8 and vSphere available components and the user doesn't need to add the components manually. Please note that the canvas UI load times may be affected and will depend on the chosen instance size.
-
Fixed minor bugs for group components and auto layout and connections on canvas.
-
The software is now renamed to QMCLOUD
Additional details
Usage instructions
- Pre-requisites
a) Choose an appropriate DNS Domain Name and URL to host the QMCLOUD platform in your environment. b) Choose an appropriate name and password for the Postgres database service in QMCLOUD c) Optional - Setup, Configure AWS application load balancer Internet facing, target groups, ssl certificate or use another proxy and routing solution as per your requirements d) Create and setup appropriate DNS A/CNAME records e) Pulumi - You will need a free Pulumi account at a minimum. Refer to the documentation for further details at https://docs.qmcloud.io
- Launch AMI
a) Launch the marketplace AMI into a desired VPC and subnet (preferably private) b) ssh into the instance using the user ubuntu and the ssh key that was used to launch the ec2 instance c) Run the following commands/script:
cd /home/ubuntu/qcloud sudo bash start_the_containers.sh
The script does the following:
Sets the Postgres password to the ec2 instance id All the other inputs (mainly ports and names) are considered as default as listed in the script Creates .env files for each of the containers required for the application Starts all the required containers using docker run command
-
Check the status of all the containers by using this command: sudo docker ps -a
-
Optional - Setup AWS ALB (only if AWS ALB is being used for routing)
a) Create and configure two target groups / one for front end and one for backend b) Register the instance in both the target groups c) The frontend is configured to listen for port tcp/3005 d) The backend is configured to listen for port tcp/3006 d) Create the AWS application load balancer e) Create listeners for 80 and 443 each. Configure default forwarding for 80 and 443 to the front-end target group f) Configure additional rule for forwarding to backend using path-based routing for the path /api/* g) Configure DNS name for the FQDN used and point it to the CNAME of the load balancer
Note: If a user plans to use a solution other than AWS ALB, appropriate routing will need to be configured.
- Access the app
a) Navigate to the fqdn or URL for the instance or the load balancer as appropriate b) You will be prompted for the first user registration. The software will prompt for user details for the first admin user. c) An email is sent to the email address with the link to set the password. Set the password using the link received in the email. Note that if you use a private IP address or a URL that is not accessible from the Internet, you will need to access the URL using a jump server or a server in the VPC where the instance is launched
- You can now login using the email address and the password
Please contact us at support@appmodz.net for further help.
Resources
Vendor resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
