So here is a short lecture just on the features you should know.
An Elastic Beanstalk and let's go have a look at them.
They're just small features but it's good that I mentioned them and my conscience will be appeased.
So if you go to hell the world and we create a new environment.
We have the option to choose a web server or a or environment.
I'll be going into worker environment later in this course so we'll just focus on web server environments.
Click on select and you can select a domain name and a pre configured platform so we'll just choose
BHP as we did from before.
Which is a simple application and then I'll configure more options.
So this is just to show you the settings.
So here we have a configuration presets which is low cost and free tier eligible.
In this case the capacity the environment type a single instance and they will have an elastic IP attached
to it.
So this is one way and then as soon as we go into high availability then we have a load balancer and
an older sibling group attached to our Elastic Beanstalk environment.
And this is better for product ready environments so low cost is great for Dev and high availability
is great for product and that's the only thing I want to show you out here.
So I'll go ahead and cancel this next I'll just go into the environments and hear that.
Next hour we'll show you the application versions.
So any time we upload a new version and we deploy it it gets created into application versions.
And as you can see here we've done five of these deploys.
So we have five application versions being created.
And we can see that the latest application version is currently deployed to end.
So this is great.
So as we start uploading more and more versions into these application versions you can imagine over
time there will be hundreds of them.
And it turns out that there is a limits in beanstalk that you can only have a thousand of them.
So at some point you need to get rid of these application versions and for this you have something called
an application version lifecycle.
So by clicking on settings here I have the application version lifecycle settings and you can create
a lifecycle policy which says that we can limit the number of application versions to say for example
200 versions or we could limit by age and say OK after 180 days you can get rid of them.
And this is just you would do you register them.
You can retain the source bundle in history or you can delete the source bundle in history as well.
So it's a good idea to retain the service bundle if you still want to delete it from the application
versions and beanstalk but be able to somehow re upload it at some points and roll back to it if she
needed to.
And finally you need to create a service role or use a service role at least to perform this application
version lifecycle settings and deletes these application versions.
So here I'll just enable a lifecycle policy and say I only want 200 version of applications and don't
worry it will not delete this one ever if it's deployed to an environment.
So it will not delete an application version that is deployed in environments.
The reason we do this again is to keep the number of application versions under control.
But the reason we like to have many application versions in here is to be able to apply them to our
stock environments and this is effectively doing a rollback for us.
OK.
Next for these environments.
If I go and click on it and click on actions I have the option to clone the environments.
So cleaning the environment is taking all the settings and applying them to a new environments.
So this is a really easy and quick way to create a new environment.
We could also create clean environments using the ABC light and we'll be seeing this later on.
So I wanted to show the clone option but I'm not going to use it.
Next week we can do is completely redo the environments so you can terminate the environment and everything
will go away.
And this is the same in the ABC ally as doing Eby terminates or you can rebuild the environments and
rebuilding the environment we'll delete everything and recreate it for you.
So as it says here for example if you have any attach Amazon ideas database instance it will be deleted
and then recreate it.
So this is again going into our discussion of do we want the instances such as Audi as that emoji be
or as soon as topics to be within our application environments or do we want them to be external.
So I'm not going to click on rebuild but you get an idea of what it would do.
And finally the last thing I want to show you is manage updates so it is possible for Elastic Beanstalk
to apply patches to your environments and for this unit you present to create and manage updates.
And so you can enable managed platform that's in the configuration tabs in here under manage updates.
Here we go.
And we could enable them and saying okay we create an update window weekly that starts Wednesday at
2:00 a.m. and we want to do minor and patch only and if anybody we can do instant replacements.
So this is a way to keep our Elastic Beanstalk up to date.
And this is why beanstalk is such a great managed service is because it will do the updates for us on
a weekly basis if we need to in a rolling manner.
And it will be manage updates.
So not going to enable it as well.
But just showing you that it exists and there is a way to keep your instance patched using manage updates
in Elastic Beanstalk.
So this is what it's like to just a little bit of like random bits here and there.
But now you've seen them.
So you're supposed to know them and then we'll see you in the next lecture.