-
标题
Amazon S3: Backup, Restore and Permissions for LiteSpeed -
说明
Amazon S3: Backup, Restore and Permissions for LiteSpeed -
解决办法
Amazon S3: Backup, Restore and Permissions for LiteSpeed
Setup Amazon S3 account on LiteSpeed Console:
Click the book icon on the ribbon | Cloud Accounts | Add
For the Cloud Vendor field, select Amazon S3 from the dropdown, and enter the account information.
Note: make sure the correct bucket is selected.
Create a backup folder on Amazon cloud under the selected bucket:
Example below shown that backup folder called LS Backups is created under the bucket of huynh-s3-bucket.
Backup to Amazon S3
Follow the Backup UI as you backup to local disk.
On the Backup Destination page:
Select Cloud from the dropdown for the Backup to field.
Select the correct cloud account.
Click the three dots to select the backup folder.
The Backup Destination page should look like this after all information are filled.
Follow the wizard to complete the backup settings.
Verify the backup files are created on the Bucket’s backup folder.
Restore from Amazon S3
Follow the Restore UI as you restore from local disk.
On the Specify Backup Source page:
Select the Cloud option and click Next.
On the Select Backup Files page:
Select the correct cloud account from the dropdown.
Click the three dots to select the backup folder.
Select the file from the backup folder.
The Select Backup Files page should look like this after all information are filled.
Follow the wizard to complete the restore settings.
Amazon S3 Permissions:
The Amazon S3 account should have the following permissions to perform backup and restore tasks.Notes: If customers have permission issues/questions, they should contact Amazon tech support directly.
For LiteSpeed version 8.9.5:
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:Get*",
"s3:PutObject",
"s3:DeleteObject",
(Note: DeleteObject is only needed if you want to delete backups or use the Litespeed parameter “init=1.”, You should assign this permissions to the user, if not the login will fail.)
Here is an IAM example policy with minimum access:
Example Policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "test1",
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:PutObject",
"s3:Get*",
"s3:DeleteObject"
],
"Resource": [
"arn:aws:s3:::bucket",
"arn:aws:s3:::bucket/*" ]
}
]
}
For LiteSpeed version 8.9.1:"s3:ListBucket",
"s3:GetBucketLocation",
"s3:Get*",
"s3:PutObject",
"s3:DeleteObject",
(Note: DeleteObject is only needed if you want to delete backups or use the Litespeed parameter “init=1.”)
Here is an IAM example policy with minimum access:
Example Policy:
{"Version": "2012-10-17","Statement": [{"Sid": "test1","Effect": "Allow","Action": ["s3:ListBucket","s3:GetBucketLocation","s3:PutObject","s3:Get*","s3:DeleteObject"],"Resource": ["arn:aws:s3:::bucket","arn:aws:s3:::bucket/*" ]}]}For LiteSpeed version 8.9.0:
"s3:ListBucket","s3:GetBucketLocation",
"s3:Get*",
"s3:GetObject",
"s3:PutObject",
"s3:ListMultipartUploadParts",
"s3:AbortMultipartUpload",
“s3:ListAllMyBuckets”,
“s3:ListObjects”,
“s3:DeleteObjects",
"s3:DeleteObject",
(Note: DeleteObject is only needed if you want to delete backups or use the Litespeed parameter “init=1.”)
Here is an example IAM policy with minimum access:
Example Policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "test",
"Effect": "Allow",
"Action": [
"s3:ListAllMyBuckets"
],
"Resource": "*"
},
{
"Sid": "test1",
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation",
"s3:PutObject",
"s3:Get*",
"s3:GetObject",
"s3:DeleteObject",
“s3:DeleteObjects",
"s3:ListMultipartUploadParts",
"s3:AbortMultipartUpload",“s3:ListObjects”],"Resource": [
"arn:aws:s3:::bucket",
"arn:aws:s3:::bucket/*" ]
}
]
}
For LiteSpeed versions 8.8. and lower:
"s3:ListBucket","s3:GetBucketLocation",
"s3:Get*",
"s3:GetObject",
"s3:PutObject",
"s3:ListMultipartUploadParts",
"s3:AbortMultipartUpload",
"s3:DeleteObject",
(Note: DeleteObject is only needed if you want to delete backups or use the Litespeed parameter “init=1.”)
Here is an example IAM policy with minimum access:
Example Policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:GetBucketLocation"
],
"Resource": "arn:aws:s3:::mybucket"
},
{
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:Get*",
"s3:GetObject",
"s3:ListMultipartUploadParts",
"s3:AbortMultipartUpload",
"s3:DeleteObject",
],
"Resource": [
"arn:aws:s3:::mybucket/folder/*"
Note: administrator access is just a policy that looks something like this:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "*",
"Resource": "*"
}
]
}