Also in reference to https://docs.airbyte.io/deploying-airbyte/on-aws-ec2, Sorry for the dumb questions in advance…. 1. Once i set up a sync using this install approach, does it continue to run in the background (even after I kill my terminal) or do I need to set up the service? 2. The docs use t2-micro - how much load can this handle? 3. Any tips on how to secure this instance so that it can be accessed only via SSL?

1. Yes it will. docker handles it for you 2. someone asked us this question not so long ago, They were able to get it to work with a t3.medium (we are going to add more info for the instances requirements https://github.com/airbytehq/airbyte/issues/1025). 3. Would you be using a self-signed certificate?

Thanks. 2. i got it working with t2.micro but wasnt sure if I should beef up the instance. It is pretty slow using t2.micro. 3. Happy to use either AWS Certificate or self-signed or LetsEncrypt - ideally having it point to a CNAME of some sort would be nice to have

Let me get back to you on 3. The UI runs behind Ngnix so it is just a matter of feeding it the right configs. Now if it runs on k8s it’s a no brained since you can expose ssl services (fargate probably has a similar mechanism)