With the increased evolution of cloud computing, new cloud security and governance practices are often postponed because of time constraints, absence of skilled people and knowledge gaps in small and medium companies.

To manage any organization’s risk and security standards, we created a streamlined rules section and a new feature called Rule Bundles.

Each bundle is a collection of rules focused on enabling organizations to achieve a specific external compliance framework or follow industry best practices for an AWS service. Rule Bundles quickly identify failing rules, understand where they fit within the organization’s AWS ecosystem, and more easily fix their root cause.

I led an initial kickoff workshop with the product manager, front and back-end developers that helped to shape the experience, learn about industry standards, gather information from internal and external users.

I sketched different ideas for the onboarding, overview and rules display in bundles.

At this stage, paper gives the ability to quickly generate interesting ideas before launching into development.

Creating individual prototypes for each flow allowed me to to get specific feedback on each part.

Later, all the insights were combined into a complex prototype.

Whilst you can have all the userflows in one complex prototype, you can’t prevent dead ends. When you test it, not all the status changes and data updates can be reflected if you don’t add logic.

To better understand the complexity of the information, I conducted research on the data structure for the bundles and frameworks that will be supported.

Then, I defined the Information Architecture that will be used to show the different pieces of information with enough flexibility to have a standard template that will enable future additions and updates for new frameworks.

This work was iterated collaboratively with the backend developers, keeping in mind the technical details and constraints.

After researching, I mapped the structure into the interface. This is where the users can see the detailed information about each rule with the documentation.

The challenge was that some rules are the same in different bundles. So we needed a way to show each bundle details.

After exploring different variations, the nested tabs alternative was selected. Although it seems to be a complex pattern, we wanted to test an initial version and get more feedback.

Some bundles have rules in common, but with different names. In order to show this subtle differences without cluttering the UI, I reused the rule categories to show more information on hover.