- 新しい順
- 投票が多い順
- コメントが多い順
The discrepancy you're observing between the describe-orderable-db-instance-options command results and actual RDS instance creation capabilities is important to understand.
When you run the command and don't see gp2 listed for db.c6gd.large but can still create an instance with that configuration, it suggests that the command output may not be showing all available options or there might be default options that aren't explicitly listed.
Unlike EC2, RDS doesn't have a dry-run option to validate configurations before creation. However, there are several approaches you can take for pre-validation:
-
Use the AWS Management Console's RDS creation wizard - it will validate your configuration choices in real-time and show you only compatible options as you make selections.
-
Use CloudFormation with the
--validate-templateoption to check if your RDS configuration is valid without actually creating resources. -
For more detailed validation, you can use the
describe-orderable-db-instance-optionscommand with different parameter combinations and filters to get more specific information about supported configurations. -
Consider using AWS Config rules or custom scripts that check against the RDS API to validate your intended configurations.
The describe-orderable-db-instance-options command is still useful for general guidance, but as you've discovered, it may not provide a complete picture of all possible configurations. For the most accurate pre-validation when using the GUI, the AWS Management Console's built-in validation during the creation process is likely your best option.
Sources
Amazon RDS examples using AWS CLI - AWS SDK Code Examples
Use DescribeOrderableDBInstanceOptions with an AWS SDK or CLI - Amazon Relational Database Service
Use DescribeOrderableDBInstanceOptions with an AWS SDK or CLI - AWS SDK Code Examples
Aurora cluster, DB Instance class for my region | AWS re:Post
