Hi everyone! I'm starting a position at a company as a "cloud architect"... at least that's the title, but I think my employer isn't very sure about what they expect from me.
Anyway, the first thing I noticed is that they've been very messy with their use of AWS resources: lots of people have created resources without following any standards, using arbitrary names, no tags, and everything created from the console (the company has started using IaC, but it's not enforced everywhere). That kind of mess.
To start, I decided to propose some guidelines for the use of REST APIs, and I'm doing some research to get ideas. So far, I've mainly found information about best practices for developing REST APIs, but now I'm looking for something more high-level: how should the scope of an API be defined (when should two APIs be merged, or when should one be split)? Also, any ideas on how to structure repositories for the IaC of REST APIs?
For now, those are the main questions I'm stuck with. If you have any comments or recommendations, I would really appreciate it.
Regards!