YES iv bloody got it working haha took some doing but i got it to work without all the faffing around with stacks etc
OK HERE WE GO.. poor explanation coming up lol please note this is done on the AWS windows server.. So with this https://github.com/afloesch/rfactor2-server-setup you really only need the top part about creating an instance once it gets to cloud formation ignore it everything there is out of date and will not work no matter what. After creating the instance and key pair you need to do a few things after that. 1st thing your going to do is go to is create an elastic IP (ONE IN RED) View attachment upload_2024-2-23_20-46-44.png Once in there use this help https://repost.aws/knowledge-center/ec2-connect-internet-gateway look for this bit View attachment upload_2024-2-23_20-49-27.png use (RED HOW TO) allocate E,ip Then use (YELLOW HOW TO) associate E,ip After you have done that make your way to Security Groups if you have not made any yet this is now the time. click on the View attachment upload_2024-2-23_20-53-12.png give your security group a name and in vpc should be your info if not dont worry it will still create a security group View attachment upload_2024-2-23_20-56-12.png once done scroll down and hit create security group.. So now you will need to do the inbound and outbound rules... by default you should have in the IN & OUT View attachment upload_2024-2-23_20-58-37.png ..... View attachment upload_2024-2-23_20-58-51.png You now need to add all the rules for rf2 server to be seen you should have inbound and outbound looking like this View attachment upload_2024-2-23_21-1-2.png now were it is blanked out is were the elastic ip goes you created before how ever it wont just take the ip as it if you try to you will get this error View attachment upload_2024-2-23_21-2-15.png
you will then need to pick the option it gives you like this View attachment upload_2024-2-23_21-5-5.png once you have done that you are almost good to go the next thing you need to do is jump on your server install RF2 server using the steam CMD option head over to security settings go to windows firewall and allow the rf2.dedicatedserver.exe through the wall then you should have a fully working and viewable server on aws
UPDATE TO THIS.... set up using the elastic ip once everything else is complete run your server once then close and remove elastic ip from you aws instance the settings will continue to work..i have recently found out the elastic ip charges you when its not being use not alot but still a charge $0.0001 something like that
