- Newest
- Most votes
- Most comments
Thanks, Riku! I looked at the nested stack and it seems my account had some AWS config settings from a previous project I have used CLI commands to clear it. I will re-run the stack and report back if I am able to move forward
aws configservice get-status aws configservice delete-configuration-recorder --configuration-recorder-name default aws configservice delete-delivery-channel --delivery-channel-name default
Hello.
There seems to be a problem with the resource being created in the nested stack "MigrationImmersionDay-AWSConfig-OEIUS1JWCTPK".
Please open "MigrationImmersionDay-AWSConfig-OEIUS1JWCTPK" from the CloudFormation console and click "Detect root cause" to check the problematic part.
The error message will probably explain why creation failed.
Hello Riku, Thanks for the prompt response that is the error I posed in the question it has the below error:
Embedded stack arn:aws:cloudformation:us-west-2:189301807318:stack/MigrationImmersionDay-AWSConfig-OEIUS1JWCTPK/13624f50-8817-11ef-86a9-0698bda0eea9 was not successfully created: The following resource(s) failed to create: [ConfigRecorder, DeliveryChannel].
I reviewed the AWS Config service and even manually tried to edit the settings to enable recorder but same issue. The CFN stack always fail with the same error message The following resource(s) failed to create: [ConfigRecorder, DeliveryChannel].
Does that mean you open the stack for "MigrationImmersionDay-AWSConfig-OEIUS1JWCTPK" and see that error in the "Event" tab? The problem is the "ConfigRecorder" you are trying to create inside the nested stack, so you need to open the "Event" tab inside the nested stack to see the details.
Relevant content
- asked a year ago
- asked 2 years ago

Clearing the AWS config information helped resolve the issue
aws configservice get-status aws configservice delete-configuration-recorder --configuration-recorder-name default aws configservice delete-delivery-channel --delivery-channel-name default