Within Google Cloud, a project is the most basic unit of resource organisation. This means that any Google resources you deploy - such as networks, firewalls, load balancers, GCE instances, databases, Kubernetes clusters, serverless resources, and so on - must belong to one, and only one, Google project. The project thus represents a resource ownership boundary, a trust boundary, and a billing boundary.
Within the LZiaB environment, we can provision sandbox projects. These are Google projects where individuals or tenants are free to deploy resources and applications, experiment, and learn the environment. Most notably: sandbox projects are the only projects within LZiaB where individuals or tenants are allowed to deploy resources manually and using the Google Console.
All other projects in LZiaB require that resources are deployed via a special service account, using infrastructure-as-code. This is how we enforce our Cloud Principles; particularly around automation and immutable infrastructure.
We offer two different flavours of sandbox environment:
| Type | Purpose | Name |
|---|---|---|
| Individual | Allows individual users to: become familiar with GCP; learn and experiment; develop; test ideas. | {org}-ecp-sandbox-{firstname-lastname} |
| Tenant | Allows tenants (typically collections of multiple users) to: conduct early PoC work with their applications; develop; experiment; to develop infrastructure-as-code; with relatively unrestricted ability to deploy resources with the Google console. | {org}-ecp-sandbox-{tenant}-{project_name} |
You can view detailed billing information about your project in the billing reports dashboard
Short Description
LZiaB Individual Sandbox Project Request
Details
Please create a LZiaB individual sandbox.
Full Name:
Email address:
Role:
Purpose:
TODO: Confirm creation of tenant sandbox as part of tenant factory.
TODO: Confirm process for individual sandbox request.
TODO: Confirm process for individuals and tenants to view billing for their sandbox. (No access to link above.)