Can I bind foundationdb to 0.0.0.0
- Dominant language
- C++
- Stars
- 16.7k
- Forks
- 1.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 126
Description
I am trying to figure out how to make the foundation DB accessible via the EC2 instance's public IP. Looks like I can only bind the foundation DB to network interfaces that are exposed within the instance, i.e., the ones that show up when I run the `ip a ' command. EC2 instances don't expose public IPs; instead, they perform Network Address Translation (NAT) from a public IP to the EC instance's private IP.
Meaning I cannot bind `fdbserver` to the instance's public IP. If it were any other server, I could just bind it to 0.0.0.0 and be good to go. But I am not able to do that with Foundation DB.
Here are my questions:
1. Is there a way to bind fdbserver on 0.0.0.0?
2. is it possible to host an FDB server/cluster on ec2 instances with their public ips?
Contributor guide
Research direction
Start with the fdbserver binding behavior described in the issue and compare it with the EC2 networking model, including the interfaces shown by `ip a` and public-to-private NAT. Determine whether binding to 0.0.0.0 or hosting a cluster through EC2 public IPs is supported, and document the confirmed deployment guidance or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, databases, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100