Skip to content
This repository was archived by the owner on May 31, 2024. It is now read-only.

Conversation

@souravskr
Copy link

Why

By default AGC comes with allowing all IPv4 to the EFS security group.

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.

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`.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant