As of now, both the aws-* and amazon-* version of the tags are synonyms for each other.
So, which one of them should we have as the master?
Do we want the aws-* style tag or the amazon-* style tag?
Add a comment
|
1 Answer
The master tag should be the official service name
For example, aws-lambda is the correct tag, because the product name is AWS Lambda (and, not to mention, everyone calls it AWS Lambda).
- amazon-ec2 should be the master because that's the official name.
- amazon-cloudwatch should be the master because that's the product name.
- amazon-s3 should be the master (see Amazon S3).
- amazon-ami should be amazon-machine-images (see Amazon Machine Images—Amazon AMI is a litlte redundant!)
- aws-cli should be the master (see AWS Command Line Interface)
aws-codedeploy should be the master (see AWS CodeDeploy)
amazon-api-gateway should be master (see Amazon API Gateway).
aws-kms should be master (see AWS Key Management Service)
As a general rule, most of the products are [amazon-*], except CLI, CodeDeploy, KMS and Lambda. Let me know if I've missed any, though.
-
3Completely agree, it's hard to remember which ones are 'Amazon' and which are 'AWS' but we should be consistent. Apr 16, 2017 at 15:45
-
I think amazon-cloudwatch is resolving in the wrong direction, it appears to be resolving to aws-cloudwatch. Apr 16, 2017 at 21:06
-
Would there be anything wrong with creating aliases for all of them so it gets automatically canonicalized by the site?– chicksMay 10, 2017 at 12:48
-
@chicks Yes, I think the idea here is for both tags to be synonymised—I intended to discuss which tag should be the 'master' (the tag that should the 'canonical' one). Is that what you're wondering about, or something else? May 10, 2017 at 14:31
-
1It wasn't clear to me that we were keeping the aliases, but rereading the question the context is more obvious.– chicksMay 10, 2017 at 16:19