DEV Community

Quoc-Hung Hoang
Quoc-Hung Hoang

Posted on ā€¢ Edited on

3 1

Quick AWS Console Navigation: A Chrome Search Engine Hack The Problem

We've all been there - navigating the AWS Console can be a pain.

Whether you're:

  • Clicking through multiple levels of the navigation bar
  • Trying to remember which category contains the service you need
  • Googling "how to find X service in AWS console"

It's time-consuming and breaks your workflow momentum.

The Solution

What if you could jump directly to any AWS service by typing aws ec2 or aws s3 in your Chrome address bar? No more searching, no more clicking through menus.
[Image: Screenshot showing Chrome address bar with "aws ec2" typed in]

All you need to type is:

aws [tab] ec2 [enter]

And you're there! It's that simple.

Setup Guide

Here's how to set this up in Chrome:

Open Chrome Settings for Search Engines

  1. Go to chrome://settings/searchEngines in Chrome
  2. Scroll down to Site Search and click Add
  3. Fill in the following details:

    Name: AWS Console
    Shortcut: aws
    URL: https://console.aws.amazon.com/%s

  4. Click "Add" to save

How It Works

Once configured, here's how to use it:

Pro Tips

  • The service name should match its URL path in the AWS Console
  • You can use this technique for other services too - not just AWS!

Conclusion
This simple Chrome setup can save you countless clicks and searches throughout your day. It's especially helpful if you frequently switch between different AWS services.
No more menu diving or Google searches - just aws [tab] and go!

Playwright CLI Flags Tutorial

5 Playwright CLI Flags That Will Transform Your Testing Workflow

  • 0:56 --last-failed: Zero in on just the tests that failed in your previous run
  • 2:34 --only-changed: Test only the spec files you've modified in git
  • 4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production
  • 5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline
  • 5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

Watch Full Video šŸ“¹ļø

Top comments (4)

Collapse
 
duyluann profile image
duyluann ā€¢

Nice tip!!!

Collapse
 
hoangquochung1110 profile image
Quoc-Hung Hoang ā€¢

Simple but powerful !

Collapse
 
dansilcox profile image
Dan Silcox ā€¢

So simple but so effective! I have a bunch of other custom search engines e.g. JIRA, Confluence, etc, but never thought to do one for AWS console!

Collapse
 
hoangquochung1110 profile image
Quoc-Hung Hoang ā€¢

Yup, we can apply this technique to a bunch of our management tools

Playwright CLI Flags Tutorial

5 Playwright CLI Flags That Will Transform Your Testing Workflow

  • 0:56 --last-failed: Zero in on just the tests that failed in your previous run
  • 2:34 --only-changed: Test only the spec files you've modified in git
  • 4:27 --repeat-each: Run tests multiple times to catch flaky behavior before it reaches production
  • 5:15 --forbid-only: Prevent accidental test.only commits from breaking your CI pipeline
  • 5:51 --ui --headed --workers 1: Debug visually with browser windows and sequential test execution

Learn how these powerful command-line options can save you time, strengthen your test suite, and streamline your Playwright testing experience. Click on any timestamp above to jump directly to that section in the tutorial!

Watch Full Video šŸ“¹ļø

šŸ‘‹ Kindness is contagious

If you found this post useful, please drop a ā¤ļø or leave a kind comment!

Okay