This repository was archived by the owner on May 31, 2024. It is now read-only.
Allow The Compute Environment Only to EFS Security Group#604
Draft
Allow The Compute Environment Only to EFS Security Group#604
Conversation
Why --- - By default AGC comes with allowing all IPv4 to the EFS security group. - Executing API through VPC endpoint for API Gateway yields following error: ``` HTTP 403 Forbidden error when connecting to my API Gateway APIs from a VPC ``` How --- - Use `ComputeEnvironment` only instead of `IComputeEnvironment` from `aws-cdk/aws-batch-alpha`. - The ComputeEnvironment has `Connections` type property which allows `engineBatch` & `workBatch` to set as the inputs for the EFS security group inbound role. - Change the endpoint type for API Gateway from `Regional` to `Private`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Why
By default AGC comes with allowing all IPv4 to the EFS security group.
How
ComputeEnvironmentonly instead ofIComputeEnvironmentfromaws-cdk/aws-batch-alpha.Connectionstype property which allowsengineBatch&workBatchto set as the inputs for the EFS security group inbound role.