Ipbx on Amazon EC2

From Taridium

You do not have permission to edit this page, for the following reason:

You can view and copy the source of this page:

[[File:ami-logo.png|right]] == Getting Started == If you already know about Amazon Machine Instances, you can start ipbx on your account here: [https://aws.amazon.com/amis/taridium-ipbx-free-5-user-edition Start your ipbx Amazon Machine Instance] === What is Amazon EC2? === Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale computing easier for developers. [http://aws.amazon.com/ec2/ Read more about Amazon EC2 here]. === Pre-Requisites === You will need an Amazon.com account and you need to sign up for EC2 services. Follow the instructions here if you haven't done so yet: [http://aws.amazon.com/ec2/ Sign-up for EC2] === Getting Started with ipbx on EC2=== Now that you're signed up for Amazon EC2, you're ready to launch an ipbx instance using the AWS Management Console. Sign in to the AWS Management Console and open the Amazon EC2 console at https://console.aws.amazon.com/ec2/. Use the email address and password you used when signing up for Amazon EC2. ====Launching the Instance==== Click on: [https://aws.amazon.com/amis/taridium-ipbx-free-5-user-edition ipbx Amazon Machine Instance] and select the region in which you would like to launch your ipbx instance on the AMI description page. Click on '''Continue''' and select the appropriate settings for your environment (e.g. default settings). ====Create an SSH Key Pair==== Under '''Choose a Key Pair''', you can choose from any existing key pairs that you have created, or you can create a new one. For this example, we’ll create a key pair: [[File:warning.gif]]'''Important''' Do not select the None option. If you launch an instance without a key pair, you will not be able to connect to your instance. Click Create new Key Pair. Type a name for your key pair and then click '''Download'''. You will need the contents of the private key to connect to your instance once it is launched. Amazon Web Services does not keep the private portion of key pairs. Save the private key in a safe place on your system. Note the location because you'll need the key to connect to the instance. Click '''Continue''' to view the settings that your instance will launch with. ====Security Group==== Under Security Details, in '''Security Group''', the wizard automatically makes a security group selection for you, but you will need to add some additional ports to the default settings in order to have a fully working ipbx system. A security group defines firewall rules for your instances. These rules specify which incoming network traffic will be delivered to your ipbx instance. All other traffic is ignored. If you're new to Amazon EC2 and haven't set up any security groups yet, AWS defines a default security group for you. The name and description for the group is quicklaunch-x where x is a number associated with your quicklaunch group. The first security group you create using the Quick Launch Wizard is named quicklaunch-1. You can change the name and description using the Edit details button. For example, in this tutorial we changed the name to quicklaunch-0. The group already has basic firewall rules that enable you to connect to the type of instance you choose. For the ipbx instance, you connect through SSH on port TCP 22 and TCP 80 (WEB). The quicklaunch-x security group automatically allows SSH traffic on port 22. Add Port TCP 80 and ports UDP 5060-5070 (SIP), port UDP 4569 (IAX2) and ports UDP 18000-20000 (RTP) to your policy to enable VoIP traffic. If you have used Amazon EC2 before, the wizard looks for an existing security group for the type of instance you’re creating. [[File:warning.gif]]'''Caution''' The quicklaunch-x security group enables all IP addresses to access your instance over the specified ports (e.g., SSH for Linux/UNIX). This is acceptable for the short exercise in this tutorial, but it's unsafe for production environments. In production, you'll authorize only a specific IP address or range of addresses to access your instance. Review your settings, and click Launch to launch the instance. A confirmation page lets you know your instance is launching. Click Close to close the confirmation page. In the Navigation pane, click Instances to view the status of your instance. It takes a short time for an instance to launch. The instance's status will be pending while it's launching. After a short period, the status of your instance switches to running. You can click Refresh to refresh the display. Record the Public DNS name for your instance because you'll need it for the next task. If you select the instance, its details (including the public DNS name) are displayed in the lower pane. You can also click Show/Hide in the top right corner of the page to select which columns to display. (Optional) After your instance is launched, you can view the quicklaunch-x security group rule that was created. On the Amazon EC2 console, under Network and Security, click Security Groups. Click the quicklaunch-x security group and you can view the security rules created. ====Connecting via SSH==== Use your previously created or uploaded SSH private key to connect to your ipbx instance by specifying the key with the -i option and your instance DNS name: [admin@mymachine ~]# ssh -i mykey.pem root@ec2-XX-XX-XXX-XXX.compute-1.amazonaws.com == Next Steps == Continue [[Initial_Configuration|here]] to start with configuring your ipbx system.

Return to Ipbx on Amazon EC2.