Skip to content

Commit 07975c3

Browse files
committed
News95/blogs: proposed edits to enterprise LN article
1 parent 01611c0 commit 07975c3

File tree

1 file changed

+22
-22
lines changed

1 file changed

+22
-22
lines changed

_includes/articles/suredbits-enterprise-ln.md

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -10,34 +10,33 @@ seed in a secure location? Et cetera, et cetera…
1010

1111
At [Suredbits][] we use Eclair for our nodes. Even though Eclair is
1212
pretty robust on its own, we took some steps to make it even more
13-
reliable. Such as using PostgreSQL as a database backend [(there is a PR
14-
in review at the time of writing)][db pr] and [AWS Secrets Manager][] to
13+
reliable---such as using PostgreSQL as a database backend [(using this PR
14+
)][db pr] and [AWS Secrets Manager][] to
1515
store private keys.
1616

1717
Eclair has a built-in online backup feature, but it requires manual
1818
setup and script writing to automate, which is not really scalable and
1919
is error prone. Running PostgreSQL at AWS RDS allows us to automate
20-
backups and replication in the way almost every DevOps engineer is
21-
familiar with, and to restore the database state when needed more
22-
easily.
20+
backups and replication in a way that is familiar to many DevOps engineers
21+
and which makes restoring the database state easier.
2322

2423
Using PostgreSQL as a remote database backend makes node failover
25-
simpler to implement, because if the node crashes for some reason
26-
there’s no need to restore the database from a backup, all you need is
27-
to point a new Eclair instance to the correct database server. [Here’s a
28-
quick demo of an automated failover implemented with two Eclair
29-
instances, and AWS RDS, ELB, and NAT Gateway.][failover demo]
24+
simpler to implement because, if the node crashes for some reason,
25+
there’s no need to restore the database from a backup---all you need is
26+
to point a new Eclair instance to the correct database server. Here’s a
27+
[quick demo][failover demo] of an automated failover implemented with two Eclair
28+
instances plus AWS's RDS, ELB, and NAT Gateway.
3029

3130
In the failover scenario depicted in the demo, we needed a secure way to
32-
share the node’s seed private key between the Eclair instances. Eclair
33-
stores it in a file on the local file system and the seed file should be
34-
backed up somewhere and restored when needed. The current implementation
35-
requires extra steps to do so in an automated fashion. AWS Secrets
36-
Manager is an encrypted storage specifically designed to securely store
37-
various kinds of secrets, including database passwords and encryption
38-
keys. All you need to do to share the seed between the instances is to
39-
point them to the correct secrets location in the config file. And once
40-
configured, the instance can be stored as an AMI image, and re-imaged as
31+
allow the node’s seed for its private keys to be shared between the Eclair instances. Eclair
32+
stores the seed in a file on the local file system which should be
33+
backed up somewhere and restored when needed. The current Eclair implementation
34+
requires extra steps to do so in an automated fashion. We instead use AWS Secrets
35+
Manager---an encrypted key/value store specifically designed to securely hold
36+
various kinds of secrets including database passwords and encryption
37+
keys. Now all you need to do to share the seed between the instances is to
38+
point them to the correct secrets location in the config file. Once
39+
configured, the instance can be stored as an AMI image which can re-imaged as
4140
many times as needed without manual configuration.
4241

4342
The measures we took are just the first steps to building
@@ -47,12 +46,13 @@ that need to be solved. For example, which Hardware Security Module
4746
Core node in a multi-instance setting. But we believe that our work is a
4847
solid base for scaling out Eclair and making it more fault-tolerant.
4948

50-
More on this topic: <https://www.youtube.com/watch?v=tbwy9mJIrZE>
49+
For more information about this topic, see our [presentation][enterprise ln vid].
5150

52-
Disclaimer: Since private keys are involved, don't use third party cloud
53-
services without a thorough risk assessment.
51+
*Disclaimer: Since private keys are involved, don't use third party cloud
52+
services without a thorough risk assessment.*
5453

5554
[suredbits]: https://suredbits.com
5655
[db pr]: https://github.com/ACINQ/eclair/pull/1249
5756
[aws secrets manager]: https://github.com/rorp/eclair/tree/aws_secretsmanager
5857
[failover demo]: https://youtu.be/L2DtolwS8ew
58+
[enterprise ln vid]: https://www.youtube.com/watch?v=tbwy9mJIrZE

0 commit comments

Comments
 (0)