Troubleshooting BYOM engine version and DB instance

The following table helps you diagnose and resolve common issues when creating and managing Bring Your Own Media (BYOM) engine versions and DB instances for RDS for SQL Server.

Error Message / Symptom	Cause	Recommended Fix
InvalidParameterValue: RDS can't create the custom engine version because the provided <Name>.ISO file doesn't match the expected installer file for engine version 15.00.4435.7.v1	The RTM file you uploaded doesn't match the SQL Server major version or edition specified in the command. For example, uploading a SQL Server 2022 ISO while targeting a 2019 engine version (15.xx).	1. Verify the engine version prefix matches the ISO: 15.xx = SQL Server 2019, 16.xx = SQL Server 2022. 2. Verify the engine parameter matches the edition: sqlserver-ee = Enterprise, sqlserver-se = Standard. 3. Upload the correct RTM file to S3. 4. Delete the failed BYOM engine version if one was created. 5. Retry create-custom-db-engine-version with the matching ISO.
CreateCustomDBEngineVersionFault: RDS was unable to access the specified installer file in the S3 bucket.	RDS could not access the S3 bucket, or ISO file not found at the specified S3 location.	1. Verify the S3 bucket does not have policies blocking RDS service access. 2. Verify the S3 bucket name in --database-installation-files-s3-bucket-name. 3. Verify the file name in --database-installation-files matches exactly. 4. Confirm the bucket is in the same Region as the BYOM engine version. 5. Check for SCPs or VPC endpoint policies that may block access. 6. Retry create-custom-db-engine-version.
InvalidParameterValue: RDS can't create the custom engine version because the provided file doesn't match the expected installer file for engine version	The CU file does not match the target engine version.	1. Identify the correct CU KB number for your target minor version. 2. Retry create-custom-db-engine-version with the matching CU version.
InvalidParameterValue: The custom engine version isn't valid. Names can include only lowercase letters (a-z), dashes (-), underscores (_), and periods (.). Specify a valid CEV, refer to https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/custom-cev.html#custom-cev.create, and try again.	Verify that your CEV name uses only supported characters and that you are using a BYOM supported SQL Server edition or version.	1. Verify you are using a supported engine: sqlserver-ee or sqlserver-se. 2. Verify the engine version is SQL Server 2019 (15.xx) or SQL Server 2022 (16.xx). 3. Retry with a supported edition and version.
InvalidCustomDBEngineVersionStateFault: You can't delete custom engine version sqlserver-ee 15.00.4465.1.v1. At least one instance and one backup is using the CEV. Change the version or delete the instances and backups, and try again.	DB instances, snapshots, or read replicas are still using the BYOM version.	1. Identify resources using this version: aws rds describe-db-instances --query "DBInstances[?EngineVersion=='<version>']". 2. Identify snapshots: aws rds describe-db-snapshots --query "DBSnapshots[?EngineVersion=='<version>']". 3. Migrate instances to a different version or delete them. 4. Delete associated snapshots and automated backups. 5. Retry delete-custom-db-engine-version.
InvalidParameterCombination: The LicenseModel parameter is required for configurations with multiple options.	BYOM is activated for this version but --license-model was omitted.	Add --license-model bring-your-own-media or --license-model license-included to your command.
The combination of engine sqlserver-se and version <version> isn't valid. Enter a valid custom engine version, and try again.	This error occurs when: (1) No BYOM engine version exists for the target engine version; (2) The target BYOM engine version is in incompatible-media or inactive status; (3) The specified engine version is not a supported major/minor combination.	To verify supported engine versions, run describe-db-engine-versions and create a BYOM engine version first using create-custom-db-engine-version.
InvalidParameterCombination: RDS can't perform the operation because the custom engine version <version> is in incompatible-installation-media status. Choose a custom engine version in one of the following statuses and try again: available, creating, pending-validation, validating.	The BYOM engine version failed validation state.	Delete the failed BYOM engine version, re-upload correct installation media, and create a new BYOM engine version.
InvalidParameterCombination: RDS does not support creating a DB instance with the following combination: DBInstanceClass=<instance class>, Engine=<Edition>, EngineVersion=<version>, LicenseModel=bring-your-own-media. For supported combinations of instance class and database engine version, see the documentation.	The instance type you specified is not supported for BYOM.	To verify if your instance class supports BYOM, use the describe-orderable-db-instance-options API: aws rds describe-orderable-db-instance-options --engine sqlserver-ee --engine-version <version> --db-instance-class <instance-class> --region <region> --query "OrderableDBInstanceOptions[?LicenseModel=='bring-your-own-media']". Alternatively, visit the Amazon RDS for SQL Server pricing page for supported instance classes.
InvalidParameterCombination: The combination of engine and version isn't valid. Enter a valid custom engine version, and try again. (on ModifyDBInstance)	To upgrade a BYOM instance, a BYOM engine version must exist for the target version and must be in at least available status. The modify-db-instance call is rejected when: no BYOM engine version exists for the target engine version; the target BYOM engine version is in incompatible-media or inactive status; the target version is not in the ValidUpgradeTarget array.	Use the describe-db-engine-versions command to list valid minor version upgrade targets. Before you apply a minor version upgrade to a BYOM instance, verify that a valid BYOM engine version exists for the target version. If it does not, create one and wait for it to become available.