This module implements an instance of the IBM Cloud Messages for RabbitMQ service.
❗ The module does not support major version upgrades or updates to encryption and backup encryption keys. To upgrade the version, create another instance of IBM Cloud Messages for RabbitMQ with the updated version and follow the steps in Upgrading to a new Major Version in the IBM Cloud Docs.
IBM Cloud Messages for RabbitMQ supports only Key Protect encryption for backups, not Hyper Protect Crypto Services. If you enable key management encryption and no value is passed for 'backup_encryption_key_crn', the value of 'kms_key_crn' is used. And if a HPCS value is set for kms_key_crn
, the database backup encryption uses the default encryption keys. For more information, see Hyper Protect Crypto Services Integration in the IBM Cloud Docs.
module "rabbitmq" {
source = "terraform-ibm-modules/icd-rabbitmq/ibm"
version = "X.X.X" # Replace "X.X.X" with a release version to lock into a specific release
resource_group_id = "xxXXxxXXxXxXXXXxxXxxxXXXXxXXXXX"
instance_name = "my-rabbitmq-instance"
}
You need the following permissions to run this module.
- Account Management
- Messages for RabbitMQ service
Editor
role access
- Messages for RabbitMQ service
Name | Version |
---|---|
terraform | >= 1.3.0 |
ibm | >= 1.70.0, <2.0.0 |
time | >= 0.9.1 |
Name | Source | Version |
---|---|---|
backup_key_crn_parser | terraform-ibm-modules/common-utilities/ibm//modules/crn-parser | 1.1.0 |
cbr_rule | git::https://github.com/terraform-ibm-modules/terraform-ibm-cbr//modules/cbr-rule-module | v1.29.0 |
kms_key_crn_parser | terraform-ibm-modules/common-utilities/ibm//modules/crn-parser | 1.1.0 |
Name | Type |
---|---|
ibm_database.rabbitmq_database | resource |
ibm_iam_authorization_policy.backup_kms_policy | resource |
ibm_iam_authorization_policy.kms_policy | resource |
ibm_resource_key.service_credentials | resource |
ibm_resource_tag.rabbitmq_tag | resource |
time_sleep.wait_for_authorization_policy | resource |
time_sleep.wait_for_backup_kms_authorization_policy | resource |
ibm_database_connection.database_connection | data source |
Name | Description | Type | Default | Required |
---|---|---|---|---|
access_tags | A list of access tags to apply to the rabbitmq instance created by the module, see https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial for more details | list(string) |
[] |
no |
admin_pass | The password for the database administrator. If the admin password is null then the admin user ID cannot be accessed. More users can be specified in a user block. | string |
null |
no |
auto_scaling | Optional rules to allow the database to increase resources in response to usage. Only a single autoscaling block is allowed. Make sure you understand the effects of autoscaling, especially for production environments. See https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-autoscaling in the IBM Cloud Docs. | object({ |
null |
no |
backup_crn | The CRN of a backup resource to restore from. The backup is created by a database deployment with the same service ID. The backup is loaded after provisioning and the new deployment starts up that uses that data. A backup CRN is in the format crn:v1:<…>:backup:. If omitted, the database is provisioned empty. | string |
null |
no |
backup_encryption_key_crn | The CRN of a Key Protect or Hyper Protect Crypto Services encryption key that you want to use for encrypting the disk that holds deployment backups. Applies only if use_ibm_owned_encryption_key is false and use_same_kms_key_for_backups is false. If no value is passed, and use_same_kms_key_for_backups is true, the value of kms_key_crn is used. Alternatively set use_default_backup_encryption_key to true to use the IBM Cloud Databases default encryption. Bare in mind that backups encryption is only available in certain regions. See Bring your own key for backups and Using the HPCS Key for Backup encryption. |
string |
null |
no |
cbr_rules | (Optional, list) List of CBR rules to create | list(object({ |
[] |
no |
cpu_count | Allocated dedicated CPU per member. For shared CPU, set to 0. Learn more | number |
0 |
no |
disk_mb | Allocated disk per member. Learn more | number |
1024 |
no |
endpoints | Endpoints available to the database instance (public, private, public-and-private) | string |
"private" |
no |
instance_name | The name to give the RabbitMQ instance | string |
n/a | yes |
kms_key_crn | The CRN of a Key Protect or Hyper Protect Crypto Services encryption key to encrypt your data. Applies only if use_ibm_owned_encryption_key is false. By default this key is used for both deployment data and backups, but this behaviour can be altered using the use_same_kms_key_for_backups and backup_encryption_key_crn inputs. Bare in mind that backups encryption is only available in certain regions. See Bring your own key for backups and Using the HPCS Key for Backup encryption. |
string |
null |
no |
member_host_flavor | Allocated host flavor per member. Learn more. | string |
null |
no |
members | Allocated number of members. Learn more | number |
3 |
no |
memory_mb | Allocated memory per-member. Learn more | number |
8192 |
no |
plan | The name of the service plan that you choose for your RabbitMQ instance | string |
"standard" |
no |
rabbitmq_version | The version of RabbitMQ to deploy. If no value passed, the current ICD preferred version is used. | string |
null |
no |
region | The region where you want to deploy your instance. | string |
"us-south" |
no |
resource_group_id | The resource group ID where the RabbitMQ instance will be created. | string |
n/a | yes |
service_credential_names | Map of name, role for service credentials that you want to create for the database | map(string) |
{} |
no |
skip_iam_authorization_policy | Set to true to skip the creation of IAM authorization policies that permits all Databases for RabbitMQ instances in the given resource group 'Reader' access to the Key Protect or Hyper Protect Crypto Services key that was provided in the kms_key_crn and backup_encryption_key_crn inputs. This policy is required in order to enable KMS encryption, so only skip creation if there is one already present in your account. No policy is created if use_ibm_owned_encryption_key is true. |
bool |
false |
no |
tags | Optional list of tags to be added to the RabbitMQ instance. | list(any) |
[] |
no |
use_default_backup_encryption_key | When use_ibm_owned_encryption_key is set to false, backups will be encrypted with either the key specified in kms_key_crn , or in backup_encryption_key_crn if a value is passed. If you do not want to use your own key for backups encryption, you can set this to true to use the IBM Cloud Databases default encryption for backups. Alternatively set use_ibm_owned_encryption_key to true to use the default encryption for both backups and deployment data. |
bool |
false |
no |
use_ibm_owned_encryption_key | IBM Cloud Databases will secure your deployment's data at rest automatically with an encryption key that IBM hold. Alternatively, you may select your own Key Management System instance and encryption key (Key Protect or Hyper Protect Crypto Services) by setting this to false. If setting to false, a value must be passed for the kms_key_crn input. |
bool |
true |
no |
use_same_kms_key_for_backups | Set this to false if you wan't to use a different key that you own to encrypt backups. When set to false, a value is required for the backup_encryption_key_crn input. Alternatiely set use_default_backup_encryption_key to true to use the IBM Cloud Databases default encryption. Applies only if use_ibm_owned_encryption_key is false. Bare in mind that backups encryption is only available in certain regions. See Bring your own key for backups and Using the HPCS Key for Backup encryption. |
bool |
true |
no |
users | A list of users that you want to create on the database. Multiple blocks are allowed. The user password must be in the range of 10-32 characters. Be warned that in most case using IAM service credentials (via the var.service_credential_names) is sufficient to control access to the RabbitMQ instance. This blocks creates native RabbitMQ database users, more info on that can be found here https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-user-management | list(object({ |
[] |
no |
Name | Description |
---|---|
adminuser | Database admin user name |
cbr_rule_ids | CBR rule ids created to restrict RabbitMQ |
certificate_base64 | Database connection certificate |
crn | RabbitMQ instance crn |
guid | RabbitMQ instance guid |
hostname | Database connection hostname |
id | RabbitMQ instance id |
port | Database connection port |
service_credentials_json | Service credentials json map |
service_credentials_object | Service credentials object |
version | RabbitMQ instance version |
You can report issues and request features for this module in GitHub issues in the module repo. See Report an issue or request a feature.
To set up your local development environment, see Local development setup in the project documentation.