Issue with SQS when deploying a new but identical stack.

[paulpilone]

I ran into this issue when deploying the new production stack where the deployment tries to attach a second SQS endpoint when one already exists (e.g. the dev stack existed when trying to deploy the prod stack). I believe the issue comes from here:

OceanBestPractices/cdk/ingest/index.ts

Line 105 in b0add5f

privateDnsEnabled: false,

.

The quick fix was to comment out privateDnsEnabled but I don't think that's the permanent solution. This should be addressed or else it might be difficult to spin up a new environment if needed.