- Configuration files such as
.bashrc and .vimrc to maintain user preferences.
- Custom scripts and user-installed binaries located within the
$HOME path.
- Project files and other development data saved in the home folder.
This persistent layer ensures that a developer's workspace remains consistent every time they launch a session.
Cloud Shell Editor and Cloud Code
The Cloud Shell Editor is a browser-based integrated development environment built on Code OSS. It works alongside the Cloud Shell Terminal, allowing developers to edit files and run commands in a single interface. Although users cannot install custom extensions, the editor includes pre-installed Cloud Code to manage cloud-native applications. This integration provides built-in tools to manage Kubernetes clusters, deploy Cloud Run services, and handle basic API tasks.
Application Testing and Secure Resource Connectivity
Cloud Shell and Editor
Cloud Shell provides a web-based command-line interface for managing cloud resources without needing any local installation. Inside this environment, the Cloud Shell Editor serves as a complete development space to write, edit, and debug code from any browser. It comes pre-packaged with the Google Cloud CLI and other common development tools, removing the need to configure complex local environments. This out-of-the-box configuration allows developers to start building and deploying applications instantly.
Cloud Code and Gemini Assist
Cloud Code enhances the browser editor with specialized tools designed specifically for cloud-native workflows. It integrates directly with Gemini Code Assist, an artificial intelligence collaborator that provides real-time help. Developers can use natural language prompts to ask Gemini to write new functions, explain complex application logic, or recommend fixes for code errors. This automated assistance speeds up the development lifecycle by reducing repetitive manual tasks.
Secure Resource Connectivity
To test applications before deployment, developers can use Web Preview to monitor local ports and preview web traffic. When accessing resources on private networks, the Cloud Shell Terminal can establish secure tunnels using Identity-Aware Proxy (IAP). This allows developers to route traffic to private virtual machines without exposing them to the public internet. Common connectivity tools include:
- Port Forwarding: Connects a local terminal port directly to a remote private service.
- Web Preview: Routes traffic through port 8080 to display the web application in a browser.
- IAP Tunneling: Wraps traffic in HTTPS to safely access private VM instances.
These methods allow for thorough application testing while maintaining strong network boundaries.
Troubleshooting and Remote Access
If a virtual machine fails to boot or loses network connectivity, the Serial Console provides an interactive text-mode connection for troubleshooting. This direct console access works even when primary connection methods like SSH or RDP are unavailable. For Windows instances, administrators can use Chrome Remote Desktop or IAP Desktop to establish a secure graphical session. Having multiple fallback connection methods ensures that infrastructure issues can be resolved during network failures.
IAM and Security Controls
Access to these cloud tools is protected by specific IAM roles, such as the Service Usage Consumer role, which controls who can enable and use APIs. To prevent data exfiltration, organizations can implement VPC Service Controls to define a security perimeter around their resources. This boundary blocks unauthorized external access and ensures that sensitive data remains within the trusted network. Applying these security controls follows the principle of least privilege, keeping the development and testing environments secure.
StudyCerts
StudyCerts