amazon-rds

Call AWS Lambda from Aurora RDS Stored Procedure Permissions Issue

耗尽温柔 提交于 2020-12-30 03:07:09
问题 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

Import Postgres data into RDS using S3 and aws_s3

ⅰ亾dé卋堺 提交于 2020-12-29 10:54:29
问题 I'm having a hard time importing data from S3 into an RDS postgres instance. According to the docs, you can use this syntax: aws_s3.table_import_from_s3 ( table_name text, column_list text, options text, bucket text, file_path text, region text, access_key text, secret_key text, session_token text ) So, in pgAdmin, I did this: SELECT aws_s3.table_import_from_s3( 'contacts_1', 'firstname,lastname,imported', '(format csv)', 'com.foo.mybucket', 'mydir/subdir/myfile.csv', 'us-east-2',

Import Postgres data into RDS using S3 and aws_s3

孤街醉人 提交于 2020-12-29 10:53:26
问题 I'm having a hard time importing data from S3 into an RDS postgres instance. According to the docs, you can use this syntax: aws_s3.table_import_from_s3 ( table_name text, column_list text, options text, bucket text, file_path text, region text, access_key text, secret_key text, session_token text ) So, in pgAdmin, I did this: SELECT aws_s3.table_import_from_s3( 'contacts_1', 'firstname,lastname,imported', '(format csv)', 'com.foo.mybucket', 'mydir/subdir/myfile.csv', 'us-east-2',

AWS RDS public access

你说的曾经没有我的故事 提交于 2020-12-08 05:47:04
问题 I am stumped with AWS configuration. My goal is to create a database that's accessible from inside and outside the network. Here is what I have. RDS instance runs postgresql. Connections from inside the VPC work correctly. The endpoint is set up to be publicly accessible - and when accessed from the outside, does in fact resolve. However, the connection hangs, indicating the traffic is blocked by somebody. Security group is good: Inbound: Port 5432 from 0.0.0.0/0 Outbound: all from 0.0.0.0/0

Having “Timeout acquiring a connection” after upgrading Knex

一曲冷凌霜 提交于 2020-12-02 12:11:45
问题 In my company, our application runs on NodeJS over multiple EC2 instances and one RDS database. Our application needed some upgrades as some dependencies were already quite old, and one of the upgrades we did that called our attention was updating our database libraries: mysql (from 2.16.0 to 2.17.0), knex (from 0.12.2 to 0.19.1) and bookshelf (0.10.2 to 0.15.1). After checking the changelog, no code changes were required, so we quickly managed to upload it to our staging server. Suddenly our

Having “Timeout acquiring a connection” after upgrading Knex

萝らか妹 提交于 2020-12-02 12:07:40
问题 In my company, our application runs on NodeJS over multiple EC2 instances and one RDS database. Our application needed some upgrades as some dependencies were already quite old, and one of the upgrades we did that called our attention was updating our database libraries: mysql (from 2.16.0 to 2.17.0), knex (from 0.12.2 to 0.19.1) and bookshelf (0.10.2 to 0.15.1). After checking the changelog, no code changes were required, so we quickly managed to upload it to our staging server. Suddenly our