Brian

Former Well-Architected Operational Excellence lead for AWS.
Left AWS. Now building a framework/tools for rapid feedback on DevOps & Cloud Adoption strategies.

[Brian @BrianCarlsonQED]

@dario_goldfarb @QuinnyPig For the "obvious" quick wins. Oversight, ignorance, or a specific reason led to the existing architecture.
Starting with establishing a relationship between application and development teams, fostering collaboration, and answering these questions is the most enduring quick win.

[Brian @BrianCarlsonQED]

@dario_goldfarb @QuinnyPig No one wants to discover design flaws via quick win breaking changes.
ReqDef is needed at the start to understand why a security best practice wasn't followed so that the design can be remediated (if needed) & the quick win safely applied.
And yes, thorough ReqDef is ongoing.

[Brian @BrianCarlsonQED]

@johncutlefish Being aware of how you are influenced by conditions and circumstances can help you view/interpret interactions in more positive ways.
Awareness of stresses in the environment may help you ask the right questions to identify underlying issues that you can help address.

[Brian @BrianCarlsonQED]

@johncutlefish We can't truly understand what may be influencing a person's behavior.
There may be work/life stresses or difference in cultural norms, challenges with language, social skills, and non-verbal ques...
We can look at how these impact us & for a given context how we can do better.

[Brian @BrianCarlsonQED]

@QuinnyPig Non-compliance, or not being able to demonstrate compliance, with regulatory requirements can come with steep fines.
Even if you decide to prioritize some quick wins, it shouldn't be to the exclusion of figuring out your actual requirements.

[Brian @BrianCarlsonQED]

@QuinnyPig There is a fundamental problem with the model.
It doesn't start with determining your security requirements, whether or not they include regulatory compliance requirements.
Security is expensive. What, how much, when, where, and why need to be informed decisions.

[Brian @BrianCarlsonQED]

@jhscott If improving reliability is the goal:
When the expected financial impact (probability x expected loss) from cloud provider outages exceeds the cost to implement and operate on a second cloud provider over the same time.

[Brian @BrianCarlsonQED]

I'm very pleased to have contributed to the #AWS Well-Architected #Sustainability pillar. Every action we take to reduce our sustainability impact makes a difference. By happy coincidence, those changes often reduce your costs as well.
https://t.co/Q03x5kkyEq

[AWS Architecture @AWSArchitecture]

NEW! AWS Well-Architected Sustainability Pillar. Get the latest design principles to learn, measure & improve your AWS workloads towards sustainability targets, using environmental best practices for cloud computing. #awswellarchitected #sustainability https://t.co/FC7oH914HU

[@[email protected] @MissAmyTobey]

reminder for people who probably won't read this: people are not fungible. not in any job, really, but especially not in teams doing knowledge work where the meshing of personalities and shared context has a such a huge impact on outcomes

[WhatWentWrongThisWeek @WhatWentWrongTW]

Join us Tues June 29th Noon EST when we discuss Disaster Recovery planning on WWWTW https://t.co/E5Q8aVfiSe.

We will answer your questions and take you from "not knowing where to start" to "knowing what to do when and why".

This isn't a small topic. It'll take a few episodes.

[Brian @BrianCarlsonQED]

We are about to go live with
"Where did all my databases and backups go?"

Join us on Twitch as we discuss what went wrong and how it might have been avoided or mitigated through operations and architecture choices.

2:00pm EST on June 15th https://t.co/XrMtc8EJwG

[Brian @BrianCarlsonQED]

@votecapgood @lilbobbypowers @jhscott How are you measuring nines? How are you measuring availability? Transactions completed/transactions attempted?

Cost optimal is getting the results needed in a timely fashion (happy customers). If there is a cost to exceeding those requirements then you are wasting money.

[Brian @BrianCarlsonQED]

@votecapgood @lilbobbypowers @jhscott Anomalies in user behavior such as initiated transactions can be compared in real time to expected values. Trends in the same may reflect deeper sentiment. Abandoned transactions/activities, especially on new features, may indicate dissatisfaction. Nothing beats talking to them.

[Brian @BrianCarlsonQED]

I'm a big fan of alternative learning and engagement methods. I like trivia, especially when then answers make you think.

[Amazon Web Services @awscloud]

Learn more about the 5 pillars of the AWS Well-Architected Framework here: https://t.co/YIKBBg2oHg
#AWSQuizoftheDay

[Brian @BrianCarlsonQED]

@benji_potter has some great advice around your AWS console...

https://t.co/TD6tDMnsPs

[Brian @BrianCarlsonQED]

Here's a fun blog post on aggregating alerts and using that insight to determine criticality...
https://t.co/B7UCXdfFDo

[Brian @BrianCarlsonQED]

@mikejulian Let the output influence your assessment:

Translating into multiple languages?
Test their understanding of internationalization/localization.

Want them to make technical content accessible?
Give them a SME, a topic, & time to demonstrate.

And ask their thoughts on plagiarism.

[Brian @BrianCarlsonQED]

The new AWS Podcast features "What's New with Well-Architected" and the "Cost Optimization" pillar.

Nate Besh brings a ton of perspective on creating financial awareness, tools to gain insight on the value generated by your spend, and making it visible.

https://t.co/DwwF8IscT8

[Brian @BrianCarlsonQED]

@MahanthJayadeva @benji_potter @SanDiegoPoke @setheliot @ericpullen I really thought I was about to get Rickrolled.
The reality was a huge letdown @MahanthJayadeva.