[Music]
hello I'm Marsha a cloud Support
Engineer here at the aw office in Dublin
sometimes customer asked me how do you
minimize downtime during quired Amazon
RDS maintenance well in this video I'll
be talking about what these maintenance
activities are how to check for them and
how to handle downtime required for this
maintenance let's get started RDS has a
number of maintenance activities that
can be performed such as modifications
that were made but were not set to apply
immediately such as pending actions
online patching to OS updates offline
patches such as DB major and minor
version changes and underlying hardware
maintenance you can review maintenance
activities using the ativ list personal
health dashboard one thing to notice
that our dias hardware maintenance
doesn't appear in the list of pending
maintenance available in the RDS console
I'll show you how to check for these
maintenance using that console later you
should see RDS maintenance in your
personal health dashboard I'll show you
specifically how to review upcoming
hardware maintenance using the personal
health dashboard from the console as you
can see I'm already logged in to the AWS
management console navigate to their
personal health dashboard
choose scheduled changes from here you
can apply filters
choose services
then scroll down and select relational
database service select apply
now add another filter event from here
search for RDS hardware maintenance
schedule
select apply you can also review
upcoming maintenance using the alias
command line interface for more
information check the ativ lea CLI
command reference documentation linked
with this video to minimize downtime for
maintenance activities it's a best
practice to deploy a multi AC setup as
opposed to having a single easy this is
because that except for a database
engine upgrade maintenance is first
performed on the standby then the
standby is promoted to the primary by a
failover maintenance is then performed
on the secondary which was the former
primary now however there is a caveat to
this regarding engine version upgrades
when you modify the database engine for
a database instance in a multi 8e
deployment Amazon RDS upgrades both the
primary and the secondary DB instances
at the same time in this case the
database engine for the entire multi AC
deployment is shut down during the
upgrade now I'll show you how to manage
an update for a database instance from
the console after signing in to the ativ
list management console open the Amazon
RDS console
in the navigation pane choose databases
when you are here you can check for
pending maintenance by scrolling to the
right you can see which instance has
maintenance under the maintenance
section choose the database instance
that has a required maintenance on the
top right go to actions and then choose
one of the following upgrade now or
upgrade at next window if you choose
upgrade at next window and later want to
delay the update you can choose differ
update differed database instance
modifications which are non immediate
modifications are applied during the
maintenance window for example you can
choose to change the database class or
parameter group during your maintenance
window
you
now I'll show you how to adjust the
preferred maintenance window from the
console
from the earliest console in the
navigation pane choose databases then
select the database instance you want to
modify
on the top right choose modify
the modifier database instance page
appears from here in the maintenance
section when you scroll all the way to
the bottom you can see update the
maintenance window
choose continue on the confirmation page
review your changes to apply the changes
to the maintenance window immediately
select apply immediately choose modify
DB instance to save your changes
modifications to the maintenance window
don't cause any impact to your currently
running instances it's a best practice
to choose a time frame when your DB
operations are at the lowest workload
thanks for watching and happy cloud
computing from all of us here at AWS
[Music]