There is a delay for AWS Config Log to capture the configuration Changes

0

we have EKS clusters being deleted on 7th Feb and this change can be found on CloudTrail. How ever in the AWS config log it only appears on 9th Feb. Please help to clarify the delay.

siying
질문됨 일 년 전431회 조회
1개 답변
0

Hello,

I hope you're doing well.

Thank you for reaching out to us with your concern.

I understand that you have few queries related to delay for AWS Config Log to capture the configuration changes.

Q: we have EKS clusters being deleted on 7th Feb and this change can be found on CloudTrail. How ever in the AWS config log it only appears on 9th Feb. Please help to clarify the delay.

 Usually, There might be a delay in recording resources with AWS Config. AWS Config records resources only after it discovers the resources. However, You're getting more time than expected. To verify this, I have replicated the same in my lab environment, where I can be able to see the config changes as expected. 

 Inorder to find the actual root cause, I would like to check your config resources details. Hence, I would request you raise a support case ticket, where we can go deep dive into the resources to find out the actual root cause.

Thank you! Have a wonderful day!

Reference:

[1] https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/TrackingChanges.html [2] https://docs.aws.amazon.com/config/latest/developerguide/view-manage-resource.html [3] https://docs.aws.amazon.com/config/latest/developerguide/faq.html

AWS
답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠