Build Cloud Shell configurations with private networking, persistent storage, and environment settings.
Last verified: May 2026
Build Cloud Shell configurations with private networking, persistent storage, and custom environment settings.
Required Fields
compartmentIddisplayNameshellEnvironment.regionOutput will appear here...Your team's developers each spend ~2 hours setting up local OCI CLI environments (downloading credentials, configuring OCI config files, installing tools). The builder helps standardize: every developer uses Cloud Shell with private networking enabled to reach the dev VCN. New developer onboarding for OCI tooling drops from 2 hours to 5 minutes. The persistent home directory means custom scripts and configs persist across sessions.
Build Cloud Shell configurations with private networking, persistent storage, and environment settings. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
The builder constructs Cloud Shell configurations: persistent storage size selection, optional private networking config (VCN + subnet binding for accessing private resources), pre-installed tooling list documentation, and shell environment setup (custom .bashrc / .profile snippets for OCI CLI defaults, kubectl contexts, terraform backend config). Output documentation guides users through enabling these settings via the OCI console (Cloud Shell config is mostly UI-driven, not API-managed).
OCI Cloud Shell is FREE and includes pre-installed CLI tools, kubectl, oci CLI, ansible, terraform, and others. For most ad-hoc OCI operations, this is dramatically simpler than maintaining a local CLI environment with credentials. Persistent storage (5 GB) survives across sessions.
Cloud Shell has direct access to your tenancy with your user's IAM permissions — no extra auth needed. This is great for quick tasks but be careful about what you run there. For automation and CI/CD, use service accounts with explicit credentials, not Cloud Shell.
Private network mode lets Cloud Shell reach private VCN resources (private DBs, internal APIs) without bastion setup. Configure a network security group + private endpoint binding to enable this. Game-changer for debugging private-network workloads.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.