Wise App
  • Wise API Integration
    • Getting Started with Wise APIs
    • API Authentication
    • API Endpoints
    • SSO Integration
    • Webhooks Integration
      • Webhook Retry Mechanism
      • Webhook Event Samples
        • Participant Joined Meeting Event
        • Sharing Stared In Meeting Event
        • Participant Left Meeting Event
        • Sharing Ended In Meeting Event
        • Meeting Started Event
        • Meeting Ended Event
        • Recording Completed Event
        • Certificate Issued Event
        • Attendance Computed Event
        • Student Added To Classroom Event
        • Teacher Added To Classroom Event
        • Student Removed From Classroom Event
        • Teacher Removed From Classroom Event
        • Student Suspension Updated Event
        • Fee Payment Completed Event
        • Fee Invoice Charged Event
        • Sessions Created Event
        • Sessions Updated Event
        • Sessions Deleted Event
    • Rate Limits and Usage Quotas
    • Common Errors
  • Wise Data Storage Policy
  • Wise Android & IOS SDKs
    • Wise Android SDK (Kotlin)
    • Wise Android SDK (Java)
    • Wise Flutter SDK
    • Wise Flutter SDK - iOS Integration
  • Third Party Integrations
    • Custom Payment Gateway Integration
      • Razorpay Payments
      • Stripe Payments
    • AWS S3 storage
    • Custom Email
Powered by GitBook
On this page
  • Create S3 Bucket (Optional)
  • Create Policy
  • Create an IAM User
  • Share the details with Wise team
  • FAQs
  1. Third Party Integrations

AWS S3 storage

Create S3 Bucket (Optional)

Create a dedicated bucket to store recordings generated by WISE. This is optional.

If you wish to store these recordings on an existing bucket, then this step can be skipped

Create Policy

  1. Create new policy in AWS

    • Policy name: WiseS3FileUploaderPolicy

    • Description: Policy to allow WISE platform to upload the raw Zoom recordings of the sessions conducted on WISE

  2. Put below JSON in order to grant the S3 upload access

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Sid": "VisualEditor0",
                "Effect": "Allow",
                "Action": [
                    "s3:GetObject",
                    "s3:PutObject",
                    "s3:PutObjectAcl",
                    "s3:ListBucket"
                ],
                "Resource": "arn:aws:s3:::<bucket_name>/*"
            }
        ]
    }
    • <bucket_name>: Put the bucket name of the existing/new bucket that you have chosen.

    • path: You can grant access as * (any path inside bucket) and choose the actual path in the Wise configuration.

    Alternatively, you can put the exact path where you want to store the files at, in order to put a restrictive access. If you do so, ensure that actual path in Wise configuration should match with this, otherwise the upload will fail due to insufficient permissions.

Create an IAM User

  1. Create an IAM user with name “WiseS3FileUploader”

  2. Proceed next to assign policy

  3. Assign the policy WiseS3FileUploaderPolicy that was created in the previous step

  4. Proceed to create user

  5. Click on the newly created user to visit its settings page

  6. Go to “Security Credentials” tab, go to “Access Keys”

  7. Proceed with “Create Access Key” option and choose “Third party service” option.

  8. Proceed to generate the keys. Download the CSV file for the generated keys and save it at a safe location.

  9. Share this file with Wise team

Share the details with Wise team

Please share the below details with Wise team

  1. Credentials file: You can share the entire credentials file which you would have got while creating IAM User in Step 9. Or you can share the Access Key and Secret Key individually.

  2. Bucket Name: Name of the bucket that you have chosen ex: mycompany-wise-recordings

  3. Path: Path inside the bucket where the files should be stored ex: "", "/production", "class_recordings", etc. Do not put spaces or special characters

  4. Region of the Bucket

FAQs

  1. What will be the name of the recording file when it is saved?

    The recording file will be named <sessionId>.mp4 and will be saved in the following location s3://<bucket>/<path of your choice>/<sessionId>.mp4. ****Please note that the sessionId would be Session ID in Wise

  2. Will the recording file be accessible on the Wise platform for downloading?

    Yes, the recording file will only be available via GetSession API and will not be accessible via the Wise platform.

  3. Will the recording file be accessible on the Wise platform for viewing in the Courses?

    If the Institute setting to share Session Recordings in the course is enabled, the recordings will the HLS encrypted and saved in Wise’s S3 (not client S3 location). The session recordings will be streaming using this HLS encrypted file.

  4. Will the link of the recording file we available in the sessions API?

    Yes, the API response will continue to have the link of the rawRecording file as currently available.

PreviousStripe PaymentsNextCustom Email

Last updated 23 days ago