Examples of using Aws-shell in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
To install the aws-shell, you use pip.
Automate AWS services by using the AWS CLI and the aws-shell.
If the aws-shell is installed, the aws> prompt is displayed.
For more information, see the AWS CLI and aws-shell Sample.
If you're using the aws-shell, omit the aws prefix from the preceding commands.
For example,you can use the AWS Command Line Interface(AWS CLI) or the aws-shell to run commands from a terminal session.
If you're using the aws-shell, you can stop using it by running the. exit or. quit command.
Step 1: Install and Configure the AWS CLI, the aws-shell, or Both in Your Environment.
If you want to use the aws-shell but haven't started it yet, start the aws-shell by running the aws-shell command.
Run the aws s3 mb command with the AWS CLI ors3 mb command with the aws-shell, supplying the name of the bucket to create.
The AWS CLI and the aws-shell are unified tools that provide a consistent interface for interacting with all parts of AWS.
Back in the environment,use the AWS CLI to run the aws configure command or the aws-shell to run the configure command.
You use the same commands with the aws-shell, except that you start commands without the aws prefix.
If you are using an AWS Cloud9 EC2 development environment, you can skip ahead to Step 3:Run Some Basic Commands with the AWS CLI or the aws-shell in Your Environment.
Step 1: Install the AWS CLI, the aws-shell, or Both in Your Environment.
You can use these keys when you access AWS services programmatically, either through one of the several AWS SDKs orby using the AWS Command Line Interface(AWS CLI) or the aws-shell.
Throughout this sample, if you're using the aws-shell, omit aws from each command that starts with aws.
If you are using an AWS Cloud9 EC2 development environment and you only want to use the AWS CLI, you can skip ahead to Step 3:Run Some Basic Commands with the AWS CLI or the aws-shell in Your Environment.
If you already installed and configured the AWS CLI, the aws-shell, or both in your environment, you don't need to do it again.
Each time the AWS CLI, the aws-shell, or your code calls an AWS service, the AWS CLI, the aws-shell, or your code must provide a set of AWS access credentials along with the call.
This sample enables you to set up theAWS Command Line Interface(AWS CLI), the aws-shell, or both in an AWS Cloud9 development environment.
In this step, you use the AWS CLI or the aws-shell in your environment to create a bucket in Amazon S3, list your available buckets, and then delete the bucket.
In this section, you use AWS Identity and Access Management(IAM)to generate a set of permanent credentials that the AWS CLI, the aws-shell, or your code can use when calling AWS services.
If you use the AWS CLI or the aws-shell, we recommend you configure the AWS CLI or the aws-shell with the credentials for an IAM administrator user in your AWS account.
If you must run a command that is not allowed by AWS managed temporary credentials,one approach would be to configure the AWS CLI or aws-shell in the environment with a set of permanent credentials, which removes this limitation.
Test the installation and configuration of the AWS CLI, the aws-shell, or both by running the DynamoDB list-tables command from a terminal session in your environment to list your existing DynamoDB tables, if there are any.
A read/write member maybe able to use the AWS CLI, the aws-shell, or AWS SDK code in your environment to take actions in AWS on your behalf.
If you have the AWS CLI or the aws-shell installed in your environment, you can use the aws configure command for the AWS CLI or the configure command for the aws-shell to store your permanent access credentials instead.
In this step, you use the AWSCloud9 IDE to install the AWS CLI, the aws-shell, or both in your environment so you can run commands to interact with AWS.