Modifying a CEV for RDS Custom for SQL Server (original) (raw)

You can modify a CEV using the AWS Management Console or the AWS CLI. You can modify the CEV description or its availability status. Your CEV has one of the following status values:

You can change the CEV status from available to inactive or frominactive to available. You might change the status toINACTIVE to prevent the accidental use of a CEV or to make a discontinued CEV eligible for use again.

To modify a CEV
  1. Sign in to the AWS Management Console and open the Amazon RDS console athttps://console.aws.amazon.com/rds/.
  2. In the navigation pane, choose Custom engine versions.
  3. Choose a CEV whose description or status you want to modify.
  4. For Actions, chooseModify.
  5. Make any of the following changes:
    • For CEV status settings, choose a new availability status.
    • For Version description, enter a new description.
  6. Choose Modify CEV.
    If the CEV is in use, the console displays You can't modify the CEV status. Fix the problems, then try again.

The Custom engine versions page appears.

To modify a CEV by using the AWS CLI, run the modify-custom-db-engine-version command. You can find CEVs to modify by running the describe-db-engine-versions command.

The following options are required:

The following example changes a CEV named 15.00.4249.2.my_cevtest from its current status toinactive.

For Linux, macOS, or Unix:

aws rds modify-custom-db-engine-version \
    --engine custom-sqlserver-ee \ 
    --engine-version 15.00.4249.2.my_cevtest \
    --status inactive

For Windows:

aws rds modify-custom-db-engine-version ^
    --engine custom-sqlserver-ee ^
    --engine-version 15.00.4249.2.my_cevtest ^
    --status inactive

To modify an RDS Custom for SQL Server DB instance to use a new CEV, see Modifying an RDS Custom for SQL Server DB instance to use a new CEV.

Creating a CEV for RDS Custom for SQL Server

Modifying an RDS Custom for SQL Server DB instance to use a new CEV

Did this page help you? - Yes

Thanks for letting us know we're doing a good job!

If you've got a moment, please tell us what we did right so we can do more of it.

Did this page help you? - No

Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.