{"__v":0,"_id":"588f722bbcace50f0052ba06","category":{"version":"588f722bbcace50f0052b9e1","project":"565f5fa26bafd40d0030a064","_id":"588f722bbcace50f0052b9e7","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-12-17T21:29:23.551Z","from_sync":false,"order":5,"slug":"server-installation-configuration","title":"Self Hosting"},"parentDoc":null,"project":"565f5fa26bafd40d0030a064","user":"565f3941ea46251700972783","version":{"__v":1,"_id":"588f722bbcace50f0052b9e1","project":"565f5fa26bafd40d0030a064","createdAt":"2017-01-30T17:04:43.410Z","releaseDate":"2017-01-30T17:04:43.410Z","categories":["588f722bbcace50f0052b9e2","588f722bbcace50f0052b9e3","588f722bbcace50f0052b9e4","588f722bbcace50f0052b9e5","588f722bbcace50f0052b9e6","588f722bbcace50f0052b9e7"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"5.3.0","version":"5.3.0"},"updates":["57e54616f3d7fc0e009c50e2","57eaedf2c878550e00b3c462"],"next":{"pages":[],"description":""},"createdAt":"2015-12-22T20:40:54.525Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":10,"body":"1. Log into AWS and create a new Ubuntu EC2 instance. \n\n2. Select the Instance Type.  For most installations the t2.micro is adequate.  Production deployments may want to move to an m3 deployment.\n\n3. In ‘Configure Instance Details’, choose the number of instances you want to deploy.  Leave all other settings as the default values. \n\n4. Choose storage settings.\n\n5. Tag your instance if desired.\n\n6. Create a new security group and add a new rule in addition to the default SSH rule: \n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"Type – HTTP, Protocol – TCP, Port Range – 80, Source – Anywhere 0.0.0.0/0 \",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]\n7. Launch the instance. \n\n8. Select an existing key pair or create a new key pair. Do not lose pem file.\n\n9. On the ‘Instances’ page, you will see that your new instance is initializing.  Once it is initialized, under ‘Network & Security’, select Elastic IPs. \n\n10. Click ‘Allocate New Address’ and select VPC from the drop-down. \n\n11. Associate this new address by clicking ‘Associate Address’ and select the instance you just created in the first input field from the drop-down.\n\n12. Connect to your instance via ssh using “ubuntu” user or the default “ec2-user” user and upload the nanoscale.io binary, key, and .conf file.  Execute the following to get nanoscale.io online with an output file called “gateway.log” \n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"sudo ./gateway >> gateway.log 2>&1 &\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\n13. If using a new installation of nanoscale.io, configure the .conf file.  For default access use these settings:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"server = true\\nconnectionString = (your DB creds) \\nhost = '0.0.0.0'\\nport = 80\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]\n14. Your new instance is now publicly accessible via the ‘Public DNS’ provided for that instance.  By going to <a target=\"_blank\" href=\"http://{insert-public-dns-here}/admin/\">http://{insert-public-dns-here}/admin/</a>, you will be able to access the newly created installation of nanoscale.io. \n\n15. Add a new user through curl.\n\n16. (Optional) Using MongoDB Step 1: Go to compose.io and provision a new DB for the instance.  Create creds, objects, and data. \n\n17. (Optional) Using MongoDB Step 2: In nanoscale.io create remote endpoints accordingly that match your new Mongo DB.\n\n18. Build out API calls through proxy calls and remote endpoints. \n\n19. Enable CORS in the API settings.  Don't forget to add “accept, access-control-allow-origin, content-type, Authorization” to CORS Allowed Headers.\n\nYour nanoscale.io are now working!","excerpt":"","slug":"install-on-aws-in-dev-mode","type":"basic","title":"Install on AWS in Dev Mode"}

Install on AWS in Dev Mode


1. Log into AWS and create a new Ubuntu EC2 instance. 2. Select the Instance Type. For most installations the t2.micro is adequate. Production deployments may want to move to an m3 deployment. 3. In ‘Configure Instance Details’, choose the number of instances you want to deploy. Leave all other settings as the default values. 4. Choose storage settings. 5. Tag your instance if desired. 6. Create a new security group and add a new rule in addition to the default SSH rule: [block:code] { "codes": [ { "code": "Type – HTTP, Protocol – TCP, Port Range – 80, Source – Anywhere 0.0.0.0/0 ", "language": "text" } ] } [/block] 7. Launch the instance. 8. Select an existing key pair or create a new key pair. Do not lose pem file. 9. On the ‘Instances’ page, you will see that your new instance is initializing. Once it is initialized, under ‘Network & Security’, select Elastic IPs. 10. Click ‘Allocate New Address’ and select VPC from the drop-down. 11. Associate this new address by clicking ‘Associate Address’ and select the instance you just created in the first input field from the drop-down. 12. Connect to your instance via ssh using “ubuntu” user or the default “ec2-user” user and upload the nanoscale.io binary, key, and .conf file. Execute the following to get nanoscale.io online with an output file called “gateway.log” [block:code] { "codes": [ { "code": "sudo ./gateway >> gateway.log 2>&1 &", "language": "shell" } ] } [/block] 13. If using a new installation of nanoscale.io, configure the .conf file. For default access use these settings: [block:code] { "codes": [ { "code": "server = true\nconnectionString = (your DB creds) \nhost = '0.0.0.0'\nport = 80", "language": "text" } ] } [/block] 14. Your new instance is now publicly accessible via the ‘Public DNS’ provided for that instance. By going to <a target="_blank" href="http://{insert-public-dns-here}/admin/">http://{insert-public-dns-here}/admin/</a>, you will be able to access the newly created installation of nanoscale.io. 15. Add a new user through curl. 16. (Optional) Using MongoDB Step 1: Go to compose.io and provision a new DB for the instance. Create creds, objects, and data. 17. (Optional) Using MongoDB Step 2: In nanoscale.io create remote endpoints accordingly that match your new Mongo DB. 18. Build out API calls through proxy calls and remote endpoints. 19. Enable CORS in the API settings. Don't forget to add “accept, access-control-allow-origin, content-type, Authorization” to CORS Allowed Headers. Your nanoscale.io are now working!