Changes between Version 89 and Version 90 of InstallationGuidelines/Amazon


Ignore:
Timestamp:
10/22/14 20:50:14 (7 years ago)
Author:
Michael Howden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstallationGuidelines/Amazon

    v89 v90  
    1111
    1212== 2. Create Instance ==
    13 === Step 1: Log in to the Management Console ===
     13=== 1: Log in to the Management Console ===
    1414* https://console.aws.amazon.com
    1515
    16 === Step 2: Select a Region ===
     16=== 2: Select a Region ===
    1717Amazon supports multiple Regions in order to provide a service closest to your users.
    1818* Namespaces of Instances, Volumes & Snapshots are unique only within a Region.
     
    2121* Bandwidth transfers are free within an Availability Zone
    2222
    23 === Step 3: Launch a new Instance ===
    24 
    25 === Step 4: Choose an Amazon Machine Image (AMI) ===
     23=== 3: Launch a new Instance ===
     24
     25=== 4: Choose an Amazon Machine Image (AMI) ===
    2626* Recommend using the AWS Marketplace Debian 64-bit image (as this has a sufficiently large HDD to start with & is EBS-backed, so has persistent storage even whilst powered down)
    2727* In time we may provide pre-built "Sahana Eden" AMIs (some old unmaintained ones may be available in some regions)
     
    2929* Larger production instances can only run 64-bit, so can't have the exact same image used.
    3030
    31 === Step 5: Choose an Instance Type ===
     31=== 5: Choose an Instance Type ===
    3232* The free starter 'micro' instance is flexible as it can run both 32-bit & 64-bit Operating Systems.
    3333
    34 === Step 5: Configure Instance Details ===
     34=== 6: Configure Instance Details ===
    3535Default settings are fine
    3636
    37 === Step 6: Create !KeyPair ===
     37=== 7: Create !KeyPair ===
    3838Ensure that you keep the generated private key safe...save as {{{private.pem}}}
    3939
    40 === Step 7: Associate Elastic IP ===
     40=== 8: Associate Elastic IP ===
    4141Each time you start an instance up, it will be assigned a new IP ('Public DNS') although this can be overcome using an Elastic IP:
    4242
     
    5050NB If you have a free EC2 instance, be sure to release your Elastic IP if you shut down your instance. IPv4 addresses are a "scarce resource" so Amazon will charge you for wasting one if you keep it assigned to your instance while you are not using it.
    5151
    52 === Step 8: Configure Security Group ===
     52=== 9: Configure Security Group ===
    5353NETWORK & SECURITY > Security Groups
    5454
     
    5858Restricting the source will add further security, but obviously also restricts your ability to administer
    5959
    60 === Step 9: Gain SSH access ===
     60=== 10: Gain SSH access ===
    6161In order to get the public key (needed by SecureCRT for instance) then you need to login using CLI & retrieve it (username 'admin' for the AWS !MarketPlace Debian, username 'root' for some other Images):
    6262{{{
     
    8484Thanks to: http://itkbcentral.blogspot.co.uk/2011/07/replace-lost-key-pair-existing-aws-ec2.html
    8585
    86 === Step 10: Add Swapfile ===
     86=== 11: Add Swapfile ===
    8787You should add swap from a swap file in order to improve performance (especially on a Micro instance):
    8888{{{