You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
Greetings ! I've been unable to open a connection to an RDS Aurora database, and I'm no expert on AWS API, so I might've been missing something obvious...
But it seems to me like Aws::RDSDataService::Client requires a credentials parameter. The readme doesn't specify how these credentials are supposed to be given. I'm not sure it can be done through the config file.
I've been able to solve the issue by patching this gem, by editing lib/active_record/connection_adapters/aurora_serverless/client.rb and adding the following line just before the instantiation of the Aws::RDSDataService::Client:
Your usage may be different tho and highlight some more docs. I suspect you are using the gem on something that does not have an IAM Role? On EC2, Containers, Lambda, we use that along with some policies to ensure the workload can access things. More details here that like should be in the Usage section. https://technology.customink.com/blog/2020/01/03/migrate-your-rails-app-from-heroku-to-aws-lambda/
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Greetings ! I've been unable to open a connection to an RDS Aurora database, and I'm no expert on AWS API, so I might've been missing something obvious...
But it seems to me like
Aws::RDSDataService::Client
requires acredentials
parameter. The readme doesn't specify how these credentials are supposed to be given. I'm not sure it can be done through the config file.I've been able to solve the issue by patching this gem, by editing
lib/active_record/connection_adapters/aurora_serverless/client.rb
and adding the following line just before the instantiation of theAws::RDSDataService::Client
:I am then able to add my credentials to my config file as such:
And it seems to work (I don't have access to any aws resource yet, but it seems to work).
I'm wondering:
The text was updated successfully, but these errors were encountered: