Hi Aseem, thanks for your insightful questions!

The blog section on creating S3 buckets using Ceph S3 credentials might have caused confusion. I'll update it to clarify that the buckets are created within Ceph, not AWS S3 and I'll provide more context on why I used both in my deployment, likely due to bridging on-premises Ceph storage with AWS services or leveraging specific AWS S3 features.

Explanation of using both AWS S3 and Ceph S3:

While both offer object storage, they often serve different purposes in a deployment:

AWS S3: Leveraged for its global reach, scalability, and integration with other AWS services.

Ceph S3: Often favored for on-premises storage, private cloud deployments, or cost-effectiveness.

In my blog, the use of both was likely motivated by a specific need to bridge on-premises Ceph storage with AWS services or leverage AWS S3's features for certain workloads.

Exposing Ceph Buckets with AWS CloudFront:

While direct CloudFront integration with Ceph isn't available, you can expose Ceph buckets to the internet using the Rados Gateway (RGW) component:

Enable HTTPS on RGW: Configure RGW to use HTTPS for secure access.

Point CloudFront to RGW: Set up CloudFront to distribute content from your RGW endpoint, effectively fronting it.

I hope this comprehensive response addresses your questions! If you have any further inquiries, feel free to ask.