Okay.
Hello loggers and welcome to the.
Easy to summarize so congratulations you're at the end of another section of the course.
Hopefully you've learnt an awful lot.
The first thing we learnt about was what.
Easy too is it's basically just a resize a ball compute capacity in the cloud or it's a way of provisioning
virtual machines in the cloud and it reduces the time required to obtain and boot new servers.
Instances two minutes rather than hours or days or weeks or months depending on where you work and it
allows you to quickly scale capacity both up and down as your computing requirements change.
So we have four different pricing models for E2 we've got on demand and this is where you pay a fixed
rate by the hour or by the second with no long term commitments.
We then have reserved.
This is where you have a capacity reservation contract terms of one years or three years.
The more you pay upfront and the longer the contract term the more discount you get.
We then have spot.
This enables you to bid whatever price you want for instance.
Capacity it basically moves around like the stock market and we then have dedicated hosts and this is
physical easy to serve as that dedicated for you and it can be useful where you've got existing server
bound software licenses or perhaps a regulation saying that you cannot use multi tenant virtualization.
Do you remember going into your exam that if a spot instance is terminated by AC to because the prices
change you're not going to be charged for that partial hour of usage.
However if you terminate the instance yourself you are going to be charged for any hour in which the
instance ran.
We then looked at our different easy to instance types and we came up with the new monarch fight.
Dr. Pixy a few so in Austin or in Australia depending on what you want.
So there is Dr Mac pixie.
She is clearly a pixie because she's got wings.
She's clearly Scottish because she's wearing tartan.
She wants to fight.
You can see there's a stethoscope around her so fight Dr Matt Pixie and like I said earlier you don't
really need to understand every single easy to instance type going into this exam where it does become
more useful is when you if you go on to do the professional level exams they will test you as to whether
or not it's a valid instance type or not.
Moving onto IBS we learned that IBS is basically a virtual hard disk drive in the cloud.
Just remember that termination protection is turned off by default so you must turn it on.
So if you do want to go ahead and protect your easy two instances from being accidentally deleted by
your developers or system administrators make sure that termination protection is turned on on an e-business
backed instance.
The default action is for the root IBS volume to be deleted when the incidence is terminated.
So if you do go in and terminate your easy two instances you are going to delete that root device volume
automatically.
But if you add additional attach volumes to that easy to instance they those additionally attach volumes
won't be deleted automatically unless you go in and check that checkbox.
Also remember that IBS root volumes of your default armies can be encrypted.
You can also use third party tools such as bit locker for Windows for example to encrypt the encrypt
the root device volume.
It can also be done when creating admires.
So we will cover that off in a few more slides just remember the lab that we did on it and you can also
do it through the AWOL console or using the API.
And also remember that additional volumes can also be encrypted.
Moving on to security groups all inbound traffic is always blocked by default all outbound traffic is
allowed.
Changes to security groups take effect immediately so as soon as you open up port 80 that effect which
takes effect immediately and then you can also have any number of E2 instances within a security group
and you can have multiple security groups attached to easy to instances and we did that when we went
in to the airforce lab we attached a our default security group as well as our web DMC security group
as well.
Moving on to again staying on security groups.
So security groups are state full.
That means that when you open up a port.
So if you open up port 80 it's going to be open for both inbound and outbound traffic network ACLU are
stateless.
When you go and do a network ACL you're going to have to open up port 80 both inbound and then also
outbound.
We're going to cover that off in the VPC section of the course.
If you create an inbound rule allowing traffic in that traffic is automatically allowed back out again
and you cannot block specific IP addresses using security groups.
Instead you're going to be using network access control.
And again we'll see that in the BPC section of the course.
And you can always specify allow rules with security group but not deny rules then we looked at CBS.
These are the different IBS types who have got General Purpose SSD or GP.
We've got provisioned eye ops SSD which has a 0 1 so those are two different flavors of SSD.
And essentially if you want your ops to go above 16000 you want to move from general purpose over to
provision de ops.
We then have hard disk drives.
So we've got three different types we've got throughput optimized hard disk drives or s.t. one we've
got cold hard disk drives or SC one.
And then we've got IBS magnetic and this is sometimes referred to just as standard as its API name.
And that's typically is previous generations so you might not see that in the exam with the throughput
optimize and cold hard disk drive.
Basically if you need to optimize throughput choose throughput optimize if you just want the lowest
cost storage available use cold hard disk drive.
Sustaining on IBS volumes exist on PBS.
So just think of as the LDS as a virtual hard disk drive in the cloud.
Snapshots exist on S3 and I want you to think of snapshots as a photograph of the disk and snapshots
are actually point in time copies of the volumes and snapshots are incremental.
So this means that only the blocks that have changed since your last snapshot are moved to S3.
And if you take a snapshot for the first time it may take some time to create.
That's because it's doing that's very first one but then it will only replicate what if you take a second
snapshot.
It's only going to replicate the Deltas so it's only going to replicate the changes to create a snapshot
for Amazon's IBS volumes that serve as a route device volumes you should always try and stop the instance
before taking the snapshot.
And that will give you a consistent snapshot but that is optional you can take snapshots on running
instances as well and you can create armies from both volumes and snapshots and you can actually change
e-books volume sizes on the fly including changing the size and the storage type and volumes will always
be in the same availability zone as the easy to instance you can't cannot have an easy to instance in
one availability zone and then an IBS volume in another bear that in mind as well.
In terms of migrating IBS so to move an easy to volume from one availability zone to another you just
take a snapshot of it you then create an army from the snapshot and then you use the AMA to launch that
easy to instance in a new availability zone.
And likewise if you want to move easy to volumes from one region to another take a snapshot of a create
name from the snapshot and then copy the AMA from one region to another and then you use the copied
Amy to launch the new easy to instance in the new region encryption snapshot some encrypted volumes
are encrypted automatically volumes restored from encrypted snapshots are encrypted automatically as
well and you can share snapshots but only if they are unencrypted and you can share snapshots with other
Edelweiss accounts or you can actually make them public as well.
Moving on to unencrypted route device volumes to route device volumes can now be encrypted when you
provision your easy to instance.
You don't need to worry about it but if you do have an unencrypted route device volume that needs to
be encrypted you need to do the following.
So you go ahead and create a snap of the unencrypted route device volume you then create a copy of the
snapshot and then select the encrypt option and then you create an army from the encrypted snapshot
and then you use that EMI to launch the encrypted instances.
So just like we did in the lab earlier on PBS versus instant Storm's instant store volumes are sometimes
referred to as ephemeral storage instant stored volumes cannot be stopped if the underlying host or
hypervisor fails you're going to lose your data and UBS backed instances can be stopped however and
you won't lose the data on this instance if it's stopped and you can reboot both and not lose your data
and by default both route volumes will be deleted on termination however EDI s volumes you can actually
tell AWB to keep the root device volume from being deleted so you can basically stop it from automatically
being deleted.
In terms of encrypting root device volumes how do we do it.
Well we created a snapshot of the unencrypted device volume.
We then created a copy of the snapshot and when we did that we selected the encrypt option.
We then create an EMI from the encrypted snapshot and then we use that HDMI to launch the new encrypted
instances so that's how we basically encrypt our root device volumes using the database console.
Don't forget you can also do it using just software like bit locker etc etc..
Moving on to cloud watch remember that cloud which is used for monitoring performance.
Cloud watch can monitor most of eight of us as well as your applications that run on Adobe US cloud
watch with easy to will monitor events every five minutes by default.
However you can have one minute intervals by turning on detailed monitoring and you can create a cloud
watch alarms which then go ahead and trigger notifications and cloud is all about performance cloud
change is all about auditing.
I'm going to have another slide of that coming up.
So what can you do with cloud watch.
Well you can create dashboards and this will allow you to see what's happening within your adult US
environment all around the world and create alarms.
And this allows you to set alarms that notify you when a particular threshold is hit like 80 percent
or 90 percent CPR utilization.
We can monitor events a club watch events helps us to respond to state changes in our AWOL resources
and you can also use logs club watch logs to help you aggregate monitor and store your logging data.
And like a safe cloud trail versus cloud watch cloud which monitors performance you think of someone
at the gym cloud trail monitors API calls in the adobe US platforms a cloud trail will tell you who
provisioned and easy to instance or who set up an S3 bucket etc etc..
We then learnt about the command line so you can interact with AWB from anywhere in the world using
the CLIA you are going to need to set up access in IAM.
This gives you an access key idea and secret access key.
The commands themselves are not in the exams but some basic commands will be useful to know for real
life.
But then looked at roles because we looked at on our easy to instance what happens if somebody goes
into our secret directory our DOT AWB directory which is in our home directory and then opens up our
configuration details I'll be able to get our access key idea and secret access key roles are a much
more secure way than storing your access key ideas and secret access key on individual easy to instances.
Roles are much easier to manage and roles can be assigned to an easy to instance after it's being created
using both the console and the command line and roles are universal.
You can use them in any region in the world.
We then went on to bootstrap scripts bootstrap scripts run.
When an easy to instance first boots and can be powerful way of automating software installs and updates.
So we've used it a little bit in this course so far.
We're going to use it a lot certainly in the next section we're going to create a bootstrap script that
installs Wordpress and we're gonna use that to connect to our audience instances.
So bootstrap scripts are incredibly useful as well.
We then learnt about instance metadata and user data.
So it's used to get information about an instance such as a public IP and to do it you just run a curl
and then 1 6 9 to 5 forward at 1 6 9 to 5 4 forward slash latest sports slash metadata.
If you want to get your user data your user data is literally your bootstrap script that is passed to
your easy to instance when it first boots up.
And again you just run a curl 1 6 9 2 5 4 1 6 9 0 2 5 4 forward slash US forward slash and then you
use a data center.
Moving on to ESFs that was the very last lab so we learnt that it supports the network file system version
for NFC for protocol.
You only pay for the storage that you use.
You don't need to pre provision.
You don't need to go in.
You know spin up an eight gig instance or something like that.
It's basically grows as you put more files on it and can scale all the way up to petabytes and it can
can support thousands of concurrent NFC East connections.
Remember if you need shared storage you can't share CBS with multiple easy two instances.
Doesn't work like that but you can create an NFL s airfares mount and then you can store your files
in there and multiple E2 instances will be able to access it.
And with airfares data is stored across multiple Availability Zones within a region.
And in terms of the consistency model you get read after rate consistency.
Moving onto easy to placement groups a placement group is simply how you place your easy to instances.
There's three different types of placement groups.
The first one is a clustered placement group.
We then have spread placement groups followed by petition placement groups a clustered placement group
is where you want low network latency high network throughput.
This will be where all your easy two instances are in the same availability zone and as close together
as possible so that you don't have any sort of latency spread placement group.
These are for individual critical easy two instances.
So you want to make sure that they are basically in different availability zones and different pieces
of hardware so if a does fail it's only going to affect the one easy to instance it's not going to take
two or three out at a time and partitioned placement groups are effectively for multiple easy two instances.
So this will be for things like heat DFS heat base and Cassandra clusters.
And this is where you have multiple E2 instances into a partition and each partition is always going
to be on separate hardware or separate racks from the other partitions.
So those are three different types of placement groups.
Just remember the clustered placement group doesn't span multiple Availability Zones whereas the spread
placement and partitioned placement group can span availability zones.
Remember that the name that you specify for a placement group must be unique within your own NWS account.
Only certain types of instances can be launched into placement groups so these will be things like compute
optimize Jeep you memory optimize storage optimized etc..
And then also remember that NWS recommend homogenous instances within a cluster of placement groups.
So this is where you have the same instance type you can't merge placement groups and you can't move
any existing instance into a placement group.
What you can do though is create an EMI from your existing instance and then launch the new instance
from the Amway into a placement group.
So that is you are at the end of the easy to section of the course I hope you had lots of fun in the
next section of the course we're gonna look at relational database services or ideas.
We're gonna be using Wordpress which we'll be using a backend my sequel instance.
And again you're gonna get a lot more hands on fun with AWP so if you've got the time please join me
in the next lecture.
Thank you.