Examkin

Question

Difficulty: Very hardCloudWatch Dashboards and Container Insights

A SysOps Administrator is designing a centralized monitoring solution for an application distributed across two AWS accounts. Account A has Amazon Elastic Container Service (Amazon ECS) clusters running on AWS Fargate in the us-east-1 Region. Account B has ECS clusters running on AWS Fargate in the us-west-2 Region. The Administrator needs to create a single, consolidated Amazon CloudWatch dashboard in Account C (us-east-1) that displays container-level CPU and memory utilization metrics from both Account A and Account B clusters. The solution must minimize custom script development and operational overhead.

Which combination of actions should the SysOps Administrator take to meet these requirements? (Select TWO.)

  1. Enable CloudWatch Container Insights on the ECS clusters in Account A and Account B by modifying the cluster settings to enable the containerInsights setting.Answer
  2. Configure CloudWatch cross-account observability by establishing a central sink in Account C and creating links to the sink in Account A and Account B, then select the appropriate source account and region when creating the dashboard widgets in Account C.Answer
  3. C
    Deploy the Amazon CloudWatch agent as an ECS daemon service on the ECS clusters in Account A and Account B to collect task-level performance metrics.
  4. D
    Create a cross-account IAM role in Account A and Account B that grants Account C permission to assume the role, and configure the dashboard in Account C to perform an STS assume-role call when rendering widgets.
  5. E
    Create a subscription filter on the /aws/ecs/containerinsights log groups in Account A and Account B to stream metric logs to an Amazon Kinesis Data Firehose destination in Account C.

Answer

To centralize container-level monitoring on ECS Fargate across multiple accounts and regions, the Administrator must modify the cluster settings to enable the containerInsights setting on the ECS clusters, and establish CloudWatch cross-account observability by configuring a central sink in the monitoring account and linking the source accounts to it.
The correct actions are enabling the containerInsights setting on the ECS clusters to natively gather Fargate performance metrics, and establishing CloudWatch cross-account observability with sinks and links to share the metrics with the centralized dashboard.

Step-by-Step Solution

1
Enable Container Insights on the ECS clusters in Account A and Account B.
Performance metrics are natively collected and published to the ECS/ContainerInsights namespace in the respective accounts and regions.
ECS Fargate tasks do not support running the CloudWatch agent as a daemon service, but Container Insights natively reports metrics directly without agent deployment.
2
Configure a CloudWatch cross-account observability sink in Account C and links in Account A and Account B.
The source accounts (Account A and Account B) are authorized to share metric data with the monitoring account (Account C) without explicit STS assume-role requests at the dashboard widget layer.
This establishes the necessary cross-account trust boundaries using the modern, native observability configuration.
3
Construct the dashboard in Account C and add metric widgets querying the cross-account data sources.
The dashboard displays centralized container metrics from us-east-1 and us-west-2 directly within a single screen.
Dashboard widgets support cross-account and cross-region selections once native links are established.

Key Concept

Centralized cross-account and cross-region CloudWatch dashboarding using Container Insights for ECS Fargate.
Estimated Time:3m 0s
Rate this question

Topics

CloudWatch Dashboards and Container Insights

More questions from this topic