[LAB-337] Dedicated private IPFS node #567
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
hevans66
approved these changes
Aug 7, 2023
| @@ -0,0 +1,37 @@ | |||
| - name: Provision Bacalhau Requester | |||
There was a problem hiding this comment.
This should probably be Provision IPFS
There was a problem hiding this comment.
Thanks for catching that.
| protocol = "TCP_UDP" | ||
|
|
||
| default_action { | ||
| target_group_arn = aws_lb_target_group.labdao_ipfs_api_tg.arn |
There was a problem hiding this comment.
It took me a bit to wrap my head around how this is working. Its probably worth putting a comment in here that we are forwarding traffic through to the IPFS node for this port only because the cli requires pinning certain files in IPFS. It seems like the thing we might forget and will confuse us later.
alabdao
force-pushed
the
ops/lab-337-dedicated-ipfs
branch
from
62f8fb7 to
e5a24b0
Compare
These changes now create and setup a dedicated IPFS node where both requester and compute now connect. Also using `private_ipfs=true` option you can make your IPFS deployment be private. Currently the swarm key for private IPFS is randomly generated at bootstrap time. Next step would be to have this key getting fetched from AWS SSM parameter store likely.
alabdao
force-pushed
the
ops/lab-337-dedicated-ipfs
branch
from
e5a24b0 to
daa1fac
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes now create and setup a dedicated
IPFS node where both requester and compute now connect.
Also using
private_ipfs=trueoption you can make yourIPFS deployment be private. Currently the swarm key for
private IPFS is randomly generated at bootstrap time.
Next step would be to have this key getting fetched from
AWS SSM parameter store likely.