Stack Self Drifts

[felipeamarante]

Describe the bug The template has a Lambda Backed Custom Resource (CustomControlTowerDeploymentLambda) that modifies the attribute of the S3 Bucket (CustomControlTowerPipelineS3Bucket) created by the same stack. Thus, causing a configuration drift and potential alerts and bigger issues. Is there any way to avoid that? Perhaps avoid custom resources that configure stack managed resources? Thx

To Reproduce Launch the Stack, check drift.

Expected behavior Expected behaviour is to have no configuration drifts after stack creation. This could cause other issues if we had any mechanisms to revert drifts automatically.

Please complete the following information about the solution:

• [x] Version: v2.2.0
• [x] Region: eu-west-1
• [x] Was the solution modified from the version published on this repository? NO
• [x] If the answer to the previous question was yes, are the changes available on GitHub? NO
• [x] Have you checked your service quotas for the sevices this solution uses? N/A
• [x] Were there any errors in the CloudWatch Logs? N/A

Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context Add any other context about the problem here.

[balltrev]

Hey @felipeamarante, thanks for bringing this to our attention, I've opened a backlog with the team to tackle this issue.