When to use it
A VPS fits custom runtimes and services requiring OS-level control. Assign someone to manage Linux, software updates, access and backups. Start with Flash Deploy when your primary goal is deploying an app from source without operating a server.
Plans and Console
The catalog provides server type, location, OS image, billing cycle and plan choices. Instance details provide lifecycle actions and browser console access. Review the displayed configuration and price before creating a server.
Security
Use SSH keys where appropriate and configure access, firewall rules, software updates and backups. Private networking connects VPS services to other products in the same org, but you still need correct listening interfaces, ports and authentication.
Step by step
- Prepare an OS choice, SSH key, software requirements and a person responsible for the server.
- Open Resource/VPS and choose catalog, location, image, CPU/RAM and billing cycle. Review costs and create the instance.
- Wait until ready and use its actual address and login details. Do not assume every OS image uses root.
- Update the OS and configure access and firewall rules. Keep the current access session open while testing a new SSH session to avoid locking yourself out.
- Install the required runtime or Docker using its documentation, configure env and automatic startup, then test the app, DNS and HTTPS.
- Set up monitoring and backups, test recovery and inspect Billing. Stop/reboot interrupt service; stopping does not necessarily end all charges. Back up data before deleting an instance.