Okay, weird to call it S3, if it is just object storage somewhere else. Its like saying "EKS" if you mean Kubernetes, or talking about "self hosting EC2" by installing qemu.
AWS S3 was the first S3-compatible API provider, nowadays most cloud providers and bunch of self hosted software supports S3(-Compatible) APIs. Call it Object Store (which is a bit unspecific) or call it S3-Compatible.
EKS and EC2 on the other hand are a set of tools and services, operated by AWS for you - with some APIs surrounding them that are not replicated by any other party (at least for production use).
Okay, weird to call it S3, if it is just object storage somewhere else. Its like saying "EKS" if you mean Kubernetes, or talking about "self hosting EC2" by installing qemu.
> weird to call it S3
I feel that is a bit of an unfair assessment.
AWS S3 was the first S3-compatible API provider, nowadays most cloud providers and bunch of self hosted software supports S3(-Compatible) APIs. Call it Object Store (which is a bit unspecific) or call it S3-Compatible.
EKS and EC2 on the other hand are a set of tools and services, operated by AWS for you - with some APIs surrounding them that are not replicated by any other party (at least for production use).
You can even do S3-on-ZFS
Which solutions do you find stable?
Wouldn't consider myself qualified to answer, but I'm not aware of any problems we had with our Oracle ZFS storage appliance.
S3 is both a product and basically an API standard.
Garage talks the same S3 API.
GarageFS S3 compatibility https://garagehq.deuxfleurs.fr/documentation/reference-manua... vs
SeaweedFS vs. JuiceFS https://juicefs.com/docs/community/comparison/juicefs_vs_sea...