Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
AWS Credential verification from the command line (CLI) - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • AWS Credential verification from the command line (CLI)
KB0723525

AWS Credential verification from the command line (CLI)


15444 Views Last updated : Jul 24, 2025 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

There are situations where the AWS Discovery fails with multiple errors and it goes difficult to understand where the issue is from, it could be AWS Credential, ServiceNow Cloud API, MID server, or any other reasons, this article will demonstrate to verify the AWS credentials from Command line to narrow down the issue.

Common Errors

<results error="Method failed: (/) with code: 401 - Invalid username/password combo" probe_time="101"> 
<result error="Method failed: (/) with code: 401 - Invalid username/password combo"> 
<output> 
<?xml version="1.0" encoding="UTF-8"?> <Response><Errors><Error><Code>AuthFailure</Code><Message>AWS was not able to validate the provided access credentials</Message></Error></Errors><RequestID>50b89cf8-152b-49f1-99e9-ecf2a5101f22</RequestID></Response> 
</output> 
<results error="Method failed: (/) with code: 403 - Forbidden username/password combo" probe_time="146"> 
<result error="Method failed: (/) with code: 403 - Forbidden username/password combo"> 
<output> 
<ErrorResponse xmlns="http://autoscaling.amazonaws.com/doc/2011-01-01/"> <Error> <Type>Sender</Type> <Code>InvalidClientTokenId</Code> <Message>The security token included in the request is invalid.</Message> </Error> <RequestId>cab3bb2b-633d-11e6-8209-eb0a64f487d1</RequestId> </ErrorResponse> 
AWS was not able to validate the provided access credentials (Service: AmazonEC2; Status Code: 401; Error Code: AuthFailure; Request ID: 0f4d4254-7ef1-4b31-9d83-dd99cbb9b471)

Prerequisite

As mentioned in our documentation (AWS credentials for Cloud Management), to configure an AWS Cloud account you need the following information from Amazon:

  • AWS account number.
  • Access key ID.
  • Secret access key

The Access key and Secret key are used in AWS credentials and the Account number is used to create Service Account

Verification from CLI

Note: Once the Credentials are saved in the ServiceNow Credentials table, the provided secret key is not visible and it will not be possible to know, Customer must need to have all the information handy for verification.

  1. Log in to the MID server
  2. Install the Command-line interface according to the OS, see:
    • Install the AWS Command Line Interface on macOS
    • Install the AWS Command Line Interface on Microsoft Windows
    • Install the AWS Command Line Interface on Linux
  3. Verify the configuration of AWS Command Line
    • Configuring the AWS CLI
  4. Command to be executed to verify the credentials: aws configure



  5. Once this command has been executed, provide the Access Key and Secret Key as provided to the ServiceNow AWS configuration, the Region and output format can be provided as per your prefer
  6. As soon as the command runs, it will pick up the provided configuration without error
  7. To verify further, you can run any other command to list out the configuration, see screenshot for an example, executed to list the S3 buckets available and failed with the authentication error




The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • KB0723525-01.png
  • KB0723525-02.png
  • Pasted image.png
  • Pasted image.png

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.