FM BetterForms Docs
BF Editorfmbetterforms.com
Engineering Reference Docs
Engineering Reference Docs
  • BF Streaming Proxy
  • Updating the Helper File
  • Connection Trouble Shooting Guide
  • Software Testing - Overview
    • Types of Testing
    • UX/UI Checklist
      • Pages
        • Login 🔑
        • Pricing 💵
        • 404 🤷‍♂️
        • Contact Us ☎️
        • Sign Up 👋
        • FAQ ❓
        • Blog Post 🗞
        • Careers 💼
        • Team 👫
        • Cart 🛒
        • Press 📸
        • Search results 🔍
      • Elements
        • Avatar 😁
        • Badge 📛
        • Button 🖲️
        • Card 🃏
        • Table 📏
        • Icon 🌠
        • Text Field ⌨️
        • Toggle 🎛️
        • Loading ⏳
        • Modal 🎉
        • Tooltip 🛠
        • Search 🕵️‍♀️
        • Navigation 🧭
        • Radio 📻
        • Checkbox ☑️
        • Tabs 🗂
        • Toast 🍞
      • Flows
        • Submitting a form 📨
        • Making a payment 💳
        • Contacting support 🆘
        • Deleting account 🗑
        • Tracking progress 📈
        • Resetting password 🤫
        • Showing input error 🚨
        • Entering a promo code 🏷️
        • Saving changes 💾
        • Canceling subscription 🛑
      • Topics
        • Responsiveness 🎚
        • Typography 🔤
        • Dark mode 🌑
        • Accessibility 🚹
        • Colors 🎨
        • UX Writing ✏️
      • Brand
        • Logo 💠
        • Social Media 🔉
        • Typography 🔠
    • FM BetterForms - Quality Assurance
    • JavaScript Libraries
  • Rollbacks and Version Control
  • BF Server Proxy
  • Base code End of Life - 0.8.78-0.8111
  • Setting up Auth0
    • Introduction
    • Getting started
      • Creating a tenant
      • Creating Application
      • Additional customizations
        • Allowed Callback URLs
    • Creating a Database
      • Choosing different login options
        • Social Connections
        • Username and password (Auth0)
        • Creating new BF Users
        • Using Auth0 in an iFrame
        • Configuring FM BetterForms
        • Additional Notes
  • Create an S3 Bucket on AWS
  • ApexCharts - Getting started
  • BF Enterprise Documentation
    • Overview
      • Features
      • Overview Diagram
    • Requirements
    • Env File
    • Setting up the Server
      • Installation
      • Loading image to a local repository
      • Starting server
      • Restarting Policies
      • Scaling up
    • Hardware Recommendations
    • FM Credentials - Helper file
    • How it works
      • Development
      • Downloading environment data
  • BetterForms Error Pages API
    • Introduction
    • Dynamic Error Page
    • Static Error Page
    • Custom error pages
    • Custom error handlers
    • Error Code List
  • BF Streaming API
  • Creating a PWA
    • Introduction
    • Getting Started
      • Making it installable
      • Browser Support
      • Sending Push Notifications
      • Sending a Push Notification from the API Endpoint
      • Adding DOM Header Insertion to be Available for Offline Use
Powered by GitBook
On this page
  • Description
  • Instructions
  • Credentials needed for BetterForms

Was this helpful?

Create an S3 Bucket on AWS

PreviousAdditional NotesNextApexCharts - Getting started

Last updated 11 months ago

Was this helpful?

Description

This is an example of how a bucket can be set up to allow specific domain(s) to upload, download, and delete objects to/from the bucket.

Instructions

  • Go to the AWS Console and choose S3

    • Type s3 on the search bar and the service will show up

  • Click on Create Bucket

  • Choose a unique bucket name (AWS will do the validation, and that involves ALL buckets from a given region, not only buckets associated to your account)

  • Select an AWS Region

  • On Block Public Access settings for this bucket leave unchecked only the box for Block public and cross-account access to buckets and objects through any public bucket or access point policies

  • Click on Create bucket

Once the bucket is created, select the newly created bucket and go to the Permission tab.

  • Scroll to the section Cross-origin resource sharing (CORS)

  • Click on Edit, shown on image above, and you will be redirected to the following page.

[
    {
        "AllowedHeaders": [
            "*"
        ],
        "AllowedMethods": [
            "PUT",
            "POST",
            "DELETE",
            "GET"
        ],
        "AllowedOrigins": [
            "<https://my.example.com>",
						"https://*.examples.com"
        ],
        "ExposeHeaders": [
            "x-amz-server-side-encryption",
            "x-amz-request-id",
            "x-amz-id-2"
        ],
        "MaxAgeSeconds": 3000
    }
]

The example above shows an object that allows origins to upload (POST / PUT), download (GET), and delete (DELETE) objects. If one of these actions should not be allowed, remove them from the methods.

Credentials needed for BetterForms

In order to be able to communicate with the bucket, we need to add the AWS access key and secret access key, it can be either an existing or newly created one.

  • If a new one needs to be created, click on the account button located on the top right, and select Security credentials.

  • Under the tab AWS IAM credentials, click on Create Access key. Download the .csv file with the secret key and save it on your local machine.

Fields that will be needed for BetterForms to create a signed URL include:

  • Region (ex. us-west-1)

  • Access Key

  • Secret Access Key

  • Bucket Name

Use a CORS configuration written in JSON, like the example below. More examples on CORS can be found on

Host (ex. )

AWS docs
s3.amazonaws.com