Questions tagged with Amazon Relational Database Service
Content language: English
Sort by most recent
We have a MariaDB RDS in version 10.5.x and instance type of r5.xlarge. I created a Blue/Green Deployment to upgrade both DB version and instance type to r6g.xlarge. It creates the master instance in Green Deployment and upgraded to the latest MariaDB version yet the Blue/Green Deployment stuck in Provisioning.
Earily we have created a Blue/Green Deployment for another RDS and everything goes smooth with a very similar background. I have no idea on what should we do regarding it.
Hi,
I have db.r5.xlarge(RDS MySQL 8.0.23) RDS instance, I would like to upgrade to 8.0.28 using inplace upgrade.
I have tested the upgrade from 8.0.23 to 8.0.28 in development instance(db.t3.medium), and it takes about 10 minutes.
I wonder is it disk-intensive on this upgrade, 'cause our development instance has rather small data size other than production environment.
Thanks,
we have our data in AWS RDS postgres db. We have a table with around 100-200 rows and we loaded up 200M rows in 3 hours timeframe. That table is indexed as well. And now we want to insert more data into the table and we see that adding 20M rows is taking 5 hours.
Our instance size is db.r6g.xlarge. And we have two AZ. I want to know the reason for slower performance in query operation and what is the best way to import that huge data into postgres table.
I have a PostgreSQL RDS database in AWS which is in a free-tier period
I have launched the database for free-tier but still I am getting charged for the RDS every month, which is of the type "$0.131 per GB-month of provisioned gp2 storage running PostgreSQL", why I am getting charged for this, like this charge for the inbound/outbound transfer, database backups or basically what I am exceeding above free-tier limits for which I am charged
Kindly provide me a solution for how I can avoid these charges, I should change the RDS configurations, change the storage type, or any other step I can take so, that I can avoid these charges
Hello,
I have a RDS Postgres used by a lambda. This lambda is used on a front end experience.
Recenlty I reached the limit of connections on the rds.
My concern is that the logs where showing this messages like a 100 times:
2023-02-27 11:00:22 UTC:3.0.139.252(47570):********@********:[23428]:FATAL: password authentication failed for user "*********"
2023-02-27 11:00:22 UTC:3.0.139.252(47570):********@*********:[23428]:DETAIL: Role "********" does not exist.
Connection matched pg_hba.conf line 13: "host all all all md5"
2023-02-27 11:00:45 UTC:3.0.139.252(52788):********@*********:[23453]:FATAL: password authentication failed for user "********"
2023-02-27 11:00:45 UTC:3.0.139.252(52788):*******@********:[23453]:DETAIL: Role "******" does not exist.
Connection matched pg_hba.conf line 13: "host all all all md5"
2023-02-27 11:01:26 UTC:3.0.139.252(58080):********@**********:[23498]:FATAL: password authentication failed for user "**********"
2023-02-27 11:01:26 UTC:3.0.139.252(58080):********@**********:[23498]:DETAIL: Role "*****" does not exist.
Connection matched pg_hba.conf line 13: "host all all all md5"
2023-02-27 11:01:33 UTC:3.0.139.252(39560):********@*******:[23539]:FATAL: password authentication failed for user "**********"
2023-02-27 11:01:33 UTC:3.0.139.252(39560):*********@*******:[23539]:DETAIL: Role "*******" does not exist.
Connection matched pg_hba.conf line 13: "host all all all md5"
This is easier a log issue because the connection limit was reached or either someone trying to bruteforce the database.
Can you confirm that this is link to the connection limit being reached ?
Also now when I look at my connections limit I see pikes like bellow:
But when I look my trafic analytics I don't have huge pikes of views at the same time.
What can this be related to ? What exatcly count as a connection ?
Thank you in advance,
Hello,
I try to create an oracle database instance but I have this error with cloudformation and I can't find a solution.
Can anyone help with this problem.
Resource handler returned message: "Access Denied to API Version: API20120917
(Service: Rds, Status Code: 400, Request ID: 172bd747-8158-4b30-8222-efaca96267e2)"
(RequestToken: 5d0b9b3a-4185-1b76-e6d3-9aab9896c076, HandlerErrorCode: InvalidRequest)
Required steps for creating SNS notification from cloudwatch log group for rds
im trying to set up a managed grafana instance in AWS and configure a datasource to pull from a RDS database (public ip). When i test the connection i get a 504 response
i can successfully connect to the connection via mysql workbench. however, with the same connection info and credentials in the add datasource -> mysql page within grafana i get the following error:
```
<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
```
I have tried adding the IP address of my managed grafana instance to the inbound TCP rules for the RDS security group roles for the instance as well:
```
Non-authoritative answer:
Name: g-7b1e9d3d37.grafana-workspace.us-east-2.amazonaws.com
Address: 3.141.179.101
Name: g-7b1e9d3d37.grafana-workspace.us-east-2.amazonaws.com
Address: 52.14.201.37
Name: g-7b1e9d3d37.grafana-workspace.us-east-2.amazonaws.com
Address: 3.132.106.29
```
Hi,
I want to understand the best way to query RDS using a lambda function to fetch data and write to another AWS account S3 bucket.
Do we need to create view?
how long lambda can be executed?
What should be batching strategy?
Can it write in parquet format?
Thanks in advance.
I need to change the default timezone of AWS Aurora PostgreSQL cluster from UTC to CST. We can change it by creating a custom cluster parameter group and then use it in the cluster.
Now my question is what will happen during daylight savings? Will there be any impact of daylight savings to the DB cluster? Do we need to make any change regarding daylight savings in the cluster, instance? Do we need to reboot the cluster?
Please suggest.
Hi,
we have a small db.t4g.micro RDS (PostgreSQL) instance as a development database and an RDS proxy in front of it.
We started sending traffic constantly to it during the last 12 hours or so and we noticed that the instance restarted on its own twice.
Looking at the monitoring tab in RDS console, we observed that the restart times coincide exactly with the times that EBS Bytes Balance dropped to zero. (CPU credit balance, Burst Balance and EBS IO Balance were all > 0).
Excerpt from the error/postgresql.log:
```
2023-03-01 04:51:55 UTC::@:[375]:LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.001 s, sync=0.001 s, total=1.754 s; sync files=0, longest=0.000 s, average=0.000 s; distance=65535 kB, estimate=65535 kB
2023-03-01 04:56:54 UTC::@:[375]:LOG: checkpoint starting: time
2023-03-01 04:56:54 UTC::@:[375]:LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.001 s, sync=0.001 s, total=0.639 s; sync files=0, longest=0.000 s, average=0.000 s; distance=65535 kB, estimate=65535 kB
2023-03-01 04:57:21 UTC:172.31.5.233(18341):postgres@dns:[384]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:21 UTC:172.31.5.233(64393):postgres@dns:[386]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:21 UTC:172.31.45.245(10055):rdsproxyadmin@postgres:[31769]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:21 UTC::@:[372]:LOG: received SIGHUP, reloading configuration files
2023-03-01 04:57:21 UTC:172.31.45.245(19305):postgres@dns:[388]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:21 UTC:172.31.5.233(19611):rdsproxyadmin@postgres:[31768]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:21 UTC::@:[372]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf"
2023-03-01 04:57:21 UTC::@:[375]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf"
2023-03-01 04:57:24 UTC::@:[373]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf"
2023-03-01 04:57:24 UTC::@:[373]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf"
2023-03-01 04:57:21 UTC:172.31.5.233(61767):postgres@dns:[383]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:22 UTC::@:[31837]:FATAL: terminating autovacuum process due to administrator command
2023-03-01 04:57:23 UTC::@:[379]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf"
2023-03-01 04:57:21 UTC:172.31.45.245(10079):postgres@dns:[401]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:23 UTC::@:[375]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf"
2023-03-01 04:57:23 UTC::@:[379]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf"
2023-03-01 04:57:21 UTC:172.31.45.245(51481):postgres@dns:[389]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:22 UTC:172.31.5.233(52633):postgres@dns:[385]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:23 UTC:172.31.5.233(17531):postgres@dns:[382]:FATAL: terminating connection due to administrator command
2023-03-01 04:57:24 UTC::@:[377]:LOG: skipping missing configuration file "/rdsdbdata/config/recovery.conf"
2023-03-01 04:57:25 UTC::@:[372]:LOG: received smart shutdown request
2023-03-01 04:57:29 UTC::@:[372]:LOG: background worker "logical replication launcher" (PID 380) exited with exit code 1
2023-03-01 04:57:29 UTC::@:[375]:LOG: shutting down
2023-03-01 04:57:29 UTC::@:[375]:LOG: checkpoint starting: shutdown immediate
2023-03-01 04:57:29 UTC::@:[375]:LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 1 recycled; write=0.001 s, sync=0.001 s, total=0.308 s; sync files=0, longest=0.000 s, average=0.000 s; distance=65535 kB, estimate=65535 kB
2023-03-01 04:57:31 UTC:127.0.0.1(49550):rdsadmin@rdsadmin:[31839]:FATAL: the database system is shutting down
2023-03-01 04:57:32 UTC::@:[372]:LOG: database system is shut down
```
Should EBS Bytes Balance exhaustion really lead to the database spontaneously restarting?
Thanks,
Nikos
I have an RDS MS SQL Server (SQL Server Web Edition) version 15.00.4236.7.v1 with instance type db.t3.large and I want to switch Storage Type from gp2 to gp3, but everytime I try to apply the change the following message shows:
> **We're sorry, your request to modify DB instance db-name has failed.**
>Cannot modify the instance class because there are no instances of the requested class available in the current instance's availability zone. Please try your request again at a later time.
RDS is running in N.Virginia (us-east-1), specifically use1-az2.
Any thoughs ?
asked 25 days ago