Utah On-Premises Discovery of AWS EKS (Amazon Elastic Kubernetes Service)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2024 08:59 AM
We are using ServiceNow (Utah) On-Premises, in order of discover your AWS services.
The current configuration, is that in the AWS Master Account, we have a Read-Only AWS IAM Role, for the use of the ServiceNow Cloud patterns.
This configuration is working properly,
And we can see the supported AWS Services being discovered,
Except, of the EKS (Amazon Elastic Kubernetes Service) clusters and their components.
While going over the official documentation for Container discovery, for the ServiceNow Utah version:
It seems that kubeapi server URL, is required as Parameter for each EKS cluster that should be discovered by ServiceNow, which don't make any sense, as the discovery should be automatically and manually.
Can someone confirm this behavior?
is there no solution for automatic AWS EKS discovery, via ServiceNow On-Premises based Discovery?
i have found the following article (Auto-Discovery of EKS Clusters😞
https://www.servicenow.com/community/itom-articles/auto-discovery-of-eks-clusters/ta-p/2320753
But it's required another MID deployed in AWS EC2, while we are bound to use On-Premises MID servers only.
- Labels:
-
Discovery
-
Orchestration (ITOM)
