DEV Community: hiroga

AWS Peacock Management Console enables to change console color as you like.

hiroga — Sat, 22 Jan 2022 20:23:39 +0000

AWS Peacock Management Console enables users to change the color of the AWS management console as like.

The browser extension is now available on both Chrome Web Store and Mozzila add-on.

In this article, I explain the motivation of development and how it works as the developer of the extension.

Motivation of development

My company starts switching from AWS Switch Role to AWS SSO for security reasons. However, we are worried that AWS SSO does not provide the feature to change color.

Changing color is a very simple, but efficient technique to avoid wrong operations. For example, making the production environment red helps operators to remind which environment they use.

AWS SSO has another problem. The account name is not shown on the menu button. Not setting an account alias is usual if AWS SSO is used. In my opinion, account name instead of account alias should be shown in the menu button.

After a little inspection, I decided to create a browser extension.

How it works

There are 3 steps to change color and show the account name.

Getting account name from AWS SSO screen
Getting account id and region in the management console.
Change color and menu button name in the management console.

1. Getting account name from AWS SSO screen

AWS SSO screen has the pair of account ids and account names.

The cookie also has an account name, but using it is not enough. When the user switched role beyond account from AWS SSO logged in user, the parameter does not change.

The account name information is stored in the browser extensions storage area. If you want to delete it, just uninstall the browser extension.

2. Getting account id and region in the management console.

Both account id and region are hidden in the management console.

// to get account id
const id = (document.querySelector<HTMLElement>('button[data-testid="awsc-copy-accountid"]')?.previousElementSibling as HTMLSpanElement)?.innerText.replace(/\-/g, '')

// to get region
const region = document.getElementById('awsc-mezz-region')?.getAttribute('content')

3. Change color and menu button name in the management console.

Changing console color is just embedding CSS, but not simple.

To ensure visibility, AWS Peacock Management Console can invert the menu icon and string color.

The extension also detects how users logged in. If AWS SSO is used, the menu button name is replaced by the account name.

Conclusion

AWS Peacock Management Console is developed to use AWS SSO convenient as AWS Switch Role.

The extension is released in Chrome Web Store and mozzila add-on. Source code is also available in GitHub. Any issues or contribution is welcome!

If this extension helps to improve your productivity, it is glad for me.

makefile styleguide as task runner

hiroga — Sun, 02 Jan 2022 22:00:25 +0000

Using make as task runner, this is style guide of makefile for me

Style Rules

Assignment to variables

Use := as possible. The variables defined by = is referred recursively and it is little tricky.

See 6.5 Setting Variables

Order or targets

Here is the preferable target order.

1. all (any name you like)
2. .PHONY
3. (other tasks)
4. clean

all is optional and should contains default tasks, like download, build, start. If you do not allow running without specifying goal, just remove this target.

.PHONY target should contain all phony targets, which name is not build output. There are two reasons to use phony target. to make sure to run target if a file of the same name exists, and to skip checking a file timestamp of the same name.

see Phony Targets (GNU make).

clean is used to be placed in the last, as I know.

Formatting Rules

Command substitution

Use $$() (double dollar) instead of \`` (backquotes).

Some articles say that backquotes has a little bit more compatibility to ancient make. However, escaping backquotes in nested command substitution is bother jobs.

TIPS: `$$(command)` vs `$(shell command)`

$(shell command) will be evaluated at the first time. $$(command) will be evaluated at the execution time.

Semicolon vs new line and TAB

Use new line and TAB for command. To keep the format constant regardless of the number of lines in the command.

Shell variables

Use $${VAR} instead of $$VAR. It help to distinguish shell variables from make variables.

Meta Rules

File name

Use Makefile, start with capital.

The manual says We recommend Makefile because it appears prominently near the beginning of a directory listing, right near other important files such as README.

References and Inspirations

Run aws-shell by docker

hiroga — Sat, 28 Mar 2020 22:51:14 +0000

TL;DR

Set this alias.

alias aws-shell='docker run --rm -it -v "$HOME/.aws:/root/.aws" hiroga/aws-shell:latest'

Details

As of 2020-03-29, aws-shell installed by Homebrew does not work.

To avoid the dependency problem, I run my aws-shell by docker.

Dockerfile is here.

https://github.com/hiroga-cc/docker-images/blob/master/aws-shell/Dockerfile

Issues

It runs creating index per invoke. I want to avoid it but do not have any good ideas.