- Newest
- Most votes
- Most comments
I have faced similar issues when creating RDS Custom for SQL Server. The best way to resolve this is to follow the recommended approach of using a CloudFormation template mention below.
You can compare your existing setup to the template and identify what setting and steps may be missing or incorrect related to your VPC, IAM, and instance profile configuration during RDS Custom database creation. By aligning to the reference CloudFormation template, you are more likely to set up the required networking, permissions, roles and other dependencies properly for a successful RDS Custom deployment. You can also use following YouTube videos for your reference to create a RDS custom instance.
-
Configure networking, instance profile, and encryption: "Configuring with AWS CloudFormation (recommended)" https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/custom-setup-sqlserver.html#custom-setup-sqlserver.iam-vpc
-
How to Create and Connect to RDS Custom for SQL Server Instance : https://www.youtube.com/watch?v=6rJArhGNens
-
Troubleshooting DB issues for Amazon RDS Custom for SQL Server: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/custom-troubleshooting-sqlserver.html
Relevant content
- Accepted Answerasked 6 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago