Prepare the guest with cloud-init
Start from an available Linux image and supply an SSH key and supported initialization input. Keep repeatable setup instructions with your application so new environments begin with the configuration you intend.
Compute / Virtual machines
Your application. Your operating system.
Run a Linux guest on QEMU/KVM. Install your application packages and administer the operating system through SSH or its browser console.
- Runtime
- Linux guest on QEMU / KVM
- Bootstrap
- Supported image + cloud-init
- Access
- SSH key / browser console
- Application
- Web server + your runtime
- Data
- Guest storage; backups managed by you
Select CPU, memory, storage and the guest image in the published offer.
- Deployment input
- Linux image + initial configuration
- Administration
- Guest operating system access
- Best fit
- Custom stacks and self-managed databases
Application architecture / Virtual machines
Give a custom stack a place to run.
Use a VM for software that needs system packages, scheduled jobs or a custom Linux setup. Keep package versions and initialization instructions with your project. Connect a separate database through the network paths you configure.
What this gives you
A guest environment you can document, reproduce and maintain through your own release process.
Where it fits
What you can do with virtual machines.
For applications that need their own Linux environment, system packages or a database you administer yourself.
Control the operating system
Install packages, configure system services and choose the application runtime inside your guest. A VM is useful when the operating system itself is part of the deployment you need to manage.
Operate through the console
Inspect resource state, manage power and use the browser console for guest access. Follow the result of each action before investigating the application running inside the machine.
Create an on-demand restore point
Use snapshot and restore operations where the service supports them. Review application consistency and the data a restore replaces; keep independent backups for recovery beyond the guest.
In practice
Room for the stack you need.
Choose a VM when the application needs system packages, a particular Linux setup or direct control of a guest operating system.
A custom application stack
Install your web server, application runtime and supporting packages in one guest environment. Keep setup instructions alongside your project.
Plan for
Runtime versions, public ports and an update routine.
A database you administer
Give database software its own VM and restrict application connections to the services that need access.
Plan for
Working set, storage capacity and a tested independent backup.
A separate test environment
Prepare a guest for a release candidate or a dependency upgrade before applying the same changes to production.
Plan for
Representative test data, configuration differences and resource lifetime.
The workflow
From configuration to a running workload.
- 01
Choose an offer
Review the image, resource allocation, region and terms in the published offer.
- 02
Prepare access
Select an SSH key and provide the initial configuration supported by the deployment form.
- 03
Operate the guest
Connect, install your application and maintain its operating system and data.
Configuration checks
Prepare the operating environment.
- Select an image compatible with your application and initialization script.
- Keep the SSH key available and confirm an alternative console access path.
- Test application recovery and maintain backups outside the guest.
Responsibilities
Know what you maintain.
Virtual machines / Questions
A few details before you start.
How does a VM differ from a container?
A VM gives you a guest operating system to administer. A container starts with a packaged application image. Choose the VM when the operating system and system packages are part of what you need to control.
Can I run PostgreSQL or another database?
You can install compatible database software in your guest. Your team handles its configuration, updates, access, backups and recovery. This is a self-managed application deployment.
When should I use a snapshot?
Where supported, an on-demand snapshot can provide a restore point before a change. Plan for application consistency and retain an independent backup; restoring a snapshot can replace newer data.
Connected products