Conflict with - Githubissues

aws-solutions / content-analysis-on-aws

As of August 30, 2023, this AWS Solution is no longer available. Existing deployments will continue to run. The functionality provided by Content Analysis on AWS will be superseded with functionality in Media2Cloud on AWS and Content Localization on AWS. We encourage you to explore these solutions.

https://aws.amazon.com/solutions/implementations/aws-content-analysis/

Apache License 2.0

96 stars 47 forks source link

Conflict with #7

Closed gmarchand closed 2 years ago

gmarchand commented 3 years ago

This resource WorkflowExecutionLambdaDeadLetterQueue has a fixed name and it's in conflict with Media Insight Engine

WorkflowExecutionLambdaDLQ already exists in stack arn:aws:cloudformation:us-east-1:xxxx:stack/mie202003-3/cd9rrrr

ianwow commented 2 years ago

Not sure how to reproduce this. Looks like something was wrong with the way CAS was deployed.

gmarchand commented 2 years ago

Hello.

I have deployed MIE stack in my account. And I have deployed another stack of Content Analysis in the same Account. Due to this fixed name (without random suffix) I can't deploy Content Analysis stack.

ianwow commented 2 years ago

I'm investigating...

ianwow commented 2 years ago

@gmarchand How are you deploying MIE and Content Analysis? There are at least three possibilities for both MIE and CAS:

Building cloud formation templates from script with build-s3-dist.sh
Clicking the Launch Stack button in the README
Clicking the "Launch in AWS Console" button in the solution page

I'm having trouble reproducing this issue.

gmarchand commented 2 years ago

Arghh, it's a long time ago. I think I deployed the stack from the README

ianwow commented 2 years ago

I've verified that multiple CAS and MIE instances can be deployed to the same region and on the same account. The WorkflowExecutionLambdaDeadLetterQueue name is a logical name. It's resource id is different for every stack, so there should be no conflicts on that resource.