Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to connect to nodes with internal IP addresses using AWS Client VPN? #104

Open
frbrkoala opened this issue Aug 1, 2024 · 3 comments

Comments

@frbrkoala
Copy link
Contributor

frbrkoala commented Aug 1, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

I'd like to connect to a node RPC API using its internal IP address from my local machine and do it safely.

Describe the solution you would like

I'd like to use AWS Client VPN, like described in this blog post: https://aws.amazon.com/blogs/database/run-a-serverless-arbitrum-full-node-on-aws/

Describe alternatives you have considered

The other way is to add my local machines' external IP address to security policy, but that might not be safe.

Additional context

@evertonfraga
Copy link
Contributor

evertonfraga commented Aug 1, 2024

Are you able to access it with SSM?

if so, i made a script that uses aws ssm start-session --target "$INSTANCE_ID" on the EC2 instance that was created by a provided stack.

You can run it like ./cf2ssh.sh sui-single-node-testnet, the parameter should correspond to your CFn stack name. If you also find that useful, we can incorporate that script to a tooling section on the project.

Copy link
Contributor

github-actions bot commented Sep 2, 2024

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Sep 2, 2024
Copy link
Contributor

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 12, 2024
@frbrkoala frbrkoala reopened this Sep 13, 2024
@github-actions github-actions bot removed the stale label Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants