Hot answers tagged

84

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 ...


41

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 ...


39

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 ...


31

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!


24

When your RDS instance is not in a VPC, then your RDS instance is associated with an RDS security group. Those security groups are controlled by the "Security Groups" section in the RDS console. From there, you can add EC2-Classic security groups for access: Select your RDS security group Select "EC2 Security Group" for the "Connection Type" Select this or ...


22

I had this same question a few months back, and ended up contacting AWS (I have Enterprise support). This was the result: Unfortunately, moving DB instance subnet group to another subnet group in the same VPC is not supported at this time. I realize our documentation says that it is supported, but that is an error. We are currently working on ...


16

Windows by default allows two RDS RDP* connections out of the box, and they are known as "administrative connections" regardless of if the user account is an administrator or not. If you need more remote connections you need to research RDS which requires it's own set of user connection licenses in addition to CALs. RDS can allow for a number of ...


16

This has been solved. I began to examine the registry because increasing CPU and RAM resources on the virtual machine did not resolve the issue. I was pointed to Microsoft's dureg tool to estimate the registry's size. Browsing via regedit, I encountered issues opening the keys under HKEY_USERS\.Default\PRINTERS. Using dureg, I started probing under that ...


16

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:


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, ...


12

A third VM would, obviously, be the most desirable but, obviously, another Windows Server license costs money. Active Directory will only disable write caching on volumes where the database files are located. Adding a dedicated volume for file service would be fine in that respect. Of all the roles to "share" on a DC a file server is probably the least ...


11

Security groups won't be visible, because VPC security groups have no meaning outide their VPC... and your Classic instance is (of course) outside the VPC. Private VPC IP addresses of the instances won't work in the security config, either, since they also have no meaning outside the VPC. The solution is that you have to open up access (in the RDS security ...


11

Note: this became kind of a long answer, so I tried to structure it so you could just read the bold text and still come away with the most important points. It's about cost. It's always about cost. As we go through here, remember that these numbers change all the time, and that it's been about two years since I looked at any of this. The cost calculation ...


11

I have several thousand folks around the globe that connect and use accounting / office software daily. As long as their response times are under 300ms we don't get complaints but ymmv. As proof of concept I set up one of our user's switches using a linux / netem box and kept pushing up the latency / packet loss until I started having complaints. It was a ...


10

Simple - take a snapshot of your current RDS instance and then restore that snapshot to a new instance in your VPC.


10

One solution (but not the only solution!) is to use what's called a Bastion Host. A Bastion Host is an ultra-low-powered server that sits in your public subnet and is the only server that allows inbound SSH connections. This server should be thoroughly hardened, and depending on your level of paranoia, there are a few techniques you can use to hide the ...


10

I feel like this is sort of subjective, as some users won't be happy unless the latency is just like a local desktop experience, and other users will be happy and not complain even if latency is 300ms. It's true that latency is a user experience-killer, though, precisely how much is a matter of individual perception. This is a pretty good video from TechEd ...


9

General rule: keep your data separated from your application. There are many reasons: You can have multiple instances of your application working from the same data set Upgrading your application will not affect your data CPU is dedicated to one thing: data for data, application for application, choose appropriate sizes for each Having read-only replicas ...


7

I fear that you may be having a problem with "licensing". I saw something similar with a couple Wyse thin clients but rather than troubleshoot the issue the Customer just opted to replace the hardware (because they only had two of the devices). This long thread on social.technet.microsoft.com is filled with users having a similar experience. The users there ...


7

Actually, one can install RDSH on Windows Server 2012 in a Workgroup environment. This configuration is appropriate when there is only one server on the network and it will provide desktop sessions to users based on the number of Remote Desktop Services client access license (RDS CALs) installed on the server, but will not provide access to RemoteApp ...


6

The licensing and broker roles generally are installed to a server that is not one of the servers providing the Remote Desktop sessions to users. I have often seen these two roles put together on a single box. In a small 3 server farm the broker/license box will probably be idle most of the time. These roles seem to work perfectly fine in a VM, so also ...


6

You can't effectively deny rights to local administrators, since regardless of what GPO you apply, they can always override it at least temporarily by editing the registry. They can also remove the computer from the domain. In general, you shouldn't use or distribute the local administrator accounts in an environment requiring top-down administrative ...


6

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


6

I'm new to AWS and had the same problem when trying to create and add a new database from the Elastic Bean Management Console. It was fixed after adding the AWSServiceRoleForRDS - role in IAM. Go to IAM --> Roles --> Create role --> AWS Service: Select RDS, and RDS use case. Click on "Next:Permissions". There you'll see that the AmazoneRDSServiceRolePolicy ...


6

Sure, login with the master user / password credentials that you used when creating the instance and then create the database: $ mysql -u{MasterUser} -p{MasterPassword} -hmysql–instance1.123456789012.us-east-1.rds.amazonaws.com mysql> CREATE DATABASE new_db; mysql> CREATE USER ... mysql> GRANT ...; Just like with any other MySQL server. If you ...


6

With more information about what you're trying to achieve and why we might be able to help more. Read Replicas You can create multiple RDS Read Replicas, then offload some of the database traffic to those replicas. Writes go to the master database. This is separate from RDS Multi-AZ which is for reliability rather than scale. Finding the Bottleneck While ...


5

With the new updated RDS UI, the username is present in the Details section of the Instance Information screen. From the List of your running Instances, click an instance name to see information about the instance. See the "Details" section of the information screen. scroll down in that screen to see the "Details" section.


5

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


5

Just create a new securitygroup with 5432 as inbound TCP connection and replace current security group on your RDS instance with the newly created one.


5

I have actually ran into this on a couple of servers running 2012 R2 recently and this solved it. Must be a 'feature'. http://www.tbngconsulting.com/blog/bid/404182/Licensing-mode-for-the-Remote-Desktop-Session-Host-is-not-configured In PowerShell, do the following: $obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting $...


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