Solutions / Development & testing
Make room to try the next thing.
Create Linux environments for development, staging, and integration testing. Keep experiments separate from production and give your team a repeatable setup process.
A starting configuration
Start with Shared CPU for light development. Compare CPU Optimized for parallel build jobs after measuring memory per worker.
Compare configurationsMake the environment recognizable
Choose a hostname and tags that identify the project and purpose. Select the operating system and SSH keys during configuration.
Keep setup repeatable
Maintain your application setup in your own scripts or deployment tooling. Take a named snapshot before a change you may want to reverse.
Retire completed experiments
Export any work you need, then use Remove in the server controls. A running or idle server continues its monthly subscription until it is removed.
Before it becomes your everyday environment.
Turn your deployment into a repeatable process. Record what runs where, how access is granted, and how you will recover when something needs attention.
Continue with the guide- Use test data in development environments.
- Estimate the prepaid monthly cost before ordering.
- Save work outside the environment before rebuilding.
- Remove unused servers and confirm billing status.
Find your next configuration.
Compare resources and current monthly prices in your chosen region.