- Newest
- Most votes
- Most comments
While the new multi-session console experience has changed how URLs are structured, there isn't a straightforward way to link directly to a specific resource or service in a particular account without knowing the random string in the URL.
However, there is an alternative approach you can use to achieve a similar result with minimal friction for users. You can create shortcut links using the AWS IAM Identity Center (formerly AWS Single Sign-On) access portal. These shortcut links allow you to specify an account ID, a permission set (role), and a destination URL within the AWS Management Console.
Here's how a shortcut link would be structured:
In this link:
- Replace "example" with your actual access portal subdomain
- Replace "123456789012" with the desired account ID
- Replace "YourRoleName" with the appropriate permission set name
- Replace "service" in the destination URL with the specific AWS service you want to link to
This method allows you to create links that will sign users into a specific account with the appropriate permissions and take them directly to the desired service or resource page. While it's not exactly the same as linking to the new multi-session console URLs, it provides a way to minimize clicks and friction for users accessing specific resources across different accounts.
Keep in mind that users will need to have the necessary permissions set up in IAM Identity Center to use these shortcut links effectively. Also, remember to URL encode the destination portion of the link to ensure it works correctly.
This approach provides a balance between the specificity you're looking for and the new multi-session console structure, allowing you to guide users to specific resources with minimal effort on their part.
Sources
Creating shortcut links to AWS Management Console destinations - AWS IAM Identity Center
Signing in to multiple accounts - AWS Management Console
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated a year ago

The problem is that Identity center needs an organisation and our accounts are under a parent company's organisation, so that is not an option... (Unless there is a way for hierarchical organisations or an account under multiple organisations)
This doesn't work for me because I don't even know if we have an access portal subdomain. If we do I don't know what it is or even who I'd ask.