1. Feature Overview
All files uploaded through custom field sets are securely stored in the LeadSquared Amazon S3 account and are not publicly available. However, if you prefer, you can configure the custom field set to store files in your own Amazon S3 account.
To learn more about CFS fields, see Custom Field Sets.
2. S3 Bucket Configuration
Before connecting your Amazon S3 bucket with LeadSquared, ensure –
1. The bucket is created in the same region as your LeadSquared account. The following are the valid LeadSquared regions –
- ap-south-1
- ap-southeast-1
- us-east-1
2. Add the following policy to the S3 bucket –
"Version":"2012-10-17",
"Statement":[
{
"Sid":"VisualEditor0",
"Effect":"Allow",
"Action":[
"s3:DeleteObjectTagging",
"s3:GetObjectRetention",
"s3:DeleteObjectVersion",
"s3:GetObjectVersionTagging",
"s3:PutObjectVersionTagging",
"s3:ListBucket",
"s3:DeleteObjectVersionTagging",
"s3:GetObjectLegalHold",
"s3:ReplicateObject",
"s3:GetObjectVersionTorrent",
"s3:PutObject",
"s3:GetObjectAcl",
"s3:GetObject",
"s3:PutObjectVersionAcl",
"s3:GetObjectVersionAcl",
"s3:PutObjectTagging",
"s3:GetObjectVersionForReplication",
"s3:DeleteObject",
"s3:PutObjectAcl",
"s3:ReplicateDelete",
"s3:GetObjectVersion"
]
}
]
}3. The bucket settings under the Permissions tab are set as follows –
4. Add the following CORS configuration to the bucket –
[
{
"AllowedHeaders": ["*"],
"AllowedMethods": ["GET","HEAD"],
"AllowedOrigins": ["https*"],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
},
{
"AllowedHeaders": ["*"],
"AllowedMethods": ["GET","HEAD"],
"AllowedOrigins": [
"http*"
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
},
{
"AllowedHeaders": ["*"],
"AllowedMethods": ["GET","HEAD"],
"AllowedOrigins": [
"*"
],
"ExposeHeaders": [],
"MaxAgeSeconds": 3000
}
]
3. Connect Your S3 Bucket to LeadSquared
On your LeadSquared account –
- Navigate to My Profile>Settings>Leads>Configure Custom Filed Sets.
- From the Authentication Type drop-down, select either Access Key and Secret Key or Cross Account IAM Role (Amazon’s recommended authentication method).
- The Role ARN must be created as follows –
- Format: arn:partition:service:region:account-id:resource-type/lsq-resource-*
- Example: arn:aws:iam:234567898765:role/lsq-resource-file-upload
- Copy and add the ARN mentioned on the UI to your role Trust Relationship.
Any Questions?
Did you find the content in this article helpful? Feel free to leave doubts/questions in the comment section below. We’ll get back to you as soon as possible.
