[offmycloud]

I think it's time for AWS to pull the curtain back a bit and release a JSON document that shows a list of all internal service dependencies for each AWS service.

[throitallaway]

Would it matter? Would you base decisions on whether or not to use one of their products based on the dependency graph?

[UltraSane]

It would let you know that if if service A and B both depend on service C you can't use A and B to gain reliability.

[withinboredom]

Yes.

[mparnisari]

I worked for AWS for two years and if I recall correctly, one of the issues was circular dependencies.

[cyberax]

A lot of internal AWS services have names that are completely opaque to outside users. Such a document will be pretty useless as a result.

[dmytrish]

+1, SREs can spend months during their onboarding basically reading design docs and getting to know about services in their vicinity.

Short of publicly releasing all internal documentation, there's not much that can make the AWS infrastructure reasonably clear to an outsider. Reading and understanding all of this also would be rather futile without actual access to source code and observability.