2 Answers
- Newest
- Most votes
- Most comments
1
Thanks for the reply!
This still didn't work. When the TSE-SE is deploying on the 'deploy' stage, it fails saying it doesn't exist but builds it few seconds later.
Then when you re-run the pipeline it says its already there.
I'm leaning towards a bug in the new 1.6.1 version of LZA.
answered 2 months ago
1
To resolve the Resource of type 'AWS::Logs::LogGroup' with identifier 'xxxxx' already exists
error when working with AWS resources like CloudFormation, follow these condensed steps:
- Use the AWS Management Console, CLI, or SDKs to check if the
LogGroup
already exists. For CLI, run:aws logs describe-log-groups --log-group-name-prefix "your-log-group-name"
- If the existing
LogGroup
is no longer required, carefully delete it to avoid data loss, using:aws logs delete-log-group --log-group-name "your-log-group-name"
- After deletions, attempt your operation again.
Resources:
Relevant content
- asked 6 months ago
- asked 8 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
same issue here. once you delete the log in some cases it is automatically created in the meantime and you get the same error. looks like a bug