- 最新
- 投票最多
- 评论最多
Hi,
I understand that when running the command “aws resourcegroupstaggingapi get-resources” you are getting resources in the output that have already been deleted.
Testing in my account this command only shows resources that still exist. I was able to test with several different resources and every time they were deleted they no longer showed up in the command. If you notice that there is a specific resource that you have deleted which is still appearing in the results of the CLI command I would recommend opening an AWS support ticket. There an engineer can help troubleshoot the specific issue.
I hope you have a great rest of your day!
I am having the same issue with EC2 snapshots. Even though the snapshot has been deleted for hours I am still able to see it return on the aws resourcegroupstaggingapi get-resources. We do not have a support plan, how can we understand the issue?
I have the same problem. With resourcegroupstaggingapi get-resources I get backup plans that have been deleted. And when I try to retag or remove them I get the error 400 ResourceNotFoundException. From the console I don't see those plans neither from Tag Editor nor AWS Backup.
Hello, I'm having the same issue, resourcegroupstaggingapi is returning unexisting or previously deleted resources. Our workflow is very elastic so lots of resources are created and deleted throughout the day, so maybe this is expected. But I'm concerned with the cost implications of having deleted resources reported by this API. Has anybody been able to fix this?