scp CREDENTIALS-FILE ubuntu@IP-ADDRESS, where CREDENTIALS-FILE is the path to your access key credentials, downloaded from Amazon, and IP-ADDRESS is the public IP address of the instance (the address you connected to via ssh).CREDENTIALS-FILE to the EC2 instance.which git displays a path, you have git.sudo apt-get install git.git clone https://gist.github.com/8553680.git $ cd 8553680
$ python
>>> import testcreds
>>> testcreds.test('YOUR-CREDENTIALS-PATH')
replacing YOUR-CREDENTIALS-PATH with the absolute path to your credentials file. The path will begin with /home/ubuntu/.
The test software has been revised. To download it to your EC2 instance, sign on to your EC2 instance and
$ cd 8553680
$ git pull
You will see some messages from git.
Now run the test using the instructions above.
If the test succeeds, you will see Test SUCCEEDED. Congratulations! You won’t have to do these steps again for this EC2
instance. These changes will be retained even if you stop and then restart
the instance.
If you get a Python file IO error, it is most likely that the path to the credentials file is incorrect.
If you get a 403 Permissions error, and your access key is for an IAM id, it is likely that your IAM id does not have a full range of permissions. In the IAM console, select your ID and go to the Permissions tab. View the policies for your id. They should include one like the following:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "*",
"Resource": "*"
}
]
}
Redditor sickan90 suggests an alternative approach: Placing your
access keys into the boto configuration file. See their
post on Reddit.
Thanks, sickan90!
server.worker subservice behind the scenes.Read the following before coming to the next class:
The Tail at Scale, from beginning up to but not including “Cross-request long-term adaptations”.
The key points:
Less important: