Lyftrondata
  • Introduction
    • About Lyftrondata
    • Lyftrondata Feature
    • Lyftrondata System Architecture
      • Lyftrondata Integration Framework
      • Lyftrondata Connector Framework
    • Core Concepts
      • Data Pipelines
      • Vision and Goals
      • Sources and Destinations
        • Types of Sources
        • Types of Destination
    • Free Trial
    • Lyftrondata Apps
      • Data Loader
        • Full Load
        • Incremental Load
      • Data Mirror
        • Prerequisite
        • Integration
      • Data Vault
      • ELT
      • ETL
      • Data Analytics
    • Faq
  • Lyftrondata Connectors
    • Source
      • πŸ“ΆSales Analytics
      • πŸ‘¨β€πŸ’»Technology Analytics
      • πŸ’ΈFinance Analytics
      • πŸ“ŠBusiness Analytics
      • 🀝Marketing Analytics
      • πŸ‡ΈπŸ‡΄Commerce Analytics
      • ☁️Weather Analytics
      • πŸ”ƒSupply Chain Analytics
      • ⏳Human Resources Analytics
    • Destinations
  • Managing Lyftrondata
    • Lyftrondata Installation
      • Requirements
      • On AWS Deployment
      • On AWS Deployment Using AMI
      • On Azure Deployment
      • On DigitalOcean Deployment
      • Deployment Info
    • Configure Lyftrondata
      • AWS S3/IAM User
      • Wasabi
      • Settings and Security
  • Developer Guides
    • Understand Lyftrondata
      • Lyftrondata Architecture
      • Libraries and Dependencies Used in Our Application
      • Services used by Lyftrondata
Powered by GitBook
On this page
  1. Managing Lyftrondata
  2. Configure Lyftrondata

Wasabi

Lyftrondata can use wasabi bucket to store and get the logos, connector and tenant details.

PreviousAWS S3/IAM UserNextSettings and Security

Last updated 1 year ago

Step 1: Access Wasabi Management Console

  1. Navigate to the wasabi Management Console by visiting and sign in with your Wasabi account credentials.

Step 2: Create Wasabi Buckets

The application requires three Wasabi buckets: <your-company-default-bucket-name>, <your-company-connectors-bucket-name>, and a <your-public-company-logos-bucket-name> bucket with a public ACL policy attached. Follow these steps to create the buckets:

  1. Click on the "Services" menu in the top-left corner of the console and select "S3" under the "Storage" section.

  2. Click on the "Create bucket" button.

  3. Enter a name for your buckets according to above suggested <your-company-default-bucket-name> and choose the region where you want to create the bucket. Click "Create bucket" to proceed.

  4. Repeat steps 2-3 to create the <your-company-connectors-bucket-name> and public <your-public-company-logos-bucket-name> buckets, ensuring the desired region for each bucket.

  5. For the public <your-public-company-logos-bucket-name>, select the bucket after creation and click on setting and navigate to the "Permissions" tab.

  6. Under "Bucket policy," click on "Edit" and paste the following JSON policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowPublicRead",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": [
        "s3:GetObject",
        "s3:GetObjectVersion"
      ],
      "Resource": "arn:aws:s3:::your-public-company-logos-bucket-name/*",
      "Condition": {
        "StringLike": {
          "aws:Referer": [
            "YOUR-OFFICE-PUBLIC-IP/32" 
          ]
        }
      }
    }
  ]
}

Replace <your-public-company-logos-bucket-name> with the name of your public logos bucket.

  1. For the connectors bucket, repeat the 5 and 6 steps and use the below JSON policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowPublicRead",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": [
        "s3:GetObject",
        "s3:GetObjectVersion"
      ],
      "Resource": "arn:aws:s3:::<your-company-connectors-bucket-name>/*",
      "Condition": {
        "StringLike": {
          "aws:Referer": [
            "YOUR-OFFICE-PUBLIC-IP/32"
          ]
        }
      }
    }
  ]
}
  1. Click on "Save changes" to apply the policy.

Step 3: Verify Setup

You can verify the setup by navigating back to the "Buckets" dashboard in the S3 service of the AWS Management Console. Ensure that all three buckets (<your-company-default-bucket-name>, <your-company-connectors-bucket-name>, <your-public-company-logos-bucket-name>) are listed.

Step 4: Create Wasabi User:

  • Go to "Users" and click on create user button.

  • Enter a username for the new wasabi user and select "Programmatic (create API key)". You can also choose "Console access" if you want the user to have access to the Wasabi Console.

  • Click "Next: Groups" if you want to add that user in to any group". You can skip this by clicking next button.

  • Click" Next: Policies" to proceed.

  • Attach the custom policy which you have created earlier and click next to review the user then create user.

  • Pop up will occur to copy Access Key and Secret Key or download the csv file which contains the Access Key and Secret Key.

Step 5: After user and bucket creation

Follow the lyftrondata installation for installation.

document
https://console.wasabisys.com/