It's also at it's heart distributed state management, and that is generally speaking very hard to do for anyone to do correctly.
You don't distribute state mgmt in S3 alone since there is no lock mechanism.
Eventual consistency is a valid distributed strategy.
If there is but one direction of distribution, e.g. when you deploy config changes, and never replace objects, this suffices.
Unix philosophy for services encourages the user to model their problem rather than their architecture. Edge computing is a brewing shitstorm at companies which are not trending in this direction.
Care to elaborate? Like every sentence you wrote?:-)