AWS guidance documentation change
Summary
Corrected spelling errors: changed 'wether' to 'whether' in multiple Spark/Flink application contexts, 'We’l' to 'We’ll', and 'fliter' to 'filter'. No functional changes.
Security assessment
The changes are purely grammatical/spelling corrections without any security implications. No security vulnerabilities, configurations, or features are mentioned or modified.
Diff
diff --git a/guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard-data-on-eks.md b/guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard-data-on-eks.md index 5bb95008e..e62c78637 100644 --- a//guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard-data-on-eks.md +++ b//guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard-data-on-eks.md @@ -29 +29 @@ Here’s a breakdown of the labels cost allocation tags you need to activate, fo - * If you’re running Spark applications (regardless of wether they’re running directly on EKS or on EMR on EKS, and regardless of how you submit them), activate the following labels: `spark-app-selector`, `spark-app-name`, `spark-exec-id`, `spark-exec-resourceprofile-id`, `spark-role`, `spark-version` + * If you’re running Spark applications (regardless of whether they’re running directly on EKS or on EMR on EKS, and regardless of how you submit them), activate the following labels: `spark-app-selector`, `spark-app-name`, `spark-exec-id`, `spark-exec-resourceprofile-id`, `spark-role`, `spark-version` @@ -31 +31 @@ Here’s a breakdown of the labels cost allocation tags you need to activate, fo - * If you’re running Spark applications (regardless of wether they’re running directly on EKS or on EMR on EKS) and are submitting them using Spark Operator, activate all the cost allocation tags from the first bullet, and also: `sparkoperator.k8s.io/launched-by-spark-operator`, `sparkoperator.k8s.io/submission-id` + * If you’re running Spark applications (regardless of whether they’re running directly on EKS or on EMR on EKS) and are submitting them using Spark Operator, activate all the cost allocation tags from the first bullet, and also: `sparkoperator.k8s.io/launched-by-spark-operator`, `sparkoperator.k8s.io/submission-id` @@ -33 +33 @@ Here’s a breakdown of the labels cost allocation tags you need to activate, fo - * If you’re running Spark applications (regardless of wether they’re running directly on EKS or on EMR on EKS) and are submitting them using Apache Livy, activate all the cost allocation tags from the first bullet, and also: `created-by`, `spark-app-tag` + * If you’re running Spark applications (regardless of whether they’re running directly on EKS or on EMR on EKS) and are submitting them using Apache Livy, activate all the cost allocation tags from the first bullet, and also: `created-by`, `spark-app-tag` @@ -35 +35 @@ Here’s a breakdown of the labels cost allocation tags you need to activate, fo - * If you’re running Spark applications (regardless of wether they’re running directly on EKS or on EMR on EKS) and are submitting them using Spark Submit, activate all the cost allocation tags from the first bullet + * If you’re running Spark applications (regardless of whether they’re running directly on EKS or on EMR on EKS) and are submitting them using Spark Submit, activate all the cost allocation tags from the first bullet @@ -39 +39 @@ Here’s a breakdown of the labels cost allocation tags you need to activate, fo - * If you’re running Flink applications (regardless of wether they’re running directly on EKS or on EMR on EKS, and regardless of how you submit them), activate the following labels: `type`, `app`, `component` + * If you’re running Flink applications (regardless of whether they’re running directly on EKS or on EMR on EKS, and regardless of how you submit them), activate the following labels: `type`, `app`, `component` @@ -60 +60 @@ We’ll click on the Virtual cluster ID, which will redirect us to the list of E -Since new data in CUR isn’t updated in real-time, we’ll choose a job id that was running around 2 days before the time this guide was written. We’l use job id `000000036gr7qbcelvv`. Copy the job id, then navigate to the "Data on EKS" sheet on the SCAD dashboard, and in it, to the "Data on EKS Workloads Explorer - Interactive Spark/Flink Jobs Visuals" section. This section provides a set of interactive visuals to easily drill down into your Spark and Flink applications costs: +Since new data in CUR isn’t updated in real-time, we’ll choose a job id that was running around 2 days before the time this guide was written. We’ll use job id `000000036gr7qbcelvv`. Copy the job id, then navigate to the "Data on EKS" sheet on the SCAD dashboard, and in it, to the "Data on EKS Workloads Explorer - Interactive Spark/Flink Jobs Visuals" section. This section provides a set of interactive visuals to easily drill down into your Spark and Flink applications costs: @@ -66 +66 @@ Since new data in CUR isn’t updated in real-time, we’ll choose a job id that -Open the "EMR on EKS Job ID" filter control above the stacked-bar chart, and paste the job id you copied into it, to fliter the visuals based on this job id. Once done, all visuals on the sheet will be filtered. The 2 visuals in the "Data on EKS Workloads Explorer - Interactive Spark/Flink Jobs Visuals" section (the stacked-bar chart and pivot table) are grouped by cluster name by default, so they’ll still show the cluster name, but will only show the cost of job id `000000036gr7qbcelvv`. You can then group by another dimension which may be interesting to you, but in this example, we’ll scroll down to the "Data on EKS Breakdown" section in the same sheet, to view more details on the job in question: +Open the "EMR on EKS Job ID" filter control above the stacked-bar chart, and paste the job id you copied into it, to filter the visuals based on this job id. Once done, all visuals on the sheet will be filtered. The 2 visuals in the "Data on EKS Workloads Explorer - Interactive Spark/Flink Jobs Visuals" section (the stacked-bar chart and pivot table) are grouped by cluster name by default, so they’ll still show the cluster name, but will only show the cost of job id `000000036gr7qbcelvv`. You can then group by another dimension which may be interesting to you, but in this example, we’ll scroll down to the "Data on EKS Breakdown" section in the same sheet, to view more details on the job in question: