AWS Management Console、アカウント色やリージョン表示など視覚設定をカスタマイズ可能に Customize your AWS Management Console experience with visual settings including account color, region and service visibility

AWS has rolled out a set of visual customization options for the Management Console, allowing users to assign distinct colors to individual accounts and to fine-tune which regions and services appear in the navigation. The update targets a long-standing pain point for engineers juggling many AWS environments: visual ambiguity that can lead to costly mistakes.

The release introduces three main capabilities. First, account colors let users tag each AWS account with a custom hue that appears in the console's navigation bar. Production environments could be marked red, staging yellow, and sandboxes green, giving an at-a-glance cue when toggling between accounts in the same browser session. Second, region visibility controls allow users to hide regions they never use, decluttering the region selector and reducing the risk of accidentally launching resources in an unintended geography. Third, service visibility settings let users show or hide services in the navigation, tailoring the console to the workloads each engineer actually touches.

Importantly, these settings are tied to the individual user's console profile rather than enforced organization-wide via IAM. That means each engineer can configure the experience to their workflow without administrators needing to change policies, and the feature comes at no additional cost. Adjustments are made from the settings menu in the top navigation.

The context here matters. Enterprises using AWS Organizations frequently operate dozens or hundreds of accounts, and incidents caused by running a destructive command in the wrong account have been a persistent operational hazard. For years, the gap was filled by community tools and browser extensions such as AWS Extend Switch Roles, the Granted CLI, and various tampermonkey scripts that injected color banners into the console. By bringing this functionality natively into the platform, AWS is effectively absorbing a popular ecosystem pattern — a move that mirrors how cloud vendors often productize community workarounds once they reach critical mass.

Competitively, the update also narrows a UX gap with other clouds. Google Cloud Console and Microsoft Azure Portal have iterated on tenant and project switching cues, and multi-account usability has quietly become a differentiator as customers consolidate workloads across providers. While the new AWS settings are modest in scope, they address a category of human-factor errors that scale with the size of an organization's footprint.

For SRE teams and anyone responsible for production operations, this is the sort of incremental polish that can pay outsized dividends. It is unlikely to change architectural decisions, but it may reduce the frequency of the dreaded wrong-account incident — and that alone is likely to make the feature widely adopted in the months ahead.