3 ms·

Very interesting. This would explain the response I got (backstory - I am a contributor to a number of open source packages / not totally clueless, but was com

Very interesting. This would explain the response I got (backstory - I am a contributor to a number of open source packages / not totally clueless, but was coming in from a micro personal account). I was like, how the heck do they afford this response for $99! (or whatever it cost back then - this was a long time ago). I kept my support plan active for a year as a courtesy though I never had another question aside from the first two I put in. That said, as a programmer I like time to focus so being asked customer questions would drive me nuts, hopefully they filter out the idiots who just can't setup things right (80% of issues are not bugs but customer setup issues).

whoknew1122 6y ago
For most services, this is how the AWS escalation path works: 1.) Support engineer receives the case. In most cases, for most services, the run-of-the-mill support engineer has gotten enough training on the service that they'd considered a SME at any AWS partner/enterprise. 2.) If front-line support engineer can't solve the case, they talk to their more tenured friends. 3.) If they still can't solve the case, they escalate to Premium Support SMEs in the service. These are support engineers that have proven they have solved complex enterprise-level cases and get specialized training from the service teams on the internals of the service. 4.) If the SME can't figure it out, it's escalated to the service team (i.e. the actual software engineers that write the code). Steps 1-3 deflect a lot of the annoying, unnecessary escalations. But sometimes escalation to the teams is unavoidable. For example, some service limits are hardcoded into the service and updates require a code push. Or (somewhat rarely) there's a service bug. That being said, Premium Support engineer have access to the backend service code for most everything. While not every PS engineer knows how to code, on more than one occasion, I've dug through a code repo to figure out why something was behaving oddly.

whoknew1122 6y ago

For most services, this is how the AWS escalation path works: 1.) Support engineer receives the case. In most cases, for most services, the run-of-the-mill support engineer has gotten enough training on the service that they'd considered a SME at any AWS partner/enterprise. 2.) If front-line support engineer can't solve the case, they talk to their more tenured friends. 3.) If they still can't solve the case, they escalate to Premium Support SMEs in the service. These are support engineers that have proven they have solved complex enterprise-level cases and get specialized training from the service teams on the internals of the service. 4.) If the SME can't figure it out, it's escalated to the service team (i.e. the actual software engineers that write the code). Steps 1-3 deflect a lot of the annoying, unnecessary escalations. But sometimes escalation to the teams is unavoidable. For example, some service limits are hardcoded into the service and updates require a code push. Or (somewhat rarely) there's a service bug. That being said, Premium Support engineer have access to the backend service code for most everything. While not every PS engineer knows how to code, on more than one occasion, I've dug through a code repo to figure out why something was behaving oddly.