Overview

After working on the Cyber.AWS capstone for an estimated 6 months, there has been a lot learned. From various AWS services, how to use policies, to general organization skills for a project of this scale. This is an overview to discuss the steps that should be taken from the beginning to the end of the next Hybrid-cloud Capstone.

Research

In our research phase, we spent the second sprint of the first semester leaning AWS. However, we were learning AWS as a whole and not with the scope in mind. Our mind map was a jumbled mess and so was the rest of the project. We were all trying to figure it out as we went along. This will stay true to the new group, however, here are some key notes to focus on when you are learning an entirely new Cloud Provider.

What will be useful for the Hybrid-Cloud?

• How are you going to connect the two?
• How are you going to organize your new environment?
  • Are there any services that are used for Hybrid-Cloud? (System Manager in AWS)
• What are you trying to connect?
• What are the requirements for the connection?
• How do you manage Security in the new environment?
• How do you manage users in the new environment?
• How does the Cloud Environment work with On-prem and Cloud accounts?
• How much does this cost?
• How do you manage cost?

KNOW WHAT YOUR CLIENT WANTS

If your client is giving ambiguous answers, go back the next week with more research and give two options rather than asking what to do entirely. Your client wants a working product by the end of this capstone, but the client isn't the one doing the research. That is where you come in to try and guide the client to the best route, while still listening to their wants and needs.

First Steps

The first steps will be taken directly from your research as well as adding in some new Organizational tips to help the environment run smoother.

• Focus on the Cloud Environment
• Create policies or security groups to work with the environment you are trying to create
• Set up Budgets

Organizational tips

• What is the naming scheme?
• How are you going to separate out infrastructure and classes?
• How can you plan for automation

While you work

This is where the true grind comes in. Research should be at a minimum by this point and the focus should be on implementation.

• Is your Cloud organization ready for On-Prem?
• Connect to your On-Prem
• Automate Everything
• How can you go back and improve your past work? Update your mindmap? Update your sprints? Pivot? or just double down and make what you have better?

Concluding Steps

This is the end, so I hope you were taking great notes. Organization of your GitHub will be crucial for this project. If someone were to see your landing page, would they know what is going on? Documentation is key, not just for capstone, but for any big project like this. It is a helpful tool for you to go back and relearn or for others to pick up where you left off.

• Update Github
• Last check-ups with the Client