Basically the error means that no Application in your EC2 instance is listening on port 8888. Did you start Jupyter notebook inside the Remote machine?
Try the command jupyter notebok list, if there’s jupyter server running in EC2, you will see it, otherwise it will come up empty. If it’s empty run Jupyter Notebook.
Because you are using Tunneling of ports, if for any reason you loose the SSH connection, your notebook is not accessible. It might be better to open up port 8888 on the server by modifying the Security Groups (on EC2) and then directly connect via http://<ec2-servername>:8888
I was able to create a p2 instance with this AMI and run through the lesson 1 notebook without any errors. As Jeremy mentioned, you need to do a git checkout & git pull inside your local repo.
@jeremy Would you be able to provide a rough outline of what software packages you installed in the AMI and in what order? It would serve as a great confidence booster to set this up on my own instance from scratch. Appreciate your attention to this request!
How long will amazon take to update our request instance for p2.xlarge? any other option to do the lesson 1 notebook because my crestle is also not running well enough.
I also search for “ami-8c4288f4” both in market place as well in community AMIs, no luck. If I am searching fastai only in community I am getting some results but they have different amAMI ID. I guess those are some old stuffs.
Is it required to clone the repository to my laptop or to aws instance?.
Some one please tell what need to be done after launching an instance in order to be able to run the course notebooks.
After running a notebook from an aws instance will the changes be saved and reflected in the notebook present in my local repo ?
@HariSumanth9
Incase you’re working on the aws instance, you might follow these steps.
Launch the instance on AWS console.
ssh -i your-aws-cert.pem ubuntu@ec2-instance-ip
cd fastai; git checkout --environment.yml; git pull
open tmux, launch jupyter jupyter-notebook --no-browser --ip='*'. Take note of the token. You need this in the next step.
Visit the ec2-instance-ip:8888 on your web browser. Enter the token to see your notebooks.
Work with the notebooks.
If you do port forwarding in step 2 using ssh -i your-aws-cert.pem ubuntu@ec2-instance-ip -L 8888:localhost:8888, then in step 5, you can access notebooks on localhost:8888 on your web browser.
If you make a few changes to your notebooks and you’d like to save them, you need to commit the changes to your aws-local-repo, push them to your remote fork and pull them to your laptop-local-repo.
