AWS Command Line Interface (AWS CLI)

Loading...

Del curso dictado por University of Colorado System

Cloud Computing Security

calificaciones

University of Colorado System

Cloud Computing Security

calificaciones

In this MOOC, we will learn Cloud Computing basics using AWS as an example, We will guide you to create AWS account, planning AWS resources for your cloud systems, create AWS EC2 instances, access them and configure the popular LAMP web services with MySQL database. We will guide you to create user accounts for your programmer or operators using AWS Identify and Access management GUI, Register your domain name and setup DNS entry for your servers using AWS Route 53 in 22 mintues! and show you how to use AWS Command Line interface to create and managing instances and services programmatically. We then introduce AWS Load balancing feature, create load balancing cluster for scalability and reliability. We also demonstrate how to diagnose the problem introduced by the health check and firewall restriction conflicts. By the end of this course, you should be able to create your own web cluster with mysql databases, setup your users with credentials to manage your AWS resources/virtual machines either through their management control interface or using AWS CLI API using scripts. You will also learn the best practice in cloud security and debugging service interaction issues may arise in the cloud systems.

De la lección

Secure Server Configuration and Integrated Access Management

In this module, we learn how to sign up AWS account, create/configure/manage AWS EC2 instances, access them and configure the Linux operating system, Apache web server, MySQL database, and PHP server side scripting support. We also learn how to follow the best security practice to create user accounts with different privileges using AWS IAM service. We learn how to use AWS Command Line Interface to create AWS EC2 instances and control AWS Resources. It allows for programming control of the EC2 instances.

AWS Command Line Interface (AWS CLI)8:58

Conoce a los instructores

Edward Chow
Professor
Computer Science

In this lesson, we show how to set up AWS Command Line Interface,

AWS CLI in short,

on an AWS Instance and allow us to use a CLI

commands to see the region available and see their endpoint and the region name,

and to stop the instance and observe its status on the EC2 dashboard.

AWS CLI provide a direct access to AWS public API,

and all these available service so long as they have public API in place.

The AWS Command Line Interface can allow you to interface with their services,

allow the development of shell scripts so that we can managing our own AWS resources.

Compared to AWS EC2 CLI,

the AWS CLI without the EC2 name there,

provide commands for a much broader set of AWS products.

Instead of goes through a long process to set up Java and figure out ways ahead of why,

we recently find out the AW Amazon Linux Instance already by default.

They already installed with AWS package.

So you don't have to go through a long process.

Once you start up your Amazon Linux Instance,

you can actually type in the command AWS and with a minus,

minus version as the option.

It will show you what version of AWS the version is,

and it show here AWS test version is 1.11.83.

They are designed using the Python code and here is showing the actual Amazon Instance ID

and this is developed using

the botocore version 1.5.46.

Once you're comfortable with this particular versions,

you can actually start to provide a credential you are going to use,

and what are the default regions you are going to access.

We do that by using AWS configure command.

A configure command once you enter,

it will ask you to enter

the access key and a secret access key, those two information.

Those are the information,

as a system inspector,

we first create an admin account.

The last step we'll ask is to download those two key, right?

Here's a phrase we need to re-enter here.

And for other customer,

IM users the system instead will send them these two key so

that when they log into the Amazon Linux Instance,

they can using this command to set it up.

You should choose a region that is closer to you or choose whatever the instance,

if you're using or tried to practice the theory of algorithm in the future.

Here, once you type in a configure,

it shows the AWS access key ID prompt and ask you to copy and paste into it.

The second entry is AWS secret key,

and yeah, we also do copy and paste.

The region here, because we are closer to Ohio,

so we enter O,

the region has a name, short name.

Their short name represent by typically the US or Europe, EU.

In Ohio, is us-east-2, all right?

So US is a region,

east or west we have here,

and then dash two is the second one.

Dash one is what your name.

You can actually go to AW website to find out all these short name for the region.

You can also run the AWS EC2,

this describe region to get a whole list,

and the last one is alpha format for the command,

can be output, can be [inaudible].

Here we show the AWS CLI command.

AWS EC2 describe region,

and it is very old available region name and their URL.

Those URL can be used in to set environment variable so that

other applications like ECI programming interface,

if you're using that can't automatically route the request

to the region based on that environment variable setup.

To shut down an instance or a set of instance,

what we need to do is to find out the instance ID from

the AWS EC2 Management Council or from some data file or database we have written down,

save these and the instance ID.

We have one instance in us-east-2, Ohio location.

It has the ID ending with 723 here.

So let us run the command aws ec2 stop-instance, this command.

It has one option --instantance-ids,

and look carefully here,

they use ID with s. So within the same command you can enter

multiple instance ID and they will be

with a single command that can be shut down together.

It looked nice to allow.

It start to say shut down,

stop the instance when this command is executed.

All of a sudden, I find out I forgot.

I just started my only single instance,

and by shutting it down,

I now cannot run and demonstrate the AWS command.

So to demonstrate how to start and stop.

So inside the EC2 Management Council,

I will show one trick.

Basically, we are trying to save the instance as the image and then allow it to commit.

So after these shut down,

we go to the EC2 Management Council.

We can confirm the instance is actually shutting down,

and at the beginning it will say stopping as the status.

After a while, maybe one minute typically,

the instance state will be changing from stopping to stopped.

To restart the instance,

we need to start our instance from the AWS CLI.

We need to have a machines that already installed with AWS.

So we've got a chicken and egg problem here.

So one way to do it is,

we would like to clone our current instance and the best way

to clone that is not to start configuring from scratch, right?

So in the AWS,

they allow you this future creating image,

and by making our instance image are performing, okay?

Explora nuestro catálogo

Inscríbete de manera gratuita y obtén recomendaciones personalizadas, actualizaciones y ofertas.

Coursera brinda acceso universal a la mejor educación del mundo, al asociarse con las mejores universidades y organizaciones, para ofrecer cursos en línea.

© 2018 Coursera Inc. Todos los derechos reservados.

Descargar en la App Store

Consíguelo en Google Play