amazon-rds

aws rds proxy throws timeout error from nodejs12.x

妖精的绣舞 提交于 2021-01-03 06:53:07
问题 I'm getting a connection timeout when I try to connect to mysql rds proxy. I'm followed this tutorial This is my code import mysql2 from 'mysql2'; import AWS from 'aws-sdk'; const getConnection = async () => { const signer = new AWS.RDS.Signer({ username: 'my-user-name', hostname: 'proxy-name.proxy-someid.us-east-1.rds.amazonaws.com', port: 3306 }); console.info('Connecting to MySQL proxy via IAM authentication'); const rdsSignerAuth = () => () => { console.info('CALL rdsSignerAuth'); return

aws rds proxy throws timeout error from nodejs12.x

心不动则不痛 提交于 2021-01-03 06:52:52
问题 I'm getting a connection timeout when I try to connect to mysql rds proxy. I'm followed this tutorial This is my code import mysql2 from 'mysql2'; import AWS from 'aws-sdk'; const getConnection = async () => { const signer = new AWS.RDS.Signer({ username: 'my-user-name', hostname: 'proxy-name.proxy-someid.us-east-1.rds.amazonaws.com', port: 3306 }); console.info('Connecting to MySQL proxy via IAM authentication'); const rdsSignerAuth = () => () => { console.info('CALL rdsSignerAuth'); return

AWS IAM Database Authentication using Java connection pool

大兔子大兔子 提交于 2021-01-03 06:44:31
问题 I am looking for a Java database connection pool that allows me to use AWS IAM Database Authentication for my Aurora MySQL. The pool should be able to work Tomcat context.xml file. I have looked at Tomcat DBCP, dbcp2, HikariCP and c3p0. But they all seem to asume the username and password is known at application startup and does not change in the lifetime of the application. For IAM database authentication the credentials change every 15 minutes so the pool needs to ask the AWS IAM for a new

Occasional 'temporary failure in name resolution' while connecting to AWS Aurora cluster

梦想的初衷 提交于 2021-01-01 07:59:24
问题 I am running an Amazon Web Services RDS Aurora 5.6 database cluster. There are a couple of lambda's talking to these database instances, all written in python. Now everything was running well, but then suddenly, since a couple of days ago, the python code sometimes starts throwing the following error: [ERROR] InterfaceError: 2003: Can't connect to MySQL server on 'CLUSTER-DOMAIN:3306' (-3 Temporary failure in name resolution) This happens in 1 every 1000 or so new connections. What is

Occasional 'temporary failure in name resolution' while connecting to AWS Aurora cluster

拥有回忆 提交于 2021-01-01 07:55:46
问题 I am running an Amazon Web Services RDS Aurora 5.6 database cluster. There are a couple of lambda's talking to these database instances, all written in python. Now everything was running well, but then suddenly, since a couple of days ago, the python code sometimes starts throwing the following error: [ERROR] InterfaceError: 2003: Can't connect to MySQL server on 'CLUSTER-DOMAIN:3306' (-3 Temporary failure in name resolution) This happens in 1 every 1000 or so new connections. What is

Call AWS Lambda from Aurora RDS Stored Procedure Permissions Issue

谁都会走 提交于 2020-12-30 03:19:34
问题 I've created a few Lambdas in AWS, and an Aurora RDS (publicly available). I couldn't execute lambdas (via call mysql.lambda_async ). When I tried that I got the error ERROR 1873: 1873: Lambda API returned error: Missing Credentials: Cannot instantiate Lambda Client . I tried attaching an IAM role called aurora-lambdas where I set full access to RDS and Lambdas and a trusted relationship between those services, but after trying various configurations I still get the issue. Do someone have

Call AWS Lambda from Aurora RDS Stored Procedure Permissions Issue

有些话、适合烂在心里 提交于 2020-12-30 03:13:50
问题 I've created a few Lambdas in AWS, and an Aurora RDS (publicly available). I couldn't execute lambdas (via call mysql.lambda_async ). When I tried that I got the error ERROR 1873: 1873: Lambda API returned error: Missing Credentials: Cannot instantiate Lambda Client . I tried attaching an IAM role called aurora-lambdas where I set full access to RDS and Lambdas and a trusted relationship between those services, but after trying various configurations I still get the issue. Do someone have

Call AWS Lambda from Aurora RDS Stored Procedure Permissions Issue

房东的猫 提交于 2020-12-30 03:13:39
问题 I've created a few Lambdas in AWS, and an Aurora RDS (publicly available). I couldn't execute lambdas (via call mysql.lambda_async ). When I tried that I got the error ERROR 1873: 1873: Lambda API returned error: Missing Credentials: Cannot instantiate Lambda Client . I tried attaching an IAM role called aurora-lambdas where I set full access to RDS and Lambdas and a trusted relationship between those services, but after trying various configurations I still get the issue. Do someone have

Call AWS Lambda from Aurora RDS Stored Procedure Permissions Issue

大兔子大兔子 提交于 2020-12-30 03:13:17
问题 I've created a few Lambdas in AWS, and an Aurora RDS (publicly available). I couldn't execute lambdas (via call mysql.lambda_async ). When I tried that I got the error ERROR 1873: 1873: Lambda API returned error: Missing Credentials: Cannot instantiate Lambda Client . I tried attaching an IAM role called aurora-lambdas where I set full access to RDS and Lambdas and a trusted relationship between those services, but after trying various configurations I still get the issue. Do someone have

Call AWS Lambda from Aurora RDS Stored Procedure Permissions Issue

喜夏-厌秋 提交于 2020-12-30 03:12:50
问题 I've created a few Lambdas in AWS, and an Aurora RDS (publicly available). I couldn't execute lambdas (via call mysql.lambda_async ). When I tried that I got the error ERROR 1873: 1873: Lambda API returned error: Missing Credentials: Cannot instantiate Lambda Client . I tried attaching an IAM role called aurora-lambdas where I set full access to RDS and Lambdas and a trusted relationship between those services, but after trying various configurations I still get the issue. Do someone have