Amazon Elastic Container Service for Kubernetes
Amazon Elastic Kubernetes Service (Amazon EKS) enables easy deployment, management, and scaling of containerized applications by using Kubernetes on AWS.
The following image describes an example of accessing your applications through Amazon Elastic Container Service for Kubernetes:
Identification
Triggers
| Pattern | Trigger Node | Attribute | Condition | Argument |
|---|---|---|---|---|
| InferClusters | DiscoveredCloudAPIResultList | discovery_method | = | 'AWS.EKS.ListClusters' |
Endpoints in the REST APIs
| REST APIs | Comments |
|---|---|
| AWS.EKS.DescribeCluster | N/A |
API Discovery of EKS
An Amazon EKS cluster can also be discovered through API Provider credentials. This type of scan provides a more extended model of Kubernetes Clusters, meaning more nodes, attributes, and links. For more information about Kubernetes clusters discovered through API, see Kubernetes.
To use this discovery method, you must configure API access to the Kubernetes cluster. For more information about the configuration setup, see the following Amazon official information resources:
-
Allowing users to access your cluster
-
Creating or updating a kubeconfig file for an Amazon EKS cluster
-
Setting up Kubernetes API Access Using Service Account
-
Troubleshooting
After you have configured and connection-enabled kubectl, it is possible to obtain a token from a cluster. To obtain a token for the API Provider, see
Discovering Kubernetes clusters
in the BMC Discovery documentation. BMC Discovery retrieves the required resources by executing API queries.
Important
Ensure that read (get/list) permissions for the required resources are granted to your Service Account.
Attributes
The pattern models the nodes with attributes and values. The following image gives an example of the BMC Helix Discovery scanned results view for Cluster:
Comments
Log in or register to comment.