Provision the same way on your own infrastructure or in the cloud
The problem
- Teams that need some resources on infrastructure you run yourself and others directly in the cloud usually end up learning and maintaining a different process for each, slowing down both.
The solution
- Nest provisions storage the same way whether it ends up on your own infrastructure or directly in AWS, Azure, or GCP, so moving between them is a configuration choice, not a new project.
Outcomes
- One request process, whether the resource lands on your infrastructure or in the cloud.
- Data stored in the cloud is encrypted at rest the same way by default, across providers.
- Honest limitation: once a cloud volume or bucket is created, Nest does not yet resize it for you — plan initial sizing accordingly, or resize it directly with the cloud provider.