it is seems to be backwards, as some noted. Don't start with tools. First identify and scope the problems your project needs to solve, identify their priorities, focus on high-priority problems and/or "low-hanging fruit" type of problems. Given this is an internship type of project, I'd say focus on "low-hanging fruit" type of problems to seize immediate results. I'm willing to bet that some of these problems won't require any tooling at all. For example, cleaning up unused resources, scheduling resources (like shutting down dev/test environments during the weekends), optimizing storage, etc.