We operate at an unprecedented scale, with unmatched architectures. We try to externalize the lessons that we think customers can use themselves, but a lot aren't as relevant. Our aim is to build the lessons learned into our platform so that customers don't need to. 2/n
-
-
We know that COEs are still interesting, but too interesting in some cases! They aren't written for public consumption and they contain many references to internal systems, tools, and processes that are proprietary. They also often reference business sensitive information. 3/n
2 replies 0 retweets 1 like -
Numbers of customers, volumes of data, features that are coming soon, etc. We'd have to spend effort removing all of that, but the folks who write and edit COEs have other things to do! 4/n
1 reply 0 retweets 2 likes -
Lastly, like anything we make public, there are perception concerns. A document like a COE can be a gift to cynical critics, it contains a neat list negatives. To a strong technical audience, this is a positive! But not to everyone. 5/n
1 reply 0 retweets 1 like -
It takes a lot to contextualize it and demonstrate the rigor, professionalism, and energy thrown at correcting the errors. But that's assumed and implicit in our COEs. It's the water we drink. 6/n
1 reply 0 retweets 1 like -
Amazon's best practices and what is out there as general DevOps best practices have diverged to a small degree. We're confident in our practices and our record, our availability speaks for itself, but it takes additional energy to explain why we do things our way! 7/n
1 reply 0 retweets 2 likes -
In summary, we're working on it, we know it's interesting material, and we can benefit too from more scrutiny, more feedback, and a bigger braintrust! But those are why :) n/n
1 reply 0 retweets 2 likes -
Thanks, appreciate this thoughtful response! Will mull this over and may end up blogging followups. Would hearing from customers that there is compelling benefit help with prioritization of the necessary work here? (1/2)
2 replies 0 retweets 0 likes -
If so what is the best way for AWS customers who believe there is value in COEs being made public to provide that feedback?
1 reply 0 retweets 0 likes -
I never remember to thread correctly ugh (3/3)
1 reply 0 retweets 0 likes
Customer feedback is the most valuable currency at Amazon, it always helps! Tweet it at me or any of us, or email! colmmacc@amazon.com. We review the general parameters of what we can share about two or three times a year with the senior exec team.
-
-
Sweet, thanks! I'll keep this in mind and will consider bringing up this topic when chatting reliability (since many folks are AWS customers!), whether there's a goof way to marshal support, etc.
1 reply 0 retweets 0 likes -
I've had some interesting discussions with folks on related topics, I a better framing is how AWS can help its customers learn from failure/incidents. Furthermore my belief is this can/should include *stories and deep examples* as well as "packaging best practices".
0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.