Use Route53 resolver endpoint security group AWS best practices, or allow BYO security group for the outbound endpoints #84
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.
Currently, the Route53 module uses the "default" security group.
Many companies have locked down the default security group. In our AWS environment, we have deleted all the inbound and outbound rules on the default security group (intentionally, to force each application to use a security group specific to it).
Additionally, the default security group does not follow AWS Best Practices for Route53 Outbound Endpoints.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/best-practices-resolver-endpoint-scaling.html
This PR stops using the default security group, and creates a security group that follows the aws best practices.
It also allows a bring your own security group for the endpoint.
Existing formats were followed.