Learn how to clean up EBS- and EFS-related resources so as not to incur unexpected charges.
- [Tutor] As always, it's important to clean up the resources that we created, so we don't incur any unexpected costs from AWS. We'll start by going to EFS. Select EFSDemo file system and choose Delete file System. "This is a destructive action that cannot be undone", that's okay for now. Again we have to confirm that we really mean it by pasting in the file system ID. Now that's going away. Now that the file system is deleted, let's go to EC2 and get rid of those nanos. I'll click on Running Instances, I'll select both EBSDemo1 and EBSDemo2, go to Actions + Instance State and choose Terminate.
Now you might notice this action down here called Delete EBS volumes. This isn't really an option that I can check but rather a reminder that if I have any EBS volumes attached to these instances that do not have the delete on termination flag set, they're going to persist past when these instances are terminated. Now that might be exactly the behavior that we want. In this case it's not so when we're done with this, we're going to go visit the EBS section of the console and clean up those volumes. For now, to get rid of these instances and their associated root volumes that do delete on termination, we'll say yes, terminate.
Now that these instances are terminated and we'll no longer be charged for them, let's head over to the Volumes section of Elastic Block Store. We can see there's one EBS volume remaining that had the Delete on Termination checkbox unchecked. So we'll go up to Actions and Delete Volume. Now that we've deleted the volume, we also need to clean up the Snapshots and the AMI's. We have to start with the AMI because we won't be allowed to delete a Snapshot that forms the basis for one. So we need to come here, look at our AMI, make sure it's highlighted, and choose Deregister.
Now that we've deregistered the AMI, we can successfully delete the Snapshot. And with that we've cleaned up everything that we created in this chapter, and we won't incur any new charges for them.
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.