AWS S3 For Recordings

Please use these instructions to share programmatic write access with Clan Meeting to upload your meeting recordings to your own cloud environment. Recordings are sent automatically at the end of each meeting.

Create a unique bucket name #

AWS S3 buckets are used to store files.

The examples below use the S3 bucket name as

your-brandname-recordings

Replace these everywhere with the format

consumerid-clanmeeting-recordings

Example:

If your Clan Meeting consumerId is hsjd9230c2, your S3 bucket name should be

hsjd9230c2-clanmeeting-recordings

Create the bucket #

1. Search for S3 in the AWS Console or sign into the AWS S3 Management Console.

2. Click the Create Bucket button.

3. Important: Enter the bucket name chosen in the previous section.

4. Select a region nearest to you. Or select as shown in the screenshot if unsure.

5. Set Object Ownership to ACLs disabled (recommended).

    

6. Leave check boxes for Block public access checked.

    

7. Set Bucket Versioning to Disable

    

   

    

8. Add any Tags if you want (optional)

    

9. Leave Default encryption at defaults: Encryption key type = Amazon S3 managed keys (SSE-S3) & Bucket Key = Enable.

    

10. Do not change any Advanced settings

     

11. Click the Create bucket button.

     

    

     

12. Check if the bucket was created successfully or not.

Create a permission policy for the bucket #

This permission policy will be assigned to the user created in a later step.

1. Search for IAM from the AWS Console or go to the AWS IAM Management Console.

2. Click Policies on the side-bar.

    

3. Click the Create Policy button.

    

   

    

4. Click the JSON tab

    

5. Copy and paste the following into the text box, taking care to replace your-brandname-recordings with the bucket name you created:

    

   xxxxxxxxxx
   19
   1
   {
   2
     "Version": "2012-10-17",
   3
     "Statement": [
   4
       {
   5
         "Effect": "Allow",
   6
         "Action": [
   7
           "s3:ListBucket"
   8
         ],
   9
         "Resource": [
   10
           "arn:aws:s3:::your-brandname-recordings"
   11
         ]
   12
       },
   13
       {
   14
         "Effect": "Allow",
   15
         "Action": ["s3:*"],
   16
         "Resource": "arn:aws:s3:::your-brandname-recordings/*"
   17
       }
   18
     ]
   19
   }
   

    

   

    

6. Click the Next: Tags button.

    

7. Click the Next: Review button.

    

8. Enter RecordingsBucketFullAccess as the Name

    

9. Description is optional

    

10. Click the Create policy button.

     

    

Create a user with access to the bucket #

1. Search for IAM from the AWS Console or go to the AWS IAM Management Console.

2. Click Users on the side-bar.

3. Click the Add users button.

4. Enter clan-meeting-recordings-user as the User name or a username of your choice.

    

5. Leave AWS Management Console access unchecked.

    

6. Click the Next: Permissions button.

    

   

    

7. Select Attach existing policies directly.

    

8. Type Recordings in the Filter policies search box.

    

   

    

9. Check the box for the RecordingsBucketFullAccess policy that was created earlier.

    

   

    

10. Click the Next: Tags button

     

11. Click the Next: Review button

     

12. Click the Create user button

     

    

     

13. Continue to the next section before closing the browser. Click on View User or the username directly.

     

    

Generate Access Keys as shown in the below screenshots #

1. Go To Security Credentials tab.

    

   

    

    

2. Scroll down to the Access Keys section and click Create Access Key.

    

   

    

    

3. Select the options as shown below.

    

   

    

   

    

    

4. Download the CSV file and share it with the Clan Meeting team.