AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company runs its applications on both Amazon Elastic Kubernetes Service (Amazon EKS) clusters and on-premises Kubernetes clusters. The company wants to view all clusters and workloads from a central location.
Which solution will meet these requirements with the LEAST operational overhead?
Other
Community
UAnonymous
A
Use Amazon CloudWatch Container Insights to collect and group the cluster information.
B
Use Amazon EKS Connector to register and connect all Kubernetes clusters.
C
Use AWS Systems Manager to collect and view the cluster information.
D
Use Amazon EKS Anywhere as the primary cluster to view the other clusters with native Kubernetes commands.
Explanation:
Explanation
Correct Answer: B - Use Amazon EKS Connector to register and connect all Kubernetes clusters.
Why this is correct:
- Amazon EKS Connector is specifically designed to connect external Kubernetes clusters (including on-premises clusters) to AWS services, allowing you to view and manage them from the AWS Management Console.
- Centralized visibility: EKS Connector enables you to see all your Kubernetes clusters (both EKS and on-premises) in a single location - the AWS EKS console.
- Least operational overhead: This solution requires minimal setup and maintenance compared to other options. You simply install the EKS Connector agent on your external clusters and they appear in the AWS console.
- Native integration: It provides a seamless experience for viewing workloads, nodes, and other cluster resources across all connected clusters.
Why other options are incorrect:
A. Amazon CloudWatch Container Insights: While Container Insights can collect metrics and logs from Kubernetes clusters, it's primarily for monitoring and observability, not for centralized cluster management and workload viewing. It doesn't provide the same level of cluster management capabilities as EKS Connector.
C. AWS Systems Manager: Systems Manager can manage EC2 instances and on-premises servers, but it's not designed for Kubernetes cluster management. It doesn't provide native Kubernetes workload viewing capabilities.
D. Amazon EKS Anywhere: EKS Anywhere is for running EKS clusters on your own infrastructure, not for viewing other clusters. It would require significant operational overhead to set up and maintain as a "primary cluster" and wouldn't provide the centralized viewing capabilities needed.
Key AWS Services Mentioned:
- Amazon EKS Connector: Allows you to register external Kubernetes clusters with AWS and view them in the EKS console
- Amazon CloudWatch Container Insights: Provides monitoring for containerized applications
- AWS Systems Manager: Configuration management and operational insights for AWS and on-premises resources
- Amazon EKS Anywhere: Run EKS clusters on your own infrastructure
Best Practice: For centralized management of hybrid Kubernetes environments (AWS EKS + on-premises), EKS Connector is the recommended AWS solution with the least operational overhead.
Comments
Loading comments...