[Q&A] AWS networking of 2.7.1 FLARE project - client can't connect to server #4302
Unanswered
atriaybagur
asked this question in
Q&A
Replies: 1 comment
-
|
Update: with FL API container logs: FL server container logs: FL client container logs (debug log mode) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Python version (
python3 -V)3.12
NVFlare version (
python3 -m pip list | grep "nvflare")2.7.1
NVFlare branch (if running examples, please use the branch that corresponds to the NVFlare version,
git branch)No response
Operating system
Ubuntu 22.04
Have you successfully run any of the following examples?
Please describe your question
Hello 👋 I am trying to set up a FLARE network in AWS and I am facing issues with clients (on one EC2 instance) not being able to connect to server (on another EC2 instance).
This is my nvflare 2.7.1 provisioning script https://github.com/londonaicentre/flip-fl-base/blob/66-feature-fl-port-consolidation/net-1_project_stag.yml#L21
I have an Amazon Web Services (AWS) network load balancer (NLB) with domain address
fl.stag.flip.aicentre.co.ukhttps://github.com/londonaicentre/FLIP/blob/4-feature-fl-port-consolidation/deploy/providers/AWS/main.tf#L352I have a 'central' EC2 instance which runs the FL API container and the FL server container in 2 separate Docker containers within the same network,
flip-fl-api-net-1andfl-server-net-1are their internal Docker addresses respectively: https://github.com/londonaicentre/FLIP/blob/4-feature-fl-port-consolidation/deploy/compose.production.nvflare.ymlI also have a 'site' EC2 instance which runs an FL client container https://github.com/londonaicentre/FLIP/blob/4-feature-fl-port-consolidation/trust/compose_trust.production.nvflare.yml#L18
The errors I am getting are the following:
FL API container logs
FL server container logs (no errors)
FL client container logs:
Note that if I change
host_names:in the provisioning file to be:then the FL API successfully connects to FL server. But the FL client seems to be trying to connect to FL server using the internal Docker name
fl-server-net-1:8002(which is not accessible from another EC2 instance) instead of the actual domain namefl.stag.flip.aicentre.co.uk:I've tried many combinations with little luck so any pointers would be greatly appreciated!! 🙏
If it comes down to the AWS setup I am using, please could you share working examples of AWS networking setups?
Thank you for your time !!
Alex
Beta Was this translation helpful? Give feedback.
All reactions