How do I terminate active resources that are no longer needed in my Amazon Web Service account?

Closing your account might not automatically terminate all your active resources. Some active resources may even continue to incur expenses after you close your account. You need to pay any usage fees incurred before the account is closed.

To avoid incurring unexpected charges, it's a best practice to regularly check if you have active resources that you no longer need in your account. Then, terminate these unnecessary resources.

To check whether there are any active resources in your account, please do the following:

1. Open the My billing dashboard.

2. In the navigation pane on the left side of the screen, choose Bills.

Ningxia Western Cloud Data Technology Co., Ltd. This entry shows the activity resources of your account in the Ningxia region

Beijing Sinnet Technology Co., Ltd. This entry shows the activity resources of your account in the Beijing region

3. If your account is a payment account in consolidated billing family. Choose Bill details by service to identify the services that are incurring charges. The Bill details by service section shows all the charges incurred by various Amazon Web Service in your account.

Note: It’s a best practice to check the current month's bill, The payment account in consolidated billing family should check the Bill details by service section and check it together with the previous month's bill to identify all services that incur charges.

Choose Bill details by account to identify the active resources of each member account of the consolidated billing family in deferent regions. You must terminate the resources in these Regions.

You need to go to the service console to delete those resources. To terminate active resources under different services, do the following:

1. Open the Amazon Web Service Management Console.

2. Open the console for the service that contains the resources that you want to terminate (for example, EC2、RDS、S3). You can find a specific service by entering the service name in the search bar.

3. After opening the service console, terminate all your active resources using the instructions linked below. Be sure to check each Region where you have allocated resources.
Tip: You can change the region using the region selector in the upper right corner of the navigation bar
For more information on avoiding unexpected charges, please refer to Avoiding unexpected charges.

For more specific guidelines of terminating the active resources of the commonly used services, Please click the link.

If you have any problem with deleting a resource, you can enter the support center and create a case to contact us.

1. How do I delete an EC2 instance?
To delete active Amazon EC2 instances, please see How do I delete or terminate my Amazon EC2 resources?

2. How do I release an elastic IP address?
To release an elastic IP address, please see How do I release an elastic IP address?

3. How do I delete EBS volumes and snapshots?
To delete EBS volumes and snapshots, please see Delete EBS volumes and Delete EBS snapshots?

4. Why is my EBS volume not deleted with the instance? If you do not check "Delete on Termination" when you configure the EBS volume during EC2 instance creation, the Amazon EBS root device volume will not be automatically deleted when you terminate the Amazon EC2 instance, and you will need to delete it manually. To delete an EC2 instance with deletion protection enabled, you must disable deletion protection.

You can click here to learn more about deleting an EC2 instance, and jump to 1:43 to watch.
You can click here to learn more about deleting Elastic IP addresses, EBS volumes, etc.

1. How do I delete S3 bucket?
To delete S3 bucket, please see How do I delete S3 bucket?

2. How do I delete bucket objects?
To delete bucket objects, please see How do I delete bucket objects?

3. Why do I have no way to delete the bucket created by Elastic Beanstalk?
If the bucket was created by Elastic Beanstalk with the name "elasticbeanstalk", you cannot delete the bucket normally because Elastic Beanstalk applies a bucket policy to the bucket it creates to allow the environment to write to the bucket and prevent it from being accidentally deleted. For more information, please see deleting Elastic Beanstalk Amazon S3 buckets..

You can click here to learn more about deleting S3.

1、 How do I delete DB instance?
To delete RDS instance, please see How do I delete DB instance?

2、 How do I delete DB snapshots？
To delete RDS instance, please see How do I delete DB snapshots?

3、 How do I delete retained automated backups of DB instances?
To delete retained automated backups of DB instances, please see Deleting retained automated backups.

4、Why do I have no way to delete a database instance, the system shows "To be able to delete the database, please modify the database and disable deletion protection"?
This is because "deletion protection" is enable for your DB instance. For more information about Deletion Protection, please see Deletion Protection.

You can click here to learn more about deleting RDS.

1、How do I delete CloudWatch alarm?
To delete CloudWatch alarm, please see How do I delete CloudWatch alarm?

2、 How do I delete CloudWatch logs？
To delete CloudWatch logs, please see How do I delete CloudWatch logs?

3、Can I delete CloudWatch logs through the console?
You can also delete logs by using the CloudWatch console, as follows:
a. Please log in to the CloudWatch console:
Click here to enter Ningxia region
Click here to enter Beijing region
b. Select "Logs" on the left, click "Log Groups", you can select the option box, click "Actions" in the upper right corner, and select "Delete Log Group(s)" to delete it.
c. At the same time, we also suggest that you click the entries in the left column to check whether there is data. If there is data, you can also delete it.

You can click here to learn more about deleting CloudWatch.