I am using minio on internal upload only. For example, discourse on 192.168.1.5 and minio on 192.168.1.6:9000. When I browse in Chrome, it tries to request 192.168.1.6:9000 which will not work.
I expect it to load from cdn.example.com which like image in post.
This problem seems to happen here as well. If you upload an image, the one you see in preview is discourse-meta.s3.dualstack.us-west-1.amazonaws.com instead of meta-s3-cdn.freetls.fastly.net.
Yeah this is indeed the case, preview does not use CDN, hiding the S3 origin from clients is an unsupported setup atm, longer term I expect even more trouble when we support direct to s3 uploads
I also found out the images uploaded are allowed to view by public. If there are future updates on this, please do not set it if CDN is set. This is because it bypass the bucket policy to enforce all objects must go through CDN.
Então, ainda estou confuso aqui… mesmo com minha URL do CloudFront em “s3 cdn url”, todas as imagens enviadas (na prévia ou não) estão usando a URL s3.dualstack e não a minha URL do CloudFront/CDN.
Isso parece ser um bug, não um recurso, já que exige que você tenha ACLs públicas para seu bucket S3. Parece que isso foi relatado aqui há anos, mas não foi corrigido: S3 CDN URL ignored when uploading into posts