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 Amazon Elastic Kubernetes Service

語言

English

Stefan

已提問 8 個月前檢視次數 235 次

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?

相關內容