amazon-rds

问题 I can't find any examples on creating a SQL Server RDS instance in CloudFormation, so I took an educated guess using an example for MySQL. Here's what I came up with: { "AWSTemplateFormatVersion" : "2010-09-09", "Resources" : { "DBInstance" : { "Type": "AWS::RDS::DBInstance", "Properties": { "DBInstanceIdentifier" : "test-db", "Engine" : "sqlserver-ex", "Port" : "1433", "DBInstanceClass" : "db.t1.micro", "AllocatedStorage" : "30", "MasterUsername" : "sa", "MasterUserPassword" : "password" } }

问题 I have oracle dump file in my AWS ec2 instance, I want to import this dump file to Oracle database in AWS RDS. I tried using with Oracle SQL developer and also using Perl script. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Procedural.Importing.html How to import oracle dump from ec2 instance to RDS in AWS Using Oracle SQL Developer method, the 'Database Copy' option is not enabled. Using Perl, getting a lot of error while running the script. [root@ip-172-28-1-70 oracle]#

问题 I think I am almost there. I created an instance of AWS BeanStalk and added an oracle DB instance to it. When I found the log, I saw the driver was loaded but it keeps saying that URL is invalid. Here are my RDS info and log message. [RDS Info] Endpoint = aa1c9autjaqoufk.c2k1ch01futy.ap-northeast-2.rds.amazonaws.com Port = 1521 Public Access = yes [System Log] 25-Jun-2018 02:42:56.759 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"] 25-Jun

问题 What is the best practice for keeping an Amazon RDS UAT database refreshed weekly from a Production version of that database? We were thinking of mirroring the production RDS, but we don't want any changes in UAT to be reflected in Production. So the thought of taking a weekly backup of production and restoring it to the UAT, but this is time consuming. Can we apply a snapshot of Production onto UAT if UAT is initially a restore of some point in time from Production? 回答1: RDS offers two

问题 Would communicating with an RDS instance through a public endpoint (RDS in a public subnet) incur more data transfer costs vs one in a private subnet, given that both RDS and the entity accessing it are in the same AZ? 回答1: The DNS Name of the Amazon RDS db instance should resolve to a private IP address when used within the VPC. Thus, the only potential charge is 2¢/GB between AZs (1¢ in and 1¢ out). If they are both in the same AZ , there should be no data transfer charge. Accessing via a

问题 I'm using C3P0 connection pool and PostgreSQL(10.3) in AWS RDS. I did a load test at low TPS (1 TPS) for 2 minutes, after load test finished, the number of connections were not dropped according to the monitoring board in AWS RDS. (See below). Neither did CPU utilization. I'm still new to database, not sure if this is expected? This seems like it's reaching RDS instance's max_connection. I did a select from pg_stat_activity , 99% of connections are idle , and most of the queries are SHOW

问题 I'm running the following rds instance. However, my write PIOPS is bottlenecked at 20% of the allocated PIOPS. db.r3.xlarge Provisioned IOPS (SSD) 5000 PIOPS 600 GB Do you have any ideas why it's stuck there? Thank you. 回答1: Your RDS instance type I/O are limited by two factors. IOPS and throughput. As you don't reach your IOPS limit it's probably your throughput which stuck here. You have a very interesting piece of documentation here. You could try to upgrade from r3.xlarge to r3.2xlarge to

问题 I'm running the following rds instance. However, my write PIOPS is bottlenecked at 20% of the allocated PIOPS. db.r3.xlarge Provisioned IOPS (SSD) 5000 PIOPS 600 GB Do you have any ideas why it's stuck there? Thank you. 回答1: Your RDS instance type I/O are limited by two factors. IOPS and throughput. As you don't reach your IOPS limit it's probably your throughput which stuck here. You have a very interesting piece of documentation here. You could try to upgrade from r3.xlarge to r3.2xlarge to

问题 I'm running the following rds instance. However, my write PIOPS is bottlenecked at 20% of the allocated PIOPS. db.r3.xlarge Provisioned IOPS (SSD) 5000 PIOPS 600 GB Do you have any ideas why it's stuck there? Thank you. 回答1: Your RDS instance type I/O are limited by two factors. IOPS and throughput. As you don't reach your IOPS limit it's probably your throughput which stuck here. You have a very interesting piece of documentation here. You could try to upgrade from r3.xlarge to r3.2xlarge to

问题 I'm using AWS for my project and Laravel 5. Just installed my laravel project in the EC2 and set up a DB in RDS. I imported the .sql file using mysql workbench. In my .env I set up the host, the DB name, user and password but when I go to the project in the browser I get an error: PDOException in Connector.php line 55: SQLSTATE[HY000] [2003] Can't connect to MySQL server on 'blue*****.************.us-west-2.rds.amazonaws.com' (4) Put the * for security reasons. So what could be wrong? Update: