Engineering Management System Infrastructure Build

We in IT have been asked to provide IT infrastructure to support something called the Engineering Management System. This Feature is to provide infrastructure to host the EMS software.

Confluence links:
https://confluence.skatelescope.org/display/OP/EMS+Sever+requirements

Tickets:
https://jira.skatelescope.org/browse/TPO-220

I had a call with Brendon.Taljaard about this on 20/Jan/2022, and here's the summary.

They require just a single Windows server, to run two complementary applications.

1. Maintenance Support Planning (LSA)
No, I don't know what LSA stands for. It's a client server thing being written in-house, with the client software talking to this server, to:
(a) check for a valid licence to use the application, over some TCP port;
(b) access a SQL Server database on the server, over some TCP port (maybe 1433?).
It will only be used by a few SKAO people, only inside the SKAO network.

2. Maintenance Management
Not sure if this is in-house software. This is accessed over HTTPS (from a web browser?), with maybe up to 200 users, both SKAO and non-SKAO, but only inside the SKAO network (assuming that the telescope sites will be inside the SKAO network, whatever that means). This app uses IIS and SQL Server. He suggested a URL of https://ils.skatelescope.org/ but we'd probably go with a .ad. one, or is it time for an internal skao.int subdomain?

So, the box will need to have SQL Server installed, which is easy in AWS, just choose it when deploying. He reckons the lowest 'edition' of SQL Server will be fine (https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-version-15), so depends on what AWS offer. The rest of the installation will be done by Brendon.

For the HTTPS side of things, a load balancer is the obvious thing, an internal one, which we don't yet have, but which would be handy anyway for other things. It would handle the SSL traffic, sending HTTP to the application server.

One or both of these services need to send out email notifications, so we'd need that setting up (shared mailbox in Exchange, enabled, with a password set, so that bounces can be caught).