Questions tagged with Database
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,
[Jeremy Daly talks about reusing RDS connections in AWS Lambda](https://www.jeremydaly.com/reuse-database-connections-aws-lambda/). I assume this principle of establishing the connection outside of the Lambda handler's context would work for Snowflake connections too?
asked a month ago
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.
Is there a way to delete old log files and old backup logs from AWS RDS ? I am getting an alert "Storage size 200 GB is approaching the maximum storage ".
On the ON-Premise databases, we would go on the database server and delete old files, what is the solution provided by AWS RDS, Oracle
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,
Starting from 2023-03-01 the `mongodump` command fails to exec on documentDB 4.0 instances. Before this date the `mongodump` command was working just fine.
Error trace:
**Failed: error checking for AtlasProxy: Unknown admin command atlasVersion**
I've used mongodb-org-tools=4.4.15 and mongodb-org-tools=5.0.15 to run the `mongodump` with the same result.
Command:
```
mongodump --ssl \
--host="$DB_HOST:$DB_PORT" \
--db="$DB_DATABASE" \
--username="$DB_USERNAME" \
--password="$DB_PASSWORD" \
--archive=./production-mongodump.gz \
--numParallelCollections=4 \
--authenticationDatabase="$DB_AUTHENTICATION_DATABASE" \
--authenticationMechanism=SCRAM-SHA-1 \
--sslCAFile=./rds-combined-ca-bundle.pem \
--gzip
```
Any ideas of what this can be?
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)
We have noticed a sudden increase in costs generated by our RDS Aurora MySQL Serverless v2 clusters that we cannot understand, and would like some help in resolving this issue.
Around February 18th, we noticed that the capacity metric on our instances was not decreasing its capacity to a minimum at night when no one was using it. Before this date, our clusters would usually maintain a minimum of 0.5 ACU during off-peak hours. However, after February 18th, the capacity stayed the entire night at 1.5 ACU, and later to 1 after we capped the max capacity at night.
We have followed the instructions recommended by some users and turned off Performance Insight, but the problem still persists. We could not find any queries generated by a user in the logs of the night where no one usually uses the system, only the ones executed internally by RDS.
We suspect that the reason for the sudden increase in costs may be due to an internal change that AWS made to the service. If this is the case, we would appreciate any information you could provide us on this change so that we can optimize our resources and reduce costs wherever possible.
We would be grateful if you could investigate this matter and provide us with a prompt response. We rely on your expertise to help us resolve this issue and continue to use AWS services effectively.
Thank you for your attention to this matter.
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 a month ago
I have 2 databases that I am using, first DynamoDB and second one is TimestreamDB. And I am trying to query from both the databases using AppSync Graphql API.
for that I am adding multiple dynamo tables as separate data sources, and for timestream I am creating VPC endpoint for TimestreamDB, and adding HTTP data source for that.
Now the question is, I can create schema, query and resolvers for Dynamo Tables. And the AWS AppSync documentation says that for now, only public endpoints are working with AppSync. Ref:"https://docs.aws.amazon.com/appsync/latest/devguide/tutorial-http-resolvers.html"
So is there any other way I can satisfy my requirements of connecting Timestream HTTP endpoint with AppSYnc?