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. AWS Setup - Click-by-Click

4.3-Creating the S3 bucket

Previous4.2-Choosing the AWS RegionNext4.4-Virtual Private Cloud - Default VPC

Last updated 5 years ago

Was this helpful?

Let's create the storage space for our parameters and scripts : an S3 bucket.

KEEP IT PRIVATE !! KEEP IT PRIVATE !! KEEP IT PRIVATE !! KEEP IT PRIVATE !!

Do you need me to repeat, or is that clear enough ?

So let's go to the S3 console (S3 is in the Storage section on the main console listing all services) :

Step 1 : Give it a name, which must conform to some name restrictions, and be unique (if warnings/errors show up, you'll need to change the name before continuing further), check the region.

You can choose any name of your liking.

The "configuration name" will have sub-folders named after it inside this bucket later on.

Then hit "Next" (to step 2)...

Step 2 : let's NOT use any option and simply click "Next" (to step 3)...

KEEP IT PRIVATE !! KEEP IT PRIVATE !! KEEP IT PRIVATE !! KEEP IT PRIVATE !!

Step 3 : Let's keep the security tight and "Block all public access" as is the default !

Then hit "Next" (to step 4)...

A quick review of our choices, then click "Create bucket"...

...and here is your own private bucket, reporting for duty !

You can guess : we'll click the blue "Create bucket" button for another 4-steps process...

If you already forgot...

🙄
👆
👆
👇
👇
Our bucket is ready