4 ms·
I think the mindmap drawn can be simplified further down into a couple of networking concepts, then most of the relationships and arrows go away, and the AWS co
by bfung 3y ago
I think the mindmap drawn can be simplified further down into a couple of networking concepts, then most of the relationships and arrows go away, and the AWS concepts can be mapped to other clouds, and even your own home network.
https://news.ycombinator.com/item?id=18925350 https://news.ycombinator.com/item?id=18925350 is an excellent visualization of the basics. Start with what a network is, what’s inside and what’s outside, and the mental model becomes way easier. Then the AWS features make a lot of sense even w/o all the details.
- dleeftink 3y agoExcellent share, thank you. In comparison, the OPs diagram offers a 'plan-it-yourself' type view of the provided AWS services, and as a mindmapping artefact, has no doubt aided the author to come to grips with the complexities of AWS. And the result is something that summarises a complex system clearly and succinctly. Thanks for sharing OP, I'll be consulting this the next time I'm wading through the AWS forest.
- mparnisari 3y agoThanks!
- dleeftink 3y agoIt's great to see learning artefacts becoming teaching artefacts, especially when they surpass the clarity of the original resources.
- Bluecobra 3y agoAgreed, my network diagrams for AWS basically has nested squares. For example, a subnet inside an availability zone square, and that is inside a VPC, and that square is inside a region. Kind of like this but looks nicer: https://images.edrawsoft.com/articles/aws-diagram-examples/example1.png https://images.edrawsoft.com/articles/aws-diagram-examples/e...
- mparnisari 3y agoYes the book I made the diagram with had lots of these drawings. IDK I preferred a mind map to solidify my understanding :)