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 access PostreSQL on AWS #41

Open
forando opened this issue Mar 29, 2021 · 3 comments
Open

How to access PostreSQL on AWS #41

forando opened this issue Mar 29, 2021 · 3 comments
Labels
question Further information is requested

Comments

@forando
Copy link

forando commented Mar 29, 2021

Hi guys,
in the re:Invent dedicated video @malnick mentioned Boundary-to-Postgres RDS usage.
Is there an example somewhere of how to do that?

@malnick
Copy link
Collaborator

malnick commented Mar 30, 2021

Hey there! You can use our built in postgres subcommand to fork psql under the hood: boundary connect postgres [flags|args].

See boundary connect -h for more info, thanks!

@malnick malnick added the question Further information is requested label Mar 30, 2021
@forando
Copy link
Author

forando commented Mar 30, 2021

Not sure if I got it right.
I tried to add Boundary Postgres RDS as a host via Boundary Web Console (created separate host_set and target for it as well). Did not find where to put db password though. Am I supposed to pass it as an argument when connecting with the client? As of now when I run boundary connect postgres -username=boundary -target-id <dedicated_target> it gets timed out.
I could not find any how-to documentation except ssh.

@malnick
Copy link
Collaborator

malnick commented Aug 9, 2021

If you're getting a time out it's most likely due to the client not being able to access the worker or the worker not being able to access the target. Make sure your security groups/IP table rules allow connections between these entities.

If you have detailed log output, that would also be handy to see here. Upgrading to the latest 0.5 release will also give you event logs, which would be valuable for debugging here too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants