This repository has been archived by the owner on Jul 21, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
HOWTO: Setup provider: Amazon Web Services (AWS)
Rabit edited this page Aug 29, 2020
·
8 revisions
This document describes how to setup your AWS account to use it in BlendNet.
TODO
By default the created Manager & Agent instances are blocking ssh connection and to enable it you will need to slightly modify the BlendNet addon sources:
- Create SSH key in your AWS console: Console->EC2->Key Pairs
- Find
createInstanceManager
andcreateInstanceAgent
functions in your localBlendNet/providers/aws/__init__.py
and uncomment--key-name
option for both and replace the key name to created one:- Before:
options = [ ... #'--key-name', 'default_key', # If you want to ssh to the instance (change createFirewall func too) ... ]
- After:
options = [ ... '--key-name', '<YOUR SSH KEY NAME>', # If you want to ssh to the instance (change createFirewall func too) ... ]
- Before:
- Find
createFirewall
function in your localBlendNet/providers/aws/__init__.py
and uncomment the ingress for 22 port:- Before:
#_executeAwsTool('ec2', 'authorize-security-group-ingress', # '--group-name', target_group, # '--protocol', 'tcp', # '--port', '22', # '--cidr', '0.0.0.0/0')
- After:
_executeAwsTool('ec2', 'authorize-security-group-ingress', '--group-name', target_group, '--protocol', 'tcp', '--port', '22', '--cidr', '0.0.0.0/0')
- Before:
- Make sure you cleaned the
blendnet-*
security groups if they are existing AWS->EC2->Security Groups, otherwise they will not be recreated. - Connect to the instance - BlendNet uses debian images, which contains
admin
user for external ssh access:
- Now you can check the service logs by run the next commands on the instance:
- Manager:
journalctl -u blendnet-manager
- Agent:
journalctl -u blendnet-agent
- Manager: