|
1 | | -# IBM Observability Instances Deployable Architecture |
| 1 | +# IBM Cloud observability instances deployable architecture |
2 | 2 |
|
3 | | -This architecture creates the observability instances on IBM Cloud and supports provisioning the following resources: |
| 3 | +This deployable architecture creates observability instances in IBM Cloud and supports provisioning the following resources: |
4 | 4 |
|
5 | | -- A resource group, if one is not passed in. |
6 | | -- A Log Analysis instance. |
7 | | -- A Cloud Monitoring instance. |
8 | | -- Creates a Cloud Object Storage (COS) instance or supports using an existing one. |
9 | | -- Supports creating KMS root keys in an existing KMS instance or using existing keys if creating new buckets. |
10 | | -- Creates a KMS encrypted COS bucket that is required to store archived logs or using an existing bucket. |
11 | | -- Creates a KMS encrypted COS bucket for setting up Activity Tracker event routing or using an existing bucket. |
12 | | -- Supports configuring the Activity Tracker event routing to the Cloud Object Storage (COS) bucket and to the Log Analysis instance . |
| 5 | +* A resource group, if one is not passed in. |
| 6 | +* An IBM Cloud Log Analysis instance. |
| 7 | +* An IBM Cloud Monitoring instance. |
| 8 | +* An IBM Cloud Object Storage instance, if one does not exist. |
| 9 | +* The root keys in an existing key management service (KMS) if the keys do not exist. These keys are used when Object Storage buckets are created. |
| 10 | +* A KMS-encrypted Object Storage bucket to store archived logs, if one is not passed in. |
| 11 | +* A KMS-encrypted Object Storage bucket for Activity Tracker event routing, if one is not passed in. |
| 12 | +* An Activity Tracker event route to an Object Storage and Log Analysis target. |
13 | 13 |
|
14 | 14 |  |
15 | 15 |
|
16 | | -**NB:** This solution is not intended to be called by one or more other modules since it contains a provider configurations, meaning it is not compatible with the `for_each`, `count`, and `depends_on` arguments. For more information see [Providers Within Modules](https://developer.hashicorp.com/terraform/language/modules/develop/providers) |
| 16 | +**Important:** Because this solution contains a provider configuration and is not compatible with the `for_each`, `count`, and `depends_on` arguments, do not call this solution from one or more other modules. For more information about how resources are associated with provider configurations with multiple modules, see [Providers Within Modules](https://developer.hashicorp.com/terraform/language/modules/develop/providers). |
0 commit comments