<blockquote>
<p>I want to be able to control how the different nodes are
interconnected to each other in this network. Is there a way to do
this on Bitcoind?</p>
</blockquote>
<p>As per <a href="https://github.com/bitcoin/bitcoin/blob/master/share/examples/bitcoin.conf" rel="nofollow noreferrer">bitcoin.conf</a> I suggest setting up the <code>connect = X.X.X.X</code> flag on your nodes. It will enforce connecting only to the peers specified by you. Not sure if this is the answer you are looking for though?</p>

CC BY-SA 4.0
2020-10-01T16:01:36.763Z
2020-10-01T16:01:36.763Z
Tony Sanak
<p>I am looking to set up a private network of Bitcoin nodes over multiple machines (e.g, on multiple VMs on Amazon EC2) for experimentation. I want to be able to control how the different nodes are interconnected to each other in this network. Is there a way to do this on Bitcoind? The regtest mode that is commonly cited as a solution for this seems to have the ability to create multiple nodes on a single machine. Can it also be used to interconnect nodes across different machines according to a specified topology?</p>

<network><private-blockchains><amazon-web-services>
Bitcoin private network on Amazon EC2
cepheus
# Bitcoin private network on Amazon EC2

(Asked by: username_0 on 2020-10-01)

I am looking to set up a private network of Bitcoin nodes over multiple machines (e.g, on multiple VMs on Amazon EC2) for experimentation. I want to be able to control how the different nodes are interconnected to each other in this network. Is there a way to do this on Bitcoind? The regtest mode that is commonly cited as a solution for this seems to have the ability to create multiple nodes on a single machine. Can it also be used to interconnect nodes across different machines according to a specified topology?

**Tags:** network, private-blockchains, amazon-web-services


---

## 1 answers

### Answer by username_1 on 2020-10-01. Score: 2

> I want to be able to control how the different nodes are
> interconnected to each other in this network. Is there a way to do
> this on Bitcoind?

As per [bitcoin.conf](https://github.com/bitcoin/bitcoin/blob/master/share/examples/bitcoin.conf) I suggest setting up the `connect = X.X.X.X` flag on your nodes. It will enforce connecting only to the peers specified by you. Not sure if this is the answer you are looking for though?


---

