Sprint Statement:

The goal of this Sprint is to get organized. From understanding our client's wants for our project to creating a layout to go forward, and solving any unresolved issues from last semester. Our focus is also on creating effective and innovative solutions for the separation of user environments.

Week 1

Week 1, we will need to create a new organization, set up billing, and create organization units before we can start to add accounts. Once the OU's are created to represent cyber.local's hierarchy, we can then add users.

Create Organization | Tanner (As we face various problems, I am putting creating a new organization on hold until we can smoothly transition into a production environment. Our testing will continue in the organization that was created last semester.)

Create OU | Tanner

Set up billing | Alex

Credit Card information | Alex

Maximum Limit | Alex

Separation of Users | Noah & Tanner

Kickoff meeting A meeting will be organized with the client to arrange the name of the new organization, implementation of the credit card, and any other features requested by the client. This will also count as our week 1 progress update

Week 2

In week 2, we will need to create users, optimize our budget reports, and create a propagated billing system.

Creating organization users | Noah Script

Budget Reports | Alex

Propogated Billing | Alex

Separate Users | Noah and Tanner

Progress update At the end of week 2, we will need to do a progress update to make sure the team is at a good point.

Week 3

In Week 3, we will join AWS with our on-prem AD, this will allow us to potentially use federated logins, or copy our policies from AD

Join AD | Whole team Progress Update

This week, I found that natively AWS member accounts have independent environments, allowing the separation of users. I have worked on creating SCP policies to prevent users from accessing billing and editing policies for the organization. Admin accounts are also able to view Members' accounts and environments. Next week I will set up Logging for the organization and update policies as necessary. - Tanner

An update following the first sprint, have created a few scripts to automate various tasks, setup basic network connections. Solved separated users...(Security Policies impacting us). Working on AD Connector.. a bit more complicated than I originally thought. - Noah

Demo We kept our test environment, but deleted almost everything. Solved separation, automation and other various tasks. Currently working on ad connector test and documentation. Would like to rebuild the Github.

Reflection The sprint went well. We had a bunch of breakthroughs in areas we were struggling. Due to the breakthroughs we have had a pretty good sprint. I believe we solved key issues which were limiting us from continuing. We also changed the path of the project slightly and believe this will help us be more efficient. By starting smaller and then getting bigger at the end.

• Sprint 1 Project video