WEBVTT
1
00:00:00.090 --> 00:00:00.923
In this lesson,
2
00:00:00.923 --> 00:00:03.060
I'm going to show you how to use the cloud,
3
00:00:03.060 --> 00:00:05.430
and we're going to do this by using a product from Amazon
4
00:00:05.430 --> 00:00:06.960
known as Lightsail.
5
00:00:06.960 --> 00:00:10.170
Now Lightsail is Amazon's entry to the cloud product.
6
00:00:10.170 --> 00:00:13.140
Instead of having to use EC2, which is for compute,
7
00:00:13.140 --> 00:00:15.120
Route 53, which is for networking,
8
00:00:15.120 --> 00:00:17.040
Aurora, which is for databases,
9
00:00:17.040 --> 00:00:18.357
Fargate, which is for containers
10
00:00:18.357 --> 00:00:20.940
and S3, which is for storage,
11
00:00:20.940 --> 00:00:22.620
we actually get all of that combined
12
00:00:22.620 --> 00:00:26.160
into one nice, easy-to-use package for us as beginners
13
00:00:26.160 --> 00:00:27.510
in the cloud.
14
00:00:27.510 --> 00:00:28.980
Now, the first thing you're going to want to do
15
00:00:28.980 --> 00:00:31.080
is get yourself an Amazon account
16
00:00:31.080 --> 00:00:35.430
by going to aws.amazon.com/lightsail.
17
00:00:35.430 --> 00:00:38.070
From here, you can click on create an AWS account
18
00:00:38.070 --> 00:00:40.320
and sign up for one for free.
19
00:00:40.320 --> 00:00:42.330
Once you do that, you'll be able to log into your account
20
00:00:42.330 --> 00:00:44.370
and get to your Lightsail dashboard.
21
00:00:44.370 --> 00:00:47.253
From here, you're going to click on create an instance.
22
00:00:48.180 --> 00:00:50.640
Once you do that, you're then going to select the region
23
00:00:50.640 --> 00:00:53.370
and availability zone that's closest to you.
24
00:00:53.370 --> 00:00:56.730
If you want to change that, simply click on change AWS region,
25
00:00:56.730 --> 00:00:59.790
and you can choose from any location around the world.
26
00:00:59.790 --> 00:01:01.860
In my case, I'm closest to the east side
27
00:01:01.860 --> 00:01:02.880
of the United States.
28
00:01:02.880 --> 00:01:05.430
so I'm going to choose either Virginia or Ohio
29
00:01:05.430 --> 00:01:07.830
for us-east-1 or us-east-2
30
00:01:07.830 --> 00:01:10.770
and I'm going to go ahead and use us-east-1 with Virginia,
31
00:01:10.770 --> 00:01:12.240
because that's a little bit closer to me
32
00:01:12.240 --> 00:01:14.460
and it'll help reduce my load times.
33
00:01:14.460 --> 00:01:15.600
Now, as you scroll down,
34
00:01:15.600 --> 00:01:17.430
you can then pick your platform.
35
00:01:17.430 --> 00:01:19.350
You have a choice between Linux and Unix
36
00:01:19.350 --> 00:01:21.480
or Microsoft Windows.
37
00:01:21.480 --> 00:01:24.600
Do be aware that Linux and Unix is cheaper on Lightsail
38
00:01:24.600 --> 00:01:26.130
than Microsoft Windows.
39
00:01:26.130 --> 00:01:27.630
And this is because Linux and Unix
40
00:01:27.630 --> 00:01:29.490
is an open source piece of software,
41
00:01:29.490 --> 00:01:31.440
so there's no licensing cost.
42
00:01:31.440 --> 00:01:33.870
For example, you could start out with the lowest plan
43
00:01:33.870 --> 00:01:34.890
on Linux or Unix
44
00:01:34.890 --> 00:01:37.140
for only $3 and 50 cents per month,
45
00:01:37.140 --> 00:01:39.930
which gives you your server and all of your configurations.
46
00:01:39.930 --> 00:01:40.980
Whereas with Microsoft,
47
00:01:40.980 --> 00:01:44.040
it is going to start out at $8 per month for the lowest level,
48
00:01:44.040 --> 00:01:45.750
because there is licensing associated
49
00:01:45.750 --> 00:01:47.610
with that server software.
50
00:01:47.610 --> 00:01:49.620
I'm going to recommend that you use Linux or Unix
51
00:01:49.620 --> 00:01:50.670
as your blueprint.
52
00:01:50.670 --> 00:01:51.720
And the reason for this
53
00:01:51.720 --> 00:01:54.090
is when you get into Core 2 of A+,
54
00:01:54.090 --> 00:01:55.410
you actually have to get comfortable
55
00:01:55.410 --> 00:01:57.180
using some commands in Linux.
56
00:01:57.180 --> 00:01:59.310
And so by creating this here in the cloud,
57
00:01:59.310 --> 00:02:01.110
while you're studying for the next couple of months,
58
00:02:01.110 --> 00:02:03.720
you can go back, log into your Linux server in the cloud,
59
00:02:03.720 --> 00:02:05.910
and use that to practice with.
60
00:02:05.910 --> 00:02:08.220
Next, we're going to choose what we want.
61
00:02:08.220 --> 00:02:10.320
Do we want an application and OS,
62
00:02:10.320 --> 00:02:12.390
or do we want the OS only?
63
00:02:12.390 --> 00:02:14.400
Essentially what this is asking is,
64
00:02:14.400 --> 00:02:16.290
do I want platform as a service
65
00:02:16.290 --> 00:02:18.300
or infrastructure as a service?
66
00:02:18.300 --> 00:02:19.830
Now, if I do OS only,
67
00:02:19.830 --> 00:02:22.710
I can choose the exact version of Linux I want to use,
68
00:02:22.710 --> 00:02:24.810
whether that is Amazon's own version of Linux
69
00:02:24.810 --> 00:02:27.780
referred to as AMI or Amazon Linux 2,
70
00:02:27.780 --> 00:02:32.780
or Ubuntu, Debian, Free BSD, openSUSE, or CentOS.
71
00:02:33.540 --> 00:02:35.790
If I want to use an app plus OS,
72
00:02:35.790 --> 00:02:36.690
this is going to give me
73
00:02:36.690 --> 00:02:38.940
not just the underlying operating system,
74
00:02:38.940 --> 00:02:41.460
but it's also going to give me some application.
75
00:02:41.460 --> 00:02:43.740
For example, if you want to create your own website
76
00:02:43.740 --> 00:02:45.270
using a WordPress log,
77
00:02:45.270 --> 00:02:48.600
you could do that by selecting WordPress here as the app,
78
00:02:48.600 --> 00:02:51.360
or maybe you want to create your own internal community,
79
00:02:51.360 --> 00:02:54.060
and you're going to use Joomla or Drupal to do that.
80
00:02:54.060 --> 00:02:55.650
Or maybe you're going to start writing
81
00:02:55.650 --> 00:02:57.510
your own custom application
82
00:02:57.510 --> 00:02:59.910
and so you want to have Node.js installed,
83
00:02:59.910 --> 00:03:01.500
that way you have that as the baseline
84
00:03:01.500 --> 00:03:02.850
and everything else you're going to code
85
00:03:02.850 --> 00:03:05.220
is going to be written in Node.js.
86
00:03:05.220 --> 00:03:07.140
By offering this app plus OS,
87
00:03:07.140 --> 00:03:08.700
this allows us to take the hard work
88
00:03:08.700 --> 00:03:10.590
out of configuring those applications,
89
00:03:10.590 --> 00:03:12.570
as opposed to getting just the operating system
90
00:03:12.570 --> 00:03:15.660
and then having to install those applications ourself later.
91
00:03:15.660 --> 00:03:17.880
In my case, I'm going to choose CentOS
92
00:03:17.880 --> 00:03:19.320
down here in the bottom right
93
00:03:19.320 --> 00:03:22.650
because CentOS is a Red Hat based version of Linux
94
00:03:22.650 --> 00:03:23.880
and most organizations,
95
00:03:23.880 --> 00:03:25.710
if they're running their own Linux servers,
96
00:03:25.710 --> 00:03:29.640
are using either Red Hat Enterprise Linux or CentOS.
97
00:03:29.640 --> 00:03:30.750
And for that reason,
98
00:03:30.750 --> 00:03:33.930
if you decide to move up into the CompTIA Linux+** course,
99
00:03:33.930 --> 00:03:36.600
you'll be using CentOS as the base operating system
100
00:03:36.600 --> 00:03:38.460
as you go throughout that course as well.
101
00:03:38.460 --> 00:03:41.280
So it's a good one for us to choose here.
102
00:03:41.280 --> 00:03:42.960
Then we're going to scroll down
103
00:03:42.960 --> 00:03:45.420
and we are going to have some other options we can configure,
104
00:03:45.420 --> 00:03:47.760
including if we want a script that will launch
105
00:03:47.760 --> 00:03:49.680
every time we load up this server
106
00:03:49.680 --> 00:03:52.590
or being able to create a unique SSH key pair
107
00:03:52.590 --> 00:03:54.570
to remotely log into this machine.
108
00:03:54.570 --> 00:03:57.450
For right now, I'm going to stick with the defaults on this,
109
00:03:57.450 --> 00:03:59.220
and then as we scroll to the bottom,
110
00:03:59.220 --> 00:04:01.770
you can see we have to choose our plan.
111
00:04:01.770 --> 00:04:04.050
Now, as I said, with the Linux option,
112
00:04:04.050 --> 00:04:05.910
we can start out at the lowest plan,
113
00:04:05.910 --> 00:04:08.400
which is $3 and 50 cents per month.
114
00:04:08.400 --> 00:04:11.280
And with Amazon, they're running a special right now,
115
00:04:11.280 --> 00:04:12.450
where if you sign up,
116
00:04:12.450 --> 00:04:14.460
you're going to get your first three months free
117
00:04:14.460 --> 00:04:16.500
and there is no contract.
118
00:04:16.500 --> 00:04:17.880
So we can actually sign up.
119
00:04:17.880 --> 00:04:19.830
It'll be free for the first three months.
120
00:04:19.830 --> 00:04:21.450
And so we're going to be able to play with this.
121
00:04:21.450 --> 00:04:23.610
And then if you delete it by the end of that three months,
122
00:04:23.610 --> 00:04:25.530
you won't be charged anything.
123
00:04:25.530 --> 00:04:27.510
Now, when you're picking out your server,
124
00:04:27.510 --> 00:04:30.120
you're going to figure out what equipment you want.
125
00:04:30.120 --> 00:04:31.050
And based on that,
126
00:04:31.050 --> 00:04:33.690
you're going to pay more or less money per month.
127
00:04:33.690 --> 00:04:35.820
As I said, Amazon is running a special
128
00:04:35.820 --> 00:04:37.350
at the time of this recording,
129
00:04:37.350 --> 00:04:40.260
where you can get any of the first three level plans
130
00:04:40.260 --> 00:04:41.790
for free for three months,
131
00:04:41.790 --> 00:04:42.990
and then after that,
132
00:04:42.990 --> 00:04:45.360
you would pay the price listed here on the screen.
133
00:04:45.360 --> 00:04:47.310
So since I'm planning on only using this
134
00:04:47.310 --> 00:04:48.840
for the next two or three months,
135
00:04:48.840 --> 00:04:51.330
I'm going to go ahead and select the $10 version,
136
00:04:51.330 --> 00:04:53.850
because this is going to gimme more memory and storage base
137
00:04:53.850 --> 00:04:55.650
on my virtual server.
138
00:04:55.650 --> 00:04:58.140
As you can see here, the first option we had
139
00:04:58.140 --> 00:05:00.810
only had 512 megabytes of RAM,
140
00:05:00.810 --> 00:05:02.250
which is really low.
141
00:05:02.250 --> 00:05:04.170
The second one is one gigabyte,
142
00:05:04.170 --> 00:05:05.820
the third one is two gigabytes,
143
00:05:05.820 --> 00:05:08.100
and it keeps doubling as we move to the right,
144
00:05:08.100 --> 00:05:10.710
and the price also doubles in turn.
145
00:05:10.710 --> 00:05:14.310
You'll notice that the first three all use one virtual CPU,
146
00:05:14.310 --> 00:05:15.870
whereas the other ones are going to use
147
00:05:15.870 --> 00:05:17.700
two virtual CPUs or more
148
00:05:17.700 --> 00:05:21.420
as we continue to the right and see the higher price plans.
149
00:05:21.420 --> 00:05:22.620
On the storage line,
150
00:05:22.620 --> 00:05:25.290
you'll see the first level starts out with 20 gigabytes,
151
00:05:25.290 --> 00:05:27.750
the second is 40, the third is 60,
152
00:05:27.750 --> 00:05:29.820
then it goes to 80, then 160,
153
00:05:29.820 --> 00:05:31.710
and it keeps raising from there.
154
00:05:31.710 --> 00:05:33.270
As you look over to the right,
155
00:05:33.270 --> 00:05:36.030
you're going to see that the maximum plan size you can go to
156
00:05:36.030 --> 00:05:38.820
is actually $160 per month.
157
00:05:38.820 --> 00:05:40.710
This is actually a pretty beefy server though,
158
00:05:40.710 --> 00:05:43.020
because you're getting 32 gigabytes of memory,
159
00:05:43.020 --> 00:05:46.440
eight virtual CPUs, and 640 gigabytes of storage
160
00:05:46.440 --> 00:05:49.110
using a fast solid state device.
161
00:05:49.110 --> 00:05:50.070
So as you could see,
162
00:05:50.070 --> 00:05:52.950
you can actually pick pretty powerful servers in the cloud
163
00:05:52.950 --> 00:05:55.470
using even something as simple as Lightsail.
164
00:05:55.470 --> 00:05:56.520
The other nice thing
165
00:05:56.520 --> 00:05:58.290
is that you can can always start out low
166
00:05:58.290 --> 00:06:00.210
and then increase over time.
167
00:06:00.210 --> 00:06:02.640
This is what's called vertical scaling.
168
00:06:02.640 --> 00:06:04.530
For example, if I decide to start out
169
00:06:04.530 --> 00:06:06.180
with this $10 per month plan,
170
00:06:06.180 --> 00:06:07.770
and I wanted to create a new website
171
00:06:07.770 --> 00:06:09.060
on this virtual machine,
172
00:06:09.060 --> 00:06:11.550
and I have 10 people per month going to that website,
173
00:06:11.550 --> 00:06:13.260
this $10 per month machine
174
00:06:13.260 --> 00:06:15.420
will be more than adequate to handle that.
175
00:06:15.420 --> 00:06:17.280
But if I start getting a thousand
176
00:06:17.280 --> 00:06:20.160
or 10,000 people a day going to my website,
177
00:06:20.160 --> 00:06:22.980
that $10 server is not going to be enough.
178
00:06:22.980 --> 00:06:26.910
But I can quickly go back and move up to a higher plan
179
00:06:26.910 --> 00:06:29.880
by simply going and creating a backup of my server,
180
00:06:29.880 --> 00:06:32.250
creating a new instance at the larger size,
181
00:06:32.250 --> 00:06:35.730
and then restoring that instance into the newer larger size.
182
00:06:35.730 --> 00:06:37.980
And at that point, that becomes my new website
183
00:06:37.980 --> 00:06:40.830
and I can delete the older instance that I had.
184
00:06:40.830 --> 00:06:42.630
Next, we're going to give our instance a name
185
00:06:42.630 --> 00:06:45.750
and I'm just going to call this LinuxPractice.
186
00:06:45.750 --> 00:06:47.790
That way I can remember what it's going to be.
187
00:06:47.790 --> 00:06:50.700
And then you can also choose how many instances you want,
188
00:06:50.700 --> 00:06:53.130
and in my case, I just want one instance.
189
00:06:53.130 --> 00:06:54.960
But if I wanted to create five of these machines,
190
00:06:54.960 --> 00:06:58.080
I could do that here by just changing this to five.
191
00:06:58.080 --> 00:07:00.480
But we're only going to create one, so I'll leave it at one.
192
00:07:00.480 --> 00:07:03.840
And then we have these key-only tags and key-value tags.
193
00:07:03.840 --> 00:07:06.450
These can be used if you're working in a large organization,
194
00:07:06.450 --> 00:07:08.790
so you can identify what project you were working on.
195
00:07:08.790 --> 00:07:11.130
And that way the billing goes to the right place.
196
00:07:11.130 --> 00:07:12.750
For example, in my company,
197
00:07:12.750 --> 00:07:14.670
we actually have two different websites.
198
00:07:14.670 --> 00:07:17.580
We have DionTraining.com, which is our main website,
199
00:07:17.580 --> 00:07:20.460
and I also have a podcast called "Your Cyber Path."
200
00:07:20.460 --> 00:07:22.410
And "Your Cyber Path" has its own website
201
00:07:22.410 --> 00:07:24.367
at YourCyberPath.com.
202
00:07:24.367 --> 00:07:27.450
"Your Cyber Path" is actually hosted in Amazon Lightsail.
203
00:07:27.450 --> 00:07:30.990
And so we actually have a tag on that that's called YCP.
204
00:07:30.990 --> 00:07:32.190
And anything that we use
205
00:07:32.190 --> 00:07:33.810
that has to do with "Your Cyber Path"
206
00:07:33.810 --> 00:07:35.670
gets tagged as YCP
207
00:07:35.670 --> 00:07:36.870
so that at the end of the month
208
00:07:36.870 --> 00:07:38.430
we can see how much it costs us
209
00:07:38.430 --> 00:07:40.260
to be able to run those services.
210
00:07:40.260 --> 00:07:42.900
This is because we're using not just one Lightsail instance,
211
00:07:42.900 --> 00:07:44.580
but multiple Lightsail instances.
212
00:07:44.580 --> 00:07:45.900
And so we want to be able to capture
213
00:07:45.900 --> 00:07:47.940
how much it costs us overall every month.
214
00:07:47.940 --> 00:07:49.140
And that way we can keep track
215
00:07:49.140 --> 00:07:50.670
of what it's costing us every month
216
00:07:50.670 --> 00:07:52.530
to run the hosting for that website
217
00:07:52.530 --> 00:07:54.510
and the associated podcast.
218
00:07:54.510 --> 00:07:55.343
Once you've done that,
219
00:07:55.343 --> 00:07:57.780
go ahead and click on create instance.
220
00:07:57.780 --> 00:07:59.790
And now Amazon is going to work
221
00:07:59.790 --> 00:08:02.070
creating this instance for us.
222
00:08:02.070 --> 00:08:04.410
So they're allocating the amount of memory we wanted,
223
00:08:04.410 --> 00:08:06.030
which was two gigabytes of RAM,
224
00:08:06.030 --> 00:08:09.510
the one virtual CPU, and the 60 gigabyte SSD.
225
00:08:09.510 --> 00:08:12.270
In addition to allocating all of that hardware for us,
226
00:08:12.270 --> 00:08:14.580
they're also going to be installing the operating system,
227
00:08:14.580 --> 00:08:18.060
and then we'll be able to log in remotely into that server
228
00:08:18.060 --> 00:08:19.410
and be able to do whatever we want
229
00:08:19.410 --> 00:08:20.850
because we own the server
230
00:08:20.850 --> 00:08:24.450
and we have root or administrative access over it.
231
00:08:24.450 --> 00:08:25.680
Now, another thing you'll notice
232
00:08:25.680 --> 00:08:28.800
is that there is an IP address associated with this server.
233
00:08:28.800 --> 00:08:30.900
Notice it is 54.159.170.130
234
00:08:33.990 --> 00:08:36.900
And we also have an IPv6 version underneath it
235
00:08:36.900 --> 00:08:40.290
listed with that long number starting with 2600.
236
00:08:40.290 --> 00:08:42.300
This is how we would address that server.
237
00:08:42.300 --> 00:08:47.300
And so if somebody went to 54.159.170.130 right now,
238
00:08:47.580 --> 00:08:48.690
it would actually bring up
239
00:08:48.690 --> 00:08:50.730
whatever this server's responding to
240
00:08:50.730 --> 00:08:53.130
if there's a web server running on it.
241
00:08:53.130 --> 00:08:55.380
In my case if I try to go to that right now
242
00:08:55.380 --> 00:08:57.060
I get connection refused.
243
00:08:57.060 --> 00:08:57.893
Why?
244
00:08:57.893 --> 00:08:59.430
Because we never installed Apache
245
00:08:59.430 --> 00:09:02.070
or another web server to answer up those calls.
246
00:09:02.070 --> 00:09:05.040
And this is because we chose to install just the OS
247
00:09:05.040 --> 00:09:07.080
and not the app plus OS.
248
00:09:07.080 --> 00:09:09.090
if you had chose to use something like WordPress
249
00:09:09.090 --> 00:09:10.440
and I went to this IP,
250
00:09:10.440 --> 00:09:12.300
you would see the welcome to WordPress page
251
00:09:12.300 --> 00:09:14.190
for you to be able to configure your WordPress server
252
00:09:14.190 --> 00:09:16.620
through this web-based interface.
253
00:09:16.620 --> 00:09:17.453
Okay.
254
00:09:17.453 --> 00:09:20.190
Now we see that our server has been fully brought up
255
00:09:20.190 --> 00:09:21.540
and it is fully running.
256
00:09:21.540 --> 00:09:23.730
And at this point we want to be able to go in
257
00:09:23.730 --> 00:09:25.710
and do stuff with this server.
258
00:09:25.710 --> 00:09:28.650
So we're going to click on where it says LinuxPractice,
259
00:09:28.650 --> 00:09:31.470
and we can see here how you can connect to your instance.
260
00:09:31.470 --> 00:09:33.990
Now, Amazon makes this super easy for us
261
00:09:33.990 --> 00:09:37.200
by making it so that we can just hit connect using SSH
262
00:09:37.200 --> 00:09:39.900
and it will actually bring up an SSH instance
263
00:09:39.900 --> 00:09:40.950
in our web browser,
264
00:09:40.950 --> 00:09:43.410
which is a remote session to that server.
265
00:09:43.410 --> 00:09:46.590
Right now, I am connected to that CentOS device,
266
00:09:46.590 --> 00:09:50.730
and you can see that I am now logged in as CentOS.
267
00:09:50.730 --> 00:09:52.740
If I wanted to see what directory I'm in,
268
00:09:52.740 --> 00:09:54.690
I could use something like pwd,
269
00:09:54.690 --> 00:09:57.090
which stands for present working directory.
270
00:09:57.090 --> 00:10:01.500
And you can see here I am in the /home/centos directory,
271
00:10:01.500 --> 00:10:04.410
which is this user's home directory.
272
00:10:04.410 --> 00:10:06.270
If you look in here and do ls,
273
00:10:06.270 --> 00:10:08.640
this will tell us what is inside of this directory.
274
00:10:08.640 --> 00:10:11.160
And in this case, there are no files or directories
275
00:10:11.160 --> 00:10:14.640
because this is a brand new server with a brand new account.
276
00:10:14.640 --> 00:10:17.250
Now, if I wanted to go to the root of this hard drive,
277
00:10:17.250 --> 00:10:20.070
I can do cd space /,
278
00:10:20.070 --> 00:10:22.080
which will allow me to change into the root
279
00:10:22.080 --> 00:10:23.370
of this hard drive.
280
00:10:23.370 --> 00:10:25.290
If you think about this in terms of Windows,
281
00:10:25.290 --> 00:10:27.240
this would be going to your internal hard disk,
282
00:10:27.240 --> 00:10:28.530
such as your C drive,
283
00:10:28.530 --> 00:10:31.140
and looking at what files and folders are there.
284
00:10:31.140 --> 00:10:34.980
Again, I'm going to type in ls and this time I'm going to do -la,
285
00:10:34.980 --> 00:10:36.330
which says I want the long list
286
00:10:36.330 --> 00:10:37.980
and I want to see the attributes.
287
00:10:37.980 --> 00:10:39.960
And this is going to show me every file and folder
288
00:10:39.960 --> 00:10:42.420
that's sitting at the root of this hard drive.
289
00:10:42.420 --> 00:10:44.820
And as you can see here, we have several of them.
290
00:10:44.820 --> 00:10:48.330
Everything in that purple color is actually a directory.
291
00:10:48.330 --> 00:10:50.040
Everything in the light blue color
292
00:10:50.040 --> 00:10:52.530
is a link that's pointing to another directory.
293
00:10:52.530 --> 00:10:55.380
For example, if you look at the line that says bin,
294
00:10:55.380 --> 00:11:00.180
that has a symbolic link going to the usr/bin directory.
295
00:11:00.180 --> 00:11:01.440
The same thing with lib,
296
00:11:01.440 --> 00:11:04.380
it's going to the usr/lib directory.
297
00:11:04.380 --> 00:11:05.550
Now, I know most of this
298
00:11:05.550 --> 00:11:07.890
probably doesn't make a lot of sense to you right now,
299
00:11:07.890 --> 00:11:09.270
but the point I wanted to make
300
00:11:09.270 --> 00:11:11.820
is that you are now connected to your Linux machine
301
00:11:11.820 --> 00:11:15.090
and can do whatever it is you want inside of it.
302
00:11:15.090 --> 00:11:16.770
So let me go back to my home directory
303
00:11:16.770 --> 00:11:21.360
by doing cd space /home/centos.
304
00:11:21.360 --> 00:11:24.270
Now, from here if I do ls -la,
305
00:11:24.270 --> 00:11:27.420
you're going to see I have no folders here,
306
00:11:27.420 --> 00:11:29.850
except for that one hidden one that starts with a dot
307
00:11:29.850 --> 00:11:31.590
called SSH.
308
00:11:31.590 --> 00:11:33.810
In Linux anything that starts with a dot
309
00:11:33.810 --> 00:11:35.940
is considered a hidden file.
310
00:11:35.940 --> 00:11:38.640
If I just do ls, you won't see any of those
311
00:11:38.640 --> 00:11:41.340
because all of those files such as bash_logout,
312
00:11:41.340 --> 00:11:45.420
bash_profile, and bashrc are considered hidden files.
313
00:11:45.420 --> 00:11:47.430
Now, if I wanted to create my own file,
314
00:11:47.430 --> 00:11:49.950
I can do that by using the command touch.
315
00:11:49.950 --> 00:11:54.240
So I'm going to say touch, and I'm going to call this file.txt.
316
00:11:54.240 --> 00:11:57.300
By doing that, I just created a new file called file,
317
00:11:57.300 --> 00:11:58.890
but that file is empty
318
00:11:58.890 --> 00:12:00.930
because I haven't done anything with it yet.
319
00:12:00.930 --> 00:12:02.460
So I'm going to go ahead and clear my screen
320
00:12:02.460 --> 00:12:05.730
and I'm going to display one more time using ls -la.
321
00:12:05.730 --> 00:12:08.640
And now you'll see file.txt is there,
322
00:12:08.640 --> 00:12:10.590
and it has no dot in front of it,
323
00:12:10.590 --> 00:12:12.960
meaning it's not a hidden file.
324
00:12:12.960 --> 00:12:15.570
Notice though, in the fifth column we have a zero,
325
00:12:15.570 --> 00:12:17.490
and this is the size of that file.
326
00:12:17.490 --> 00:12:19.650
That file is zero bytes in size
327
00:12:19.650 --> 00:12:21.660
because there is no contents.
328
00:12:21.660 --> 00:12:22.800
When I use the touch command,
329
00:12:22.800 --> 00:12:24.780
I'm just creating an empty file.
330
00:12:24.780 --> 00:12:27.060
Now, if I wanted to enter something into that file,
331
00:12:27.060 --> 00:12:29.160
I can do that by using a text editor.
332
00:12:29.160 --> 00:12:32.520
And on Linux, there's a text known as vi.
333
00:12:32.520 --> 00:12:36.690
So going to type in vi space file.txt and hit Enter.
334
00:12:36.690 --> 00:12:40.350
And by doing that, I can now see that this was a blank file.
335
00:12:40.350 --> 00:12:42.150
Notice all those little squiggly lines
336
00:12:42.150 --> 00:12:43.620
notice the tilde just shows me
337
00:12:43.620 --> 00:12:45.900
that each of those lines is blank.
338
00:12:45.900 --> 00:12:47.910
Now, if I wanted to type something here,
339
00:12:47.910 --> 00:12:50.880
the first thing I need to do is type in the I key.
340
00:12:50.880 --> 00:12:53.220
This moves me into what's called insert mode,
341
00:12:53.220 --> 00:12:55.530
and now I can type things into here
342
00:12:55.530 --> 00:12:56.850
and be able to write them.
343
00:12:56.850 --> 00:13:00.723
So I'm going to say this is Jason's test file.
344
00:13:02.550 --> 00:13:07.550
We are writing information into it using VI, okay?
345
00:13:08.610 --> 00:13:09.630
Now that we are done,
346
00:13:09.630 --> 00:13:12.870
I'm going to go ahead and type in the Escape key,
347
00:13:12.870 --> 00:13:14.910
which puts me back into command mode.
348
00:13:14.910 --> 00:13:17.340
Then I'm going to use the colon key
349
00:13:17.340 --> 00:13:19.830
and you can see the colon now shows up at the bottom.
350
00:13:19.830 --> 00:13:22.680
I'm going to do w for write and q for quit,
351
00:13:22.680 --> 00:13:24.360
which will then save this file.
352
00:13:24.360 --> 00:13:26.550
And you'll notice it says one line was written,
353
00:13:26.550 --> 00:13:28.650
72 characters were written.
354
00:13:28.650 --> 00:13:33.030
So if I clear my screen and I do ls -la this time,
355
00:13:33.030 --> 00:13:35.340
you can now see that we have 72 bytes there
356
00:13:35.340 --> 00:13:38.190
instead of zero bytes inside the file.
357
00:13:38.190 --> 00:13:40.800
Now in Linux, if you want to display the contents of a file
358
00:13:40.800 --> 00:13:41.670
to the screen,
359
00:13:41.670 --> 00:13:43.830
you can do that by typing cat.
360
00:13:43.830 --> 00:13:47.700
So I'm going to do cat and then my file name of file.txt.
361
00:13:47.700 --> 00:13:48.570
And when I do that,
362
00:13:48.570 --> 00:13:50.790
we can now see the contents of that file,
363
00:13:50.790 --> 00:13:52.920
which is, this is Jason's test file.
364
00:13:52.920 --> 00:13:56.490
We are writing information into it using VI.
365
00:13:56.490 --> 00:14:00.420
So as you can see, I have full access on this Linux system
366
00:14:00.420 --> 00:14:02.820
to pretty much do whatever we want at this point,
367
00:14:02.820 --> 00:14:04.500
because we own this server.
368
00:14:04.500 --> 00:14:07.440
I could start installing programs, I could run a web server.
369
00:14:07.440 --> 00:14:09.210
I could do pretty much anything I want
370
00:14:09.210 --> 00:14:11.400
because it is my own server
371
00:14:11.400 --> 00:14:13.740
and nobody else has access to it.
372
00:14:13.740 --> 00:14:15.210
The only real limitation here
373
00:14:15.210 --> 00:14:17.550
is that we are using a command line interface
374
00:14:17.550 --> 00:14:19.560
instead of a graphical user interface.
375
00:14:19.560 --> 00:14:21.660
So you have to get comfortable using Linux
376
00:14:21.660 --> 00:14:22.560
in the command line
377
00:14:22.560 --> 00:14:25.170
if you want to run and operate this server.
378
00:14:25.170 --> 00:14:27.270
Now, this is a very common thing in the cloud.
379
00:14:27.270 --> 00:14:29.820
Most cloud servers are going to be text-based
380
00:14:29.820 --> 00:14:31.770
because we don't want all the extra overhead
381
00:14:31.770 --> 00:14:33.120
and processing requirements
382
00:14:33.120 --> 00:14:35.730
that a graphical user interface provides for us.
383
00:14:35.730 --> 00:14:36.563
Because of this,
384
00:14:36.563 --> 00:14:38.640
when we use a text-based interface like this,
385
00:14:38.640 --> 00:14:41.280
we can use less expensive and less powerful servers
386
00:14:41.280 --> 00:14:44.220
and still provide support to a large audience.
387
00:14:44.220 --> 00:14:46.320
For example, if this was a web server,
388
00:14:46.320 --> 00:14:48.150
this little $10 per month web server
389
00:14:48.150 --> 00:14:50.700
can host probably a hundred to 500 people
390
00:14:50.700 --> 00:14:52.020
pretty comfortably.
391
00:14:52.020 --> 00:14:53.850
Now, if I started getting thousands of people,
392
00:14:53.850 --> 00:14:56.880
I would have to upgrade to the 20 or $40 per month plan
393
00:14:56.880 --> 00:14:58.890
and keep upgrading as my audience grew
394
00:14:58.890 --> 00:15:00.750
for my particular website.
395
00:15:00.750 --> 00:15:01.650
Let's go ahead and go back
396
00:15:01.650 --> 00:15:04.170
to our Amazon Lightsail interface.
397
00:15:04.170 --> 00:15:06.510
And here you can see that you can also connect to this
398
00:15:06.510 --> 00:15:08.370
using your own SSH client
399
00:15:08.370 --> 00:15:09.900
instead of using the browser-based one
400
00:15:09.900 --> 00:15:11.520
that I just demonstrated.
401
00:15:11.520 --> 00:15:13.770
If we go to the next tab, you'll see Storage.
402
00:15:13.770 --> 00:15:16.560
And here you could see I have a single system disk
403
00:15:16.560 --> 00:15:18.690
that was 60 gigabytes in size.
404
00:15:18.690 --> 00:15:20.490
Now you may find that 60 gigabytes
405
00:15:20.490 --> 00:15:21.960
is not enough space for you.
406
00:15:21.960 --> 00:15:22.980
And if that's the case,
407
00:15:22.980 --> 00:15:25.140
you can actually add additional attached disks
408
00:15:25.140 --> 00:15:26.760
using the interface here.
409
00:15:26.760 --> 00:15:29.550
To do that, we'll simply click on create new disk,
410
00:15:29.550 --> 00:15:30.690
and then you'll be able to select
411
00:15:30.690 --> 00:15:32.490
how big of a disk you want.
412
00:15:32.490 --> 00:15:35.730
Now, again, disk space here is on an SSD,
413
00:15:35.730 --> 00:15:37.140
which is more expensive
414
00:15:37.140 --> 00:15:40.140
than using older, slower, traditional hard disks.
415
00:15:40.140 --> 00:15:42.810
And because of that, you'll see the cost associated with it
416
00:15:42.810 --> 00:15:45.810
is going to be based on your size that you choose.
417
00:15:45.810 --> 00:15:47.700
For every gigabyte of space you want,
418
00:15:47.700 --> 00:15:49.650
you're going to be paying 10 cents per month.
419
00:15:49.650 --> 00:15:52.980
So if that 60 gigabyte space wasn't enough for me
420
00:15:52.980 --> 00:15:55.830
and I wanted to have an additional 64 gigabytes,
421
00:15:55.830 --> 00:15:56.663
I can do that,
422
00:15:56.663 --> 00:16:00.480
but it's going to cost me $6.40 per month to do that.
423
00:16:00.480 --> 00:16:02.700
Now, the great thing about using a cloud-based interface
424
00:16:02.700 --> 00:16:03.660
like this though,
425
00:16:03.660 --> 00:16:06.360
is that you can also choose any size you want.
426
00:16:06.360 --> 00:16:10.740
So let's say I wanted to have a one terabyte drive.
427
00:16:10.740 --> 00:16:13.980
I could do that by doing 1,024 gigabytes.
428
00:16:13.980 --> 00:16:18.870
And you can see that would cost me $102.40 cents per month
429
00:16:18.870 --> 00:16:21.630
to attach that to my Linux server.
430
00:16:21.630 --> 00:16:22.830
Just to show you how this works,
431
00:16:22.830 --> 00:16:24.030
I'm going to go ahead and create one
432
00:16:24.030 --> 00:16:26.130
that is 10 gigabytes in size.
433
00:16:26.130 --> 00:16:28.020
This will cost me $1 per month.
434
00:16:28.020 --> 00:16:31.500
I can give it a name such as StorageDisk,
435
00:16:31.500 --> 00:16:34.113
and then I can go ahead and create that disk.
436
00:16:35.040 --> 00:16:35.880
Once you do that,
437
00:16:35.880 --> 00:16:38.430
you need to select the instance you want to attach it to.
438
00:16:38.430 --> 00:16:40.200
In our case, I only have one,
439
00:16:40.200 --> 00:16:42.030
which is my LinuxPractice machine,
440
00:16:42.030 --> 00:16:43.830
but if I had several instances,
441
00:16:43.830 --> 00:16:45.570
such as my Dion Training website
442
00:16:45.570 --> 00:16:47.820
and another one for "Your Cyber Path" website
443
00:16:47.820 --> 00:16:48.690
and things like that,
444
00:16:48.690 --> 00:16:50.940
I could choose which one I want it to be attached to.
445
00:16:50.940 --> 00:16:52.800
And then you'll see that the path to this disk
446
00:16:52.800 --> 00:16:57.090
is going to be /dev/xvdf on my Linux system
447
00:16:57.090 --> 00:16:58.260
once I attach it.
448
00:16:58.260 --> 00:17:00.450
So I'll go ahead and hit attach,
449
00:17:00.450 --> 00:17:05.220
and now that is going to be put into place on my Linux system.
450
00:17:05.220 --> 00:17:07.230
Next, we're going to go back here to home,
451
00:17:07.230 --> 00:17:09.360
and then we're going to go down to LinuxPractice again,
452
00:17:09.360 --> 00:17:11.160
and here, we're going to click on metrics.
453
00:17:11.160 --> 00:17:14.460
With metrics, I can see how hard my system is working.
454
00:17:14.460 --> 00:17:18.180
Now you can see here that this is my CPU overview graph.
455
00:17:18.180 --> 00:17:20.490
And as you see, we launched this server
456
00:17:20.490 --> 00:17:25.170
right around 3:52 PM on July 17th.
457
00:17:25.170 --> 00:17:26.880
And originally when we started up the server,
458
00:17:26.880 --> 00:17:30.300
it was operating at about 20% CPU utilization.
459
00:17:30.300 --> 00:17:31.620
That's because there was a lot going on
460
00:17:31.620 --> 00:17:33.390
when we first started up that server
461
00:17:33.390 --> 00:17:35.490
and it had to bring itself up.
462
00:17:35.490 --> 00:17:36.720
Once that happened, though,
463
00:17:36.720 --> 00:17:38.400
and we got back to our normal workload
464
00:17:38.400 --> 00:17:40.320
when I was in the command line doing things,
465
00:17:40.320 --> 00:17:42.900
you could see it drop down to about 1%.
466
00:17:42.900 --> 00:17:45.540
This is what we call the sustainability zone.
467
00:17:45.540 --> 00:17:47.640
Now, because this is a cloud-based system
468
00:17:47.640 --> 00:17:49.710
and we're using a virtual processor,
469
00:17:49.710 --> 00:17:52.140
Amazon is doing a lot of hard work on the backend
470
00:17:52.140 --> 00:17:54.210
to make sure we're getting good performance.
471
00:17:54.210 --> 00:17:56.850
Let's say, for example, I use this to host a website
472
00:17:56.850 --> 00:17:59.070
and I get a lot of people that jump on my website
473
00:17:59.070 --> 00:18:00.570
all at the same time.
474
00:18:00.570 --> 00:18:02.760
Well, what'll happen is there'll be an increased demand
475
00:18:02.760 --> 00:18:04.530
and the processor will go up.
476
00:18:04.530 --> 00:18:06.090
As that processor goes up,
477
00:18:06.090 --> 00:18:08.940
you'll see it go into, what's called the burstable zone.
478
00:18:08.940 --> 00:18:13.290
If you get between 40 and 60 or 80%, you can actually burst,
479
00:18:13.290 --> 00:18:14.400
which means that Amazon
480
00:18:14.400 --> 00:18:15.643
is going to give you additional capacity
481
00:18:15.643 --> 00:18:19.410
to be able to handle that load so your server won't crash.
482
00:18:19.410 --> 00:18:22.410
Now they will do this for a certain amount of time per month
483
00:18:22.410 --> 00:18:23.370
based on your system.
484
00:18:23.370 --> 00:18:24.990
And so you only have a certain amount
485
00:18:24.990 --> 00:18:27.240
of burstable capacity available.
486
00:18:27.240 --> 00:18:28.650
You can see here on the bottom graph,
487
00:18:28.650 --> 00:18:31.140
that's the remaining CPU burst capacity.
488
00:18:31.140 --> 00:18:33.240
And we have lots of additional burst capacity
489
00:18:33.240 --> 00:18:34.740
available on our system
490
00:18:34.740 --> 00:18:36.840
because we haven't really bursted
491
00:18:36.840 --> 00:18:38.550
because we're not running a lot of stuff
492
00:18:38.550 --> 00:18:40.350
on this server yet.
493
00:18:40.350 --> 00:18:42.600
As we move up, you can also click on here
494
00:18:42.600 --> 00:18:43.980
and see other facts,
495
00:18:43.980 --> 00:18:47.340
things like your CPU utilization, your burst capacity,
496
00:18:47.340 --> 00:18:49.800
your burst capacity in minutes or percentage.
497
00:18:49.800 --> 00:18:52.620
You can also see your incoming and outgoing network traffic,
498
00:18:52.620 --> 00:18:54.210
as well as status check failures,
499
00:18:54.210 --> 00:18:55.830
instance status check failures,
500
00:18:55.830 --> 00:18:58.500
system status check failures, and things like that.
501
00:18:58.500 --> 00:19:01.380
For example, if we look at the incoming network traffic,
502
00:19:01.380 --> 00:19:03.330
you could see that there was traffic started
503
00:19:03.330 --> 00:19:05.940
and then over time that traffic has gone down.
504
00:19:05.940 --> 00:19:07.620
Now, why has that traffic gone down?
505
00:19:07.620 --> 00:19:10.680
Because the only person who has access to this server is me,
506
00:19:10.680 --> 00:19:12.570
and I've been talking to you for the last few minutes
507
00:19:12.570 --> 00:19:14.610
and not entering commands back and forth,
508
00:19:14.610 --> 00:19:17.190
which is why we saw that drop off as we got here
509
00:19:17.190 --> 00:19:19.500
to 4:05 in the afternoon.
510
00:19:19.500 --> 00:19:21.330
Next we can click on networking.
511
00:19:21.330 --> 00:19:24.360
And from here, you can see our public and private IP
512
00:19:24.360 --> 00:19:27.510
as well as our firewall for our device in IPv4
513
00:19:27.510 --> 00:19:31.560
and our IPv6 networking and our IPv6 firewall.
514
00:19:31.560 --> 00:19:32.520
In addition to that,
515
00:19:32.520 --> 00:19:35.490
we have the ability to do load balancing or distribution.
516
00:19:35.490 --> 00:19:37.470
And this would allow us to have multiple servers
517
00:19:37.470 --> 00:19:39.690
that are answering up for a single website.
518
00:19:39.690 --> 00:19:42.570
In our case, we are not sharing traffic with anybody.
519
00:19:42.570 --> 00:19:45.420
We are only using a single server that we are talking to,
520
00:19:45.420 --> 00:19:46.950
and that server's controlled by us
521
00:19:46.950 --> 00:19:48.780
and being used only by us.
522
00:19:48.780 --> 00:19:50.250
But if I was running a website
523
00:19:50.250 --> 00:19:52.800
and I was going from 100 people, to 1,000 people,
524
00:19:52.800 --> 00:19:54.180
to 10,000 people,
525
00:19:54.180 --> 00:19:55.860
I can actually have multiple systems
526
00:19:55.860 --> 00:19:57.540
working together in tandem
527
00:19:57.540 --> 00:20:00.030
to load balance across multiple instances
528
00:20:00.030 --> 00:20:02.640
to answer up requests from all of those people.
529
00:20:02.640 --> 00:20:04.290
Next, we can go back to the top
530
00:20:04.290 --> 00:20:06.240
and you can see that we have Snapshots.
531
00:20:06.240 --> 00:20:07.350
Now, snapshots are the way
532
00:20:07.350 --> 00:20:09.900
that you can do a backup of your system.
533
00:20:09.900 --> 00:20:11.100
When you take a snapshot,
534
00:20:11.100 --> 00:20:13.140
it's going to take an image of the hard drive
535
00:20:13.140 --> 00:20:14.430
and store it in the cloud,
536
00:20:14.430 --> 00:20:15.720
so that if anything happens,
537
00:20:15.720 --> 00:20:18.150
you can then revert back to that snapshot.
538
00:20:18.150 --> 00:20:21.060
In our case, I have the automatic snapshots disabled,
539
00:20:21.060 --> 00:20:23.400
which means it's not going to do a backup of my server
540
00:20:23.400 --> 00:20:24.750
every single day.
541
00:20:24.750 --> 00:20:26.820
This is actually considered a bad security practice
542
00:20:26.820 --> 00:20:28.500
because we want to be able to have snapshots
543
00:20:28.500 --> 00:20:29.850
if something goes wrong.
544
00:20:29.850 --> 00:20:32.670
So I'm going to go ahead and turn on my automatic snapshots.
545
00:20:32.670 --> 00:20:35.310
And you'll see that this will automatically take a snapshot
546
00:20:35.310 --> 00:20:36.540
every single day,
547
00:20:36.540 --> 00:20:39.450
and it will store my seven most recent snapshots.
548
00:20:39.450 --> 00:20:42.960
This way, it's a rolling backup that I can always look at.
549
00:20:42.960 --> 00:20:45.510
Automatic snapshots are build the same way
550
00:20:45.510 --> 00:20:46.950
as a manual snapshot.
551
00:20:46.950 --> 00:20:48.420
And so if you wanted to learn about the billing,
552
00:20:48.420 --> 00:20:50.400
you could look at that by clicking on that link.
553
00:20:50.400 --> 00:20:53.400
I'm going to say, I understand and I'm going to enable it.
554
00:20:53.400 --> 00:20:54.240
In addition to that,
555
00:20:54.240 --> 00:20:57.480
instead of waiting for 2:00 AM to happen for that snapshot,
556
00:20:57.480 --> 00:21:00.060
I can create a snapshot anytime I want.
557
00:21:00.060 --> 00:21:02.340
When I do that, I'm just going to give it a name.
558
00:21:02.340 --> 00:21:03.750
This case, they already have one.
559
00:21:03.750 --> 00:21:06.720
It's a server name dash and a unique identifier
560
00:21:06.720 --> 00:21:07.950
and hit create.
561
00:21:07.950 --> 00:21:08.783
When you do that,
562
00:21:08.783 --> 00:21:11.940
it's going to take a snapshot or backup of my entire server.
563
00:21:11.940 --> 00:21:14.370
And that way, if it breaks or something goes wrong,
564
00:21:14.370 --> 00:21:17.430
I could always restore it from that snapshot.
565
00:21:17.430 --> 00:21:18.810
Next we have Tags.
566
00:21:18.810 --> 00:21:20.010
And if you look at Tags,
567
00:21:20.010 --> 00:21:22.200
this is anything where you're going to be able to label
568
00:21:22.200 --> 00:21:24.090
this particular Lightsail instance
569
00:21:24.090 --> 00:21:26.640
so you can keep track of things, such as its status,
570
00:21:26.640 --> 00:21:28.770
or the cost is associated with it.
571
00:21:28.770 --> 00:21:30.840
After that we have the History tab,
572
00:21:30.840 --> 00:21:33.810
and this will tell us what has happened with this instance.
573
00:21:33.810 --> 00:21:35.970
You could see that we originally created this instance
574
00:21:35.970 --> 00:21:37.620
at 3:56 PM,
575
00:21:37.620 --> 00:21:41.100
we attached that 10 gigabyte hard disk at 4:10 PM,
576
00:21:41.100 --> 00:21:43.650
we created a snapshot at 4:15 PM,
577
00:21:43.650 --> 00:21:46.140
and we enabled an add-on at 4:15 PM
578
00:21:46.140 --> 00:21:48.300
for those automatic snapshots.
579
00:21:48.300 --> 00:21:50.760
The last tab we have is the Delete tab.
580
00:21:50.760 --> 00:21:52.560
And this delete tab is going to be the one
581
00:21:52.560 --> 00:21:54.360
that allows us to delete this server
582
00:21:54.360 --> 00:21:55.890
if we no longer need it.
583
00:21:55.890 --> 00:21:57.780
So let's say two months has gone by
584
00:21:57.780 --> 00:22:00.390
and you decided you no longer want to play with this server
585
00:22:00.390 --> 00:22:02.947
and you don't want to be charged that $3.50,
586
00:22:02.947 --> 00:22:05.730
$5 or $10 per month to keep it running.
587
00:22:05.730 --> 00:22:08.580
Well, you can simply go in here and click Delete,
588
00:22:08.580 --> 00:22:10.530
and this will delete the instance.
589
00:22:10.530 --> 00:22:12.900
Now, if you delete this right now,
590
00:22:12.900 --> 00:22:14.130
we have that storage disk
591
00:22:14.130 --> 00:22:15.870
that's still attached to the instance.
592
00:22:15.870 --> 00:22:17.580
It will unattach the storage disk,
593
00:22:17.580 --> 00:22:19.800
but it won't delete the storage disk.
594
00:22:19.800 --> 00:22:20.820
This is why storage disk
595
00:22:20.820 --> 00:22:22.830
can be actually a pretty beneficial thing
596
00:22:22.830 --> 00:22:25.680
because I can store files from this Linux machine
597
00:22:25.680 --> 00:22:27.120
onto that storage disk,
598
00:22:27.120 --> 00:22:28.590
delete the Linux system,
599
00:22:28.590 --> 00:22:31.440
and then reattach that storage disk to another system
600
00:22:31.440 --> 00:22:33.660
like another Linux system or a Windows system
601
00:22:33.660 --> 00:22:36.120
that I would want to use in this cloud environment.
602
00:22:36.120 --> 00:22:37.200
And this is a good way to get data
603
00:22:37.200 --> 00:22:39.120
from one cloud instance to another
604
00:22:39.120 --> 00:22:40.920
inside of Lightsail.
605
00:22:40.920 --> 00:22:42.960
In addition to that, you'll also see at the top
606
00:22:42.960 --> 00:22:45.270
we have the Stop and the Reboot button.
607
00:22:45.270 --> 00:22:48.150
If I hit stop, this will power down that instance.
608
00:22:48.150 --> 00:22:49.050
And that can be useful
609
00:22:49.050 --> 00:22:50.850
if you no longer want to use this instance
610
00:22:50.850 --> 00:22:52.320
but you know you're going to come back to it
611
00:22:52.320 --> 00:22:53.610
in a couple of weeks,
612
00:22:53.610 --> 00:22:54.930
or you can reboot it
613
00:22:54.930 --> 00:22:56.730
and you use that anytime you're having an issue
614
00:22:56.730 --> 00:22:57.660
with your server,
615
00:22:57.660 --> 00:23:00.150
or you need to reboot it to install some piece of software
616
00:23:00.150 --> 00:23:03.150
or apply some kind of a configuration setting.
617
00:23:03.150 --> 00:23:04.350
So that was a quick introduction
618
00:23:04.350 --> 00:23:06.690
on how you can create your own cloud-based server
619
00:23:06.690 --> 00:23:08.520
using Amazon Lightsail.
620
00:23:08.520 --> 00:23:11.430
I do recommend that you do this yourself, give it a try,
621
00:23:11.430 --> 00:23:12.990
and that way you'll have CentOS machine
622
00:23:12.990 --> 00:23:14.850
that you can play with anytime you want
623
00:23:14.850 --> 00:23:15.963
sitting in the cloud.