[#286] Fix: Terraform plan can't be applied because of VPC endpoint misconfiguration #309
+1
−26
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.
What happened 👀
Insight 📝
VPC endpoints are a good way to optimize because they lower traffic costs. However, they also come with hourly charges, and in cases where there is not much traffic, using a VPC endpoint might end up being more expensive than just paying for the traffic. I believe the decision to add a VPC endpoint should be made on a per-project basis and should not be included in the template by default. For most projects, it makes sense to have VPC endpoints for development with regular deployments and debug logs, but for staging and production, it might be better not to use VPC endpoints.
Proof Of Work 📹
Before the fix we weren't able to apply TF plan generated from our code:
After the fix TF plan can be applied without error ✅