nextflow-io / nextflow-io/nextflow
Nextflow can only provision Fargate resources with public IP on AWS batch
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
Bug report
Nextflow can only provision Fargate resources with public IP on AWS batch
Expected behavior and actual behavior
According to the company's security policy, we aren't allowed to create Fargete resources with public IP.
But the public ip is hard code.
" container.withNetworkConfiguration( new NetworkConfiguration().withAssignPublicIp(AssignPublicIp.ENABLED) )
"
https://github.com/nextflow-io/nextflow/blob/master/plugins/nf-amazon/src/main/nextflow/cloud/aws/batch/AwsBatchTaskHandler.groovy#L566
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in plugins/nf-amazon/src/main/nextflow/cloud/aws/batch/AwsBatchTaskHandler.groovy at the referenced network configuration around line 566. Trace how AWS Batch Fargate network settings are selected, then verify the behavior for deployments that must not assign a public IP. Done means Fargate resources can be provisioned without the hard-coded public-IP requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, groovy
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100