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: docs/patterns/single-new-eks-observability-accelerators/single-new-eks-opensource-observability.md
+21-3Lines changed: 21 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ please read the [service documentation](https://docs.aws.amazon.com/eks/latest/u
18
18
- AWS Distro For OpenTelemetry Operator and Collector for Metrics and Traces
19
19
- Logs with [AWS for FluentBit](https://github.com/aws/aws-for-fluent-bit)
20
20
- Installs Grafana Operator to add AWS data sources and create Grafana Dashboards to Amazon Managed Grafana.
21
-
- Installs FluxCD to perform GitOps sync of a Git Repo to EKS Cluster. We will use this later for creating Grafana Dashboards and AWS datasources to Amazon Managed Grafana.
21
+
- Installs FluxCD to perform GitOps sync of a Git Repo to EKS Cluster. We will use this later for creating Grafana Dashboards and AWS datasources to Amazon Managed Grafana. You can also use your own GitRepo to sync your own Grafana resources such as Dashboards, Datasources etc. Please check our One observability module - [GitOps with Amazon Managed Grafana](https://catalog.workshops.aws/observability/en-US/aws-managed-oss/gitops-with-amg) to learn more about this.
22
22
- Installs External Secrets Operator to retrieve and Sync the Grafana API keys.
23
23
- Amazon Managed Grafana Dashboard and data source
24
24
- Alerts and recording rules with AWS Managed Service for Prometheus
6. Install project dependencies by running `npm install` in the main folder of this cloned repository
85
+
6. Install project dependencies by running `npm install` in the main folder of this cloned repository.
86
+
87
+
7. The actual settings for the hosted zone name and expected subzone name are expected to be specified in the CDK context. Generically it is inside the cdk.context.json file of the current directory or in `~/.cdk.json` in your home directory.
88
+
89
+
Example settings: Update the context in `cdk.json` file located in `cdk-eks-blueprints-patterns` directory
7. Once all pre-requisites are set you are ready to deploy the pipeline. Run the following command from the root of this repository to deploy the pipeline stack:
102
+
8. Once all pre-requisites are set you are ready to deploy the pipeline. Run the following command from the root of this repository to deploy the pipeline stack:
0 commit comments