- Newest
- Most votes
- Most comments
In the end I found a workaround to this issue. I simply recreated both of the stacks in CloudFormation, using the same names, templates, parameters and tags as initially, and then ran the delete again. It deleted the new stacks and was able to progress and delete the project.
answered a year ago
To resolve your issue with deleting a DataZone project where underlying resources (EMR Serverless applications) were already deleted through CloudFormation, you'll need to follow a specific approach since the project deletion is failing due to missing resources.
When you delete a project in Amazon DataZone, it attempts to clean up all associated resources, but in your case, it's failing because it's looking for CloudFormation stacks that no longer exist. This is a common issue when resources are deleted outside of their parent service's management interface.
Here's how to address this:
- First, check for any remaining resources associated with your project. Look for:
- Any remaining ENIs (Elastic Network Interfaces) in the VPC/subnets
- Any requester-managed VPC endpoints that might have been created
- Any other AWS resources like IAM roles, Glue databases, Athena workgroups, or CloudWatch log groups
- For the project that's stuck in deletion:
- Try using the RetainResources parameter with CloudFormation to skip the resources that are causing the deletion to fail
- Alternatively, consider using the FORCE_DELETE_STACK option with the DeletionMode parameter
-
If you're dealing with a conformance pack or config rule issue, you may need to delete these from their respective service consoles rather than directly through CloudFormation
-
As a last resort, you might need to contact AWS Support as they can help identify any hidden dependencies and potentially help remove the project from the backend
Remember that deleting a DataZone project is irreversible and will delete all project contents including data sources, environments, assets, glossaries, and metadata forms. However, it doesn't automatically delete non-DataZone AWS resources that DataZone may have helped create - which is why manually deleting the CloudFormation stacks first has caused this issue.
Sources
Sagemaker Unified Studio | AWS re:Post
Delete project - Amazon DataZone
I can't delete endpoint, that was created by me previously | AWS re:Post
Troubleshooting CloudFormation - AWS CloudFormation
answered a year ago
Relevant content
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 5 years ago
