1 of 1 people found this helpful
You should speak specifically to a 'dba' about this, preferably one with AWS experience. The reality is, Tableau will connect fine to any of these instances, even the smallest one. Some factors you'll need to consider:
- Will you have other tools connecting to this? Will there be a realtime application sitting on top of this responsible for creating, adding to and editing the data?
- How many users will be using Tableau realtime?
- How many reports do you think you'll have?
- How many queries do you imagine you'll be running per second or minute?
- Do you currently have an internally hosted database? If so, what are the specs of that for comparison.
Here's my general advice on AWS:
- Do you really need an EC2 instance for this? Couldn't you just fire up an RDS instance and not worry about the overhead of installing and configuring MySql?
- AWS is built to scale. If you start on the highest tier, do some analysis and find out you're not using anywhere near the capacity then you can pretty easily take a point in time backup, shut down your RDS instance and spin up from the backup on a different level tier. I'd personally recommend you start on a lower tier and size up as needed rather than going big, early.
- You need to be conscious of security. If you don't know what you're doing, you're going to expose your database to the whole wide world and that could be pretty bad. Even if you lock down with secure user accounts, you'll end up using resources because hackers are going to be trying to brute force your DB's to guess the password. If your only application connecting directly to this DB will be Tableau, it should be easy enough to whitelist the IP Address range of your WAN/Tableau Server.
Excellent explanation TOM very helpful, thanks!