Phoenix Support for Aurora PostgreSQL IAM Authentication

sr

·May 20, 2025 07:51 PM

Does Phoenix supports Aurora PostgresSql IAM auth instead of usrname/pwd auth

9 comments

· Sorted by Oldest

sr
·
RunLLM Does Phoenix supports Aurora PostgresSql IAM auth instead of usrname/pwd auth
RunLLM
APP
·
The Phoenix documentation I have ingested does not mention support for AWS Aurora PostgreSQL IAM authentication in place of standard username/password authentication; all references to database connectivity use traditional credentials in the connection string or environment variables. If you have specific requirements or a particular deployment scenario, providing those details may help clarify possible alternatives or workarounds. If this doesn't help, please reach out to the Phoenix support team for further assistance.
💡 Hint: Mention RunLLM in the thread for followups.
Mikyo
·
Hey Sr, I'm not super familiar with the iam auth. Can you link me to how this typically is configured? Does it require setting up the role on phoenix? if so I'm not sure
sr
·
Our org discourages usage of traditional standard username/password authentication, so I am looking for alternate way of authentications
Mikyo
·
Gotcha. That makes sense. Shoot me an example of what you are thinking and I can see how it links up with sqlalchemy
sr
·
Our infrastructure is in AWS and would like to connect from Phoenix (which we would be deploying into ECS Fargate ) to Aurora via IAM role
Roger Y.
·
according to Claude, we need to create a new db connection every 14 minutes using a new auth token generated by the boto3 SDK
sr
·
Roger, Sorry didn't get it, does this Auth token can be generated only with usr/pwd DB authentication?
Roger Y.
·
the credentials probably look like the following, but the session token expires every 15 minutes, which means a new db connection would need to be established with a new token when that happens
👍1

sr
·
RunLLM Does Phoenix supports Aurora PostgresSql IAM auth instead of usrname/pwd auth
RunLLM
APP
·
The Phoenix documentation I have ingested does not mention support for AWS Aurora PostgreSQL IAM authentication in place of standard username/password authentication; all references to database connectivity use traditional credentials in the connection string or environment variables. If you have specific requirements or a particular deployment scenario, providing those details may help clarify possible alternatives or workarounds. If this doesn't help, please reach out to the Phoenix support team for further assistance.
💡 Hint: Mention RunLLM in the thread for followups.
Mikyo
·
Hey Sr, I'm not super familiar with the iam auth. Can you link me to how this typically is configured? Does it require setting up the role on phoenix? if so I'm not sure
sr
·
Our org discourages usage of traditional standard username/password authentication, so I am looking for alternate way of authentications
Mikyo
·
Gotcha. That makes sense. Shoot me an example of what you are thinking and I can see how it links up with sqlalchemy
sr
·
Our infrastructure is in AWS and would like to connect from Phoenix (which we would be deploying into ECS Fargate ) to Aurora via IAM role
Roger Y.
·
according to Claude, we need to create a new db connection every 14 minutes using a new auth token generated by the boto3 SDK
sr
·
Roger, Sorry didn't get it, does this Auth token can be generated only with usr/pwd DB authentication?
Roger Y.
·
the credentials probably look like the following, but the session token expires every 15 minutes, which means a new db connection would need to be established with a new token when that happens
👍1