1

00:00:00,030  -->  00:00:05,430
Welcome back to backspace Academy.
In this lab on Elastic Beanstalk

2

00:00:05,430  -->  00:00:11,070
we're going to be using the elastic Beanstalk
service to deploy a NodeJS application

3

00:00:11,070  -->  00:00:16,199
and deploy it to a highly available and
fault tolerant architecture. So starting

4

00:00:16,199  -->  00:00:19,910
off in the Elastic Beanstalk console
again we get there from services and

5

00:00:19,910  -->  00:00:26,849
Elastic Beanstalk once we're there we
can see a welcome screen there

6

00:00:26,849  -->  00:00:31,380
if we haven't got any Elastic Beanstalk
environments already. What I'd like to do

7

00:00:31,380  -->  00:00:39,059
now is just click on get started and
we'll give our application a name

8

00:00:39,059  -->  00:00:44,520
We'll select nodejs as our platform and we're
just going to use the sample

9

00:00:44,520  -->  00:00:51,719
application that AWS use and we're going
to click on configure more options now

10

00:00:51,719  -->  00:00:54,629
if we didn't click on configure more
options and just clicked straight on

11

00:00:54,629  -->  00:00:59,399
create application it would launch our
environment as a single instance

12

00:00:59,399  -->  00:01:03,629
so it wouldn't be a highly available and fault
tolerant architecture and so as we can

13

00:01:03,629  -->  00:01:07,439
see here our capacity is just a single
instance and we don't have a load

14

00:01:07,439  -->  00:01:12,060
balancer so what we need to do is we
need to select high availability and

15

00:01:12,060  -->  00:01:16,080
there we can see our capacity has
changed and it's going to be in an auto scaling

16

00:01:16,080  -->  00:01:21,180
group that will have instances
ranging from 1 to 4 and we can change

17

00:01:21,180  -->  00:01:26,720
that as well and also we can see there
that we've got a load balancer as well

18

00:01:26,720  -->  00:01:31,020
so what we'll do is we'll click on now
we'll click on create' app and what it's

19

00:01:31,020  -->  00:01:34,290
going to do it's not only going to
create that elastic beanstalk

20

00:01:34,290  -->  00:01:40,680
application for us it's going to create
an environment to launch our code on and

21

00:01:40,680  -->  00:01:46,740
that will be a highly available and
fault tolerant architecture, ok so after

22

00:01:46,740  -->  00:01:50,759
a certain amount of time we've got there
our environment has been launched and

23

00:01:50,759  -->  00:01:54,360
we've got the big green tick there, now
what we can do is we can go to this

24

00:01:54,360  -->  00:01:58,649
endpoint up the top here which will be
the URL for our application our web

25

00:01:58,649  -->  00:02:02,340
application, so we click on that and
there we can see that is the sample

26

00:02:02,340  -->  00:02:08,700
nodejs application from AWS now that
will be deployed to a HA and FT

27

00:02:08,700  -->  00:02:12,989
architecture what that means is it will
have an auto scaling group and ec2

28

00:02:12,989  -->  00:02:16,459
instances will
launched by that and it will also have

29

00:02:16,459  -->  00:02:20,540
an elastic load balancer as well so
let's just make sure that that has

30

00:02:20,540  -->  00:02:24,920
actually occurred,
so we go to services then go over to ec2

31

00:02:24,920  -->  00:02:30,500
and if you remember we had our auto
scaling group was varying between one

32

00:02:30,500  -->  00:02:33,590
and four depending on demand, so there
we can see we've got one instance

33

00:02:33,590  -->  00:02:40,430
running now if we scroll down we should
be able to find a load balancer there as

34

00:02:40,430  -->  00:02:49,069
well so there we go we've got our
elastic load balancer there that is been

35

00:02:49,069  -->  00:02:53,900
created by elastic beanstalk and it's
got one instance in service we should

36

00:02:53,900  -->  00:03:01,489
also have an auto scaling group and
there we go we've got an auto scaling

37

00:03:01,489  -->  00:03:05,389
group as well and then we can see it's
got a desired capacity of one which is

38

00:03:05,389  -->  00:03:09,919
what we're at now and a minimum to
maximum of four depending on demand on

39

00:03:09,919  -->  00:03:15,260
those instances so what we'll do now is
that we've pretty well finished a lab

40

00:03:15,260  -->  00:03:18,709
what we need to do now is clean this all
up to make sure that we don't get a bill

41

00:03:18,709  -->  00:03:24,440
so the best way to do it is not to go in
and delete resources what you need to do

42

00:03:24,440  -->  00:03:28,519
is go into all applications and then
just select that application here with

43

00:03:28,519  -->  00:03:33,769
actions and delete the application so
that will delete your application and it

44

00:03:33,769  -->  00:03:39,049
will also delete that environment that
was created by elastic Beanstalk so we

45

00:03:39,049  -->  00:03:43,340
click on delete so it doesn't look like
anything's happened but if you click on

46

00:03:43,340  -->  00:03:47,479
that environment you will see that is
now terminating your environment and

47

00:03:47,479  -->  00:03:51,620
after a few minutes those all those
resources they auto scaling group that

48

00:03:51,620  -->  00:03:55,819
elastic your load balancer the instances
all will be removed from your account

49

00:03:55,819  -->  00:04:00,229
and you won't get billed for that so
that brings us to the end of a pretty

50

00:04:00,229  -->  00:04:05,709
straightforward lab and I look forward
to seeing you in the next lecture