This support forum is no longer in use. Please use the Cloudinary Community at https://community.cloudinary.com/ to receive assistance from other members of the community and from Cloudinary's support team. For account-specific questions or if you believe that you've encountered a bug, please contact the Cloudinary team directly via the "submit a request" option on this support site.

S3 wellknown files not working

Follow
Avatar
CloudAccount WARDA

Hello to everyone,

I'm doing an integration with Cloudinary from my S3 buckets on AWS. We followed the guide for the setup: https://support.cloudinary.com/hc/en-us/articles/203276521-How-do-I-allow-Cloudinary-to-read-assets-from-my-private-S3-bucket- 

The issue that we find out is that the read from S3 buckets is working also if the .wellknown file is not present inside the bucket. In the specific we need to allow only one specific cloudname to read from the specific bucket.

How can we achieve that?

Best regards

0

Comments

6 comments

Sort by Date Votes
  • Avatar
    Loic Verger Del Bove

    Hi there,

    Thanks for reaching out.

    The .wellknown file is actually only checked 1 time when setting up the bucket that's why it is still working if you delete it. The important part is when you give permissions to Cloudinary via the permissions tab and since this configuration is specific to a bucket, if you only set it for 1 bucket then we will only ask this bucket and not the others.

    Hope that helps.

    Best,

    Loic

    0
    Comment actions Permalink
  • Avatar
    CloudAccount WARDA

     Hi Loic,

     

    we tried to setting up and other test account created without the .wellknown files but Cloudinary is still working also without the file. 

    Is there some extra configuration that we need?

    Best regards,

     

     

    0
    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov
    • Edited

    Hi,

    I've tested on my side but was not able to reproduce this. You won't need any other configuration changes and the .wellknown file is required by default.

    To look into it further, please share with us details and examples of the steps you've performed on a brand new bucket and the results and we can then check our logs. If you'd like to share this with us directly (not as part of this forum post) then you could raise a private ticket with us via - https://support.cloudinary.com/hc/requests/new

    Looking forward to your updates.

    0
    Comment actions Permalink
  • Avatar
    CloudAccount WARDA

    Hi Aleksandar,

    the test that we did is the following:

    • We create this Cloudinary account1
    • We configured wellknown on S3 bucket per account1
    • With account1 we're able to integrate Cloudinary with s3
    • We create a new Cloudinary account2
    • We didn't configure wellknown on  S3 buck for account2 account
    • At this point account2 is still able to read files from our s3 bucket -> the bucket is the same that we were using to read with account1.

     

    The other account that we create has te following account name: test-seecommerce-wrong.

     

    0
    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov

    Hi there,

    Thanks for sharing those steps and the account that you were testing with.

    After some digging, I found out why I wasn't able to reproduce, but you were able to. This doesn't reproduce when performing a synchronous upload (which is the default and the one I was testing with) but based on your account that you shared, I checked the logs and saw that you were performing an asynchronous (async=>true) upload.

    I've raised this internally with our team to also review and I'll keep you updated on the progress and resolution.

    0
    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov

    Hi,

    Just to close the loop on this one - a fix was released for this Async flow. Please test this out again and let me know how it goes now?

    0
    Comment actions Permalink

Post is closed for comments.