It is severely outdated. I'll discuss with the MVPs whether it should be removed. As you can see from the component's version page, the last version is marked "under development", and was published over four years ago, by someone who hasn't been active since.

Hi Kilian,

I got it working. But the component is half broken.

We are able to use the component to write files on amazon S3.
But normally the component should return multiple values like 'url' esc..
The main problem is, it doesn't return anything, so I think that part of the API in the component is very outdated.

I wouldn't delete it, since it is still partially working. We just need someone with .NET knowledge to update the API.

We are considiring fixing the component whenever we have time, since our production environment depends on it.
Whenever we fixed the broken part of the component we will contact you with a newer and fixed version.

Greetings,
Niels

Hi Niels and Kilian,

I ran into the same problems and this is a useful component. I do not have the development (let alone .Net) skills to make this a solid component again, but I believe I did manage to get it to work with an upgrade to the new AWS SDK. Maybe you should give it a try Niels, it works for me? Keep in mind that setting the right access policies in S3 is crucial as well.

See attached.

Denis.

Niels, Denis,

I managed to contact the original author, and I'm now a team member. So if you agree on the usefulness of the new version, I'd be happy to add you to the team.

Update -

I have updated the SDK from version 1.5 to version 4.0.

Could somebody check if it works now?

Claring,

Thanks for working on this. I plugged in your new component and just tested the FetchFile functionality. It did not work for me. Unfortunately, I do not have the time to debug it right now, maybe later, as the version I posted earlier in this thread works for me.

I am in need of this component as well. Could someone give me an example of how to use it?

The two functions I need most are saving the files to S3 and fetching the URL. Would be really helpfull if we get this wokrking.

Thanks in advance,

Erik.

Update, I noticed a difference!

But only in the FetchFileUrl function, I was still using HTTP, but I recall reading that the Amazon stopped accepting HTTP calls.

Denis Mulder could you check if it works in the new version? 1.02?

Hi Claring,

I still do not get it to work with your version 1.02. I tried to fetch the URL and save a file, both failed. Not sure why, I have not been debugging, just swapped my version of the extension with yours and then it fails.

That's so weird.....

So this time I've taken your xif as a base, let me know if the attached xif works.

If you have time could you please test the version attached to this message too.

Let me know if either of them work. ( I can only seem to attach 1 file per post... sorry about that )

Hmm, we could always do this experiment some other time.

Thanks alot for testing!

I will upload this version.

Hi Guys, I would really appreciate an example of this one, as I am not sure about the fields in the S3File structure. Could you give me a quick overview on that?

Thanks for all the work,
Erik.

Hey Erik,

Here's a list:

Name = Not being used
Bucket = The bucket name
SubFolder = The folder where the file is located
Key = Looks like this is the file name
Content = Used in update, and save (and is filled in fetch), I suspect this is the binary of the file
Uuid = Not being used
url = Is filled in when using fetchfileurl
KeyCopy = Used for duplicate file, is a duplicate of the Key (which looks like it's the file name)
ResponseCode = Not being used
NewSubFolder = Used for duplicate, which is also used as the destination folder.

If you still have any questions please let me know.

Hi All, 

I tried using all the extensions uploaded in this thread and i'm having an issue. Please see below screenshot of the error encountered.

Can somebody help me understand the error? I'm not sure if i'm missing something on my aws account configuration.

Thanks and have a great day ahead.

Regards,

Froi