You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,6 @@ This module implements IBM Event Streams for IBM Cloud with topics, partitions,
12
12
13
13
The Event Streams service supports payload data encryption that uses a root key CRN of a key management service, such as Key Protect or Hyper Protect Crypto Services. You specify the root key CRN with the `kms_key_crn` input. For more information, see [Managing encryption in Event Streams](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-managing_encryption).
14
14
15
-
Before you run the module, configure an authorization policy to allow the Event Streams service to access the key management service instance with the reader role. For more information, see [Using authorizations to grant access between services](https://cloud.ibm.com/docs/account?topic=account-serviceauth).
16
-
17
-
You can't manage the policy in the same Terraform state file as the Event Streams service instance. When you issue a `terraform destroy` command, the instance is only soft deleted and remains as a reclamation resource for a while to support recovery (reclamation). An authorization policy must exist when the instance is hard deleted or reclaimed or else the unregistration of the instance from the root key fails on the backend. If the policy doesn't exist, the only way to unregister the instance, which is a requirement for deletion of the root key, is by opening a support case. For more information, see [Using a customer-managed key](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-managing_encryption#using_encryption).
18
-
19
15
<!-- Below content is automatically populated via pre-commit hook -->
20
16
<!-- BEGIN OVERVIEW HOOK -->
21
17
## Overview
@@ -25,6 +21,7 @@ You can't manage the policy in the same Terraform state file as the Event Stream
25
21
*[Examples](./examples)
26
22
*[Basic example](./examples/basic)
27
23
*[Complete example with topics and schema creation.](./examples/complete)
@@ -134,13 +134,16 @@ You need the following permissions to run this module.
134
134
| <aname="input_create_timeout"></a> [create\_timeout](#input\_create\_timeout)| The timeout value for creating an Event Streams instance. Specify `3h` for an Enterprise plan instance. Add 1 h for each level of non-default throughput. Add 30 min for each level of non-default storage size. |`string`|`"3h"`| no |
135
135
| <aname="input_delete_timeout"></a> [delete\_timeout](#input\_delete\_timeout)| The timeout value for deleting an Event Streams instance. |`string`|`"15m"`| no |
136
136
| <aname="input_es_name"></a> [es\_name](#input\_es\_name)| The name to give the Event Streams instance created by this module. |`string`| n/a | yes |
137
-
| <aname="input_kms_key_crn"></a> [kms\_key\_crn](#input\_kms\_key\_crn)| The root key CRN of the key management service (Key Protect or Hyper Protect Crypto Services) to use to encrypt the payload data. [Learn more](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-managing_encryption) about integrating Hyper Protect Crypto Services with Event Streams. Configure an authorization policy to allow the Event Streams service to access the key management service instance with the reader role ([Learn more](https://cloud.ibm.com/docs/account?topic=account-serviceauth)). You can't manage the policy in the same Terraform state file as the Event Streams service instance ([Learn more](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-managing_encryption#using\_encryption)). |`string`|`null`| no |
137
+
| <aname="input_existing_kms_instance_guid"></a> [existing\_kms\_instance\_guid](#input\_existing\_kms\_instance\_guid)| The GUID of the Hyper Protect Crypto Services or Key Protect instance in which the key specified in var.kms\_key\_crn is coming from. Required only if var.kms\_encryption\_enabled is set to true, var.skip\_iam\_authorization\_policy is set to false, and you pass a value for var.kms\_key\_crn. |`string`|`null`| no |
138
+
| <aname="input_kms_encryption_enabled"></a> [kms\_encryption\_enabled](#input\_kms\_encryption\_enabled)| Set this to true to control the encryption keys used to encrypt the data that you store in IBM Cloud® Databases. If set to false, the data is encrypted by using randomly generated keys. For more info on Key Protect integration, see https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-key-protect. For more info on HPCS integration, see https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hpcs|`bool`|`false`| no |
139
+
| <aname="input_kms_key_crn"></a> [kms\_key\_crn](#input\_kms\_key\_crn)| The root key CRN of the key management service (Key Protect or Hyper Protect Crypto Services) to use to encrypt the payload data. [Learn more](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-managing_encryption) about integrating Hyper Protect Crypto Services with Event Streams. |`string`|`null`| no |
138
140
| <aname="input_plan"></a> [plan](#input\_plan)| The plan for the Event Streams instance. Possible values: `lite`, `standard`, `enterprise-3nodes-2tb`. |`string`|`"standard"`| no |
139
141
| <aname="input_region"></a> [region](#input\_region)| The region where the Event Streams are created. |`string`|`"us-south"`| no |
140
142
| <aname="input_resource_group_id"></a> [resource\_group\_id](#input\_resource\_group\_id)| The resource group ID where the Event Streams instance is created. |`string`| n/a | yes |
141
143
| <aname="input_schemas"></a> [schemas](#input\_schemas)| The list of schema objects. Include the `schema_id` and the `type` and `name` of the schema in the `schema` object. | <pre>list(object(<br/> {<br/> schema_id = string<br/> schema = object({<br/> type = string<br/> name = string<br/> fields = optional(list(object({<br/> name = string<br/> type = string<br/> })))<br/> })<br/> }<br/> ))</pre> |`[]`| no |
142
144
| <aname="input_service_credential_names"></a> [service\_credential\_names](#input\_service\_credential\_names)| The mapping of names and roles for service credentials that you want to create for the Event Notifications streams. |`map(string)`|`{}`| no |
143
145
| <aname="input_service_endpoints"></a> [service\_endpoints](#input\_service\_endpoints)| The type of service endpoints. Possible values: 'public', 'private', 'public-and-private'. |`string`|`"public"`| no |
146
+
| <aname="input_skip_iam_authorization_policy"></a> [skip\_iam\_authorization\_policy](#input\_skip\_iam\_authorization\_policy)| Set to true to skip the creation of an IAM authorization policy that permits all Event Streams database instances in the resource group to read the encryption key from the KMS instance. If set to false, pass in a value for the KMS instance in the existing\_kms\_instance\_guid variable. In addition, no policy is created if var.kms\_encryption\_enabled is set to false. |`bool`|`false`| no |
144
147
| <aname="input_storage_size"></a> [storage\_size](#input\_storage\_size)| Storage size of the Event Streams in GB. Applies only to Enterprise plan instances. Possible values: `2048`, `4096`, `6144`, `8192`, `10240`, `12288`. Storage capacity cannot be reduced after the instance is created. When the `throughput` input variable is set to `300`, storage size starts at 4096. When `throughput` is `450`, storage size starts starts at `6144`. |`number`|`"2048"`| no |
145
148
| <aname="input_tags"></a> [tags](#input\_tags)| The list of tags associated with the Event Steams instance. |`list(string)`|`[]`| no |
146
149
| <aname="input_throughput"></a> [throughput](#input\_throughput)| Throughput capacity in MB per second. Applies only to Enterprise plan instances. Possible values: `150`, `300`, `450`. |`number`|`"150"`| no |
An end-to-end example that uses the [Profile for IBM Cloud Framework for Financial Services](https://github.com/terraform-ibm-modules/terraform-ibm-event-streams/tree/main/modules/fscloud) to deploy an instance of Event Streams.
4
+
5
+
The example uses the IBM Cloud Terraform provider to create the following infrastructure:
6
+
7
+
- A resource group, if one is not passed in.
8
+
- An IAM authorization between all Event Stream instances in the given resource group and the Hyper Protect Crypto Services instance that is passed in.
9
+
- An Event Streams instance that is encrypted with the Hyper Protect Crypto Services root key that is passed in.
10
+
- A sample virtual private cloud (VPC).
11
+
- A context-based restriction (CBR) rule to only allow Event Streams to be accessible from within the VPC.
12
+
13
+
:exclamation:**Important:** In this example, only the Event Streams instance complies with the IBM Cloud Framework for Financial Services. Other parts of the infrastructure do not necessarily comply.
14
+
15
+
## Before you begin
16
+
17
+
- You need a Hyper Protect Crypto Services instance and root key available in the region that you want to deploy your Event Streams instance to.
description="Region to provision all resources created by this example"
10
+
default="us-south"
11
+
}
12
+
13
+
variable"prefix" {
14
+
type=string
15
+
description="Prefix to append to all resources created by this example"
16
+
default="fs-cloud"
17
+
}
18
+
19
+
variable"resource_group" {
20
+
type=string
21
+
description="An existing resource group name to use for this example, if unset a new resource group will be created"
22
+
default=null
23
+
}
24
+
25
+
variable"resource_tags" {
26
+
type=list(string)
27
+
description="List of tags associated with the Event Steams instance"
28
+
default=[]
29
+
}
30
+
31
+
variable"schemas" {
32
+
type=list(object(
33
+
{
34
+
schema_id =string
35
+
schema =object({
36
+
type =string
37
+
name =string
38
+
})
39
+
}
40
+
))
41
+
description="The list of schema object which contains schema id and format of the schema"
42
+
default=[]
43
+
}
44
+
45
+
variable"topics" {
46
+
type=list(object(
47
+
{
48
+
name =string
49
+
partitions =number
50
+
config =object({})
51
+
}
52
+
))
53
+
description="List of topics. For lite plan only one topic is allowed."
54
+
default=[]
55
+
}
56
+
57
+
variable"existing_kms_instance_guid" {
58
+
description="The GUID of the Hyper Protect Crypto service in which the key specified in var.kms_key_crn is coming from"
59
+
type=string
60
+
}
61
+
62
+
variable"kms_key_crn" {
63
+
type=string
64
+
description="The root key CRN of a Hyper Protect Crypto Service (HPCS) that you want to use for disk encryption. See https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hpcs&interface=ui for more information on integrating HPCS with Event Streams instance."
0 commit comments