[Music]
hello hello welcome to solving with AWS
solutions your deep dive in
architectures built by AWS that are
ready to deploy instantly in the cloud
I'm Robbie your host joined today with a
woman who likes sequels better than the
original hey rock Shauna how are you
doing hey doing awesome Rob how's it
going for you not bad so today we are
talking about operations conductor what
exactly does this solution do so
operations conductor or ops conductor
enables customers to automate their
operational tasks through a simple UI by
configuring event or time-based triggers
for managing their resources so what
does this mean for customers so one of
our key pillars in the AWS well
architected framework is focused on
operational excellence here we recommend
that customers perform operational
procedures as code and automate them so
customers across all industries tell us
they find it challenging to do this at
enterprise scale
can you imagine thousands of resources
across multiple accounts and regions but
don't worry
ops conductor solves this business
problem by enabling customers to
automate their operational tasks easily
that's pretty cool so let's take a
closer look at ops conductor let's do it
all right Rock Shauna ops conductor talk
to me about some of the design
considerations for it
sure but actually before we go into that
I want to talk about important solution
concepts okay yes so we have two main
things actions and tasks okay actions
are pre-configured and those are what
comes along with the deployment of the
solution okay and an example could be
you know easy to create snapshot easy to
copy snapshot so on and so forth and
we've set those up as part of the
solution itself exactly and an important
point is that these actions are
essentially automation documents they
hold the logic for what tasks are
required to be run and these automation
documents are all on AWS Systems Manager
which is our engine behind it's nuts
connector so what's the task so a task
is when you configure these actions to
perform on your specific resources in
your specific accounts okay can I have
multiple actions per task it's a one on
one relation so you take a specific
action and you configure that to
do your specific tasks and you can do
further configuration on it like you
know you can choose to run it on a
specific schedule or you know on a
specific event when say my cpu threshold
let's hit and I want to run this
automation task
I got it I got it so how does that fit
into the architecture than a Vox
conductor yeah so let's talk about the
solution design so I'm on the solution
landing page and getting into the
architecture diagram when you deploy the
solution you're gonna have an ops
conductor UI okay which is going to help
you create these tasks from our action
catalog and basically automate these and
run it on your resource this is the
front end where I'm configuring creating
that relationship between the tasks in
the action exactly okay so it's powered
by AWS amplify which is our development
platform to build mobile and web
applications okay and it's going to be
hosted on an Amazon simple storage
service s3 bucket and it's gonna be
sitting behind a cloud front for content
delivery network typical front-end then
so how does that interface with the
services itself yeah so there are gonna
be a lot of lambda function sitting in
the background we are gonna have a user
microservice which is gonna love you to
you know manage your user access to the
UI it allows you to invite edit delete
users then we have an action micro
service which basically takes these
automation documents from a double
Systems Manager and applies the key and
the values for the document tags okay
which is how those documents get pulled
into ops conductor sorry yeah and the
important thing about that is the next
time you create your own action in your
aw Systems Manager as long as you apply
the key and the value this lambda is
gonna pull that into your ops conductor
UI that's streaming it then exactly okay
and then we have the task micro service
which helps you create edit and delete
tasks on the UI okay right so the
important thing here is that when you
create a task on the UI and you can
create a task based on a schedule or a
given event as I mentioned before but
when you create a task a new
CloudFormation template gets created and
deployed into your Amazon s3 bucket so
we're automating the creation of this
templates but we have to apply them the
customers apply them yeah customers will
have to deploy the template once they
create the task this is basically that
task specific template makes sense yeah
customers will have to deploy it in
every
region in which they want the resources
to run the automation tasks okay got it
so what else is happening so when you
create a task the next step is a
resource selector lambda function is
going to be triggered which is going to
queue up all your operational tasks that
you've selected to be performed on your
specific resources and it's going to
send these messages to an Amazon simple
queue service all right and from sqs
it's gonna be sent to a queue consumer
lambda function which is gonna take in
all that information and run the
automation for you that's actually
conducting a lot of this stuff exactly
Jonker there's going to be triggered
whenever an event happens based on a
cloud watch event rule and it's gonna
take in all the automation documents
from aw Systems Manager apply all these
you know tasks specific configuration
that you as a user had given and it's
gonna run conduct the operations awesome
so Rukhsana we have lots of actions we
could create and associate with a task
can you walk me through an example of
vertical scaling for an ec2 instance yes
sure so I've completed a deployment of
operations cut it I'm gonna walk you
through that UI no tasks so far but you
can basically get started yeah you can
use this to create your tasks as well as
add and invite other users manage other
users I invited you robbed in to join
alright so let's talk about tasks so all
of the magic starts when you click on
get started ok so this is gonna take you
to your actions catalog so these are all
predefined as part of the solution
itself exactly these are all what we
have predefined for you but you can
definitely go customize and add more
actions ok as automation documents in
systems manager it'll be pulled over
here so these are the actions how do I
tell this to a task yeah so you can
create the task from here here let me
create the resize instance ok alright
I'm gonna click on this alright so I'm
trying to create the resize instance
task so let's go through the step by
step procedure so I have to give a task
name and description so this particular
task will be resizing an ec2 instance
based upon some parameters yep it's
gonna be based on on CPU utilization
okay whether it's high or low awesome
all right so we're naming the task
exactly then you'll have to give a
target tag for the task ok this is
probably one of the most in
in steps so this is any tag that you
want to create but once you create the
task you will have to go and apply this
tag to all of the resources on which you
want to run the operations what's tying
this together to the actual report okay
so give a name give a target name and
then you can give the complete range of
instances with which you want to you
know resize go up or down depending on
the utilization gotcha and this is now
the thresholds that you were talking
about earlier so if it falls below or
goes above now we're seeing where that
thresholds come through yep and then the
next step is you can choose to create
your tasks to happen either based on a
schedule or based on an event okay so
this one's five hours it looks like yeah
so I'm gonna do it based on a schedule
of every five Armos it's gonna check
okay and then the fun part here is you
can choose any number of accounts and
any number of regions on which you want
to run your operations tasks on so if I
have multiple accounts we could apply
them here and yeah have one task for
multiple accounts exactly you don't have
to worry about your multi account
environment really manage it for you
just make sure you deploy that specific
task template in every account and every
region that's awesome so this seems like
a great way to consolidate and help
conduct a lot of the operations for your
workloads exactly that's awesome thanks
for honor thanks Rob
so ops conductor takes the operational
burden away from customers so that they
could focus on innovating and delivering
cutting-edge applications at high
velocity that's right
as a result you'll be able to reduce
operational complexity achieve effective
resource and cost management limit human
error and enable your systems to respond
consistently to events so what are you
waiting for go ahead and deploy ops
conductor from our AWS solutions website
[Music]
you