AWS discovery using STS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2022 03:04 PM
I am trying to discover using STS in AWS. I configured the roles and a MID in AWS with IAM role attached to assume role. Refresh sub accounts action shows error. Pattern discover log shows error
"message" : "2022-08-13 20:13:36: Exception occurred while executing operation Cloud REST Query. Custom operation Failed to run script due to the following error: JAVASCRIPT_CODE_FAILURE: com.snc.sw.exception.CommandFailureException: Cloud credentials are missing for https://organizations.us-east-1.amazonaws.com . Not able to generate the temporary credentials. Please check the mid server logs for exact error. (script_include:AwsApiCommand; line 260). Custom operation Failed to run script due to the following error: JAVASCRIPT_CODE_FAILURE: com.snc.sw.exception.CommandFailureException: Cloud credentials are missing for https://organizations.us-east-1.amazonaws.com . Not able to generate the temporary credentials. Please check the mid server logs for exact error. (script_include:AwsApiCommand; line 260)"
With this type of discovery, it is supposed to be credential less.
Anyone tried this disco?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2022 04:08 AM
Hi, we did implement the credential less based AWS discovery without any issue. For more details on the implementation pls check https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0957891
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2022 06:09 PM
will check. thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2022 08:49 PM
Pat - what did you get from mid server logs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2022 10:25 AM
Hello Pat,
Were you able to overcome this issue? We receiving the same error.
Thanks,
Billy