Amazon Web Services – Initial Configuration:

Amazon Web Services – Initial Configuration:

    1. If you don’t have an AWS account, create a free tier account. Non-Profits may be eligible for $2000 in yearly AWS credits through Techsoup. Apply here.
    2. If you already have an AWS account, open TrueStack Direct Connect on the marketplace and click continue, then sign in to your account.
    3. Use 1-click or manual launch.
        Choose your instance type. We recommend start out with a t2.micro instance and then move up from there if you need more processing power.
        Choose your region.
        Under Security Group, leave the default, “Create new based on seller settings”.
    4. Ensure the instance gets a public IP. Change it to an elastic IP later (see recommendations below).

Public IP

    1. Be sure the instance is part of the TrueStack Security Group.
    2. After launch, find the public IP from the description tab of the EC2 instance. Open a browser, we recommend using Google Chrome. Find and copy the public IP into the address bar.

Description1

    1. The IP should redirect to a Truestack web address. This is the address you can use in the future to access your interface. If the IP doesn’t redirect to a TrueStack web address, restart the EC2 instance for your AWS dashboard.

RedirectedIP

    1. Accept the EULA.
    2. Find your EC2 Instance ID from the description tab. This is your temporary password. Copy it into the password field and login. We recommend that you change this password on the Settings tab after you log in.

InstanceID

Additional Required Steps:

    1. Add an elastic IP. Shutdown the instance before adding an elastic IP. To shutdown the instance, choose the instance then click on Actions, Instance State, Stop.
      StopInstance
      Without an elastic IP, connected computers may have to clear their DNS cache every time the instance restarts and gets a new Public IP.
      To add an elastic IP, click on Elastic IPs under the Network and Security section of your EC2 dashboard.  Allocate a new IP and associate it with your TrueStack Direct Connect Instance.  Start the Instance.
    2. Troubleshooting: After changing to an elastic IP if your instance isn’t accessible through Chrome by the IP try these steps:
      1. Clear your DNS cache on the computer
      2. Clear the cache in Chrome
      3. Shutdown your TrueStack Direct Connect instance and start it again.  The elastic IP associates with a Truestack.net DNS name on startup.  By shutting down and re-loading your server you will re-initiate this process.
    3. Disable Change Source/Dest. Check. Choose the instance. Click on Actions, Networking, Change Source/Dest. Check. Click Yes, Disable.

ChangeSourceDestination

    1. On the default VPC add an additional route. This will allow the Windows domain controller to communicate with the connected computers. Without this route you will not be able to manage AD connected computers with powershell, the command line or group policies.
      On the EC2 Dashboard click on Default VPC on the right side.
      VPC
      On the VPC dashboard, click on Your VPC.
      If you have multiple VPCs, choose the VPC that is associated with the subnet connected to your TrueStack Direct Connect instance.
      Click on the route table associated with the VPC to open it.
      VPC2
      Choose the route table, click on the Routes tab and click Edit.
      In the Source add 5.5.0.0/20
      In the Destination choose your TrueStack Direct Connect Server. if it doesn’t automatically appear, cut and paste the Instance ID from the description tab of the instance on the EC2 dashboard.
      Click save.
      VPC3

Recommendations:

  1. Use the ? help.
  2. Change the password after logon.
  3. Create backups from the Admin tab.
  4. Periodically run the updates.  Create a backup before you update the server.
  5. If you have multiple Windows servers in your AWS account that need to communicate on the same domain, add this rule to your security group.
    On the EC2 Dashboard, click on Security Groups and choose the TrueStack Direct Connect Security Group.
    Click on the Inbound tab and click Edit.
    Click Add Rule.
    The Type should be All Traffic.
    Set Source to Custom.
    Set the IP subnet to the CIDR subnet that your TrueStack Direct Connect instance is in. For Example 10.0.0.0/24.
    Click Save.
    SecurityGroup

Leave a Reply

Your email address will not be published. Required fields are marked *