amazon-rds-aurora

I inherited some code that uses sqlalchemy with psycopg2, which needs to run on AWS. RDS Postgres supports iam-based authentication, but the way it does it is rather kludgy: you request a temporary password using the AWS RDS API, which is good for about 15 minutes, and you pass that as the password. The code I have effectively does e = create_engine(make_sqlalchemy_string()) , where make_sqlalchemy_string() makes an aws api call, gets the temporary password, and everything is good for a while. Except something, somewhere in the sqlalchemy code closes the connection, and then the password is no

Not a duplicate of AWS Aurora MySQL serverless: how to connect from MySQL Workbench . Aurora Serverless doesn't support public connections yet. I used Cloud9 to create an EC2 instance on the same VPN as the database. I then connected to the database from the Cloud9 terminal. My (GraphQL Prisma) service that I'm attempting to host (on Zeit Now) only takes a HOST and a PASSWORD for configuration. How can I make the EC2 instance act as a proxy that I can treat exactly as a database endpoint. Can tunneling fully do that and I'm just bad at it? I think this blog may help you. The idea, is make a

I am getting this error when executing a GRANT statement on my Aurora DB instance in AWS: The MySQL server is running with the --read-only option so it cannot execute this statement My user is not read-only though, so why is this happening? It turned out to be a silly mistake, but posting it anyway in case anyone else has the problem: I was accessing the replica instance by mistake - I had copied the endpoint for the replica, and it is read-only apparently. So if you have this problem, verify that you are connecting to the Primary Instance or best of all the DB Cluster endpoint. Edit:

I hope this is not too vague of a question, but I have looked far and wide but have not been able to find anything helpful for this error. I have a .NET 4.5.2 web service tier (using ServiceStack & Dapper) that has been receiving these two errors infrequently ever since we deployed the service. The first error: 2017-09-29 18:13:26.637 +00:00 [Error] Class: "TokenRepository" | Method: "GetToken" System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The message received was unexpected or badly formatted ---

I've got an AWS Aurora DB cluster running that is 99.9% focused on writes. At it's peak, it will be running 2-3k writes/sec. I know Aurora is somewhat optimized by default for writes, but I wanted to ask as a relative newcomer to AWS - what are some best practices/tips for write performance with Aurora? Bill Karwin From my experience, Amazon Aurora is unsuited to running a database with heavy write traffic. At least in its implementation circa 2017. Maybe it'll improve over time. I worked on some benchmarks for a write-heavy application earlier in 2017, and we found that RDS (non-Aurora) was