Open paulpilone opened 1 year ago
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:https://github.com/iodepo/OceanBestPractices/blob/b0add5fc008a3f7a2bbdefab68007e987a2a0064/cdk/ingest/index.ts#L105.
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.
privateDnsEnabled
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:https://github.com/iodepo/OceanBestPractices/blob/b0add5fc008a3f7a2bbdefab68007e987a2a0064/cdk/ingest/index.ts#L105.
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.