Learn how to clean up RDS resources so as not to incur unexpected charges.
(Narrator) As usual, it's important to make sure that we clean up the resources that we no longer need so that we won't be charged for them. I'm going to individually select each of these databases, except for the MySQL source database. We're going to use it in a future lesson. I'll select the restored MySQL, go up to Instance Actions, and choose delete. I'll be asked if I want to create a final snapshot, and the answer is no. I don't really care about this instance anymore. Click the acknowledgement checkbox, and choose delete. Repeat the steps for the Aurora read replica.
And uncheck the MySQL that we just selected so that the instance actions will become available. Choose delete, say no to the final snapshot, and acknowledge the deletion. What's this error? It says that because this is a read replica, we can't delete it right away. We have to cancel, go back out, and promote this to its own full-fledged RDS instance. This will decouple it from the source database. Click Instance Actions, and go to Promote Read Replica. This says it will take a few minutes to complete, and replication will stop.
That makes sense, so click Promote Read Replica. Now that we've promoted the Aurora read replica, we should be able to go to Instance Actions and choose delete. We don't want the snapshot, and we acknowledge that we won't get back this data again. Now both the read replica and the restored database are in the deleting process. And the MySQL source database sticks around for a future lesson. If you're planning to follow along, do keep it. Otherwise, you want to delete it, so you won't be charged for it.
Now that both instances are fully deleted, there's one more thing you should look at. Under Snapshots on the RDS Dashboard, you'll see any snaps that have been taken as backups of your instances over time. So because these instances did not live long enough to actually kick in their nightly backup, there's nothing here except the one that backs up the currently active instance. However, you want to check here, because these snapshots would incur a cost on your bill if they're left sitting around.
Join AWS architect Brandon Rich and learn how to configure object storage solutions and lifecycle management in Simple Storage Service (S3), a web service offered by AWS, and migrate, back up, and replicate relational data in RDS. Find out how to leverage flexible network storage with Elastic File System (EFS), and use the new AWS Glue service to move and transform data. Plus, learn how Snowball can help you transfer truckloads of data in and out of the cloud.
- What is data management?
- AWS S3 basics
- S3 bucket creation
- S3 upload and logging
- S3 event notifications
- S3 data lifecycle configuration
- Working with Amazon Elastic Block Store volumes
- Creating and mounting an EFS
- Creating an AWS RDS instance
- RDS backup and recovery
- Moving data with AWS Database Migration Service
- Moving data with Data Pipeline and Glue
Skill Level Intermediate
Amazon Web Services: Monitoring and Metricswith Sharif Nijim2h 4m Intermediate
Amazon Web Services: Data Serviceswith Lynn Langit4h 30m Intermediate
Amazon Web Services: High Availabilitywith Sharif Nijim2h 17m Intermediate
Amazon Web Services for Data Sciencewith Lynn Langit3h 56m Intermediate
2. Object Storage
3. File Systems
4. Database Services
5. Getting Data to AWS
6. Moving Data in AWS
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.