# Faster AWS Console Navigation with Chrome Site Search

> TLDR aws + [TAB] + ec2 + [ENTER] is all you need. No need to enter the entire AWS Console...

- Author: Gabriel Koo (AWS Community Builder)
- Published: 2025-02-11
- Topics: aws, cloud, console
- HTML: https://gabrielkoo.com/blog/fast-aws-console-navigation-with-chrome-site-search-b9e/
- Original canonical URL: https://dev.to/aws-builders/fast-aws-console-navigation-with-chrome-site-search-b9e

## TLDR

`aws` + `[TAB]` + `ec2` + `[ENTER]` is all you need.

No need to enter the entire AWS Console URL every time, or consuming your energy in searching EC2’s icon in the console.

## Background

So you may navigate different AWS console pages daily during work/project.

Say you want to access the EFS service page in AWS Console, you typed in the URL bar but - Nope, no direct link since I didn't visit that page before on my browser.
![Open EFS Console page](/assets/img/ac1b68a059ee.png)

So what if I want to navigate to EC2 service page?
Better, but still I have to do some cursor navigation.
![Open EC2 Console page](/assets/img/810395bec601.png)

It takes extra attention for you to navigate to the right AWS Console's service page, even if you can type in the entire service name slug with your muscle memory 🧠. Typing the entire URL probably works, but it's more prone to errors.

## Faster Way with Chrome Native Site Search

1. Go to `chrome://settings/searchEngines` in Chrome
2. Scroll down to `Site search`
3. Click `Add`
4. Fill in the following details:

    Field | Value
    ---|---
    Name | `AWS Console`
    Shortcut | `aws`
    URL with %s in place of query | `https://console.aws.amazon.com/%s`
   
    ![Create site search](/assets/img/e31489221551.png)

## Let's Try It

![See it in action](/assets/img/e86aac802f23.gif)

With Chrome's Site Search feature, here's what required to navigate to the EC2 console page:

1. Type `aws` in the URL bar
2. Press `[SPACE]` or `[TAB]`
3. enter the service name in lower case slug, e.g. `ec2`, `efs`, `ecs`, `s3`

It will redirect you to `console.aws.amazon.com/<service_name>`, which will in turn redirect you to `<you_default_region>.console.aws.amazon.com/<service_name>`.

It's quicker and much more handy, isn't it?