Having issues with connecting ServiceNow to AWS using IAM keys.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2014 01:48 PM
Hi,
I'm having issues with connecting ServiceNow to AWS using IAM keys.When I perform an Update Keypairs it doesn't return anything and when I check the error logs all I see is "Error: Request failed with status code: 401". I checked my CloudTrail logs and I don't see any attempts of connectivity.
Following this: http://wiki.servicenow.com/index.php?title=Configuring_Amazon_EC2_for_Cloud_Provisioning I'm not getting past the Update KeyPairs section.
I've performed the following bits of troubleshooting:
- Enabled Cloudtrail on the AWS Training account and I see absolutely no attempts from the IAM account
- Using the same IAM keys I tested a simple Get-EC2KeyPairs from powershell on my local client and that works perfectly fine
- Checked the proxy for any attempt from the Mid-Server, the ADFS servers and the ADFS Proxy Servers and there is absolutely no attempt from those servers out to anything amazon related
- Checked the logs on Service Now and I can see it using the existing workflow of "Update EC2 Keypairs"
- Checking the event logs for errors shows a debug error of "Request failed with status code: 401" — but no further information on what is returning that unauthorised code — and I'm going to assume its attached to the GetEC2KeyPair event — but again, no real way to attach it to any event seeing as there is no Session ID, source, destination or anything else attached to that log message.
- In the logs it does show it attempting to connect to the FrankFurt region, so I even created a KeyPair in that region to no avail.
- Did wonder if the workflow "Update EC2 KeyPairs" had been tampered with but I couldn't find a way to see previous revisions of workflows to even check let alone revert back any changes.
- Tried both formats of AWS Account number — with and without the hash between each 4 digits
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2014 11:39 PM
You should try to crete a key pair in your AWS account within the EU (Ireland) region.
I had similar issue has ServiceNow was only retrieving the key pair from that region.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2015 03:53 PM
Karen,
I was having the same issue and it turned to be a region loaded from demo data that matched region in EC2 that had the keypair associated with it. I deleted the Amazon Region in my ServiceNow instance and then the discovery worked like a charm.