Skip to main content
Solved

AWS S3 integration behaviour when altering linked record

  • 21 June 2024
  • 2 replies
  • 25 views

Hi,

Our team is considering offloading the files in our Thinkwise application from our on-prem server to an S3 instance, in order to reduce back-up size and improve file storage performance.

However, we are unsure what happens to a file in S3, when a database record it is linked to is altered or deleted. Is a file automatically moved if a record is altered, is it automatically deleted if a record is deleted?

We couldn’t find any documentation on this in the Thinkwise documentation, but we would like to know what behaviour to expect.

Thanks in advance!

This topic has been closed for comments

2 replies

Mark Jongeling
Rank
Userlevel 7
Badge +23

Hi Jeroen,

Records can link to files in AWS S3 but mutation of the file will not result in the deletion of the file, unless you create a Delete file/folder process flow for it of course. So your files in S3 will reside until cleaned up manually or automatically using process or system flows. Feel free to test this with a test file 😉

"Wake me up before you low-code"
Jeroen de Klerk
Rank
Userlevel 3
Badge +2

Hi Jeroen,

Records can link to files in AWS S3 but mutation of the file will not result in the deletion of the file, unless you create a Delete file/folder process flow for it of course. So your files in S3 will reside until cleaned up manually or automatically using process or system flows. Feel free to test this with a test file 😉

Hi Mark,

Thanks for the quick answer!

That makes sense, that way we can separately control this behaviour and take into account potential back-up strategies.

At this moment we are still considering our options, but we definitely will take this into account once we get to a testing phase.

Thanks again!

Terms & ConditionsCookie settings