Very very good video. This should be an example for other tutorials. It combines a introduction with a demo and with performance analytics, in just 12 minutes. And everything is very clear. Thank you !
An alternative "AWS approved" proxy, is the Heimdall Proxy. It includes features as query caching, read/write split, and connection pooling. Heimdall supports all database types in RDS.
would believe you if you would at least create the database connection outside of handler function ))) when using lambdas is always good thing to establish connection outside of handler function. Did not get what problem the RDS Proxy is solving, especially the token used and so on. In traditional way of establishing connections we anyway used to store the credentials in secret manager and even rotate those, nothing changed (it seems in this video). Having additional role added to the lambda just to communicate with RDS proxy, can you elaborate on latency ? What is the latency ? Why in each lambda you need to pass the token? In short, does this RDS proxy solves the problem of many connections established from lambdas ? Or a simple use and correct approach which you did not respect in this video, which is creating connections outside of handler function solves the problem ?
I don't see why create a connection outside the handler function would reduce the number of connections to the database. Unless you are thinking in a scenario where the lambda would only require a database connection under certain circumstances. One of the objectives of RDS Proxy is to externalize a connection pool in order to limit the amount of connections that could be opened to the database. So, even if you have a Proxy with 100 connections that is used by a lambda that could be triggered thousands of time, the maximum number of connections to the database would be 100, and if this amount is reached and a new instance of the lambda requires one more, it would wait for it to be available (or throw a exception, depending on the timeout configured).
Hi there. I have located the following doc which may assist you: go.aws/3VXpGjV. 🔍 For any additional questions, you're welcome to reach out via our re:Post community of experts, here: go.aws/aws-repost. 📨 ^AM
This is good, but how would this work, if say, your RDS db needs to connect o Redshift? More specifically, an RDS postgres db connects to redshift though Foreign Servers, how does proxy handle the credentials to connect to redshift of the redshift credentials are rotated?
my application uploads a file to s3, this triggers a lambda function that transforms the file and uploads it as a record to an RDS Database. With this approach I'm exausthing my database allowed concurrent connections. Using an RDS proxy endpoint instead of a direct database connection will help me with that?
It makes sense to me to leave RDS Proxy to close the connection after the idle timeout (default 30 minutes) because the point of RDS Proxy is that you want the connection to hang around for a while in case it's needed again. When you open the connection, if there's already one open it will reuse it. If you close it in your code it defeats the object of RDS Proxy.
Has anyone been able to get this working with Aurora Postgres? I've followed the exact same pattern using pg and keep getting MD5 errors. Connection succeeds when using the cluster host value but not the proxy endpoint. Spent half the day on with AWS tech support and they can't figure it out. This was a great video btw. Unfortunate that AWS tech support is so lacking though.
Are you using it from within a lambda? You can't access the proxies from a public address. You also need to make sure your lambda is added to the same VPC.
Very very good video. This should be an example for other tutorials. It combines a introduction with a demo and with performance analytics, in just 12 minutes. And everything is very clear. Thank you !
Thank you so much, Rob! 😀
Best Intro Video Ever Made By AWS....Period.... 👍🙏
Wow, more demos like this pls.
An alternative "AWS approved" proxy, is the Heimdall Proxy. It includes features as query caching, read/write split, and connection pooling. Heimdall supports all database types in RDS.
Excellent video! Thanks a ton!!
Glad you enjoyed it! ^NR
Best demo video from amazon 😍👏🏻👏🏻👏🏻👏🏻👏🏻👏🏻👏🏻👏🏻
Best Regards From Mexico City. Manuel Silva
Can we have java example for connection to RDS proxy ?
beautiful demo, thanks!
Is RDS proxy out of preview? as the document says its currently in preview
How to connect when IAM Authentication is disabled , is there any tutorial or documentation for that.Please help
Native pw or secrets
This was very helpful, but I'm struggling to find a way to do the part from 9 minutes in C#. Please can someone point me in the right direction?
would believe you if you would at least create the database connection outside of handler function ))) when using lambdas is always good thing to establish connection outside of handler function. Did not get what problem the RDS Proxy is solving, especially the token used and so on. In traditional way of establishing connections we anyway used to store the credentials in secret manager and even rotate those, nothing changed (it seems in this video). Having additional role added to the lambda just to communicate with RDS proxy, can you elaborate on latency ? What is the latency ? Why in each lambda you need to pass the token?
In short, does this RDS proxy solves the problem of many connections established from lambdas ? Or a simple use and correct approach which you did not respect in this video, which is creating connections outside of handler function solves the problem ?
I don't see why create a connection outside the handler function would reduce the number of connections to the database. Unless you are thinking in a scenario where the lambda would only require a database connection under certain circumstances. One of the objectives of RDS Proxy is to externalize a connection pool in order to limit the amount of connections that could be opened to the database. So, even if you have a Proxy with 100 connections that is used by a lambda that could be triggered thousands of time, the maximum number of connections to the database would be 100, and if this amount is reached and a new instance of the lambda requires one more, it would wait for it to be available (or throw a exception, depending on the timeout configured).
Is this proxy endpoint we can also use to connect to my DB from PgAdmin client ?
Hi there. I have located the following doc which may assist you: go.aws/3VXpGjV. 🔍 For any additional questions, you're welcome to reach out via our re:Post community of experts, here: go.aws/aws-repost. 📨 ^AM
Are you planning to release Proxy only for Read instances (autoscale cluster)?
This is good, but how would this work, if say, your RDS db needs to connect o Redshift? More specifically, an RDS postgres db connects to redshift though Foreign Servers, how does proxy handle the credentials to connect to redshift of the redshift credentials are rotated?
remove the foreign servers! :D
@@WoodyKafou1 no, that doesn't work.
Great video. Thanks.
my application uploads a file to s3, this triggers a lambda function that transforms the file and uploads it as a record to an RDS Database. With this approach I'm exausthing my database allowed concurrent connections. Using an RDS proxy endpoint instead of a direct database connection will help me with that?
Yes
Is proxy is specific to user like dbuser here? If we create another user we cannot use proxy?
So is this just aws hosted version of proxysql?
As of today the docs say "Amazon RDS Proxy is available in preview for Aurora MySQL, RDS MySQL, Aurora PostgreSQL, and RDS PostgreSQL."
Awesome presentation! BTW, I can see you are not closing the connection, is that ok? are you waiting for RDS proxy to do that for you? thx
It makes sense to me to leave RDS Proxy to close the connection after the idle timeout (default 30 minutes) because the point of RDS Proxy is that you want the connection to hang around for a while in case it's needed again. When you open the connection, if there's already one open it will reuse it. If you close it in your code it defeats the object of RDS Proxy.
Is this still in preview
Has anyone been able to get this working with Aurora Postgres? I've followed the exact same pattern using pg and keep getting MD5 errors. Connection succeeds when using the cluster host value but not the proxy endpoint. Spent half the day on with AWS tech support and they can't figure it out. This was a great video btw. Unfortunate that AWS tech support is so lacking though.
Are you using it from within a lambda? You can't access the proxies from a public address. You also need to make sure your lambda is added to the same VPC.
Is failover really 25 seconds with RDS proxy and 40 seconds without? That's really long.