eagles9999 wroteHave you checked the permissions on the S3 bucket. If they are read/write I would have thought that you could write to it and you can definitely read from it
Well, if you have your S3 content as "Public" (Which mine will not be", then you can use standard URL HTTP GET and POST commands. However, for private data, you will then need to authenticate yourself.
If you want to cal S3 from a "Client" side, you will use REST to do "Data Accessing", but if you need to do from a server side (Like Aware server), then you need to connect via SDK (.Net, JAVA, PHP and Python).
The biggest problem with S3 Objects (lets say a large image or PDF (10MB)) is that, first it has to be uploaded to aware server and then using SDK it has to be streamed to S3 and then become converted back to an object and stored in a bucket. When a use needs that image, you have to do reverse. You have to stream that object first to Aware, save and convert it back to an image, before Aware can send it back to user. This can get very messy and slow.
Found a much better solution, when I can get an SSD "Block storage up to 100TB"and mount/attach it to my Instance as just a disk drive, i.
i.e. Drive D:, where in Aware I can set my Image patch to D:\myImages\abc.jpg and Aware uses that, but all the images are actually stored some place else and not on my Instance storage. BUT, this BLOCK storage is 3 times more expensive than S3, but much faster than S3.
However, I found a MUCH BETTER solution than
