<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<title></title>

</head>

<body>

<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">

<div>

<div>Hello everyone,<br>

<br>

This is the Green Team, we focus on the system performance and user experience. We find a topic that talks about why the AWS console design is bad and how to improve it.

<a href="https://www.gorillastack.com/news/redesigning-the-aws-console-what-i-would-like-to-see/">

https://www.gorillastack.com/news/redesigning-the-aws-console-what-i-would-like-to-see/</a><br>

<br>

As for the perspective of our team, we should observe and learn from the cases we used. AWS console is a good case for bad user experience. Based on this case, we found more posts talk about the good design of a web page.<br>

<a href="https://www.elegantthemes.com/blog/resources/10-rules-of-good-ui-design-to-follow-on-every-web-design-project">https://www.elegantthemes.com/blog/resources/10-rules-of-good-ui-design-to-follow-on-every-web-design-project</a><br>

<a href="http://johnsteinmetz.net/blog/ux-why-is-amazon-so-bad-at-user-experience/">http://johnsteinmetz.net/blog/ux-why-is-amazon-so-bad-at-user-experience/</a><br>

<br>

Additional, we also keep an eye for performance. Which is the practical optimizing for EBS.

<a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html">

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSPerformance.html</a><br>

<br>

-Green Team<br>

</div>

</div>

</div>

<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">

<div></div>

</div>

</body>

</html>