- Newest
- Most votes
- Most comments
I have encountered similar situations while creating RDS Custom for Oracle. I found starting/restarting the base ec2 instances clearing up this problem usually. I would hence suggest you check the status of the base ec2 instances.
Thanks Govardhanan, but when the RDS Custom status change to Incompaible-create, I can`t find the EC2 instance which is created by RDS Custom anymore...
There are few areas to check on this issue:
-
Follow official doc to make sure your VPC and IAM created per requirements. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/custom-setup-sqlserver.html#custom-setup-sqlserver.review
-
Select correct VPC , Subnet Group and instance profile during the DB Creation
-
Check security group, if Security Group used by RDS is not same as default security groups (the one associated with VPC endpoints), make sure necessary file ports open
Relevant content
- asked 10 months ago
- Accepted Answerasked 10 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
And there is an AccessDenied error in CloudTrial, event name is PutTargets Error Message is : User: arn:aws:sts::xxxxxxxxx:assumed-role/AWSServiceRoleForRDSCustom/SLRManagement is not authorized to perform: events:PutTargets on resource: arn:aws:events:us-east-2:xxxxxxxxx:rule/do-not-delete-rds-custom-db-KXBOWMDX2LBPGHYDTJQHC7PJD4-xxxxxx because no identity-based policy allows the events:PutTargets action. Is it the root cause for this issue?