IBM Cloud Databases for Redis module

This module implements an instance of IBM Cloud Databases for Redis.

❗ The module does not support major version upgrades or updates to encryption and backup encryption keys. To upgrade the version, create another instance of Databases for Redis with the updated version and follow the steps in Upgrading to a new Major Version doc in the IBM Cloud Docs.

Overview

• terraform-ibm-icd-redis
• Submodules
  • fscloud
• Examples
  • Advanced example
  • Basic example
  • Financial Services compliant example
• Contributing

terraform-ibm-icd-redis

Usage

IBM Cloud Databases 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 Documents.

provider "ibm" {
  ibmcloud_api_key = "XXXXXXXXXX"
  region           = "us-south"
}

module "redis" {
  source            = "terraform-ibm-modules/icd-redis/ibm"
  version           = "X.X.X" # Replace "X.X.X" with a release version to lock into a specific release
  resource_group_id = "xxXXxxXXxXxXXXXxxXxxxXXXXxXXXXX"
  region            = "us-south"
  instance_name     = "my-redis-instance"
}

Required IAM access policies

You need the following permissions to run this module.

• Account Management
  • Databases for Redis service
    • Editor role access

Requirements

Name	Version
terraform	>= 1.3.0
ibm	>= 1.70.0, <2.0.0
time	>= 0.9.1, < 1.0.0

Modules

Name	Source	Version
backup_key_crn_parser	terraform-ibm-modules/common-utilities/ibm//modules/crn-parser	1.1.0
cbr_rule	terraform-ibm-modules/cbr/ibm//modules/cbr-rule-module	1.29.0
kms_key_crn_parser	terraform-ibm-modules/common-utilities/ibm//modules/crn-parser	1.1.0

Resources

Name	Type
ibm_database.redis_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.access_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

Inputs

Name	Description	Type	Default	Required
access_tags	A list of access tags to apply to the Redis 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/databases-for-redis?topic=databases-for-redis-autoscaling in the IBM Cloud Docs.	object({ disk = object({ capacity_enabled = optional(bool, false) free_space_less_than_percent = optional(number, 10) io_above_percent = optional(number, 90) io_enabled = optional(bool, false) io_over_period = optional(string, "15m") rate_increase_percent = optional(number, 10) rate_limit_mb_per_member = optional(number, 3670016) rate_period_seconds = optional(number, 900) rate_units = optional(string, "mb") }) memory = object({ io_above_percent = optional(number, 90) io_enabled = optional(bool, false) io_over_period = optional(string, "15m") rate_increase_percent = optional(number, 10) rate_limit_mb_per_member = optional(number, 114688) rate_period_seconds = optional(number, 900) rate_units = optional(string, "mb") }) })	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({ description = string account_id = string rule_contexts = list(object({ attributes = optional(list(object({ name = string value = string }))) })) enforcement_mode = string tags = optional(list(object({ name = string value = string }))) }))	[]	no
configuration	Database Configuration. Default values will get picked up if not all the values are passed.	object({ maxmemory = optional(number) maxmemory-policy = optional(string) appendonly = optional(string) maxmemory-samples = optional(number) stop-writes-on-bgsave-error = optional(string) })	null	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	Specify whether you want to enable the public, private, or both service endpoints. Supported values are 'public', 'private', or 'public-and-private'.	string	"private"	no
instance_name	The name to give the Redis 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. Members can be scaled up but not down.	number	2	no
memory_mb	Allocated memory per member. Learn more	number	4096	no
redis_version	Version of the Redis instance to provision. If no value is passed, the current preferred version of IBM Cloud Databases 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 Redis 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 Redis 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 Redis 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. Users block is supported by Redis version >= 6.0. 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 Redis instance. This blocks creates native redis database users, more info on that can be found here https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-user-management&interface=ui	list(object({ name = string password = string # pragma: allowlist secret type = optional(string) role = optional(string) }))	[]	no

Outputs

Name	Description
adminuser	Database admin user name
cbr_rule_ids	CBR rule ids created to restrict Redis
certificate_base64	Database connection certificate
crn	Redis instance crn
guid	Redis instance guid
hostname	Database connection hostname
id	Redis instance id
port	Database connection port
service_credentials_json	Service credentials json map
service_credentials_object	Service credentials object
version	Redis instance version

Contributing

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.