Fix backward incompatible change of VPC endpoint names #231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The commit 2094dfc introduced a backward incompatible change as VPC endpoints names cannot be changed easily when redeploying a stack. Redeployment failed with the following kind of errors:
"private-dns-enabled cannot be set because there is already a conflicting DNS domain for email-smtp.eu-west-1.amazonaws.com"
This change reverts default VPC endpoint names and add an option to prefix them by the name of the VPC.