AWS EBS / STAND ALONE SQL SERVER
Last updated
Last updated
(c) 2024 Data Illusion Zumbrunn. All rights reserved. Reproduction strictly forbidden.
This tutorial will guide you through the couple of steps required to setup and run ngSurvey on Amazon Web Services Elastic Beanstalk using a separate stand alone RDS SQL Server database.
1) Start by opening the link below to open the EBS application creation wizard with pre-configured settings to setup ngSurvey with NgInx as a reverse proxy.
2) On the just opened application configuration and chose Public S3 URL.
3) Go to the network settings and set a VPC, your instance must be in the same VPC as the database that you will create in step 4.
4) Wait that your instance gets ready, once its ready go to the RDS section to create your database, make sure that your virtual private cloud VPC is the same that you have setup in 3 for your EBS instance
ngSurvey supports also mySQL or MariaDB as a database. If you're using mySQL or MariaDB make sure to use a valid mySQLor MariaDB connection string in step 8.
5) Once the database is created you must grant the network access from the EBS instance to your database. Open your database Connectivity & Security pane and open its default VPC security group.
7) Go back to your database dashboard and write down the Endpoint name
8) Now that your database is ready and allows traffic from your EBS instance go back to your EBS instance configuration and set an environment variable "ConnectionStrings:NGSurveyDB" and set its value to with the connection string using your database endpoint eg: Server=yourdatabasesendpoint;Initial Catalog=NGSurveyDB;User ID=youradminuser;Password=yourpassword.
9) Check that ngSurvey was properly configured using this link (replace the instance url by your own instance ur)l : http://yourinstanceurl/api/system/status. This might take a 1-2 minutes to load if ngSurvey is currently setting up your database for the first time.
9) You can now go to your instance URL to use ngSurvey.
If ngSurvey doesn't start go to your EBS instance log tab and download the last 100 lines.
Check the nginx log and eb-docker log for any error message.
6) Edit the inbound rules o the security group add a new inbound rule that will allow all traffic coming from your EBS instance.
