AWS provides two ways of infrastructure configurations
1) AWS ManagementWeb Console
2) AWS CLI (Command Line Interface)
Using the AWS web console:
++++++++++++++++++++++++++++++
It is a graphical method to connect to various AWS resources, their configuration,
modification, etc. It is simple to use and does not require knowledge of scripting.
AWS Command Line Interface:
++++++++++++++++++++++++++++++
Usually, the script provides you with the flexibility to manage multiple AWS
resources, infrastructures effectively.
For example, we can use the script to deploy multiple resources without the need to
go through a complete configuration wizard each time.
Prerequisites to Use AWS CLI
+++++++++++++++++++++++++++++
1) Create AWS Account: In order to configure AWS CLI, an AWS account needs to be
created if you do not have one. Please register for the AWS account. The new AWS
account includes 12 months of free tier access.
2) Install AWS CLI: AWS CLI is available for Windows, MAC and Linux distribution of
OS.
a) For windows : https://awscli.amazonaws.com/AWSCLIV2.msi (download and
install)
b) MAC and Linux: Please follow these steps (execute below commands)
$ sudo apt-get install -y python-dev python-pip
$ sudo pip install awscli
3) Once Installation completed then execute below commands
-> Open command prompt
-> Execute below command
$ aws --version (It should give AWS CLI version)
$ aws configure (To connect with AWS Cloud)
3) Create AWS IAM User with 'Programmatic Access' permission
User Creation Response
+++++++++++++++++++++++
On the user creation success screen, two important pieces of information are
provided.
1) Access Key ID
2) Secret access key
-> We are going to store this information securely and will not share this
information.
-> Alternatively, CSV file download option is available, CSV file contains the
details.
-> Safely store the key or downloaded “CSV” file, as we will not be able to
retrieved Secret Access Key again.
-> Click on close and you will end up on the user dashboard. The newly created user
is available now.
AWS CLI – Configuration
+++++++++++++++++++++++
Step1: Click on the demo user, the pertinent details corresponding to user will be
shown.
Permissions
Groups
Tags
Security Credentials
Access Advisor
Step2: We want to use a Security Credentials object, click on the Security
Credentials tab.
Step3: Here we are seeing Access Key ID, which was recently created with status
marked as “Active”
Step4: In this case, the Access Key status provides an important security feature
to the administrators.
Step5: Now we have the user, therefore allowing us access to AWS resources
programmatically.
Configuring Terminal/Command Prompt
+++++++++++++++++++++++++++++++++++
1) Log in to the terminal window (“mac”/ Linux”) or command prompt (“Windows”).
2) Before we can access the AWS resources using CLI (command-line interface), we
will need to configure the CLI.
3) We will run the following command to configure AWS CLI
$ aws configure
AWS Access Key ID : Created as part of new security credentials
AWS Secret Access Key : Corresponding to the “AWS Access Key” selected
Default Region name : AWS regions, we are using ap-south-1
Default Output format : Json
4) Now we are all set with the profile.
Working with AWS S3 Service using AWS CLI
+++++++++++++++++++++++++++++++++++++++++
Step1: In this case, we will be using AWS S3 (Simple Storage Service) as an
example.
In brief, AWS S3 is an object storage service.
Step3: Next, we are going to run “aws s3 ls" (to display bucket lis)
$ aws s3 ls
Step4: After listing out the content of the existing bucket, let us try to create a
new s3 bucket using AWS CLI
$ aws s3 mb s3://ashokitbucket
Step5: As a result of the command execution, the bucket should be created
Step6: Furthermore, let us try to create a bucket in a region other than the
default region for the CLI profile, in our case the default region is ‘us-east-1’
Step7: After the command has been executed, let us check, if the bucket has been
created and what is the region of the bucket.
Working with EC2 service using AWS CLI
+++++++++++++++++++++++++++++++++++++++++
List out all ec2 instances
++++++++++++++++++++++++++++
$ aws ec2 describe-instances
Note : It will list down all the data in JSON format
For example, we can search for instances with a given type:
$ aws ec2 describe-instances --filters Name=instance-type,Values=t2.micro
or a tag key:
$ aws ec2 describe-instances --filters "Name=tag-key,Values="EC2VM-2"
Create a New Key Pair for EC2 Instances
++++++++++++++++++++++++++++++++++++++++
-> Before launching a new EC2 instance we’ll need an SSH key pair that we’ll use to
connect to it securely.
$ aws ec2 create-key-pair --key-name ashokitkey --output text > ashokitkey.pem
The above command will create a new key in the AWS named ashokitkey and pipe the
secret key directly to the location we specify, in this case, ashokitkey.pem.
Launch New EC2 Instances
++++++++++++++++++++++++
$ aws ec2 run-instances --image-id ami-0a3277ffce9146b74 --instance-type t2.micro
--key-name ashokitkey
Stop and Start an EC2 Instance
++++++++++++++++++++++++++++++
$ aws ec2 stop-instances --instance-ids <instance-id>
And start again:
$ aws ec2 start-instances --instance-ids <instance-id>
Terminate an Instance
++++++++++++++++++++++
$ aws ec2 terminate-instances --instance-ids <instance-id>
