- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 01:32 AM
Hi All,
We have configured AWS Cloud Discovery in our organisation and it is working fine. Now I need to remove some Old Cloud Service Accounts which have already been added to the current Cloud discovery job to discover. Like Other discovery jobs (CI Based) we are removed from the Discovery Range but for the cloud, I am not finding any option to remove the configured Service Account. Only I can see the Cloud Service Account (cmdb_ci_cloud_service_account) where we define the master and child.
Can someone please help with this?
Thanks
Balaji
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2024 10:56 PM
ok makes sense and that's the solution forward for now. you have to remember to set up regular checks to add accounts as needed - it won't be immediate. you can keep that as part of the account creation/termination request workflow also if there's one.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 03:27 AM
Have you set system property “glide.discovery.cdu.auto_refresh_sub_accounts_and_ldcs” to the value true?
This should auto-refresh any new accounts getting added, and old accounts removed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 05:20 AM
Hi Ram,
Thanks for the Quick response.
Currently "glide.discovery.cdu.auto_refresh_sub_accounts_and_ldcs" is false.
How to remove those old accounts, Currently we have created all Service Accounts In "cmdb_ci_cloud_service_account " and linked to one Master Ac. Now need to remove a few ac which is no use. Shall we delete or just remove the master ac link?
Does anything need to be done in the current discovery job which is configured or it will auto-refresh once we mark that property as true?
Thanks
Balaji
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 09:41 AM
Hi Ram,
I set the sys property to true and updated Service Ac by removing the parent ID. When the discovery job runs again, it reverts those Service ACs and links to the parent ID, updating the Operational status to operational.
Should I create a New AWS Discovery job for this as existing reverting?
Thanks
Balaji Prusty

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2024 09:46 AM
discovery is using API calls through patterns to get latest data and updates the information. do you see it is wrong? e.g. an account that is called operational in cmdb, is not really so? please sahre more details if so.