Questions tagged with Amazon Relational Database Service
Content language: English
Sort by most recent
I have read most, all?, of the AWS troubleshooting guides on RDS/Aurora and we tried a bunch of things. We have a cluster with one reader and one writer. About two days ago they failed over and flipped automatically. Not sure why, not even sure it's related, but it happened and we didn't notice because things kept humming along. This morning, however, our apps, and IDEs started receiving too many connection errors when trying to connect. We could connect directly to the read instance, but couldn't write. Rebooted both, waited for the writer instance to recover, and same issue. Failed over to flip the instances, no real change. Flipped back, no change. Rebooted the writer again, no change. As we finally gave up and started restoring a snapshot, write connections just resumed on their own. There was about a half hour gap between the previous reboot and no additional event logs that would indicate it just took a while to reboot or failover. This feels like there was an AWS issue, but of course I don't see anything mentioned in the health dashboard. Our max connection param was set to the default for this version of MySQL and worked out to 90 for the db.t2.medium's we're running on. According to Cloudwatch we have never seen much more than about 15, so it seems odd that we were even receiving too many connection errors. It would be great to know what changed to break things and then how they were resolved because right now I have a working instance but no real clue as to what may have changed this morning. Any ideas?
For some reason, out of nowhere AWS autoscale decided to shut down our EC2 instance and a new one was launched, but now, even if our Backend is up and running on an ECS cluster container and the DB is running on RDS, there seems like our DB is unreachable, meaning on my website/application appears that the DB is offline. I have admin privileges, but I did not setup AWS, I just suppose to 'maintain' it and although im not completely clueless I'm not expert in the field. I'm unable to figure out what causing our issue. Security groups, and VPC are all setup correctly, havent touched it, all that got sorted automatically with the new autoscale group/template launch. If anyone could direct me or suggest some basic troubleshooting options(even though I feel like i checked most of them but still) that would help, would be much appreciated. Thanks, Csaba
I have an Aurora DB setup with MYSQL8.0 in Oregon (This is Aurora serverless v2 and there is no Data API in this version). This has VPC, subnets, VPC security group and public access turned on. The main route table of the VPC has a route with `com.amazonaws.us-west-2.s3` as destination and an endpoint of the vpc as target. When I try loading data into aurora from S3 (the bucket is in N.California) using the `LOAD DATA FROM S3 's3-us-west-1:....` statement, I keep getting `ERROR 1815 (HY000): Internal error: Unable to initialize S3Stream`. I have also rebooted the DB's writer instance after all the IAM and VPC changes. What am I missing?
Hello everyone, We are experiencing a problem with our Organizational Multiple Accounts where the automatic snapshot is randomly missing after a few days. I have contacted AWS support and they have identified it as a technical issue. They suggested that we upgrade our subscription plan as a first step. Have any of you faced the same problem, or do you have any solutions?
Hi, I tried following [this procedure](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) to import the data of a MySQL 8.0 instance running on my development laptop, through S3, to a new Aurora MySQL v3 cluster. First issue was that I had to use Percona XtraBackup 8.0, since 2.4 does not support MySQL 8.0. Then, creating the new cluster through the Console gives me the following validation error: > You can't restore to aurora-mysql 8.0.mysql_aurora.3.02.2 from an S3 backup of mysql 8.0. This used to work from a local MySQL 5.6 to an Aurora MySQL v1, but, unfortunately, that version is now EOL. I can't see any references to MySQL 8.0 on the page linked above, nor from the similar [CLI operation page](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-from-s3.html). Does this mean restoring from S3 is not available for Aurora MySQL v3? If so, what are the alternatives? My use case is to spin up a replica of our whole production environment, using locally prepared test data, from a single (terraform) command. Also, maybe it would be good to update the various documentation to explicitly state that MySQL 8.0 is not supported, since I imagine a lot of people had to migrate to it, following the EOL of 5.6. Cheers, Cyril.
I am getting **PDO::prepare(): MySQL server has gone away** error in my error logs. After the RDS Aurora mysql version upgrade i am getting this error simultaneously. I am not able to find the root cause of this error. current version of mysql is 2.10.3. I follow this post but no luck. https://aws.amazon.com/premiumsupport/knowledge-center/rds-mysql-server-gone-away/
created a RDS and default user is admin backup is in s3 and added option group for SQLSERVER_BACKUP_RESTORE ,iam role also but when i run the restore command i.e exec msdb.dbo.rds_restore_database @restore_db_name='backupdb', @s3_arn_to_restore_from='arn:aws:s3:::Bucketname/backupfile27022023.bak'; its showing an error as The EXECUTE permission was denied on the object 'rds_restore_database', database 'msdb', schema 'dbo'. admin is master user but it doesn't have the execute permission. How to solve it
To generate a bash script to automate the process of creating snapshots of aroura psql database backup and export the same to s3 bucket with aws iam credentials cron job for every 3 hours and hold snapshots for 30 days
I am trying to export a snapshot to an S3 bucket, from our Aurora Postgres Serverless v2 cluster. I keep getting the following error message: "The specified db snapshot engine mode isn't supported and can't be exported." AFAICT from the user guide, Serverless v2 does support exporting snapshots to S3: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-export-snapshot.html Our engine is Aurora PostgreSQL, version 10.21, region is eu-west-1, encrypted.
In the CLI doc for [creating db instance](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html) and [creating db cluster ](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-cluster.html), it is mentioned that if publicly accessible flag is not specified explicitly, then the behavior is dependent on DBSubnetGroupName being specified or not. In my case, I specified the DBSubnetGroup which consists of public subnets and yet, the db instances created were not publicly accessible.
Couldnt execute this query without superuser permission ALTER ROLE user WITH REPLICATION; Im running a postgres db even I have enabled RDS_SUPERUSER role to that user.
Hello, I would like to know if its possible to configure a RDS Proxy RO Endpoint to fallback to the writer instance if there are no read replicas in the cluster? My software is configured to use both RDS Proxy Endpoints (writer and read-only) but if I delete the RDS read replica instance (because there is not enough load to justify the cost) I am getting connections errors to the Proxy RO endpoint. Thanks for help, I hope this is clear.