Solely to address 'least permissive' practices during the engagement of a developer with an AWS account having been engaged to work to create a Alexa skill(s) on behalf of another AWS account.

Although some of the role templates in IAM are comprehensive, the concept of "Least permissive is always the best approach." 'could' be strengthened by being verifiable to a posted AWS best practice set of specific outlined activities.

The benefit is that a 3rd party sees that AWS has published those permission sets; the Dev. is able to refer to AWS distilling a best-practices starting point, and 'least permissive' being always assumable at onset.

Our hifi devices have a feature which we call pins, but can be more generally described as presets - a bit like the ones you'd find on a car radio. It provides instant access to preselected music.

We'd like to offer these through our Smart Home Skill, for the moment, we've overloaded the Channel API permitted 6 channels 1 to 6 and also PIN x where x is a the number 1 to 6. This makes starting a pin rather awkward as you need to ask:

Alexa, change channel to PIN 4 on Kitchen

Would it be possible to introduce a more general synonym like "preset" instead of "channel".

For example,

"Alexa, invoke preset 4 on Kitchen" or
"Alexa, activate preset 4 on Kitchen"

Both would be much easier to say. Even better if we could substitute "preset" with our term "pin".

Ideally:

"Alexa, invoke pin 4 on Kitchen".

It would be great if there was an Alexa Support Center Portal comparable to the AWS Support Center Portal.

This would make it much easier to submit and track any and all Alexa specific support requests beyond posting to the Alexa forums which is great for a variety of general to specific questions, but falls short for addressing specific account-related and proprietary questions and such.

Further, having this feature would minimize time and friction going back-and-forth between the AWS Support Team through the AWS Support Center and the Alexa Support Team through the Alexa Forums, Contact Us, Email, etc and other communication channels.

Ultimately, having this Alexa Support Center communication channel would really enable driving and fostering a more positive developer experience in getting particularly important and time-sensitive support requests accountably and successfully addressed.

In the end, this would be especially useful for resolving emergency requests, Alexa Forums posts escalation requests, private, and other specific account-related requests as well as unique requests that are not well suited for the Alexa Forums, Email, Contact Us, etc communication channels.