PDF Archive

Easily share your PDF documents with your contacts, on the Web and Social Networks.

Share a file Manage my documents Convert Recover PDF Search Help Contact

armaAWSguide .pdf

Original filename: armaAWSguide.pdf

This PDF 1.4 document has been generated by Writer / LibreOffice 5.0, and has been sent on pdf-archive.com on 06/03/2016 at 05:11, from IP address 92.19.x.x. The current document download page has been viewed 1137 times.
File size: 56 KB (1 page).
Privacy: public file

Download original PDF file

Document preview

Arma 3 Server Hosting Using Amazon EC2
6 March 2016
This guide includes all (most) the things that you need to know in order to configure a Windows
server that can host Arma 3 servers using Amazon EC2.
Amazon will let you set up one Windows Micro instance with a public IP and run it for 750 hours
for free. Use this Guide to use that free option and get a quality test environment for your game
servers up and running, fast. Otherwise feel free to choose any instance type your game servers will
need, but be sure to look into the associated costs first:
If you wish to read Amazon's official version of the following guide, view it here. It goes into much
more detail:

Create an Amazon EC2 account
Create an account and log in to the AWS management console: http://aws.amazon.com/console/
Go to the tab for EC2.

Choose data center
Now it is time to choose the data center for your first Windows server instance. Use the Region drop
down menu in the top left corner.
Choose a data center that is close to your players. What you want is the lowest possible latency
between the game servers and your players. It is possible and easy to set up Windows server
instances in several data centers, but this guide will cover the first instance in just one data center.

Create a Windows instance
Launch a new instance. A wizard to help you do this will be started.
• Select Microsoft Windows Server 2012 R2 Base, 64 bit
• Select a t2.micro instance if this is just for testing, to keep hosting cost to a minimum.
Otherwise you can choose any instance type your game servers will need.
• Enable termination protection. This way you can not erase the Windows server instance by
• Key = Name, Value = Arma3Server (Or choose whatever you want here, this is just a text
description for the instance to make it easier to know the purpose of this instance, when you
have several similar instances.)
• Select Create a new Key Pair. Note: You will only need to do this once for this Amazon EC2
• Choose the default security group.

Start the Windows instance
Start the instance.
On the page with a list of all your instances, make sure the instance has started and the status check
in OK.
NOTE: The Windows server will have the same IP even if it is rebooted. If you stop and start the
instance however, the IP will change.

Connect to the instance
On the page with a list of all your instances, make sure the instance has started and the status check
in OK, then click the button marked Connect at the top of the screen. In the pop-up window, select
Get Remote Desktop File. Once this downloads and opens up, select yes to any security pop-ups
until you get to the Windows login screen. Minimize the remote desktop window and go back to the
AWS page. In the same pop-up as before, select Get Password. Follow the instructions to decrypt
the password. This will be the Windows login password. Reopen the remote desktop connection and
log in. You can then minimize or close this window for now. Reopen the downloaded remote
desktop file to connect again.

Configure the EC2 firewall
Back in the AWS Dashboard for your instance, select Security Groups from the left hand side
options and select Create Security Group. Enter whatever name and description you wish. Select the
inbound tab, press Add Rule and add the following:
• Inbound Custom UDP rule: port 2302-2305, source Anywhere (
• If you will be hosting several Arma 3 servers, then leave at least 10 ports between the next
port range (e.g. 2312-2315)

Configure Windows Firewall
Open the Remote Desktop Connection to your instance for this step. Open up the Server Manager
application from the start menu or task bar. In the top right, from the drop down menu marked
Tools, select Windows Firewall with Advanced Security. In the firewall manager window, from the
list on the left, select Inbound Rules then select New Rule from the right side list and follow the
steps to allow UDP port range 2302-2305, similar to the previous step.

Install Arma 3 Server
Now you are ready to install the Arma 3 server on the instance. For information on how, just follow
Bohemia Interactive's Dedicated Sever Guide, for Windows, of course. I could include the steps in
this guide, but I would just be copy-pasting.

Sources and Useful Links
To put this guide together, I used content and information from the following sources:
- Bohemia Interactive's dedicated server wiki page.
- Amazon EC2 Windows guide.
- Amazon EC2 pricing guide
- Official Arma 3 Server & Administration forum.
- Arma 3 development Subreddit.
- Arma 3 Subreddit
- I used this guide as the framework for putting mine together. A lost of the information is outdated
as the AWS interface had changed.
Thanks for reading, sorry for any errors and if you end up getting billed a shit ton from Amazon,
don't blame me.
- mk101
BTC: 14RrKbVHmi8Se4ES6U2bPdLoy7AK1PN14b

Document preview armaAWSguide.pdf - page 1/1

Related documents

ec2 instance run command remote1295
untitled pdf document
resolute issues with the hosted quicken for windows
microsoft support for windows xp performance and windows 7

Related keywords