- Newest
- Most votes
- Most comments
The 403 Access Denied error you're encountering when trying to access AWS Skill Builder course content typically indicates an authentication or authorization issue between your browser session and the Skill Builder learning platform. Here's what's likely happening and how to resolve it:
The most common causes for this error are: (1) An expired or invalid session token - your Skill Builder session may have timed out or become corrupted, (2) Browser cache or cookie issues that are preventing proper authentication, or (3) A problem with your course registration or enrollment status.
To resolve this issue, try these steps in order:
First, sign out of AWS Skill Builder completely, then clear your browser cache and cookies specifically for the skillbuilder.aws domain. After clearing the cache, sign back in to Skill Builder and attempt to access the course again. This resolves the majority of 403 errors as it refreshes your authentication tokens.
If that doesn't work, try accessing Skill Builder in a different browser or in an incognito/private browsing window. This helps determine if the issue is related to browser-specific cache or extension conflicts.
Verify that you're still properly enrolled in the course by navigating to your Skill Builder dashboard and checking your active courses. If the course doesn't appear or shows an unusual status, you may need to re-enroll.
Regarding the Apollo Client and CatalogSingleSelectAttribute errors you're seeing in the console - these are typically frontend framework warnings and are usually not the root cause of the 403 error. They may be symptoms of the page failing to load properly due to the authentication failure.
If none of these steps resolve the issue, it's possible there's a service-side problem with that specific course module or your account's access permissions. In that case, you should contact AWS Support through the AWS Support Center at https://console.aws.amazon.com/support/ to report the issue. When you do, provide details about which specific course and module you're trying to access, and mention the 403 error from the LRS endpoint. The support team can investigate whether there's an issue with the course content or your account's enrollment status that requires their intervention.
answered a month ago
Our team is aware of this issue and is actively working to resolve it. As a workaround, if you clear your cache or access through a private browser, the AccessDenied error should resolve.
answered a month ago
Relevant content
asked 6 months ago
asked 20 days ago
- AWS OFFICIALUpdated 10 months ago
