aws-solutions/content-analysis-on-aws

Conflict with

gmarchand opened this issue · 6 comments

gmarchand commented

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

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

gmarchand commented

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

I'm investigating...

ianwow commented

@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

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

ianwow commented

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.