Fantasy Grounds - Port Forwarding - Transparent Op
  • Fantasy Grounds - Port Forwarding and a "transparent" OpenVPN setup
  • General
    • Introduction - F.G.Comms
    • GM's machine barriers
    • Internet connection barriers
    • Some NO-GO Situations
    • VPN solutions
  • Proposed Solution
    • "Transparent" OpenVPN-based Port Forwarding
    • Tools
    • Amazon Web Services
    • Setup process overview
  • Local setup - Step-by-step
    • Step 0 : Preparation
    • Step 1 : OpenVPN + Easy-RSA & "new-PKI"
    • Step 2 : Create your own PKI
    • Step 3 : Setup OpenVPN connections
  • AWS Setup - Click-by-Click
    • Step 4 : Your AWS environment
    • 4.1-Creating the IAM Role
    • 4.2-Choosing the AWS Region
    • 4.3-Creating the S3 bucket
    • 4.4-Virtual Private Cloud - Default VPC
    • 4.5-Creating an AWS Key Pair
    • 4.6-Creating an AWS Security Group
    • 4.7-Filling the bucket
    • 4.8-Building the Launch Template
  • Transfer & First Test
    • Step 5 : Transfer to S3
    • Step 6 : Launch time !
    • Step 7 : Connect, test, fix glitches
    • Step 8 : Destroy/"Terminate" after use
  • Use your server
    • Regular Usage Pattern
  • Simultaneous FG games / 1 VPN Server
    • Lifting the "1 GM at-a-time" restriction
    • FGU vs. FGC networking
    • VPNs for both FGC + FGU (LAN mode)
  • Upgrading our setup for "N-at-a-time", FGC/FGU
    • Untitled
  • Appendixes
    • Acronyms and definitions
    • AWS acronyms
    • AWS admin user + API access key
    • AWS, DNS, DDNS, CRL...
    • Possible (?) developments
  • Links
    • Fantasy Grounds Web
    • Fantasy Grounds Discord
    • FG College Web
    • FG College Discord
    • FG College KB
    • Our "EU" Discord
    • OpenVPN
    • AWS
Powered by GitBook
On this page

Was this helpful?

  1. Transfer & First Test

Step 8 : Destroy/"Terminate" after use

PreviousStep 7 : Connect, test, fix glitchesNextRegular Usage Pattern

Last updated 4 years ago

Was this helpful?

So, we're happy ! (hopefully ?)

And we have finished our tests or game session...

And we have disconnected our VPN client connection...

So, what do we do now ?...

We break our new toy !

Ok, but why ???

Well, because :

  • when we are not hosting a game, we don't need it

  • if we are out of the Free Tier bounds, we want to keep our costs as low as possible

  • we'll be sure we can re-create our environment in a matter of minutes in the unlikely event of catastrophic failure

  • it is a good starting point to explore, later on, the for the long term.

So we go to the EC2 Console -> Instances and we "Terminate" our instance :

A quick confirmation dialog, and then our instance goes...

And after about 1 minute...

From that point, it is as if it had never existed...and after some time (1H or so ?) it will have completely disappeared from your EC2 console.

AWS Spot offer
Terminating = erradication !