AWS AmazonRDS: BYOM SQL Server troubleshooting: add 2025 support, fix status names
Summary
Updates the RDS for SQL Server BYOM troubleshooting table: adds SQL Server 2025 (17.xx) to supported engine-version guidance, renames the CEV status from `incompatible-media` to `incompatible-installation-media`, standardizes 'Amazon S3'/'Amazon RDS' naming, replaces an inline `describe-orderable-db-instance-options` CLI example with links to pricing and instance-class docs, and adds a new row for the `Duplicate filter value for filter Engine Edition` error pointing to AWS License Manager integration docs.
Security assessment
This is a troubleshooting/error-message reference update. The only security-adjacent text (S3 bucket policies, SCPs, VPC endpoint policies blocking RDS access) is pre-existing content that was merely reworded with 'Amazon' prefixes, not newly added or changed in substance. No vulnerability, CVE, credential, encryption, or authorization change is described; the substantive edits are adding SQL Server 2025 (17.xx) support, correcting the CEV status name to `incompatible-installation-media`, and adding a License Manager duplicate-filter error row.
Evidence
+`CreateCustomDBEngineVersionFault: RDS was unable to access the specified installer file in the S3 bucket.` | Amazon RDS could not access the Amazon S3 bucket, or ISO file not found at the specified Amazon S3 location. | 1\. Verify the Amazon S3 bucket does not have policies blocking Amazon RDS service access. 2. Verify the Amazon 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`.
Diff
diff --git a/AmazonRDS/latest/UserGuide/sqlserver-byom-troubleshooting.md b/AmazonRDS/latest/UserGuide/sqlserver-byom-troubleshooting.md index 708e076..0a3bb00 100644 --- a//AmazonRDS/latest/UserGuide/sqlserver-byom-troubleshooting.md +++ b//AmazonRDS/latest/UserGuide/sqlserver-byom-troubleshooting.md @@ -13,2 +13,2 @@ 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 <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, 17.xx = SQL Server 2025. 2. Verify the engine parameter matches the edition: `sqlserver-ee` = Enterprise, `sqlserver-se` = Standard. 3. Upload the correct RTM file to Amazon 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.` | Amazon RDS could not access the Amazon S3 bucket, or ISO file not found at the specified Amazon S3 location. | 1\. Verify the Amazon S3 bucket does not have policies blocking Amazon RDS service access. 2. Verify the Amazon 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`. @@ -16 +16 @@ Error Message / Symptom | Cause | Recommended Fix -`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. +`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), SQL Server 2022 (16.xx), or SQL Server 2025 (17.xx). 3. Retry with a supported edition and version. @@ -19 +19 @@ Error Message / Symptom | Cause | Recommended Fix -`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`. +`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-installation-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`. @@ -21,2 +21,3 @@ Error Message / Symptom | Cause | Recommended Fix -`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](https://aws.amazon.com/rds/sqlserver/pricing/) 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. +`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 that your instance class supports BYOM, see [Amazon RDS for SQL Server pricing](https://aws.amazon.com/rds/sqlserver/pricing/). In the unbundled On-Demand instance pricing tables, for **License Model** , choose **Bring your own media**. To check from the command line, see [DB instance class support for Microsoft SQL Server](./SQLServer.Concepts.General.InstanceClasses.html). +`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-installation-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. +`InvalidParameterValueException: Duplicate filter value for filter Engine Edition.` | A self-managed license with the same engine edition filter value already exists in this AWS Region. | Use the existing license configuration, or delete it and create a new one. For more information, see [Integrating BYOM DB Instance with AWS License Manager](./sqlserver-byom-license-manager.html).