If you don't already have an Amazon Web Services account, you will need to register for one and set up your credentials. Visit the EC2 homepage:
Click the "Sign Up Now" link.
This process may take a few minutes and you will be required to verify your identity using a phone.
Before setting up your PANDA server, you will need to configure your security group so that web requests will be able to reach it.
To do this, visit the Security Groups section of the EC2 Management Console:
Select the "default" security group from the list, and then click the "Inbound" tab in the bottom pane of the window. Click the “Create a new rule” dropdown to add rules for HTTP, HTTPS and SSH.
If you don't mind your PANDA being accessible to anyone on the internet, you can enter 0.0.0.0/0 in the Source field for each. This will make your PANDA visible to the public. (Although it's highly unlikely anyone would find it unless you gave them the link.) More discerning users will want to enter a private IP or subnet assigned to their organization.
Click “Apply rule changes”.
Visit the Instances section:
Click "Launch Instance". Select "Classic Wizard" and click "Continue". Click the "Community AMIs" tab and search for ami-1af12273. It may take a moment to return a result. When it does, click "Select".
On the next page you'll need to select an Instance Type. PANDA has been optimized with the expectation that most organizations will run it on an m1.small instance. (At a cost of roughly $70 per month.) This should provide adequate capacity for small- to medium-sized groups. We don't recommend trying to run it on a t1.micro unless you will only be using it for testing.
Once you've selected your instance type, skip over Availability Zone and click "Continue". Keep clicking "Continue" and accepting all the default options.
If you have never used Amazon EC2 before you will be required to create a keypair.
Even if you don't know what this is:
Email it to yourself.
Do not leave it on a computer you do not own.
Do not lose it or delete it.
It is the only way to administer your PANDA server if you ever need to.
Keep clicking the "Continue" button until it becomes a "Launch" button. Click "Launch". Click the “Close” button.
Once you see that your PANDA server’s state is “running,” you've completed your installation and will want to verify that your new PANDA is available. You can browse directly using to your instance using its "Public DNS Name". Navigate to the EC2 Instances section:
Select your instance from the list. The public DNS name will be listed among the instance details in the bottom pane. It will look something like this: ec2-50-16-157-39.compute-1.amazonaws.com. Visit this in your browser, like so:
You can login using the default user credentials:
Or the default administrator credentials:
If you wanted to set up a PANDA, but don’t want the expense of having it running all the time then you can now “Stop” it and have it ready next time you want to use it. To do so, visit the instances page:
Select your instance from the list. Right-click on it and select “Stop”. Your PANDA will stop running, but will be saved so that you can restart it whenever you want. In the meantime you will pay only for the storage cost of the instance data (less than $1 per month).
If you choose to leave your instance running it will cost you approximately $70 per month.
User group: http://bit.ly/pandagroup
Additional documentation: http://bit.ly/pandadocs