Why is my deleted EKS cluster still showing as compliant or noncompliant in my AWS Config rule?

I deleted my EKS Cluster. Why is my EKS Cluster still showing as compliant or noncompliant in my AWS Config rule?

主题

管理与治理容器

标签

AWS Config 亚马逊弹性 Kubernetes 服务

语言

English

Stefan

已提问 8 个月前236 查看次数

1 回答

最新
投票最多
评论最多

这些答案有用吗？为正确答案投票，以帮助社区从您的知识中受益。

-1

Hello,

AWS Config tracks changes in the configuration of your AWS resources, and it regularly sends updated configuration details to an Amazon S3 bucket that you specify. For each resource type that AWS Config records, it sends a configuration history file every six hours. Each configuration history file contains details about the resources that changed in that six-hour period. Each file includes resources of one type, such as Amazon EC2 instances or Amazon EBS volumes. If no configuration changes occur, AWS Config does not send a file.

ladybug

已回答 8 个月前

专家

Antonio_Lagrotteria

已审核 8 个月前

Stefan
8 个月前
That is all clear, though I am looking at the resources page of AWS Config (or the ListDiscoveredResources API) which shows me the latest state not the changes. In that view, my EKS Cluster is still present despite it being deleted (and that view even showing the CloudTrail event of being deleted).

Why is my deleted EKS cluster still showing as compliant or noncompliant in my AWS Config rule?

相关内容