Should AWS improve the tag section of each service?

Your suggestion for improving the tagging experience in AWS services, particularly in S3, is a valid point that many users might appreciate. Currently, AWS does offer some tools to help manage tags across resources, but there's always room for improvement in user experience.

While AWS doesn't currently offer the exact functionality you're describing within individual service consoles, they do provide some centralized tag management capabilities. The Tag Editor in the AWS Resource Explorer console allows users to manage tags across multiple resources and services. This tool can help streamline the process of applying consistent tags across different resources.

For your specific use case of creating multiple S3 buckets with the same tags, you might find it helpful to use the Tag Editor to apply tags to multiple resources at once. This could potentially save time compared to manually entering tags for each bucket individually.

Regarding your suggestion for tag groups and IntelliSense-like functionality, these are interesting ideas that could indeed enhance the tagging experience. AWS does recognize the importance of effective tagging strategies and provides guidance on creating business-relevant tag groupings along technical, business, and security dimensions. Common tag categories include things like Project, Owner, and Environment - which align with the tags you mentioned.

While the current implementation may not be as streamlined as you'd like, AWS does continually evolve its services based on customer feedback. Your idea about preventing spelling errors and providing suggestions based on previously used tags could potentially improve consistency and reduce errors in tagging across an organization.

In the meantime, to help manage tags more efficiently, you might consider using AWS CLI or SDKs for bulk operations, or explore third-party tools that offer enhanced tagging capabilities. Additionally, establishing a clear tagging strategy within your organization can help maintain consistency even without automated suggestions.
Sources
Tagging resources - AWS CodePipeline
Add tags to selected resources - Tagging AWS Resources and Tag Editor
Tagging categories - Tagging AWS Resources and Tag Editor

Though there is no intellisence support for tagging, you can enforce the tags and values via tag policy. You can use Resource Groups & Tag Editor to identify the tagging issue (for example, different spelling or alternatives for same word- dev, Dev, development). Upon enforcement, it will not impact the already deployed resources but only updating existing or deploying new resources.

https://docs.aws.amazon.com/whitepapers/latest/tagging-best-practices/implementing-and-enforcing-tagging.html https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_supported-resources-enforcement.html