- We're ready to look at the final pillar
implemented against our widget maker's design.
So we want to see how we implement
a good cost scenario for the Widget Maker's organization.
So we're going to take a look now at all
of those five systems that we're moving into AWS.
See how we do it as inexpensively as possible.
First of all we're looking order processing,
well we want to make sure we use managed databases.
Because remember, this is going to cut down
on operational hours for those who have
to manage these databases.
Because we're not managing the operating system.
We're not managing the individual instances.
We're just managing the database service itself,
that's running and managed by the RDS managed service.
For inventory management, we're going to do exactly
the same thing, use a managed database.
And then for payroll, we'll also use a managed database.
We've got an extra tip here that's very important.
We're going to use the read replica as needed.
In other words remember, we've got payroll
maybe every week, maybe every two weeks
but we've got payroll only on certain days
and on certain frequencies.
So what we can do is actually bring
up the read replica when we need it,
but not actually run it all the time
when it's not being used.
So we're not being charged for this instance
that we're not actually utilizing.
For example you could have the read replica
brought online during down time,
the evening before payroll.
That kind of practice allows it
to have time to get the data replicated into it
so payroll processing can occur.
I'm not saying that every scenario
would justify that kind of operation
but if it works for you,
you're really only running the instance
for a few hours every couple of weeks.
The next thing that we're going to
is look at our user data,
we want to make sure we're monitoring
the use of this user data
and watching was users are putting
inside of their S3 buckets.
We've always done this in the past,
we've often controlled our shares
on Window's service for example.
Limiting what kind of data people
can put inside of those shares
so that they're not filling our storage up
with unnecessary data.
In the same way, in our S3 buckets
since we're paying for storage based on size
we want to make sure that we're not
putting unnecessary information in there.
So we want to monitor it and address overuse
or misuse and make sure that we're only using
that for proper business data storage.
And then finally we look at our website.
We want to use the right instance class
so we get the performance that
we need out of it but no more.
Remember we can always upgrade the class later
if our website starts getting more traffic.
We also want to monitor access
and determine what kind of access
is coming into the server and address improper access.
For example if someone found a vulnerability in WordPress
to where they could upload a whole bunch
of large pirated files or something
that other people could download by the thousands.
The next thing you know, your website
is being hit very heavily and your being charged
for bandwidth fees from AWS.
So you want to monitor, if something unusual like
that's happening, you want to be able to intervene
and stop it before your cost go through the roof.
So these are all some things that we can do to make sure
we have a cost optimized design for Widget Makers.
Well we've gone from, we've got Widget Makers
in their on-premises only deployment
to giving them a good plan that can work in the cloud.
We can see that we have resiliency designed into that plan
because we're using multi-AZ deployments.
We're using elastic load balancing where it's needed.
We're using the right technologies
where we need those technologies.
We've also implemented a well-performing solution
because we've made sure we're using things like
managed services for our databases.
And we've made sure that we've implemented
our website behind an ELB cluster,
giving us the performance we need out of our website.
We've also managed our S3 buckets to make sure
that we're getting the performance we need out of them
by having different buckets for different departments.
We also see that we've got security in our solution.
We're making sure we've got
the right IAM user roles and groups.
And we're making sure that we're using encryption
where we need to use encryption.
We have the solid security foundation we need.
And finally we're making sure that things
are monitored and managed in such a way
that we have our costs as low as possible.
With a solution like this
I think Widget Makers will be very happy.
(soft upbeat music)