Minecraft Java Edition Indir
Ted Brathwaite
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
My kids recently asked if they can start playing Minecraft with their friends. After a little discussion I discovered that they were all just playing single player and talking about it later. Well, we all know one of the joys of Minecraft is playing with your friends on a server - so I set about setting up a safe server space for them all.
- Bedrock: this is the newer 'unified' version that allows cross platform play for every platform except Mac/Linux using the Bedrock Client.
- Java Edition: this is the original version (kept up to date) that allows cross play for Windows, Mac and Linux provided you are using the Java Edition Client.
After realising that Franck's tutorial is for Bedrock, and my kids would need Java I tried finding and following various tutorials online. Very few of them would work, simply because Amazon moves so quickly with the EC2 Instances, it's hard for tutorials to stay relevant. I even spent a good hour on the phone to a geek mate Jack Skinner to pick his brains looking at ports and routing, tcp/udp - to no avail.
You have a number of options for the type of instance you want. Franck managed to get Bedrock to run on a t2.micro, however the Java Edition is a bit more intense and so you will need a t2.small or a t2.medium to run, depending on how many connections you'll have. For 2 to 3 kids a t2.small will be fine. Once selected click Configure Instance Details.
Here you can enter a Name tag and a value for this. This will show up on the main instance screen and allows you to easily find it if you have lots of instances. You can also tag for a cost centre here too if you split/manage your billing with tags. The last screen is the Security Group screen.
This is the screen where we allow access to the server. I created a security group with the name MineCraft-Server (and a description for easy remembering later), and then added a rule for Custom TCP. Minecraft Java Edition communicates with TCP over port 25565. Set the source to Custom and 0.0.0.0/0 to allow access from anywhere and add a description.
Hit review and launch and fire up your instance. This will pop up a window for creation of a security key pair. Now if you are familiar with SSH and remote connecting to a server, feel free to do this (highly recommended), however if you don't want to faff around with SSH, then choose Proceed without a key pair. (note this means you will NOT be able to SSH to the instance)
AWS removed Java from their Amazon Linux EC2 machines, so we'll have to install a version and this is where I ran into all sorts of issues. I used various tricks to install Java 1.8.0 and OpenJDK Java 11, making sure it was always up to date, but no matter what I did I always ran into an issue where the Minecraft Java Server edition was complied with a newer version. We have to use Amazon Corretto to get Java 16 installed, which will then run Minecraft.
We'll use the EC2 Instance Connect to open up a new browser window with an SSH like terminal in it for working with our box. Check the details (record the Public IP Address - you'll need that for connecting Minecraft later) and click Connect.
But don't get too excited yet, it's about to fail for you. The first time you run this it looks to check if the eula file has been accepted. And because the file never existed it sets one up for you. Your SSH window should look like this.
This will bring you into the file to edit it. Use the arrow keys to move the box cursor around to the end of line with eula=false. Now to edit it hit i on your keyboard and you should see the word -- INSERT -- at the bottom of the screen. You are now in edit mode. Change the false to true.
That's it, now we can start our server - but before we get carried away, if we simply run the java command again now, as soon as we close the SSH window our server will stop running. We need a way to keep it running, so we'll use screen to do that.
I hope that helps - given the speed at which AWS and the world of software moves this might well be out of date as soon as I post it. Maybe it'll help someone, I know it's meant my kids have a server to play on with their friends customised to their needs.
Update: kids had a bit of a nasty surprise today when one of their friends' brother decided to share the server details with not so nice folks. So we very quickly explored creating a whitelist. This isn't hard, you simply create a .json file with the uuid and name of each person you want to allow access to the server, then in server properties you allow white_list to true. For more details check out this article
d3342ee215