Open EugeneFinch opened 11 months ago
here's the proof :
Hi @EugeneFinch ,
the resources in the provided stack are all restricted to the VPC including DNS resolution via Rout53 private hosted zone. There are different ways to extend such a solution, e.g. via reusing the same VPC and adapting the security groups.
The recommended way would be to create a VPC for all blockchain node related workloads and use VPC Private Link (https://aws.amazon.com/privatelink/) to connect these VPCs without having any information being exposed to pubic internet. You can then expose the required resources via security groups.
Let me know if that helps.
It appears the said deployment creates a private load balancer which is not accessible from a third-party server (not AWS). Is it possible to amend repository to make it possible to access it externally? currently a blocker for us.