- Newest
- Most votes
- Most comments
It sounds like the JavaScript code in the management console running in your browser might just be failing to receive a response from an API it's calling, hence displaying the Network error message.
If you open Developer tools (F12) in your browser, does the Console tab show any errors when loading the page? If not, you could check from the CloudTrail logs both in your current region and in us-east-1 for any errors that the APIs themselves might have returned, including access denied errors that might be caused regardless of otherwise full permissions, if a service control policy in the organisation or a VPC endpoint policy (if you're going through an endpoint) denied the request.
There are several warnings about cookies missing SameSite, and some errors about Cross-Origin Requests failing:
Content-Security-Policy: The page’s settings blocked the loading of a resource at data:text/plain;base64,Cg== (“connect-src”).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://prod.log.shortbread.analytics.console.aws.a2z.com/1x1.png?severity=info&message=uiMounted&payload=<more-stuff-elided>. (Reason: CORS request did not succeed). Status code: (null).
[above pair of errors is repeated again]
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://access-analyzer.us-east-1.amazonaws.com/policy/generation?principalArn=arn%3Aaws%3Aiam%3A%3A<AWS-account-ID>%3Auser%2F<username>. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.
[above error is repeated three more times]
Source map error: Error: JSON.parse: unexpected character at line 2 column 1 of the JSON data
Resource URL: https://us-east-1.console.aws.amazon.com/iam/home?region=us-east-2#
Source Map URL: index.js.map
Source map error: Error: request failed with status 403
Resource URL: https://a.b.cdn.console.awsstatic.com/a/v1/<elided>/main.js
Source Map URL: main.js.map
So one kind of CORS error is coming back with a null status code, the other kind is specifically to do with the Access Analyzer but is still returning 200 (success), and then come some warnings about status 403 errors ("forbidden" iirc).
Given that context, I'm willing to toss this into the "probably nothing we can do about this" category. :-)
answered 2 years ago
Relevant content
asked 2 years ago
asked 3 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 9 months ago

I think you're correct in pointing to the browser console. I've posted a more detailed reply as a separate answer, just to get formatting controls.