- Newest
- Most votes
- Most comments
Hello.
It is unclear what kind of SQL query Lambda is executing, but is it possible that session fixation is being performed as described in the document below?
When you run certain SQL queries when using RDS Proxy, a phenomenon called pinning occurs.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy-managing.html#rds-proxy-pinning
Hi,
Thank you so much for your question.
RDS Proxy has the pinning feature to prevent unexpected query results. This feature uses a single dedicated connection per application connection.
You can see how many connection comes from your application and goes to the backend DB instance using the CloudWatch metrics.
- DatabaseConnections
- ClientConnections
- DatabaseConnectionsCurrentlySessionPinned
In addition to this, RDS Proxy automatically scale based on backend DB instance capacity as stated in the document. You can see the estimate number of management connections using SHOW PROCESSLIST
.
I hope this might help.
Hi,
I would suggest one very simple thing to start with: create your own measure of the connections from the client side.
For example, having a SQS queue or Redis cache where each of the requesting client deposits a timestampedmark when it starts a request (possibly with the sql request itself) and deposits a second mark when the request ends.
Then, you can easily analyze by parsing those marks what the real database activity is from requester standpoint and also surface the lon-running requests via the timestamps.
Best,
Didier
Relevant content
- asked a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago