106

AWS RDS max_connections limit variable is based on Instance type, so you can upgrade your RDS or make more replica. The RDS types with max_connections limit: t2.micro 66 t2.small 150 m3.medium 296 t2.medium 312 m3.large 609 t2.large 648 m4.large 648 m3.xlarge 1237 r3.large 1258 m4.xlarge 1320 m2.xlarge 1412 m3.2xlarge 2492 r3.xlarge 2540 Referring by ...


54

The issue was that the inbound rule in the Security Group specified a security group as the source. Changing it to a CIDR that included my IP address fixed the issue. Open the database security group in AWS; and choose "Edit inbound rules"; "Add rule". There is a "My IP" option in the dropdown menu; select that option to auto-populate with your computer's ...


51

You can change the max_connections value by either updating the default parameter policy or create a new one - I'd suggest going with the latter. Go to RDS Parameter Groups Create a new Parameter Group (AWS wil leave everything as default) search for the max_connections value Change the value to use Go to RDS instance and modify Select new Parameter group ...


36

The master username is now listed in the RDS Dashboard. Select the "Instances" listing and expand the DB instance. Press the looking glass tab on the left. The master username is listed in the left column. Hope this helps!


33

About 2 years ago, I was tasked with evaluating Amazon RDS for MySQL. I wrote some posts in the DBA StackExchange about my findings and observations: Jul 25, 2012 : Scaling Percona datacenters: setup and replication Aug 02, 2012 : Local database vs Amazon RDS Sep 21, 2012 : MySQL 5.5 Runs Out of Memory, Drops All Connections When Creating Many Databases In ...


31

This is Amazon's own user that is used by Amazon to perform updates, run backups and do other maintenance tasks. That said, Amazon's support should be able to advise you. In general, you don't need to (and should not) know the password.


29

The "selected" answer is correct, but I wanted to add some extra information as most people using EB and RDS together should have the same requirement too - even if they don't know it yet. First question: Why would you want the RDS instance to exist outside the EB environment? Answer: So that the lifetime of the RDS instance is not tied to the lifetime of ...


27

You do likely need log_bin_trust_function_creators = 1 on RDS but that isn't the issue, here. You can specify a DEFINER value other than your own account only if you have the SUPER privilege. — http://dev.mysql.com/doc/refman/5.6/en/stored-programs-security.html When a stored program (proc, function, event, or trigger) is running, everything it does has ...


27

Yes, your understanding is correct. There's no AWS charging based on CPU usage -- you pay the same for an instance whether its CPU usage is 0% or 100%.


26

RDS instances are managed by Amazon. As such, to prevent you from breaking things like replication, your users - even the root user you set up when you create the instance - will not have full superuser privileges. http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.PostgreSQL.CommonDBATasks.html When you create a DB instance, the master user ...


24

It is basically available RAM. See answer from AWS here https://forums.aws.amazon.com/thread.jspa?threadID=209720 and the official documentation is here http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_BestPractices.html. If you have a lot of freeable memory you can downgrade to a smaller instance. If you are running out of freeable memory, then it ...


24

First, note that you may be looking at the incorrect operation -- you describe that you want to change storage size, but have quoted documentation describing storage type. This is an important distiction: RDS advises that you won't experience an outage for changing storage size, but that you will experience an outage for changing storage type. Expect ...


23

Answer from the AWS support: In order to associate an existing database to a EB Environment you have to take a snapshot of it via the Management Console and then choose "create a new RDS database" under the Data Layer. There does not appear to be a way to associate a running RDS instance to an existing EB Environment without launching a new one ...


23

RDS instances can change their IPs unexpectedly, so they should not be used nor are they provided in the console or API (although you can technically dig for them). The DNS endpoint provided in the AWS console will resolve to the internal IPs from within Amazon's network.


23

For an RDS instance in VPC to "publicly" (Internet) accessible, all of the subnets it is attached to must be "public" -- as opposed to "private" -- subnets of the VPC. A public subnet is essentially defined as a subnet that has the Internet Gateway object (igw-xxxxxxxx) as its route to "the Internet," or at least to any Internet destinations you need to ...


23

There are multiple things at play here... Each table is stored in its own tablespace By default, the parameter group for Aurora clusters (named default.aurora5.6) defines innodb_file_per_table = ON. That means each table is stored in a separate file, on the Aurora storage cluster. You can see which tablespace is used for each of your tables using this ...


18

Was facing similar issue, and this is how I resolved it: Click on the security group for the RDS instance and check the inbound rules. You might see something like this: Have to set the IP range to contain your IP or just select "Anywhere" in the Source dropdown, to make it accessible from localhost or anywhere:


15

It is 2019 now. It is 'Databases' on the sidebar, 'Configuration' on the navigation bar. And look for username.


15

Here's what you can do to change max_connections or any other parameter in an AWS RDS (mysql) instance: From RDS console go to Parameter Groups Create a new parameter group based on the default group and name it my-param-group Modify max_connections or other parameters in my-param-group Go back to instance main page and click Modify in Instance Action ...


14

For instance store-backed EC2 instances, one trick is to add a comment to the user data script containing a version number, date, or similar, then change that whenever you want the instance recreated: { "Resources" : { "MyEC2Instance" : { "Type" : "AWS::EC2::Instance", "Properties" : { // ... other ...


14

Yes, reserved instances are a billing construct wherever they're available (RDS, EC2, ElastiCache, etc.). No changes are necessary for the instance - if you buy a m3.large instance in us-west-2a, one of your m3.large instances in us-west-2a will immediately begin charging at the lower hourly rate.


14

I got a solution Amazon RDS will not give you SSH access to its database server. That means you don’t have the opportunity to view any of the log files, even the slow query log, for the database. But RDS provides a way to play with the slow queries. If your slow queries are many then this table will hold too many queries to handle. You cannot truncate the ...


14

Actual info for Postgresql t3-instances (default.postgres10 parameter group): db.t3.micro - 112 max_connections db.t3.small - 225 max_connections db.t3.medium - 450 max_connections db.t3.large - 901 max_connections db.t3.xlarge - 1802 max_connections db.t3.2xlarge - 3604 max_connections Its similar for default.postgres9 and default.postgres11


14

The default sslmode for PostgreSQL is prefer which means it will encrypt the connection with the certificate provided by the server but will not verify it. If I were to change the sslmode setting to verify-ca or verify-full then I would need to install the intermediate certs in a particular directory and then it would do proper verification. As I'm not ...


13

RDS has recently added a stored procedure to accomplish this: EXEC rdsadmin.dbo.rds_modify_db_name N'<OldName>', N'<NewName>' Source: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.SQLServer.CommonDBATasks.RenamingDB.html


13

Reserved instances are a billing construct only. If you buy a reserved instance for a m1.small in us-west-2a, all that means is that one of your on-demand RDS instances that's an m1.small in us-west-2a receives that lower hourly price (and incidentally, if you delete that instance and make a new one, the reservation's lower hourly rate just shifts onto the ...


12

Amazon has recently issued a press release announcing that you can now change the VPC for existing RDS instances: You can now easily change the Amazon Virtual Private Cloud (Amazon VPC) used by your Amazon RDS DB instance. You can specify a new VPC for an existing DB instance deployed in Single-AZ configuration by using the Amazon RDS Management Console, ...


11

You can refer to http://aws.amazon.com/rds/faqs/#23 or you can use the CLI with a scheduled task: aws rds create-db-snapshot --db-snapshot-identifier DBName-Snapshot-20131125 --db-instance-identifier DBName


11

You can also modify query_cache_size and max_allowed_packet parameters via the AWS Management console. Use this AWS documentation as your guide, link


11

Notice the constraint in the docs when using --db-instance-indentifier: --db-instance-identifier (string) The user-supplied instance identifier. If this parameter is specified, information from only the specific DB instance is returned. This parameter isn't case-sensitive. Constraints: - If supplied, must match the identifier of an existing ...


Only top voted, non community-wiki answers of a minimum length are eligible