.svg?alt=media&token=f31f417e-1743-4ed1-8244-f1ad9a4fd041)
Configuring P12 Files
Last updated
Was this helpful?
Last updated
Was this helpful?
P12 files contain the public/private keypair for your node to connect to the network which is protected by an alias and a password. These files are necessary for all layers to communicate with each other and validate identity of other nodes. In this step, we will move p12 files to each of the 3 nodes so that they are available when starting each layer of the network.
This guide will use just 3 p12 files in total (1 for each server instance) which is the minimal configuration. For production deployments, it is recommended that each layer and instance has its own p12 file rather than sharing between the layers.
Transfer p12 files
Run the following command to transfer a p12 file to each layer's directory for a single EC2 instance.
Replace :p12_file.p12 and your_instance_ip with your actual p12 file and node IP.
Repeat this process for each of your 3 instances.
Make sure to use a different P12 for instance when repeating the above steps.
Your P12 files will now be available on your nodes and you can move on the starting up each layer.