That sounds super interesting, @chrissyhroberts!
I think that in such a project, you should focus on scalability for many reasons. Not planning on a scalable infrastructure forces you to make an initial bet and hope that it will be enough, incurring in higher costs from day one (when you don't need to support high volumes) and forcing you to stick to a hardware stack.
You can look to scalability from different perspectives when dealing with the app server and the database.
I'd highly recommend using a managed database service such as AWS RDS. This will let you easily increase your database resources to match your needs as time passes, deal with backups, replication, etc.
With a reasonable amount of memory, the app server shouldn't be the bottleneck but since it's harder to scale, I'd suggest having a strategy that lets you replace it smoothly. When you need a bigger machine, you can use DNS to switch traffic from the old server to the new one with some down-time, or have a load balancer in front of them for better results, and easier management.
Monitoring the infrastructure should be a priority too. I'd strongly recommend activating your cloud provider's metrics, which can measure stuff like response times from Aggregate, etc.
Replicating the running app server into a beefier machine, increasing database resources... all this is fairly easy to manage if you can use a cloud provider. If you have to do this in-house, I'd suggest to have the app server and the database in two different hosts, which will let you deal better with infraestructure growth.
If you can't do any of this, then it's easy: I'd go for the biggest machine you can afford CPUs are not so important, and any modern 2-4 core CPU will be enough (if not, we're the ones doing something wrong :D). In any case, invest first on big NVMe/SSD drives, then memory (at least 8GB for Aggregate, maybe? not sure), then CPU.