storytold/terraform-aws-observability-accelerator
2
0
Fork 0
mirror of https://github.com/storytold/terraform-aws-observability-accelerator.git synced 2026-10-09 00:09:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Correcting the formatting issues in the markdown (#159)

Browse Source
This commit is contained in:
Vijay Chintalapati
2023-05-18 05:40:36 -07:00
committed by GitHub
parent 40bcc06563
commit 0cc8dc52d9
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/eks/multicluster.md
+6 -1
View File
@@ -6,7 +6,8 @@ This example shows how to use the [AWS Observability Accelerator](https://github
#### 1. EKS clusters #### 1. EKS clusters
Using the example [eks-cluster-with-vpc](../../examples/eks-cluster-with-vpc/), create two EKS clusters with the names: Using the example [eks-cluster-with-vpc](https://aws-observability.github.io/terraform-aws-observability-accelerator/helpers/new-eks-cluster/), create two EKS clusters with the names:
1. `eks-cluster-1` 1. `eks-cluster-1`
2. `eks-cluster-2` 2. `eks-cluster-2`
@@ -15,6 +16,7 @@ Using the example [eks-cluster-with-vpc](../../examples/eks-cluster-with-vpc/),
We recommend that you create a new AMP workspace. To do that you can run the following command. We recommend that you create a new AMP workspace. To do that you can run the following command.
Ensure you have the following necessary IAM permissions Ensure you have the following necessary IAM permissions
* `aps.CreateWorkspace` * `aps.CreateWorkspace`
```sh ```sh
@@ -41,6 +43,7 @@ As a security best practice, we will provide to Terraform a short lived API key
run the `apply` or `destroy` command. run the `apply` or `destroy` command.
Ensure you have the following necessary IAM permissions Ensure you have the following necessary IAM permissions
* `grafana.CreateWorkspaceApiKey` * `grafana.CreateWorkspaceApiKey`
* `grafana.DeleteWorkspaceApiKey` * `grafana.DeleteWorkspaceApiKey`
@@ -61,10 +64,12 @@ terraform init
#### 2. Deploy #### 2. Deploy
Verify by looking at the file `variables.tf` that there are two EKS clusters targeted for deployment by the names/ids: Verify by looking at the file `variables.tf` that there are two EKS clusters targeted for deployment by the names/ids:
1. `eks-cluster-1` 1. `eks-cluster-1`
2. `eks-cluster-2` 2. `eks-cluster-2`
The difference in deployment between these clusters is that Terraform, when setting up the EKS cluster behind variable `eks_cluster_1_id` for observability, also sets up: The difference in deployment between these clusters is that Terraform, when setting up the EKS cluster behind variable `eks_cluster_1_id` for observability, also sets up:
* Dashboard folder and files in `AMG` * Dashboard folder and files in `AMG`
* Prometheus and Java, alerting and recording rules in `AMP` * Prometheus and Java, alerting and recording rules in `AMP`