If the DB instance isn't in a VPC, then the instance might be using a DB security group to gate traffic. Any DB security group associated with the DB instance.For general information about VPC and DB instances, see Scenarios for accessing a DB instance in a VPC. You can specify an IP address, a range of IP addresses, or another VPC security group. If necessary, add rules to the security group associated with the VPC that allow traffic related to the source in and out of the DB instance. Any Amazon Virtual Private Cloud (Amazon VPC) security groups associated with the DB instance.If your DB instance is in the failed state, see Why is my Amazon RDS DB instance in a failed state? Be sure that your DB instance allows connectionsīe sure that traffic from the source connecting to your DB instance isn't gated by one or more of the following: Depending on the size of your DB instance, it can take up to 20 minutes for the DB instance to become available for network connections. If you recently launched or rebooted your DB instance, then confirm that the DB instance is in the available state in the Amazon RDS console. Resolution Be sure that your DB instance is in the available state For more information, see Run an automation. The automation doc also checks security groups based on the primary IP address of the EC2 instance, but that automation doesn't check specific ports. However, ephemeral ports aren't verified. This automation document can diagnose network ACLs based on the primary IP address of the Amazon Elastic Compute Cloud (Amazon EC2) instance. Or you can use the AWSSupport-TroubleshootConnectivityToRDS AWS Systems Manager Automation document to diagnose the issue for you. Tip: You can use the following troubleshooting steps to identify the source of the connectivity issue. The client is running on a version that's incompatible with the database version.You don't have the required database permissions to access the instance.You're using an incorrect user name or password at the database level to access the instance from the DB client.The user authentication is incorrect because of one of the following reasons:.The Multi-AZ DB instance failed over, and the secondary DB instance uses a subnet or route table that doesn't allow inbound connections.The wrong DNS name or endpoint is used to connect to the DB instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |