When MoonBank was initially set up, infrastructure resources were set up on-the-fly by various members of the MoonBank technical team. Several different on-premises and Software-as-a-Service solutions are being utilized. Think about options to solve the issues below.
DNS: DNS is being hosted by the domain registrar, and changes take 24 to 48 hours to propagate.
Graphics/blob Artifacts: Company graphics, images, etc. are being emailed around to the different teams.
Continuous integration pipeline: MoonBank is currently using a paid GitHub.
Docker repository: Containers are currently published using a paid Docker Hub account.
Authentication: The technology staff is currently having to set up separate authentication and hard-coding usernames/passwords everywhere.
Data load: Over 300TB of existing data resides on some early development servers. This data needs to be moved to Google Cloud, and the network connection won't be able to handle the data transfer.
Data processing: One of the data scientists did some early work using Apache Spark on an Apache Hadoop infrastructure. This needs to be moved to Google Cloud very quickly and kept operational until it can be re-platformed.
Email: Email is currently running outside of Google Cloud. This is MoonBank's primary authentication system. Users don't want to have to maintain TWO different passwords. What are our options for Single-Sign-On (SSO)?
Permissions: Google permission primitives (Owner, Editor, Viewer, Browser) are not granular enough. Pre-defined roles are not exactly what we need (some changes can be made). How can we handle our specific needs?
Security: News about cloud bucket breeches/security issues are all over the news. How can we monitor buckets and other systems for security?
Security: Only MoonBank credentialed IT staff and automation should be able to access cloud resources directly. How will this be enforced?
Application alerts: The operations team needs to monitor our cloud operations and receive alerts, including custom metrics. How will that be handled?
Monthly account statements are presented to customers in PDF format for download. How will we create and store these PDFs, and how will customers be able to access?
Don't leave money on the table
You are always cost omptimizing, as long as all requirements are met, chose the cheapest solution
Obey the Principle of Least Privilege RFC4949 - Internet Glossary
Use Seperation of Duty RFC4949 - Internet Glossary
Don't use default in production