Operations Management

Getting Started with AWS Operations Instantly Using AWS CloudShell - A Guide to the Browser-Based Shell Environment

Launch with a single click from the console and start working immediately in an environment with AWS CLI, SAM CLI, and CDK pre-installed. Scripts are preserved with 1 GB of persistent storage.

約 3 分で読めます

Features and Use Cases of CloudShell

CloudShell is a browser-based shell environment that can be launched directly from the AWS Management Console. Simply click the terminal icon at the top of the console, and an Amazon Linux 2023-based shell starts up in seconds. Major tools such as AWS CLI v2, SAM CLI, CDK, Terraform, Python, Node.js, Git, jq, kubectl, and eksctl come pre-installed, allowing you to begin operating AWS resources without any additional installation. It is particularly useful when setting up a local environment is difficult, for temporary administrative tasks, and for rapid response during troubleshooting.

Authentication and Security

CloudShell automatically inherits the credentials of the IAM principal logged into the console. There is no need to configure access keys or manually set environment variables; the permissions available in the console can be used directly from the CLI. You can control access to CloudShell itself through IAM policies, restricting its use to specific users or roles. Each CloudShell environment is isolated per session, and you cannot access another user's environment. Sessions automatically stop after 20 minutes of inactivity, but data in persistent storage is retained.

Persistent Storage and Customization

CloudShell provides 1 GB of persistent storage per region in the home directory ($HOME). Scripts, configuration files, and .bashrc customizations are preserved across sessions. You can also install packages via pip or npm under $HOME. Upload (up to 1 GB) and download features make file transfers with your local machine straightforward. This is convenient for uploading CloudFormation templates for deployment or downloading query results. Note that persistent storage is automatically deleted if CloudShell is not used for 120 days, so backing up important files to S3 is recommended. For a comprehensive guide from basics to advanced usage of CloudShell, check out books on Amazon.

CloudShell Pricing

CloudShell is free to use. There are no additional charges for the compute environment, 1 GB of persistent storage, or any of the pre-installed tools. You only pay for the resources created or operated by AWS CLI commands executed from CloudShell. Sessions automatically terminate after 20 minutes of inactivity, and persistent storage is deleted after 120 days of non-use. Compared to the cost of setting up a local environment or the EC2 instance charges for Cloud9, CloudShell is the most cost-effective option for simple AWS operations and script execution.

Summary

CloudShell is a free shell environment that lets you start AWS CLI operations instantly from your browser. With pre-installed AWS CLI, Python, Node.js, and Git, you can begin working without any additional setup, and IAM credentials are automatically configured. The 1 GB persistent storage retains your scripts and configuration files, allowing you to continue work across sessions.

Related Services

AWS CloudShellA free managed shell environment that lets you run AWS CLI instantly from your browser

Related Articles

Getting Started with AWS Cloud9 - Setting Up and Using a Browser-Based IDEA cloud IDE that lets you complete AWS development entirely in the browser. Learn about Lambda development with a pre-installed SAM CLI environment and pair programming through real-time collaborative editing.Browser-Based Shell Environment - Instant CLI Access with AWS CloudShellExplains the browser-based shell environment powered by AWS CloudShell. Covers the CLI environment available instantly from the AWS Management Console, pre-installed development tools, automatic IAM authentication integration, secure file management, and practical tips for improving operational efficiency.Centralizing SaaS Audit Logs with AWS AppFabric - OCSF Standardization and Security Lake IntegrationLearn how AppFabric collects audit logs from SaaS applications, standardizes them to OCSF format, and builds analysis pipelines.

More on This Topic

How AWS Keeps Time Internally - Amazon Time Sync Service and Leap Second Smearing DesignLearn how Amazon Time Sync Service works, how GPS and atomic clocks provide high-precision time sources, the design decision to absorb leap seconds through smearing, and why time synchronization matters in distributed systems.Centralizing SaaS Audit Logs with AWS AppFabric - OCSF Standardization and Security Lake IntegrationLearn how AppFabric collects audit logs from SaaS applications, standardizes them to OCSF format, and builds analysis pipelines.Implementing Feature Flags with AWS AppConfig - Safe Configuration Deployment and RollbackRoll out configuration changes independently from code deployments using Linear and Exponential strategies. Ensure safety with automatic rollback triggered by CloudWatch alarms.Architecture Review - Systematically Evaluate Workloads with the AWS Well-Architected ToolLearn about architecture reviews using the AWS Well-Architected Tool. Covers evaluation based on the six pillars, improvement planning, and custom lens usage.Audit Log Design and Operations - Complete API Activity Recording with CloudTrailLearn how to design audit logs using AWS CloudTrail, including recording API activity, long-term storage in S3, and compliance automation through integration with AWS Config.Lessons from AWS Incident Reports (COE) - How Past Major Outages Shaped Design PrinciplesAnalyze the root causes of past major incidents including the S3 outage, us-east-1 DNS failure, and Kinesis outage from AWS's published Correction of Errors (COE) and incident reports, and explain how they changed AWS's design principles.Tag Design Determines Operations - Trivia and Practical Naming Conventions for AWS Resource Tagging StrategyWe explain why AWS resource tags are not just labels but the foundation for cost allocation, access control, and automation, covering tag key naming conventions, how to use the 50-tag limit, and governance through tag policies.Why AWS Service Quotas Exist - Multi-Tenant Design That Protects Shared InfrastructureExplain how AWS service quotas (formerly service limits) are not mere restrictions but a design to protect other customers in a multi-tenant environment, covering the noisy neighbor problem, soft vs hard limits, and what happens behind quota increase requests.

Similar Articles and Services

Browser-Based Shell Environment - Instant CLI Access with AWS CloudShellExplains the browser-based shell environment powered by AWS CloudShell. Covers the CLI environment available instantly from the AWS Management Console, pre-installed development tools, automatic IAM authentication integration, secure file management, and practical tips for improving operational efficiency.AWS CloudShellA browser-based, pre-authenticated managed shell environment for running AWS CLI and development tools directly from the consoleGetting Started with AWS Cloud9 - Setting Up and Using a Browser-Based IDEA cloud IDE that lets you complete AWS development entirely in the browser. Learn about Lambda development with a pre-installed SAM CLI environment and pair programming through real-time collaborative editing.Cloud IDE Development Environment - Building a Team Development Platform with AWS Cloud9Learn how to build a cloud-based integrated development environment with AWS Cloud9. This article covers full-stack development from the browser, real-time pair programming, CodeCommit integration, local Lambda testing, and other practical techniques to accelerate team development.