4 of 4 people found this helpful
This question comes up from time to time so let me summarize the current state:
We do not support using a DBaaS (Azure, Amazon RDS, etc.) for the backend database for PI AF (and also PI Vision). Although it is possible to make it work for PI Vision, using a DBaaS to host the backend SQL database for AF (PIFD) and Vision (PIVision) is not supported and there is no current plan to support it. Since those servers do not have a master database, are not windows-based (local groups, etc), wouldn't allow our feature checks and dependencies (i.e. replication, maintenance, audit, afplugin, etc.) there is no current workaround for PIFD (AF).
I think it is also important to note that the DBaaS do not offer the same degree of performance as an on-prem setup. The performance is very rarely better than a SQL Express implementation...
You can see one of the previous conversations here:
1 of 1 people found this helpful
Do note Gabriel Michaud-Verreault's warning that this is NOT a supported configuration by OSIsoft.
Now, having said that, it is possible to do this, as I did it a little over a year ago. You can read the details at Re: Way to run PI AF SQL scripts without sysadmin role My test EC2 instance of PI AF seemed to work fine, but there are aspects that I didn't fully test. For the most part I was able to create AF databases and manage the Elements and Templates within with no apparent issues.
I would lean towards your first option, to use two separate EC2 instances, as this is most like a standard on-prem type configuration. I found that the second option can work, but lack of official support, and the 'hack' nature of getting it installed would worry me in a production environment.