AWS CloudShell provides a browser-based command line without local CLI installation.
Browser shell and permissions
AWS CloudShell is a browser-based shellA command-line environment in which a user runs commands. for running AWS CLI commands without installing command-line tools locally. It normally uses the credentials from the AWS Management Console session.
How it works
- Sign in to the console and launch CloudShell. IAM permissions control whether you can create and start the environment and session.
- Run the pre-installed AWS command line interface (CLI) using Bash, PowerShell or Z shell. Console credentials are normally forwarded; if forwarding is denied, configure credentials manually. AWS still evaluates applicable policies for each request.
- Use the home directory for files that must persist between sessions, or create a virtual private cloud (VPC) environment. A VPC is an isolated virtual network. Select a subnetA range of IP addresses within a VPC., a range of network addresses, and security groupsA set of rules controlling traffic to and from associated resources., which control allowed traffic. A VPC environmentA CloudShell environment that uses a selected VPC, subnet and security groups. has no persistent storageStorage whose data remains available between shell sessions..
Exam cues
- If the question says run AWS CLI commands without a local installation, think CloudShell, because the CLI is pre-installed in the browser-based shell.
- If the question says reach resources in a private VPC, think a CloudShell VPC environment, because it uses the selected subnet and security groups.
- If the question says prevent automatic forwarding of console credentials, think deny
cloudshell:PutCredentials, because users must then configure credentials manually.
Remember
- Outside VPC environments, the private home directory has 1 GB of persistent storage per Region. Files may be deleted after 120 days without a session in that Region.
- A VPC environment deletes its home directory on timeout, deletion or restart. Creating one also requires VPC-specific EC2 permissions.
- Inactivity ends sessions after 20 to 30 minutes, or 10 minutes in GovCloud. Continuous sessions end after about 12 hours.
- CloudShell itself has no additional charge; other AWS resources and standard data transfer rates still apply.
Trap: A running process does not count as interaction and cannot prevent an inactive CloudShell session from ending.
Trap: Denying console upload and download URLs does not block all file transfers; other clients can still transfer files.
Da documentação da AWS (19)
- CloudShell is a browser-based pre-authenticated shell launched from the AWS Management Console, with AWS CLI version 2 pre-installed.
- CloudShell supports Bash, PowerShell and Z shell.
- Console credentials are normally forwarded to CloudShell, but IAM can deny cloudshell:PutCredentials and require manual credential configuration.
- IAM policies control CloudShell access and which CloudShell actions are allowed.
- AWSCloudShellFullAccess grants permission to use CloudShell and all its features.
- AWS evaluates applicable policies to authorize requests made by a principal.
- Console launch requires CreateEnvironment, CreateSession, GetEnvironmentStatus and StartEnvironment permissions.
- CloudShell provides 1 GB of private persistent home directory storage per Region at no additional cost, except in VPC environments.
- Persistent storage in a Region is deleted after 120 days without launching CloudShell in that Region unless the user takes action.
- A CloudShell VPC environment uses a selected VPC, subnet and security groups.
- A VPC is a logically isolated virtual network in which AWS resources can be launched.
- A subnet is a range of IP addresses in a VPC.
- A security group controls traffic allowed to reach and leave the resources associated with it.
- A CloudShell VPC environment has no persistent storage, and its home directory is deleted on timeout, deletion or restart.
- Creating a VPC environment requires VPC-specific EC2 permissions, including permission to create a network interface.
- CloudShell sessions end after 20 to 30 minutes of inactivity, or 10 minutes in GovCloud; running processes do not count as interaction.
- A continuously running CloudShell session ends after approximately 12 hours even with regular interaction.
- Denying CloudShell file upload and download URL actions blocks the console transfer feature but does not prevent other file transfer clients.
- CloudShell has no additional service charge, but other AWS resources and standard data transfer rates are charged.
Flashcards
Nada para revisar aqui agora. Escolha outros tópicos ou outro filtro.
·
Todos os 9 flashcards em lista
Which AWS service provides a browser-based shell with AWS CLI access using console credentials?
AWS CloudShell. The CLI is pre-installed and console credentials are normally forwarded.
A developer needs a browser shell to reach resources in a private VPC. Which CloudShell environment can use that VPC?
A CloudShell VPC environment, configured with a VPC, subnet and security groups.
Does an AWS CloudShell VPC environment preserve files in its home directory after it times out?
No. VPC environments have no persistent storage and the home directory is deleted on timeout.
How can an operator use the AWS CLI to interact with infrastructure from a browser?
Launch AWS CloudShell from the AWS Management Console. It provides a pre-authenticated shell with AWS CLI version 2 installed.
A user can launch AWS CloudShell but cannot run an infrastructure command. What authorization should the team examine?
Check the policies applicable to the principal and the requested AWS action. CloudShell access and AWS request authorization are evaluated through IAM policies.
A team needs a browser shell in a selected VPC subnet to interact with private infrastructure. What can it configure?
Create an AWS CloudShell VPC environment with the required VPC, subnet, and security groups.
An administrator denies cloudshell:PutCredentials. Can a user still launch CloudShell and use console credentials automatically?
The user can launch it with the required launch permissions, but must configure credentials manually.
What permissions are needed to launch AWS CloudShell from the AWS Management Console?
Allow CreateEnvironment, CreateSession, GetEnvironmentStatus, and StartEnvironment.
Does AWSCloudShellFullAccess give a CloudShell user permission to call every AWS service?
No. The policy grants CloudShell access; AWS still evaluates applicable policies for each service request.