You could have a look at Amazon EFS. 

https://aws.amazon.com/efs/

@Erwin Ekkel We're struggling to understand what the relevance is of the Project folder specification and the related Code file folder. We have moved to a different development server, after which we got some creation issues. But after upgrading to the Thinkwise Platform 2021.3 Release the whole Creation process is run by Indicium. Our setup is as follows:

• The Windows GUI for the SF is running on a local Windows Server
• The Indicium for the SF is running on AWS ElasticBeanstalk

The Project folder specification (and as a result the Code file folders) are referring to a local location that is not accessible by Indicium, nothing is added to these folders when we run the Creation steps, and nevertheless we can still Execute the source code. What functionality are we missing and what is going to break for us in the next TWP 2022.1 Release when more will be done through Indicium?

When generating source code there is an option “write to disk”. When activated this will write the source code files to the project folder destination. In the 2022.1 release there is also the option to write program objects to disk. 
Currently it is not possible to write source code files to a file storage location like AWS or Azure. 
For write to disk to work indicium needs access to a physical folder, this should be the folder that is set as the project folder specification. 

 

@Erwin Ekkel Since it is also planned for Release 2022.1 to improve the Write file process action (see responses from Jasper here), it would be great if this feature is used within the Software Factory as well. This would make it a lot more flexible as well as easier for us to automate deployments. Perhaps also good to use the File storage functionality for these specific Source code files and Program objects?

Hi @Arie V and @g.c.d.vanderschoot ,

This is indeed what we are working on right now; (New) process actions that will allow you to write files to a file storage location. This will work for both Files and Folders.

In addition to that, we have an User story to convert these Software Factory processes to use file storage. This way you would be able to reconfigure that inside IAM and be able to write your Deployment package directly to your AWS S3 bucket. 

In addition to that, we have an User story to convert these Software Factory processes to use file storage. This way you would be able to reconfigure that inside IAM and be able to write your Deployment package directly to your AWS S3 bucket.

This sounds very promising! Is it planned to be part of Release 2022.2? That’ll help us decide the way we cope with Release 2022.1’s limitations.

We plan to certainly release the process actions that can use File storage. Using this for the SF processes is something we are going to look into to ensure all processes can run smoothly.

@Erwin Ekkel This is apparently not supported for Windows Servers. 

The AWS alternative for Windows servers is Amazon FSx, but we can't find any confirmation that this service works with Elastic Beanstalk.

Has anyone at Thinkwise tried and tested a solution to successfully write files from Elastic Beanstalk? 

Yes The 2022.2 version of the platform is set to release mid-July.

This will bring the file and folder connectors that work with File storages such as AWS S3 bucket.