Question about Limitation on Serving Non-HTML Content

Website, Application, Performance DNS & Network
1

Hello, I know this topic is already asked many times, but let me ask according my condition. I hope that anyone who had similar experience would give me an enlightenment.

I have a website for conducting online exam. An institution (a business) can make their own account and then they can begin uploading their content into it. The content are:

  1. Their business logo, header images (for their own portal), and profile pictures
  2. Set of questions, usually it contains mostly text, several images, and maybe audio files (max 4MB each file) for listening question type.

I hosted the images and audio files on AWS-S3, and I have one CNAME DNS (proxied) with Cloudflare to my S3 Bucket. Currently, the DNS is covering the business logo, header images, profile pictures, and assets files (CSS, JS, website images). The audio and images from question sets directly taken from S3 temporary URL, since I am afraid that Cloudflare will disable my account (Pro Plan).

So for this matter, I would like to ask about my condition regarding Cloudflare TOS “2.8 Limitation on Serving Non-HTML Content”, is my site considered as “serving a disproportionate percentage of pictures”? For additional information, my site currently serve about 40K users a day, conducting online exam. Serving the question content (contain images) from proxied Cloudflare DNS is my goal to minimize cost, since Cloudflare will cache the images (right?).

If I am breaking their TOS, can I just turn off :logo: to :ngrey: and I am good to go? Or maybe any advice for me to select which part of my content that should be out from Cloudflare proxy?

Thank you.

2

(I am not a lawyer, nor am I a Cloudflare representative. Don’t trust your business to something some random person on the Internet says etc.)

A host name that is :ngrey: will never have an issue with 2.8.

Yes. Serving “normal” web content is fine. It sounds like this applies to you

You get into issues if you are hosting imageboard type sites that have an excessive payload of images on each page compared to whatever “normal” is.

Issues will also arise if you are using :orange: to serve other rich media, such as audio and video files.

The really simple solution here is to use R2 as a replacement for S3. You will avoid the AWS egress fees, and R2 is excluded from 2.8 (check out the Supplemental Terms linked to in 2.8)

3

Ok thanks for your answer, I will include R2 into my consideration.

4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.