AWS Credentials

[niitnishant]

Hi Friend,

I am trying to do a test validation of my AWS Account Credentials for one of the amazon integration. I am repeatedly getting authentication failed message as below. However the i have provided very correction informations- Account Number, Access Key ID, and Secret Access Key.

Any hint around it , please ? I am on Jakarta release.

[Chandu Telu]

http://wiki.servicenow.com/index.php?title=Configuring_Amazon_Web_Services#gsc.tab=0

[Martin Grosskop]

As I understand it, in Jakarta release discovery of AWS is via MID server - not the way it was in previous releases.

So do you also need a MID Server for the Credentials test?

[gauravchoudhury]

Yes, that is correct.

Cloud discovery has changed, starting with the Jakarta release.

How Cloud Discovery works...

Types of cloud Discovery:

Service account cloud discovery

Discovers all resources in an AWS or Azure service account, including all datacenters in the account. The discovery process launches the necessary patterns to find all resources in a service account. You launch this type of cloud discovery from the Service Account form and track the discovery in the Cloud API Trail and Cloud Orchestration Trail.

Cloud application discovery

Discovers only the cloud resources in a service account for a pattern that you specify. You launch this type of cloud discovery from a Discovery schedule and track the discovery in the Discovery Status. This process is the same when discovering configuration items, IP addresses, or networks. You should have an understanding of how patterns work. See Pattern customization for more information.

Tracking the results of a Cloud Discovery

Typically, you track a discovery through the ECC queue and the discovery status, which shows you see all records for a particular discovery. For Service account cloud discovery, check the Cloud API Trail and Cloud Orchestration Trail. Records in these trails show you the same information in the ECC queue, including which MID Server processed and the log entries created for the discovery.

AWS Config and Azure alerts

Your instance can detect notifications and alerts from AWS and Azure clouds. Discovery can then make the necessary updates.

Note: You do not need the Cloud Management application to use cloud discovery. The Discovery plugin includes the necessary components from Cloud Management to perform cloud discovery.

Source: Link

[gauravchoudhury]

1. Add the Cloud Management capability to the MID Servers that you want to use for Cloud Discovery.
2. Set up credentials for either AWS or Azure:
   • Create AWS credentials.
   • Set up AWS Identity Access Management (IAM) users.
   • Collect the Azure Client ID and Tenant ID.
   • Create Azure credentials (service principals) for Cloud Management.
3. Create a service account for cloud discovery.
4. Decide if you want to run service account cloud discovery or cloud application discovery.
   • To run Service Account cloud discovery:
     1. Discover the logical datacenters in the service account.
     2. Discover the resources in those datacenters.
     3. Run discovery again on specific VMs to get data about them.
   • To run discovery on cloud resources in a service account using a specific pattern, see Run cloud application discovery.
   Note:Open the Cloud API Trail and the Orchestration Trail if you encounter any issues with the discovery.
5. Check the CMDB to see the discovered CIs specific to AWS and Azure clouds.
6. Configure AWS config or Azure alert services so that you know when changes to your cloud resources occur.

[bernyalvarado]

Hi Martin,

From what I remember even the K17 labs (in Jakarta) perform a whole discovery of aws services and all its underlined infrastructure without any having to install or use any MID Server.

Thanks,

Berny