Where to run the SG-AWS-RunShellScript-Setup.yml Script and SG-AWS-RunPowerShellScript-Setup.yml Script in AWS?Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Need more information on Where to run the SG-AWS-RunShellScript-Setup.yml Script and SG-AWS-RunPowerShellScript-Setup.yml Script in AWS? Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Release Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Please follow the below to get more information regarding how to execute these scripts manually in the AWS. 1. Navigate to All > Service Graph Connector for AWS > Setup 2. On the Getting started page, select Get Started 3. In the Configure the AWS environment section of the Service Graph Connector for AWS page, select Get Started. 4. For the Download the scripts task, select Configure 5. When you download all the scripts onto your local machine, select Close to close the Download the scripts dialog box and return to the guided setup 6. Provide these scripts to your AWS Team and request them to run manually for the Object id for which we are facing the issue. 7. Please follow the below path to run these scripts manually: AWS Resource Explorer >> Search for these scripts >> Select these scripts >> Select Run Command >> Choose Instance manually >> In the Output, please provide the S3 Bucket details >>Enable the CloudWatch Logs for more info >> After execution, please check the Command Id >> Open and check the Output 8. We can even download the results. 9. Now search with the command id in the S3 bucket to get the CPU related details that will be carried forward to the ServiceNow by the SG-AWS-SSM-GetS3Object data source. Please go through the below KB to get more information regarding the CPU related info fetched by the SGC AWS: How SGC AWS brings the CPU Related Deep Discovery Information(cpu_core_count,cpu_manufacturer, cpu_speed,.etc)