RDS for Db2 licensing options
Amazon RDS for Db2 has one licensing option: Bring Your Own License (BYOL).
Bring Your Own License
In the BYOL model, you use your existing Db2 database licenses to deploy databases on Amazon RDS. Verify that you have the appropriate Db2 database license for the DB instance class and Db2 database edition that you want to run. You must also follow IBM policies for licensing IBM database software in the cloud computing environment.
Note
Multi-AZ DB instances are cold standbys because the Db2 database is installed but
not running. Standbys aren't readable, running, or serving requests. For more
information, see IBM Db2 licensing information
In this model, you continue to use your active IBM support account, and you contact IBM directly for Db2 database service requests. If you have an AWS Support account with case support, you can contact AWS Support for Amazon RDS issues. Amazon Web Services and IBM have a multi-vendor support process for cases that require assistance from both organizations.
Amazon RDS supports the BYOL model for Db2 Standard Edition and Db2 Advanced Edition.
IBM IDs
In the BYOL model, you need your IBM Customer ID and your IBM Site ID to create, modify, or restore RDS for Db2 DB instances. You must create a custom parameter group with your IBM Customer ID and your IBM Site ID before you create an RDS for Db2 DB instance. For more information, see Adding IBM IDs to a parameter group. You can run multiple RDS for Db2 DB instances with different IBM Customer IDs and IBM Site IDs in the same AWS account or AWS Region.
Important
If you're an existing IBM Db2 customer, you can find your IBM Customer ID and your
IBM Site ID on your Proof of Entitlement certificate from IBM. For
more information, see the instructions about how
to view your IBM Customer ID and IBM Site ID
If you're a new IBM Db2 customer, you must first purchase a Db2 software license
from IBM
If we can't verify your license by your IBM Customer ID and your IBM Site ID, we might terminate any DB instances running with these unverified licenses.
Adding IBM IDs to a parameter group
Because you can't modify default parameter groups, you must create a custom parameter group and then modify it to include the values for your IBM Customer ID and your IBM Site ID. For information about parameter groups, see Working with DB parameter groups in a DB instance.
Important
You must create a custom parameter group with your IBM Customer ID and your IBM Site ID before you create an RDS for Db2 DB instance.
Use the parameter settings in the following table.
Parameter | Value |
---|---|
rds.ibm_customer_id |
<your IBM Customer ID> |
rds.ibm_site_id |
<your IBM Site ID> |
ApplyMethod |
immediate , pending-reboot |
These parameters are dynamic, which means that any changes to them take effect
immediately and that you don't need to reboot the DB instance. If you don't want the
changes to take effect immediately, you can set ApplyMethod
to
pending-reboot
and schedule these changes to be made during a
maintenance window.
You can create and modify a custom parameter group by using the AWS Management Console, the AWS CLI, or the Amazon RDS API.
To add your IBM Customer ID and your IBM Site ID to a parameter group
-
Create a new DB parameter group. For more information about creating a DB parameter group, see Creating a DB parameter group.
-
Modify the parameter group that you created. For more information about modifying a parameter group, see Modifying parameters in a DB parameter group.
To add your IBM Customer ID and your IBM Site ID to a parameter group
-
Create a custom parameter group by running the create-db-parameter-group command.
Include the following required options:
-
--db-parameter-group-name
– A name for the parameter group that you are creating. -
--db-parameter-group-family
– The Db2 engine edition and major version. Valid values:db2-se-11.5
,db2-ae-11.5
. -
--description
– A description for this parameter group.
For more information about creating a DB parameter group, see Creating a DB parameter group.
-
-
Modify the parameters in the custom parameter group that you created by running the modify-db-parameter-group command.
Include the following required options:
-
--db-parameter-group-name
– The name of the parameter group that you created. -
--parameters
– An array of parameter names, values, and the application methods for the parameter update.
For more information about modifying a parameter group, see Modifying parameters in a DB parameter group.
-
To add your IBM Customer ID and your IBM Site ID to a parameter group
-
Create a custom DB parameter group by using the Amazon RDS API CreateDBParameterGroup operation.
Include the following required parameters:
-
DBParameterGroupName
-
DBParameterGroupFamily
-
Description
For more information about creating a DB parameter group, see Creating a DB parameter group.
-
-
Modify the parameters in the custom parameter group that you created by using the RDS API ModifyDBParameterGroup operation.
Include the following required parameters:
-
DBParameterGroupName
-
Parameters
For more information about modifying a parameter group, see Modifying parameters in a DB parameter group.
-
Now you are ready to create a DB instance and attach the custom parameter group to the DB instance. For more information, see Creating an Amazon RDS DB instance and Associating a DB parameter group with a DB instance.
Integrating with AWS License Manager
To aid in monitoring RDS for Db2 license usage in the BYOL model, AWS License Manager
The following table shows the product information filters for RDS for Db2.
Filter |
Name |
Description |
---|---|---|
Engine Edition |
|
Db2 Standard Edition |
|
Db2 Advanced Edition |
To track license usage of your RDS for Db2 DB instances, you can create a self-managed license. In this case, RDS for Db2 resources that match the product information filter are automatically associated with the self-managed license. Discovery of RDS for Db2 DB instances can take up to 24 hours.
To create a self-managed license to track the license usage of your RDS for Db2 DB instances
-
Create a self-managed license.
For instructions, see Create a self-managed license in the AWS License Manager User Guide.
Add a rule for an RDS Product Information Filter in the Product Information panel.
For more information, see ProductInformation in the AWS License Manager API Reference.
To create a self-managed license by using the AWS CLI, call the create-license-configuration command. Use the
--cli-input-json
or --cli-input-yaml
parameters to pass the parameters to the command.
Example
The following code creates a self-managed license for Db2 Standard Edition.
aws license-manager create-license-configuration --cli-input-json file://rds-db2-se.json
The following is the sample rds-db2-se.json
file
used in the example.
{ "Name": "rds-db2-se", "Description": "RDS Db2 Standard Edition", "LicenseCountingType": "vCPU", "LicenseCountHardLimit": false, "ProductInformationList": [ { "ResourceType": "RDS", "ProductInformationFilterList": [ { "ProductInformationFilterName": "Engine Edition", "ProductInformationFilterValue": ["db2-se"], "ProductInformationFilterComparator": "EQUALS" } ] } ] }
For more information about product information, see Automated discovery of resource inventory in the AWS License Manager User Guide.
For more information about the --cli-input
parameter, see
Generating AWS CLI skeleton and input parameters from a JSON or YAML
input file in the AWS CLI User Guide.