Skip to content

Commit 146a57c

Browse files
authored
fix: Clarify DA variables and README (#178)
1 parent b787a78 commit 146a57c

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

solutions/secure/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
This architecture creates an Elasticsearch instance on IBM Cloud and supports provisioning of the following resources:
44

55
- A resource group, if one is not passed in.
6+
- A KMS root key, if one is not passed in.
67
- An Elasticsearch instance on IBM Cloud with KMS encryption.
78
- Autoscaling rules for the Elasticsearch instance, if provided.
89

solutions/secure/variables.tf

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -116,12 +116,12 @@ variable "kms_endpoint_type" {
116116

117117
variable "existing_kms_key_crn" {
118118
type = string
119-
description = "The existing root key CRN of the Hyper Protect Crypto Service (HPCS) to use for disk encryption."
119+
description = "The CRN of an existing Hyper Protect or Key Protect root key to use for disk encryption. A new KMS root will be created if omitted."
120120
default = null
121121
}
122122

123123
variable "existing_kms_instance_guid" {
124-
description = "The GUID of the Hyper Protect Crypto Services instance. The value is used only to create an authorization policy."
124+
description = "The GUID of an existing Hyper Protect or Key Protect instance in the same account as the Elasticsearch database instance. Always used to create an authorization policy and if 'existing_kms_key_crn' is not specified also used to create a KMS root key"
125125
type = string
126126
default = null
127127
}

0 commit comments

Comments
 (0)