User Tools

Site Tools


access:new_aws_vpc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
access:new_aws_vpc [2017/03/30 17:49]
mjallison
access:new_aws_vpc [2017/03/30 21:46] (current)
mjallison
Line 6: Line 6:
  
   - Create the VPC   - Create the VPC
-     - Name the VPC "​ProdNet"​ or "​TestNet",​ etc. +     - Name the VPC "​ProdNet"​ or "​TestNet",​ etc. We'll use XNet or XSubnet for examples from here on out.
      - Assign an IPV4 CIDR Block - 10.0.0.0/16      - Assign an IPV4 CIDR Block - 10.0.0.0/16
      - Set "​tennancy"​ to default      - Set "​tennancy"​ to default
      - Tag VPC for "​class"​ as "​access"​ or "​development",​ etc.      - Tag VPC for "​class"​ as "​access"​ or "​development",​ etc.
-     - Create at least one subnet in the VPC - Name something resembling the VPC name, e.v. ProdSubnet.1 +     - Create at least one subnet in the VPC - Name something resembling the VPC name, e.v. XSubnet.1 
-       - Map zones to subnets, suggest the following (Using the Virgina ​region)+       - Map zones to subnets, suggest the following (Using the Virginia ​region)
          - 1a to XSubnet.0          - 1a to XSubnet.0
          - 1b to XSubnet.1          - 1b to XSubnet.1
Line 17: Line 17:
          - etc.           - etc. 
      - Create an internet gateway, attach it to the VPC.      - Create an internet gateway, attach it to the VPC.
-     - Edit the VPC rout table+     - Edit the VPC route table
        - Associate at least 1 subnet with the route table. ​        - Associate at least 1 subnet with the route table. ​
        - For Access, one subnet is enough, generally our instance work has been in zone 1b, so XSubnet.1        - For Access, one subnet is enough, generally our instance work has been in zone 1b, so XSubnet.1
-       - Add the internet gateway to the Rout Table, with destination 0.0.0.0/ ​+       - Add the internet gateway to the Route Table, with destination 0.0.0.0/ ​
   - Create EC2 instance   - Create EC2 instance
-    - Name the EC2 instance, ​tag EC2 instance with same tag from VPC+    - Name the EC2 instance, ​e.g. '​Production-A',​ '​Production-B',​ etc. 
 +    - Tag EC2 instance with same tag from VPC 
 +    - Name the EC2 security group to '​XNet-EC2-SG'​
     - Edit the EC2 security group to:     - Edit the EC2 security group to:
         - allow for all incoming on 34015 - 0.0.0.0/​0 ​         - allow for all incoming on 34015 - 0.0.0.0/​0 ​
Line 46: Line 48:
     - Attach access store to EC2 instance via EC2 console     - Attach access store to EC2 instance via EC2 console
     - Attach EFS store to EC2 instance     - Attach EFS store to EC2 instance
 +    - Modify /etc/fstab to add the following line ''/​dev/​sdf ​   /​mnt/​access ​ ext4    defaults ​       0   ​0''​
     - Copy following files     - Copy following files
       - /​mnt/​access/​tools/​bashrc to ~/.bashrc       - /​mnt/​access/​tools/​bashrc to ~/.bashrc
access/new_aws_vpc.1490896157.txt.gz · Last modified: 2017/03/30 17:49 by mjallison