4 ms·
Boggles my mind that AWS still doesn't support something like this.
by jcims 5y ago
Boggles my mind that AWS still doesn't support something like this.
- jiggawatts 5y agoAWS and Azure have different philosophies: Azure uses a unified resource manager that has everything in "one place". AWS uses a "federation of systems" with almost nothing in common, except for authentication. Azure's approach is more consistent and makes things like resource graph relatively easy to implement. AWS's approach is more robust against failure, because the various service offerings are more independent and have fewer common failure points. This isn't just theory, it matches my experience pretty well. I hate how in AWS I have to switch portals to go from service-to-service, whereas in Azure the "Resource Groups" contain all related resources in one place, even if it's a random mix of IaaS and PaaS. Conversely, I've been bitten by several wide-spread Azure outages. Repeatedly. It all depends on your business requirements. For me, the consistency is more important. For other people, availability is far more critical.
- jcims 5y agoAgree on your points. I just think they could define a standard service discovery/enum interface and leave the implementation to the product team. Basically Config.
- nathanwallace 5y agoAWS is trying to do this with Cloud Control [1]. It's a common interface for resource inventory and provisioning and seems to come out of internal APIs for the CloudFormation service. It currently seems better suited to provisioning use cases and is still fairly limited as an inventory interface [2]. 1 - https://aws.amazon.com/cloudcontrolapi/ https://aws.amazon.com/cloudcontrolapi/ 2 - https://steampipe.io/blog/aws-cloud-control https://steampipe.io/blog/aws-cloud-control