Hello,
I'm wondering if anyone is self-hosted in an RDS environment on aws or Azure? We are hoping to do it but don't know how to do it given the need to create a proxy account that is a local admin on the database server.
Thank you,
Lou Ann
Not knowing too many of the details of how Amazon or Azure RDS works, I can at least say that the use of a local administrator account for tessitura is not strictly required (despite what the installation documentation may tell you). It's certainly not a best practice as far as security is concerned.
In our last server rebuild, I made a point to configure SQL Server to run as an active directory managed service account. Getting this running was actually way easier than I expected, and didn't create any obvious issues with Tessitura, EXCEPT for Extractions. This part may be similar to using a managed database service.
Extracting to file requires that an xp_cmdshell proxy account be configured with rights to write to the extraction output directory and select from the impresario_cci database (or the equivalent tables in impresario post-V15). I was able to get this to work with a regular AD user account. This may be the sticking point for any kind of RDS service, since they all seem to flat-out disallow any kind of xp_cmdshell usage, regardless of what proxy account rights it has.
Hi Lou Ann,
Currently we don't support running Tessitura in the AWS RDS service or the Azure Elastic Pool SQL Service. While you can load Tessitura into these environments (speaking here to AWS RDS in particular) and have primary functions like selling tickets or entering contributions work, some parts of the software that require access to functions or resources not contained in the Impresario database will not work. Extraction output, as Nick mentions below, is a good example. So if you want to run Tessitura in AWS or Azure your best option is to run your own virtual server and SQL instance. This is what we do for our Hosting Services in RAMP.
Thanks,
Ron