Skip to content

AWS IoT LPWAN Management Console Permission Error

0

First off: While not a great idea, I am trying this as the root user, so I should have permissions (and so far had permissions). Accessing the correct region and trying to list my gateways I get the error "You don't have permission to list your gateway." and a second popup stating "You don't have permission to get your resource." Given that I can list the same resources using the cloudshell ('aws iotwireless list-wireless-gateways' in the same tab, same region, same user) tells me there is something wrong. Logging in using an anonymous tab in another window does not fix it, so I doubt its cookie etc related. Is there anything I can do to reset this on my end or get more details on the error? Would creating an IAM user fix the issue?

asked a year ago98 views

2 Answers
5

Would suggest to check on below at the first place:

  • Check for SCPs: If you're in an Organization, inspect the SCPs attached to your account. You can find guidance in this AWS troubleshooting guide.
  • Use CloudTrail: Look at the CloudTrail logs for failed ListWirelessGateways or GetResource calls. They’ll show which policy blocked the request.
  • Try a different browser profile: Even though you ruled out cookies, a fresh browser profile (not just an incognito tab) can help eliminate cached session artifacts.
  • Create an IAM user with admin access: This can help isolate whether the issue is tied to the root user session. If the IAM user works fine, the problem may be session-specific.
  • Reset the Console session: Sign out completely, clear cache, and sign back in. Sometimes stale session tokens cause odd behavior.
EXPERT

answered a year ago

0

Hey,

Hope you're keeping well.

This is likely a console-side permission evaluation issue rather than an actual lack of IAM rights, especially since the CLI works with the same credentials. In the AWS Management Console, some IoT Wireless LPWAN pages make additional API calls (like GetResource or ListTagsForResource) that might be blocked by an SCP or service control restriction even for root. Check AWS Organizations > Policies for any SCPs that could limit IoT Wireless actions, and review CloudTrail for the exact denied API calls when loading the console page. Creating an admin IAM user and testing in a fresh browser profile can help isolate whether it’s a session or account-level restriction.

Thanks and regards,
Taz

answered 9 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.