AWS guidance documentation change
Summary
Restructured documentation by moving prerequisites, deployment, and post-deployment details to separate pages. Added new sections for labels/tags exploration, data on EKS, and cost allocation guides. Updated dashboard metrics to include GPU cost tracking and improved navigation links.
Security assessment
The changes focus on documentation organization, cost allocation features, and dashboard functionality improvements. No security vulnerabilities, access controls, or encryption mechanisms are mentioned. The added content relates to cost tracking granularity and operational guidance rather than security controls.
Diff
diff --git a/guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard.md b/guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard.md index c9dbd1b35..2dcdac4e9 100644 --- a//guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard.md +++ b//guidance/latest/cloud-intelligence-dashboards/scad-containers-dashboard.md @@ -3 +3 @@ -IntroductionDemo DashboardCID’s Containers Cost Allocation Dashboards ComparisonAuthors +Demo DashboardCID’s Containers Cost Allocation Dashboards ComparisonLearn moreAuthors @@ -7,2 +6,0 @@ IntroductionDemo DashboardCID’s Containers Cost Allocation Dashboards Comparis -## Introduction - @@ -15 +13 @@ The dashboard has three tabs: - * KPI visuals per cost metric (CPU cost, RAM cost, shared cost, total cost) + * KPI visuals per cost metric (CPU cost, GPU cost, RAM cost, shared cost, total cost) @@ -25 +23 @@ The dashboard has three tabs: - * Cluster Breakdown + * Cluster Breakdown: @@ -28,0 +27,8 @@ The dashboard has three tabs: + * Labels/Tags Explorer: + + * Drill down into your pods/tasks split cost by dimensions that are customized using K8s pod labels/AWS ECS tasks tags, and combine them with tagged AWS resources costs to implement Total Cost of Ownership (TCO) + + * Data on EKS: + + * Allocate costs to Spark and Flink applications running on EKS (directly or using EMR on EKS), with ability to combine EMR on EKS service cost and split cost + @@ -34 +40 @@ The dashboard has three tabs: -Get more familiar with Dashboard using the live, interactive demo dashboard following this [link](https://cid.workshops.aws.dev/demo/?dashboard=scad-containers-cost-allocation) +Get more familiar with Dashboard using the live, interactive demo dashboard following [this link](https://cid.workshops.aws.dev/demo/?dashboard=scad-containers-cost-allocation) @@ -53,83 +59 @@ Please visit review the [Containers Cost Allocation dashboards comparison in the -### Prerequisites - - 1. Deploy one or more of the foundational dashboards: [CUDOS, Cost Intelligence, or KPI Dashboard.](./cudos-cid-kpi.html) - - 2. Enable Split Cost Allocation Data: - - 1. In Cost Management Preferences: - - - -You can enable SCAD for ECS, SCAD for EKS or both. If you enable SCAD for EKS, selecting "Resource requests" will include only resource requests data, without actual usage. To have actual usage data for your pods in CUR, either select the "Amazon Managed Service for Promentheus" option and follow [this guide](https://docs.aws.amazon.com/cur/latest/userguide/split-cost-allocation-data-resource-amp.html), or select the "Amazon CloudWatch Container Insights" option and follow [this guide](https://docs.aws.amazon.com/cur/latest/userguide/split-cost-allocation-data-cloudwatch.html) - - 2. In your CUR: - -Legacy CUR - - - - -CUR 2.0 - - - - - - - - 1. Make sure that the following AWS-generated cost allocation tags are active: - -Amazon EKS - - - - -Amazon ECS - - - - -AWS Batch - - - - -Please notice that these tags are present only once you enabled SCAD for the relevant service (EKS/ECS), and that it takes some time for them to be present after enabling SCAD. The tags may not be present if you don’t use the respective service. - - 2. Wait till the SCAD data updated in Athena: - - - - -After enabling Split Cost Allocation Data for EKS or ECS, and activating the AWS-generated cost allocation tags, allow at least 24h (can get up to 48h) for new columns and data to be reflected in Athena CUR table. - -Also, please note that CUR Backfill isn’t supported for SCAD. Even if you request the CUR Backfill from AWS Support, the SCAD fields won’t be populated. Data will only be populated for the current month, as stated in the [SCAD documentation](https://docs.aws.amazon.com/cur/latest/userguide/enabling-split-cost-allocation-data.html): - -_Once activated, split cost allocation data automatically scans for tasks and containers. It ingests the telemetry usage data for your container workloads and prepares the granular cost data for the current month._ - -To validate that the new Split Cost Allocation Data columns exist in CUR: - -Legacy CUR - - - 1. Open Athena console and change to CUR database - - 2. Expand CUR table and filter it as in the below screenshots to view the columns: Split line item columns (relevant for EKS and ECS): - - - -EKS cost allocation tags (relevant only if you’re using EKS): - - - -ECS cost allocation tags (relevant only if you’re using ECS):  - -AWS Batch cost allocation tags (relevant only if you’re using AWS Batch on ECS): - - - - - - -CUR 2.0 - + * [Prerequisites](./scad-containers-dashboard-prerequisites.html) @@ -137,118 +61 @@ CUR 2.0 -Run the following Athena queryin against the CUR 2.0 table: - -EKS cost allocation tags columns (relevant only if you’re using EKS): - - - SELECT DISTINCT "key" - FROM "<table_name>" - CROSS JOIN UNNEST(MAP_KEYS("resource_tags")) AS "t"("key") - WHERE "key" LIKE 'aws_eks%' - -Expected result: - - - +---+-----------------------+ - | # | key | - +---+-----------------------+ - | 1 | aws_eks_node | - | 2 | aws_eks_deployment | - | 3 | aws_eks_namespace | - | 4 | aws_eks_cluster_name | - | 5 | aws_eks_workload_name | - | 6 | aws_eks_workload_type | - +---+-----------------------+ - -ECS cost allocation tags columns (relevant only if you’re using ECS): - - - SELECT DISTINCT "key" - FROM "<table_name>" - CROSS JOIN UNNEST(MAP_KEYS("resource_tags")) AS "t"("key") - WHERE "key" LIKE 'aws_ecs%' - -Expected result: - - - +---+----------------------+ - | # | key | - +---+----------------------+ - | 1 | aws_ecs_cluster_name | - | 2 | aws_ecs_service_name | - +---+----------------------+ - -AWS Batch cost allocation tags columns (relevant only if you’re using AWS Batch on ECS): - - - SELECT DISTINCT "key" - FROM "<table_name>" - CROSS JOIN UNNEST(MAP_KEYS("resource_tags")) AS "t"("key") - WHERE "key" LIKE 'aws_batch%' - -Expected result: - - - +---+-------------------------------+ - | # | key | - +---+-------------------------------+ - | 1 | aws_batch_job_definition | - | 2 | aws_batch_job_queue | - | 3 | aws_batch_compute_environment | - +---+-------------------------------+ - -Only once you see all these columns (respective for the service you use), proceed with the dashboard installation below. - -### Deployment - -CloudFormation - - -###### Note - -**Prerequisite** : To install this dashboard using CloudFormation, you need to install Foundational Dashboards CFN with version v4.0.0 or above as described [here](./deployment-in-global-regions.html#deployment-in-global-region-deploy-dashboard) - - 1. Log in to to your **Data Collection** Account. - - 2. Click the Launch Stack button below to open the **pre-populated stack template** in your CloudFormation. - -[  ](https://console.aws.amazon.com/cloudformation/home#/stacks/create/review?templateURL=https://aws-managed-cost-intelligence-dashboards.s3.amazonaws.com/cfn/cid-plugin.yml&stackName=SCAD-Containers-Dashboard¶m_DashboardId=scad-containers-cost-allocation) - - 3. You can change **Stack name** for your template if you wish. - - 4. Leave **Parameters** values as it is. - - 5. Review the configuration and click **Create stack**. - - 6. You will see the stack will start in **CREATE_IN_PROGRESS**. Once complete, the stack will show **CREATE_COMPLETE** -