Idea ID: 1764591

uCMDB Discovery: Amazon Web Service (Gaps in Discovery detail in AWS)

Status : Delivered
over 2 years ago

Hi Team,

As UCMDB have capability to discover Cloud(Amazon) using “AWS by Web Service”, but we are not getting enough configuration detail about the environment. Below are list of GAP we see as of now.


Pretty much every component in AWS can be tagged, where there is a tag; we should retrieve it for all components not just Compute.



  • VPC Tag (key=Name and value = ServerName)     
  • Tenancy              
  • Subnet Tag (key=Name and value = ServerName)              
  • IGW ID 
  • IGW Tag (key=Name and value = ServerName)    
  • NAT Gateway ID              
  • NAT GW Tag (key=Name and value = ServerName)           
  • NAT Elastic IP Address    
  • NAT Private IP Address  
  • Route Table ID  
  • Route Table Tag (key=Name and value = ServerName)     
  • Main Route Table           
  • Routes (Destination & Target)    
  • Network ACL     


  • Termination Protection 
  • Monitoring         
  • Private FQDN     Differentiate between private/public FQDN)
  • Elastic IP             
  • Interface # & Subnet ID 
  • CPU
  • Memory

Load Balancer

  • LB Protocol         (HTTPS/HTTP etc..)
  • LB Port 
  • Instance Protocol            
  • Instance Port (target group)         (HTTPS/HTTP etc..)
  • Elastic IP

Security Group

ConfigurationDocument CIT should be exportable, one of attribute DocumentContent is type Byte and can not be used in Report/View.

  • The AWS tags idea has been implemented in CMS 2019.05 product release while the additional attributes on AWS content was released with CP2019.08. Check out the release notes for CMS 2019.05 and CP2019.08 for details. Thanks to all of our contributors for helping us continue to improve our products!

  • Added one more point in gap list : "Security Group"

  • Great news, this idea has been accepted on our product roadmap. Subscribe to receive updates. (This is not a formal commitment, and subject to change)

    We expect to release the ability to capture AWS tags in their native form as attributes on a CI in our upcoming release, and have placed the ability to capture tags from other platforms in our near-future roadmap.  

    We have placed onto our roadmap the ability to capture the identified attributes in this ER into our near-term roadmap as well.

  • Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team