We’re working on a requirement to generate a report in TXT format, encrypt it using PGP, and then transfer it to an SFTP location.
Since this doesn’t seem to be achievable using out-of-the-box functionality in SailPoint ISC, we’ve identified a couple of potential approaches:
Trigger a workflow in ISC, with the downstream processing (TXT generation, PGP encryption, and SFTP transfer) handled on a Windows Server via a PowerShell script.
Use AWS Lambda to handle the entire process end-to-end.
We’d appreciate your input on which approach would be more effective and maintainable. Also, are there any alternative methods or best practices you’d recommend for this type of requirement?
@shariqmt thanks for posting your very interesting question!
Provided each could be accessed with encryption for the text being transferred, which of the two environments would be more likely to change - your Windows server or AWS Lambda workspace? Do both support adequate backup and restore functionality? Can each allow granular administrative access?
Also, is there anything that would interfere with your future use of Lambda, such as transitioning from AWS to another IAAS platform? And for maintaining what you develop, would your admins needing maintenance access be equally able to access your Lambda or Windows server environments?
Another consideration might be updates - how frequent would Lambda or Windows updates be, and how likely would those be to affect your solution?
Hope this provides some insight into considerations - looking forward to see what others suggest here!