UI for Nextflow Pipelines 🚀
An private hosted DNS zone is used to identify batchbot. the INTERNAL_HOST ansible var should be batchbot.labmed.internal or similar.
- Go to the Route53 console
- Ensure that the VPC hosting batchbot, as well as the aws-admin-batch VPC are associated with the "labmed.internal" hosted zone.
- Find the internal IP address of the instance that hosts batchbot (eg. 10.0.0.118)
- add A records for {{ INTERNAL_HOSTNAME }} --> IP address
Because the AWS Batch infrastructure does not live in the same VPC as the Batchbot application (aws-admin-batch vs dokku-stack-apps or similar), you must create a VPC peering connection between them. This is currently not part of the CFT deployment and must completed manually
-
Create a new VPC peering connection, selecting the AWS batch VPC as well as the VPC in which batchbot is hosted.
-
After creating, accept the peering request in the console.
-
Add route tables for each, eg:
- aws-admin-batch-private-subnet-rt
- dokku-stack-apps-routetable
-
For the aws-admin-batch-private-subnet-rt, add a route "10.0.0.0/16" --> the peering connection ID (pcx-xxx...)
-
For the dokku-stack-apps-routetable, add a route "172.0.0.0/16" --> the peering connection (pcx-xxx...)
-
Update the security group of the dokku-stack-apps stack to allow inboutn 172.0.0.0/16 traffice.