Hi Jeroen,

I see you use the Windows GUI tag, does that indicate you are using the Windows GUI? The Windows GUI may not be able to reach the AWS S3 bucket and therefore cannot read or download the file. Does that sound plausible?

When using external storage like AWS S3 you'll effectively create a link to the file. The file will be downloaded once you try to open it. The data type you can use for this is either varchar or nvarchar; it will store the location of where the file is located; I think a relative path as the base path can be modified in IAM.

Hi @Mark Jongeling,

Thanks for your reply!

The Windows GUI may not be able to reach the AWS S3 bucket and therefore cannot read or download the file. Does that sound plausible?

We are able to upload to AWS S3 from within the GUI without issue, so connectivity does not seem to be a problem.

I think a relative path as the base path can be modified in IAM.

What should we define as base path, and what should we then store in the varchar field? Currently all we did is configure AWS S3 file storage according to the docs and added an NVARCHAR column to an existing table. Is there any additional steps we might have missed or still need to take for this to work correctly?

Hey Jeroen,

We are able to upload to AWS S3 from within the GUI without issue, so connectivity does not seem to be a problem.

Are you using Indicium Basic or using system flows to upload files to AWS S3?

What should we define as base path, and what should we then store in the varchar field?

AWS doesn't work with base paths, my bafd. You define the bucket which weffectively is your base path. Using the file name you can steer where the file is stored I believe. I haven't worked with AWS myself yet.

You will need a column with a (n)varchar domain using the File upload control and a Storage location that points to AWS. That in turn will ensure that uploading the file will record the file name in the column and allow you to download it when pressing the control in the GUI.

@Jeroen de Klerk could it be that the AWS User doesn’t have all required Action permissions? See the Policy template here for some pointers: https://docs.thinkwisesoftware.com/docs/deployment/aws_bucket_as_file_cache#create-a-user-with-programmatic-access

@Jeroen de Klerk, do you still require assistance on this?

Hi @Jeroen de Klerk, I assume you no longer need any help from our side. Since multiple responses have been given, I would like to ask you to select a best answer so that this topic can be closed.

Hi @Jeroen van den Belt,

Apologies for the lack of responses, my personal responsibilities within our department have changed since posting this question, so I have not been involved in this transition as much.

@peter.bongers and @John Lunenburg what is the progress on this? Has there been any progress on this?

Thanks for checking in Jeroen!

HI @Jeroen van den Belt,

Thanks for following this question.

We have succeeded in setting up a Thinkwise app with an Universal GUI environment in which we can upload and download a file to AWS S3. The issues we had when Jeroen created this question, were mainly caused by using the Windows GUI with AWS S3.

We are still figuring out how to use the preview screen component in combination with S3. Do you know if we can use the preview component?

@John Lunenburg the Preview component works with any File storage location. It should simply be a matter of creating a Screen Type that includes the Preview Screen Component for the Subject with the File in it.

Then make sure the File Control is the first one in the Data Model that can be interpreted by the Preview component, before URL Controls or HTML Controls. See this topic for some remarks on that (Docs are not yet updated): 

@Arie V That was the solution. Thanks for your help.

There was a column with a HTML Control that had a lower order than the AWS file column for that table in the Data Model.

@John Lunenburg Good to hear! We’ll make sure to make this more explicit in the Documentation soon.