Item logo image for Console Hopper

Console Hopper

consolehopper.com
5.0(

2 ratings

)
ExtensionDeveloper Tools45 users
Item media 5 (screenshot) for Console Hopper
Item media 1 (screenshot) for Console Hopper
Item media 2 (screenshot) for Console Hopper
Item media 3 (screenshot) for Console Hopper
Item media 4 (screenshot) for Console Hopper
Item media 5 (screenshot) for Console Hopper
Item media 1 (screenshot) for Console Hopper
Item media 1 (screenshot) for Console Hopper
Item media 2 (screenshot) for Console Hopper
Item media 3 (screenshot) for Console Hopper
Item media 4 (screenshot) for Console Hopper
Item media 5 (screenshot) for Console Hopper

Overview

For AWS: hop between consoles fast — role-picker search, account tags, deep-link services, env-coloured tabs, tab groups.

Console Hopper turns the AWS SAML role-picker into a fast, filterable launcher and makes a tab strip full of AWS consoles instantly readable. If you have access to dozens — or hundreds — of AWS accounts via SAML SSO, the default role list is a long, unsorted scroll. Console Hopper gives every row a star, a service deep-link, and a one-click sign-in, and gives every open console tab a colour-coded favicon plus an account name in the title. NEW IN 1.11.0 • One row per session in the Active AWS sessions panel — a jump used to fold its hub and the sessions reached through it into a single row, so a hub with more than one jump could push sessions out of sight. Now every session has its own row: a hub is marked "hub · N jumps" and each jump sits indented beneath it, so the rows always match the "N of 5" count. Sign a single session out on its own, or a hub takes its jumps with it and highlights them on the confirm. NEW IN 1.10.0 • Know when a sign-in has gone stale — once your sign-in has expired, a banner across the top of the page says so and tells you to sign in to AWS again through your identity provider, and the Sign In and jump buttons grey out because they can no longer post a working sign-in. Sessions you already have open keep working. NEW IN 1.8.0 • Already signed in? It opens instead — a role you're already signed in to shows Open instead of Sign In, and opens a tab in that session. Signing in again would replace the session and sign its open tabs out. Launch Sets and jumps reuse live sessions too: a jump never restarts the hub session your other jumps depend on, and a role's extra tabs in a set open in the session its first tab signed in to. • Make room for a set — when a Launch Set needs more of AWS's five console sessions than are free, its confirmation lists your sessions with a Sign out button each ("Frees enough" marks one that makes room on its own; a hub and the sessions jumped through it are one row), and Open stays off until the whole set fits. A set whose roles are all signed in opens from any role picker page, however long it has been open. • Room before you sign in — signing in to a role, or jumping to an account, when all five AWS sessions are in use now lists your sessions to sign out first (a hub a jump goes through is kept), instead of AWS's "Session limit reached" page in the new tab. • Long names fit — the role picker grows to fit your longest account and role names, up to 90% of the window (General Settings → Maximum page width). A name that still doesn't fit is shortened in the middle, keeping the end that tells similar names apart, and shows in full when you hover it. • Ended sessions — when an AWS session ends while its tabs are still open, the tab group Console Hopper made for it turns grey and reads "Ended · …", so the tab strip matches what's really signed in. • Multi-session off? It says so — Console Hopper's session features (the session counter, Open on a role you're already signed in to, making room for a Launch Set) need AWS multi-session support, which AWS leaves off until you turn it on. When it's off, the counter reads "Multi-session is off" and shows how to turn it on, instead of showing nothing. • Jumps follow the new-tab rule — ⌘/Ctrl-click or middle-click on a jump opens it in a new tab, like any role. • The sessions panel signs a hub and the sessions jumped through it out together; "Sign out idle" no longer counts a hub as idle while its jumps are in use. • Fixes — console tabs stay in their region in the first minutes after a sign-in too; Account Names and Tags point out lines they can't read instead of dropping them; a tab title keeps its account prefix once; toasts stack instead of overlapping. NEW IN 1.7.0 • Launch Sets — open every console a ticket needs in one click. Save the console tabs a piece of work needs under a name (usually the ticket id) — each tab with its own role, landing service and region, several tabs per role if you like — and open them all at once, next to the role picker. Save one from a search or filter ("Save current view"), or record the console tabs you already have open ("Save open tabs", exact pages included). A Sets column beside the filters holds them; the Launch Sets panel in the side menu reorders (drag), edits, archives and restores them. One confirmation covers the whole set when it includes sensitive roles or would go past AWS's five-session limit. • Tags belong to an account + role, not the whole account — tag the one role a ticket needs and only that row carries it. Existing account tags are copied onto each of that account's roles, so nothing is lost. • Filter rows stay on one line — chips that don't fit fold into a +N chip, so the panel no longer grows as tags pile up. Drag chips along a row to reorder it, drag one out of +N to keep it in view, or onto +N to tuck it away. • Sessions panel: signing a session out also closes its console tabs, and "Sign out idle" signs out every session with no console tab open. • Fixed: if Console Hopper is installed twice (say, a store copy and a developer copy), the second copy stands aside instead of doubling every row. WHAT YOU GET • Filter and search the role list Filter by organisation, environment (prod/test/dev), account type (Management / Security / Logging / …), role-name keyword (Admin / ReadOnly / PowerUser / …) or your own tags. Each filter row stays on one line — extra chips fold into a +N chip — and you order the chips by dragging. The search box is separator-insensitive (type "test 123" to find "test123") and supports scoped terms — tag:, role:, name:, account:, env:, type:, org: — combined with a space (and), a comma (or) or a leading - (exclude), with "quotes" for an exact phrase. It pops out into a roomy card with click-to-insert suggestions and a live match count. Every filter group is editable from the side menu. • Tag roles Give an account + role your own short labels — prod-network, pci, a ticket number — and organise by them. A tag belongs to that one role, so tagging your admin role doesn't tag the account's other roles. Add or remove tags inline from a chip on each row (with autocomplete), or edit in bulk from the side menu. Tags get their own filter row and are searchable with tag:. • Launch Sets Save the console tabs a ticket needs and open them all in one click. Each tab keeps its own role, landing service and region; one role can have several tabs. Save from the current search or filters, or from the console tabs you have open. The tabs open next to the role picker and are grouped the way your tab-group setting says; roles you're already signed in to open in their session, and if a set needs more sessions than are free you choose which to sign out. Reorder, edit, archive and restore sets from the Launch Sets panel. • Save searches as shortcuts Turn a useful query + filter combination into a named chip in one click, then re-apply the whole view — search and filters — whenever you need it. Set any shortcut (or Favorites, Recent, or a tag) as your "Start View" so the picker opens on it every load. • Rename accounts Map specific account IDs to a friendly name via "Account Names". The custom name replaces the AWS account name in the list and is used for filtering, grouping and tab titles. • Jump to account (role chaining) For accounts you can only reach by assuming a role from a hub — including accounts that aren't in your role list at all. Configure each org once under “Jump Profiles” (org name, hub account id, role to assume, and optionally the region to land in) and a “Jump to account” button appears in the search column. Enter the destination account id, pick a region, add an optional session label — Console Hopper signs into the hub (or uses your hub session if it's already open) and opens AWS's Switch Role pre-filled, one click and you're in. It lands you in the region you chose rather than whichever one AWS picks for that account, and when several console sessions are open it selects the right one for you instead of leaving you to guess. The new tab is titled with your session label, and recent jumps are one click away in the popover. Save the destinations you use often — via "Jump Destinations" in the side menu, or the "Save as a named destination" tick when you jump — and they appear as ⤳ rows in the main list itself, with a dashed environment stripe, the hub they go through, and their own service and region picks. • Favorites and Recent Star roles you use often. Recently signed-in roles are tracked automatically (configurable limit). • Deep-link into a service Each role row has a service dropdown. Pick one before Sign In and you land straight in that service's own console for that role, instead of the console home page and another two clicks. A handful of common destinations are set up by default, and you can add, rename or remove any of them from the side menu. • Per-sign-in region Each role row also has a region dropdown — choose which AWS region a sign-in lands in. It defaults to your region and remembers your last pick per role; turn off “Remember the region I pick per role” in General Settings and every row always opens on your default instead. Edit the offered regions via “Regions”. • Console tabs stay in their region Some AWS consoles are account-wide and carry no region of their own, so visiting one drops the region from the console address — and the next regional console you open lands wherever your AWS profile's default Region points rather than where you were working. Console Hopper remembers what region each console tab is in and sends the tab back, while leaving alone any region you picked yourself from AWS's own region menu. • Room for long names The picker grows to fit your longest account and role names, up to a share of the window you choose. A name that still doesn't fit is shortened in the middle and shown in full when you hover it. • Copy account ID Click the account-id button on any row to copy the 12-digit id. • Colour-coded console tabs Every AWS console tab opened through the plugin gets a coloured favicon (env colour) and an account-name title prefix, so ten open tabs are still distinguishable at a glance. • Tab groups — visual containers Console Hopper drops each new console tab into a Chrome tab group: by role, by organisation, or by a per-ticket override tag. Same role always gets the same colour, and a group whose session has ended turns grey. Note: tab groups are a Chrome visual feature only — they don't isolate cookies. For real session isolation, combine with Chrome profiles. • Sensitive-sign-in confirmation Configure which role-name keywords (default: "admin") and which account types are sensitive. Signing into a matching role/account pops a "are you sure?" modal so you don't accidentally land in production. • Active AWS sessions AWS allows five concurrent console sessions per browser profile, and normally only tells you once you have hit the limit. A counter at the foot of the right column turns amber with one slot left and red when full. Open it to see every session — account, role, region, tab group, when it started, how long it has left and how many tabs it still has open — and sign any one of them out to free a slot (its console tabs close with it), sign out every session that has no tab open, or sign out all of them. A hub and each session jumped through it get their own row, the jumps nested beneath the hub. A sign-in or jump that needs a session when all five are in use shows the same list first. This needs AWS multi-session support, which is off until you turn it on (in any AWS console tab, your account name at the top right → Turn on multi-session support); while it's off, the counter says so. Session metadata only; cookie contents are never read. • Clear AWS sessions One click signs you out of your AWS console sessions by clearing aws.amazon.com authentication cookies (your console favourites and settings are kept). Sessions held elsewhere — an IAM Identity Center portal on awsapps.com, for instance — are outside the extension's reach and stay signed in. • New-tab sign-in ⌘/Ctrl-click, middle-click or ⌘+Enter opens the console in a new tab, for jumps too. A "Sign-in" side-menu option sets the default; the modifier inverts it. • Drag-to-reorder Hold and drag any role row to set your preferred order. "Reset Order" in the side menu restores AWS's default. • Light / dark / auto theme, compact mode, keyboard shortcuts / or Ctrl/Cmd+K (or a tap of Alt) focuses search, ↑/↓ moves the selection, Alt+arrows walk the search suggestions, Enter signs in to the selected role, Esc closes modals / clears filters. • Export / import settings as JSON Share your configured orgs, envs, account types, role names, services, tags, favorites and shortcuts with a teammate. • Org-agnostic Ships with generic placeholders. You rename Org A / Org B / Org C and fill the patterns to match your real organisations. No hard-coded vendor names anywhere. PRIVACY Console Hopper runs entirely in your browser. It does not contact any server of ours, send telemetry, or collect personal data. It talks only to AWS: to read which console sessions you have open, to sign one out when you ask, and — when you open a Launch Set — to post the sign-in page's own SAML response to AWS's sign-in endpoint once per tab that signs in (a role you're already signed in to opens in its session without it), exactly as the page's Sign In button does. That response is the only authentication information Console Hopper ever handles: it is held in memory, one single-use copy per tab, for at most five minutes, and never goes anywhere but AWS's own sign-in endpoint. Your password, MFA codes and AWS access keys are never seen, and cookie contents are never read. All settings (favorites, custom org / env / type / role labels, recent signins, preferences) are stored in chrome.storage.local — they never leave your device unless you click "Export Settings" yourself. PERMISSIONS — WHY • storage — persist your preferences and configuration locally • tabs — group new console tabs, open a Launch Set's tabs next to the role picker, open a tab in a session you're already signed in to, list your open console tabs for "Save open tabs", notice a tab group whose session has ended, and close a signed-out session's tabs • tabGroups — create and colour Chrome tab groups for each account+role combination, and grey out one whose session has ended • host access — limited to AWS SAML sign-in pages and AWS console pages, so the plugin can enhance the role-picker, decorate console tabs, and ask AWS which console sessions you have open. No other sites are touched. INSTALL 1. Install from the Chrome Web Store. 2. Open your AWS SAML sign-in URL. The role picker is now the Console Hopper UI. 3. On first load, a welcome panel walks you through the highlights. 4. Configure your organisations, environments, account types, role names and services from the side menu (hover the right edge). This extension is community-built and not affiliated with Amazon Web Services. "AWS" is a trademark of Amazon.com, Inc.

Details

  • Version
    1.11.0
  • Updated
    October 23, 2026
  • Size
    123KiB
  • Languages
    English
  • Developer
    Website
    Email
    ccoe-plugin@cutspace.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization

Console Hopper has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.

Console Hopper handles the following:

Authentication information

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps