TConfirming what Sam said
LHyperdrive can be used from one aws lambda or only inside a worker?
AOnly from within a Worker.
A@hyperdrive
For all of you who've asked about connecting to your database without exposing it to the public Internet, we're ready to go live. Say hello to Hyperdrive, now with support for Cloudflare Tunnels!
https://developers.cloudflare.com/hyperdrive/configuration/connect-to-private-database/
For all of you who've asked about connecting to your database without exposing it to the public Internet, we're ready to go live. Say hello to Hyperdrive, now with support for Cloudflare Tunnels!
https://developers.cloudflare.com/hyperdrive/configuration/connect-to-private-database/
Cloudflare Docs
Hyperdrive can securely connect to your private databases using Cloudflare Tunnel and Cloudflare Access.
Sletsgo!
Mdamn!
M@Hyperdrive new feature just dropped!
C
AThanks Matt. Pings are hard, apparently....
HSo if I am reading this correctly, Hyperdrive needs a public domain for the tunnel, correct? You can't point Hyperdrive directly at the ArgoTunnel domain(I don't remember the exact domain name off the top of my head)
ACorrect.
HWould it be possible to make Tunnels/Hyperdrives on the same account be able to communicate with each other directly?
AIn what sense? The traffic flow right now is
Worker<->Hyperdrive<->DatabaseLike, where I give my Hyperdrive a Tunnel ID, then it connects directly, so that there is no outside evidence that I have a connection to my DB exposed
AAh. We're poking at that, it's a possible future option. CC @thomasgauvin
PHow does this impact performance?
AIn almost all scenarios it's going to be very comparable to current performance. I wouldn't reach for this to solve perf problems, but I wouldn't expect it to be slower than your current setup.
AWith (really) big bulk inserts you might see some slowdowns. Please let us know if you do, as that's something we would want to address.
PI don't personally. Only case would be data import but there's an inbuilt 4 second budget for that and if that budget is surpassed there's no real consequences
AI meant if you do try it and do see slowdowns. We know some folks do larger inserts, but we don't think it should move the needle much for those. It's just an area of interest.
IOk
PHow can I move hyperdrive to active ?
Is there a way to get hyperdrive connection string from the dashboard
Must hyperdrive be used with a worker ? I need the connection string to add on my vercel deployment DATABASE_URL
Is there a way to get hyperdrive connection string from the dashboard
Must hyperdrive be used with a worker ? I need the connection string to add on my vercel deployment DATABASE_URL
DHyperdrive is only for Workers. It will say active if it’s received queries recently
PThank you. It won't work for my use case then.
Zif i want to use hyperdrive+tunnel to access a private db in google cloud sql, do i need to run an instance in gcp to run the tunnel daemon?
AYes, you'll need somewhere running cloudflared that has access to your database, for the traffic to egress from
ADoes Hyperdrive have any mechanism for rotating the connection string or are you supposed to change the ID and re-deploy workers? Tried looking around, but couldn't find anything on this.
MThe connection string is unique to the Worker you call it in and can’t be used outside Hyperdrive or your account, so it can’t be leaked. cc @thomasgauvin for docs here.
AWhat Matt said, the Hyperdrive ID and your connection string are not secrets. Also, if the underlying secrets (password/client secret) were leaked, those can be updated either via Wrangler or API, so you don't need to make a whole new Hyperdrive if it isn't convenient.
HWhat would be the process if you need to rotate because you are switching providers(or for another reason)?
HJust swap out the IDs?
AAt some point it's probably easiest to make a new one for the new provider, and then just swap out the ID in wrangler.toml, yeah.
MHowdy! Is there any type of logging viewable for hyperdrive private database tunnels? I have a postgresql server that is connectable directly via ssh port forwarding, via the tunnel established for hyperdrive
cloudflared access tcp, and of course on the machine itself. However, running the recommended test code (const sql = postgres(env.XXXX.connectionString);) results in a connection timeout with no further info provided. Thanks!
CDid anyone managed to connect a digital ocean manage postgres to a worker?
Ctried with both hyperdrive and none and it just times out, on my local it works perfectly
MYeah, that's the same issue to which I was referring in my thread yesterday (hyperdrive) - I was building a full-stack in Workers Pages and the local hyperdrive dev connection worked OK, but the hyperdrive private connection seemed to be unable to talk to the tunnel, timing out in the process. I had a very productive chat with @AJR, who is looking into the issue
AMay or may not be the same issue. Is the DO connection behind a tunnel? Or publicly accessible?
NIs there a better channel for asking questions specific to Tunnels? I'm having a connectivity issue setting up my database, but believe I've isolated it to the Tunnel.
NI followed the instructions at https://developers.cloudflare.com/hyperdrive/configuration/connect-to-private-database/ and wanted to test database connectivity, so I allowed myself through the Access Application, and am receiving connection timeout errors while trying to connect directly from pgAdmin.
Cloudflare Docs
Hyperdrive can securely connect to your private databases using Cloudflare Tunnel and Cloudflare Access.
AIf the questions are specifically about Hyperdrive through a tunnel this is the channel. Have you had a chance to look through some of the debugging points in this thread?
hyperdriveHowdy! Is there any type of logging
hyperdriveHowdy! Is there any type of logging
NI read about the logging there, and found that no logs were being generated by my connection attempts.
AOkay. If you DM me your hyperdrive ID, I'll dig a bit when I'm back in office Monday and see what I can turn up
NThank you! I'll try to do a bit more troubleshooting this weekend, and will send that over if it doesn't work.
Cpublic accessible: here you have a reproduction if it helps: pages-helpPostgres timesout on cloudflare:
I disabled hyperdrive for the reproduction, the the issue is the same (with/without hyperdrive)
I disabled hyperdrive for the reproduction, the the issue is the same (with/without hyperdrive)
AIf hyperdrive is out of the equation it gets harder for me to help with that, I'm afraid. I'll ask internally on Monday and see if anyone on some of the other dev platform teams knows something about it
JHey everyone, cross post here from the Rust channel and wondering if anyone can help.
Is anyone else using Rust alongside a Postgres database with Hyperdrive? I'm getting some weird intermittent connection issues, that is like either the worker can't connect or is timing out. I'm wondering if it's something to do with this background work happening and the connection not quite being ready.
Is anyone else using Rust alongside a Postgres database with Hyperdrive? I'm getting some weird intermittent connection issues, that is like either the worker can't connect or is timing out. I'm wondering if it's something to do with this background work happening and the connection not quite being ready.
J
JAdditional context, when I run locally with a local database it works absolutely fine
JOk, so I figured this out and just following up here.
It's actually to do with using SQL prepared statements. There's a great write up here. If I switch all the queries to use
https://exograph.dev/blog/wasm-pg-explorations-2#hyperdrive-with-the-extended-query-protocol
It's actually to do with using SQL prepared statements. There's a great write up here. If I switch all the queries to use
query_typed it works perfectly. If the folks building Exograph are around then thankyou https://exograph.dev/blog/wasm-pg-explorations-2#hyperdrive-with-the-extended-query-protocol
AYes, the exograph folks are around here occasionally, and that's a good write-up. While we don't officially support extended protocol messages in tokio-postgres right now, their fork seems to work quite well for people.
