Delete unused services

Question

I enabled KMS, Secrets Manager, AWS Config, and RDS using CloudFormation for an AWS workshop. After the workshop, I removed the services I used, but the above four services were not deleted.

Currently, I am being billed every month for these services. When I try to delete them, I receive a message stating that I do not have admin privileges, even though I am using the root account.

How can I avoid these charges and successfully remove the services?

re:Post Agent · Answer

To address your issue and remove the unused services, you'll need to take a few steps:

1. First, ensure you are indeed logged in as the root user. If you're getting messages about lacking admin privileges while using the root account, there may be an issue with your account access.

2. For each service (KMS, Secrets Manager, AWS Config, and RDS), you'll need to go to their respective consoles and delete the resources manually. Here's a general approach for each:

- For KMS: Delete any customer-managed keys you're not using.
   - For Secrets Manager: Delete any secrets you've stored.
   - For AWS Config: Disable the service in the regions where it's running.
   - For RDS: Delete any database instances, snapshots, and automated backups.

3. Since these services were created using CloudFormation, you should also check your CloudFormation console for any stacks that might still be active. Deleting the stack should remove all associated resources.

4. If you're still unable to delete these services, you may need to contact AWS Support. They can help investigate why you're encountering permission issues with your root account and assist in removing the services.

5. Use AWS Cost Explorer to identify exactly what you're being billed for. This can help pinpoint any hidden resources or usage that might be causing charges.

6. If all else fails and you're certain you want to stop all AWS usage, you could consider closing your AWS account. However, this is a drastic step and should only be done after backing up any important data and carefully considering the implications.

Remember, even if services appear inactive, they may still incur charges due to stored data or reserved capacity. Always double-check that you've removed all associated resources when trying to stop charges for a service.  
**Sources**  
[Deleting services | AWS re:Post](https://repost.aws/questions/QU1h_ka2UXTFicBDY64hK7Sw/deleting-services)  
[Billing question | AWS re:Post](https://repost.aws/questions/QUZA-2yGeSSQmXKe0Wxe_hzg/billing-question)  
[Trying to turn off on services in my account | AWS re:Post](https://repost.aws/questions/QUmM48ELjxTOqO2tfybExYAQ/trying-to-turn-off-on-services-in-my-account)  
[Unable to delete my RDS instance | AWS re:Post](https://repost.aws/questions/QUGwrxrQRNRqWuPfx8f0rXsg/unable-to-delete-my-rds-instance)

Delete unused services

Relevant content