Has anyone gotten S3 working as a Download Site?

Good morning Justin,

Jeff Atwood has a good article about emulating folders in the Amazon S3 service (Using Amazon S3 as an Image Hosting Service). So the way you'd do it is to create a download site URL that wyBuild understands. Something like this:

http://s3.amazonaws.com/your-account/updates/%file%

Then upload your files with the object names prepended with the "updates/" "folder" name. Like "updates/wyserver.wys", etc.

Does that make sense?

Hi Sam,

Thank you for the help. I got that far, but the specific issue, which I completely forgot to elaborate on in my initial post (!), is that it can't be a public folder since it is for an internal deploy. I will therefore need a pre-authenticated url, and I am not sure if anyone has gotten that working for calls not using the Amazon API.

Any thoughts?

Thanks!Justin

Figured it out! I used http://www.smestorage.com/wiki/cloudftp/ to create an FTP endpoint to my S3 files. As a side note, supporting S3 directly via the API would be a cool feature to add!

Thanks!

I will therefore need a pre-authenticated url, and I am not sure if anyone has gotten that working for calls not using the Amazon API.

As a side note, supporting S3 directly via the API would be a cool feature to add!

Are you talking about supporting downloading from S3 or uploading to it? We do plan to support uploading to S3 (it's on our roadmap).

Both, really. I actually don't really see the difference between downloading and uploading -- when would they ever not be the same place?

They would be if you're using traditional HTTP or FTP download sites. That is, you don't want to give your customers write permission to your web servers.

Makes sense. In the case of S3, you can give different permissions to different users, so you could restrict the fetching while empowering the updater with write privileges. Can't wait to see the feature added!

+1 for Amazon s3 support.

We don't use S3 here at wyDay, but we do plan to support it. However, since we don't use S3 here we'll have to do some research about the various ways of accessing S3.

For instance, it's my understanding that S3 can be accessed using plain old HTTP (and wyUpdate supports HTTP). Isn't this good enough? If not, what other method would you prefer to access your S3 account (documentation links preferable)?

Give me a use-case so I can wrap my head around it.

Hi Sam,

Use case for s3 would be to simply deploys the updates from within wyBuild (rather than it uploading to a ftp).

In s3's scenario you would enter your AWS S3 credentials and bucket name, then wyBuild would upload the new versions of our applications to that bucket using the Amazon AWS SDK via a Rest API (from memory).

You can use this SDK within your wyBuild Application:

http://aws.amazon.com/sdkfornet/

I use S3 for my updates...it works fine. Just use the standard link to the wyserver file and upload the update packages to the same directory. Haven't had any issues doing it.

I too use S3 no problems.

I was referring to the publishing of updates to accept S3 as well as FTP for ease and an automated process.

You're right. We'll get an S3 account and start playing around. We'll shoot for the 2.7.0 release of wyBuild.

Hey Sam, is this still on the radar? Is there an ETA yet for 2.7.0? Our software depends heavily on this feature becoming a reality, as our current band-aid method has several flaws.

I thought you just needed S3 as an upload site? Why can't you use HTTP accessible download sites from your S3 account?