Cloud Shell Editor, Cloud Code, and Cloud Shell Terminal

Cloud-Native Development with Cloud Code and Editor

Integrated Development Environment

Cloud Code is a powerful extension that integrates Google Cloud services directly into the Cloud Shell Editor and Cloud Shell Terminal. This extension is available by default and allows developers to manage the entire lifecycle of their applications directly inside the web browser. It simplifies cloud-native development by providing customized templates and configuration snippets for services like Google Kubernetes Engine (GKE) and Cloud Run. By utilizing these integrated features, development teams can avoid switching between different tools and work much more efficiently.

Automated Build Cycles

To speed up development, Cloud Code uses Skaffold to automate the creation of Container Images and provide continuous feedback as you write code. Developers can build these containers using several integrated methods directly from their workspace. This automation ensures that shifting from local coding to active cloud deployment is fast and reliable. The supported container build methods include:

• Buildpacks compile secure images directly from source code without needing a Dockerfile.
• Jib provides an optimized pathway for containerizing Java applications.
• Docker serves as the standard platform for building and running containerized environments.

Kubernetes Manifest Management

Managing Kubernetes Manifests is made much simpler through intelligent authoring and real-time configuration validation. The editor provides real-time linting and context-based completions to ensure your YAML configuration files are completely accurate before deployment. You can easily deploy these configured applications to GKE or run them locally on test clusters like minikube. Catching and validating these manifest errors early prevents deployment failures and keeps your cloud infrastructure aligned with best practices.

Debugging and Monitoring

Cloud Code provides a tailored debugging experience that allows you to set breakpoints and step through code running on live clusters. The system automatically handles complex network tasks like port forwarding so that you can focus on resolving issues within your GKE or Cloud Run services. You can also monitor your applications using the integrated Log Viewer and Cloud Run Explorer to watch resource statuses and read real-time application logs. These tightly coupled tools enable developers to troubleshoot problems rapidly without leaving the editing environment.

Security and API Management

Security is enhanced through direct integration with Secret Manager, which lets you securely store and fetch sensitive information like API keys programmatically. Developers can also browse and enable Cloud APIs and install required client libraries directly within the editor interface. This centralized management ensures that all necessary cloud resources remain easily accessible while maintaining a strong security posture. Using these native features helps your team maintain strict security standards throughout both the implementation and management phases.

Management of the Cloud Shell Environment and Persistence

Cloud Shell Lifecycle and Environment

Cloud Shell provides a temporary virtual machine running a Debian-based operating system to help you manage your Google Cloud resources. This system is completely ephemeral, meaning the underlying virtual machine is automatically discarded after one hour of inactivity. Because it is designed for immediate administrative use, it comes pre-installed with the Google Cloud CLI (gcloud CLI) and other essential software development kits (SDKs). This ensures that operators can run management commands immediately without needing any local machine configuration.

Persistent Storage and Customization

To ensure your work is not lost when the temporary virtual machine is discarded, Google provides 5 GB of free persistent disk storage mounted as your home directory. This storage is completely private to each user and remains attached to your profile even when switching between different projects. Your files and custom configurations persist reliably across different sessions, meaning you do not have to recreate your workspace each time you log in. Important items that stay saved between your sessions include:

• Configuration files such as .bashrc and .vimrc which customize your command-line environment.
• Custom scripts and software binaries installed within the $HOME folder.
• Project files and general application data stored inside your home directory.

Cloud Shell Editor Capabilities

The Cloud Shell Editor is a built-in integrated development environment based on Code OSS. It allows you to browse directory trees and edit files directly in your web browser while keeping the Cloud Shell Terminal open in a split window. While you cannot install custom marketplace extensions in this environment, Cloud Code is pre-installed to assist you with developing cloud-native applications. This setup provides out-of-the-box management tools for Kubernetes clusters, Cloud Run services, and general cloud resource operations.

Application Testing and Secure Resource Connectivity

Browser-Based Command Line and Editor

Cloud Shell acts as a browser-based tool that provides a centralized command-line interface for managing Google Cloud resources. The accompanying Cloud Shell Editor allows developers to write, edit, and debug their code directly in the web browser. Because this environment comes pre-loaded with the Google Cloud CLI and other essential development tools, there is no need to install any software locally. This zero-setup environment allows developers to quickly build and test applications without the hassle of configuring local operating systems.

Cloud Code and Gemini Assist

Cloud Code integrates directly with Gemini Code Assist, which is an artificial intelligence collaborator designed to help you write and manage code. Developers can use natural language prompts to ask Gemini to write new functions, explain complex logic, or suggest fixes for errors. This integration significantly speeds up the development process by providing real-time assistance and reducing the time spent on repetitive tasks. By working alongside this AI assistant, developers can understand existing codebases faster and deploy high-quality code with fewer bugs.

Secure Connectivity Options

To safely test your applications, you can use the Web Preview feature to monitor local ports and view how your app functions. The Cloud Shell Terminal also supports port forwarding, which lets you establish secure connections to services running inside private networks. This secure path is often achieved by creating secure tunnels through Identity-Aware Proxy (IAP) to reach virtual machines that do not have public IP addresses. There are three key connectivity options available:

• Port Forwarding: Maps a local port on your virtual terminal to a remote cloud service for direct testing.
• Web Preview: Allows you to view and interact with web applications running on port 8080 through your browser.
• IAP Tunneling: Provides a secure, encrypted way to access private cloud resources without exposing them to the public internet.

Using these options allows you to validate application behavior while keeping your backend cloud infrastructure safe and private. By keeping resources off the public internet, you significantly reduce the attack surface of your application. This setup ensures that only authenticated developers can interact with active test services.

Troubleshooting and Remote Access

When a virtual machine experiences boot or networking issues, you can use the Serial Console to troubleshoot the problem in text mode. This tool provides interactive access to the virtual machine's system output, which is essential when standard SSH or RDP connections fail. For Windows-based machines, tools like Chrome Remote Desktop or IAP Desktop allow you to manage the graphical interface securely over the web. Having these alternative connection methods ensures that administrators can diagnose and fix instances even during major network failures.

IAM and Security Controls

Managing access to these development tools requires assigning specific Identity and Access Management (IAM) roles, such as the Service Usage Consumer role, to ensure only authorized users can enable and use APIs. You can further protect your project environment by using VPC Service Controls, which create a strict security perimeter around your resources to prevent data theft. This security boundary ensures that sensitive information stays within your trusted network and cannot be exfiltrated to the outside. Following the principle of least privilege ensures that your testing and implementation environments remain secure and organized.