IT Pre-requisites - Connector API & EPO API
Server access
- App server (to install API)
- Recommended specs: minimally 2 cores, and minimally 4GB ram, better 8GB, ideal 16GB,
- With Windows (server) (new enough to install .Net core) (2016 and newer)
- Minimally 160 GB disk
- SQL Server access
- 3 data disks preferred (4 including OS disks)
- Minimally 3 physically separate disks (OS, backup, data), preferred 4 physically separate disks (OS, backup, MDF data files, LDF log files)
- Size of data disks at least approx. 5 times the size of the largest database
- Recommended specs: minimally 4 cores, preferred 16GB, cost effective 8GB
- 3 data disks preferred (4 including OS disks)
- Installed apps
- IIS (with .Net Core)
- SQL Management studio (can also be on the SQL machine directly - in which case we need access to the SQL machine)
Port forwarding
- Ports: 443, and optional port 80 (see SSL section below)
SSL
The application requires SSL for all its communication between the client and the API.
There are two approaches here, the client handles the SSL certificate itself, or we facilitate the SSL certificate. The last case, we do this using Let's Encrypt, and use auto-renewal. For this, we need a port 80 on the forwarded IP to go to the App server.
- Port forward on 443 to the app server
- IF, we need to provision SSL, then we need the port forward of port 80 as well.
- if you provision SSL, we'd need the domain name
Hairpin NAT configuration (aka NAT loopback)
- Setup hairpin NAT on the firewall / router
Users
- User to access the App server and possibly SQL server
- User to access the SQL instance. (sa user, so we can create limited access users for our APIs)
- SMTP user / Email relay / SendGrid user
Other
- File storage location (stored files uploaded to EPO.
- SMTP account such as Sendgrid