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. Appendixes

AWS admin user + API access key

PreviousAWS acronymsNextAWS, DNS, DDNS, CRL...

Last updated 5 years ago

Was this helpful?

Ok let's create an AWS admin user with the AWS IAM console :

We'll give AWS console acces to this ZeFerby guy, so he needs a console password.

And we want him to be able to use SDK-based and third-party tools like CloudBerry Explorer for Amazon S3, so he'll need programmatic access as well.

Finally this guy is only a temporary user in one of my accounts, so i give him a simple password that will not live long...

Let's go on with "Next: Tags". I don't use tags here, so I click "Next: Review" :

Here I check the details are what I want and click "Create user"...

Now I download the (ugly) credentials.csv file for reference (it contains the password and the programmatic Access "Key ID" + "Secret Key") before clicking "Close" !

Adding / Removing access methods :

You can edit existing IAM Users to add / remove / edit /renew access methods : console access with password, programmatic access key, etc...

Clicking on "Next: Permissions", we arrive at this screen where we click the "Attach existing policies directly" box, and we check the mark on the AdministratorAccess listed policy :

✅
Newly created administrator IAM User