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
demandé il y a un an431 vues
1 réponse
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
répondu il y a un an

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions