- Newest
- Most votes
- Most comments
I understand your concern regarding the deletion of AWS OpsWorks Stacks items and the associated billing. You are correct that AWS OpsWorks Stacks has reached its end of life and is no longer supported. The service was officially disabled for both new and existing customers on May 26, 2024.
Given this situation, you won't be able to delete the OpsWorks stacks, layers, and other related items through the usual methods in the CLI or console. AWS strongly recommends that customers migrate their workloads to other solutions as soon as possible.
Regarding your concern about billing, since you've already deleted the EC2 instances and other associated resources, you should not incur any additional charges for those. The OpsWorks stack and layer configurations themselves do not typically incur charges - the costs are generally associated with the actual resources they manage, such as EC2 instances, EBS volumes, and other AWS services used within the stack.
However, to ensure you're not being billed for any remnants of your OpsWorks setup and to clean up your account, I would recommend the following steps:
-
Double-check that all associated resources (EC2 instances, EBS volumes, Elastic IP addresses, load balancers, RDS instances, etc.) have been properly terminated or deleted.
-
Review your AWS bill carefully to ensure no unexpected charges are appearing related to OpsWorks or its associated resources.
-
Reach out to AWS Support for assistance. Since OpsWorks Stacks has been disabled, they should be able to help you remove any lingering configurations or address any billing concerns. You can contact them through AWS re:Post or AWS Premium Support.
While there isn't a direct workaround for deleting the OpsWorks configurations through the usual interfaces, AWS Support should be able to assist you in cleaning up these remnants from your account.
Sources
AWS OpsWorks Stacks - AWS OpsWorks
Stacks - AWS OpsWorks
Delete a Stack - AWS OpsWorks
Deleting AWS OpsWorks Stacks Instances - AWS OpsWorks
answered 2 years ago
Relevant content
asked 5 years ago
asked 3 years ago

Open a support case with AWS and provide details of your resource IDs(Do not post them here), the service team will assist with your request.