Backup Storage

Last update: October 05 2026Open in Markdown

By default, all backups are stored in a service bucket in Selectel S3. You can create backup storage — a bucket in S3 where infobase backups can be saved.

Using your own backup storage provides full access to backup files, allows you to configure replication to another pool, download backups, and migrate them to third-party infrastructure outside of Selectel.

You can work with backup storage in the control panel or via the Cloud for 1C API. Learn how to work with S3 in the S3 product overview instruction.

How it works

You create backup storage based on an existing or new S3 bucket, after which you can save all new backups there.

S3 has a flat address structure—there are no folders or hierarchy in the storage, but for convenience, you can create and view simulated folders (directories). A folder name is a prefix in an object name. When connecting a bucket, you can specify a prefix and configure saving backups to a simulated folder.

There are three ways to connect S3:

• automatically — you can attach an existing bucket or create a new one. The service user and access policies for working with the bucket will be created automatically;
• manually — you can attach an existing bucket. You must create the service user and access policies manually;
• using the API — you can attach a bucket from any projects accessible to a service user with the S3 User role. You must create the service user and access policies manually.

Bucket limitations and recommendations

Only buckets with Virtual-Hosted addressing can be attached to the backup storage. A single bucket or simulated folder can only be attached to one storage in the selected pool and project.

The backup storage and the information database must be in the same pool. The S3 bucket can be in any pool.

For optimal performance, we recommend choosing buckets that are:

• private;
• in the region where the infobase is located.

A bucket is connected to backup storage using a service user and bucket access policies. If you modify or delete the service user or bucket access policies:

• the backup storage will switch to the ERRORED status;
• saving backups to storage will be unavailable;
• the backup plan will be disabled for all related information databases;
• downloading backups will only be available from S3.

Pricing

Storing files in a bucket is charged according to the S3 pricing model and prices.

When an infobase is deleted, backups in the linked bucket will be stored for another 30 days. When backup storage is deleted, backup files are not deleted and continue to be billed — to stop billing, delete the buckets.

Create backup storage automatically

When creating storage, the following will be created and configured by default:

• service user GO1C_SERVICE_USER;
• access policy for the service user GO1C_UPLOAD_BACKUP_POLICY;
• access policy for the current user ALL_OTHER.

A bucket can be attached automatically by a user with the Account Owner role and users with role combinations:

• member in the Account scope and iam.admin;
• member in the Project scope and iam.admin.

New bucket

1. In the control panel, in the top menu, click Products and select Cloud for 1C.

2. Go to the Backups section.

3. Click Create backup storage.

4. Select the region and pool where the backup storage will be created. The pools of the infobase and backup storage must match.

5. Select the backup storage creation method — Automatically.

6. Select the region and pool where the bucket will be created. We recommend creating the bucket in the same region as the infobase.

7. In the Bucket field, select New S3 bucket. A private bucket with Virtual-Hosted addressing and Standard storage class will be created.

8. In the Bucket name field, enter the name of the new bucket. For S3 API compatibility, the bucket name must be unique within S3 and comply with Amazon S3 bucket naming rules; for more details, see the Bucket naming rules guide in the Amazon documentation.

9. In the Prefix field, specify the prefix for the simulated folder (directory) where the backup files will be stored.

   If you need to create a new folder, specify its name according to Amazon S3 bucket naming rules. The folder will be created when you create the backup storage.

   If you want the backup files to be stored in the root of the bucket, leave the field empty.

10. Click Create.

Existing bucket

1. Make sure that the bucket meets the bucket limitations and recommendations.

2. In the control panel, in the top menu, click Products and select Cloud for 1C.

3. Go to the Backups section.

4. Click Create backup storage.

5. Select the region and pool where the backup storage will be created. The pools of the infobase and backup storage must match.

6. Select the backup storage creation method — Automatically.

7. Select the region and pool where the bucket is located.

8. In the Bucket field, select a bucket from the list.

9. In the Prefix field, specify the prefix for the simulated folder (directory) where the backup files will be stored.

   If you need to create a new folder, specify its name according to Amazon S3 bucket naming rules. The folder will be created when you create the backup storage.

   If you want the backup files to be stored in the root of the bucket, leave the field empty.

10. Click Create.

Create backup storage manually

1. Prepare the bucket for connection.
2. Create backup storage.

1. Prepare the bucket for connection

Create a new bucket

1. Make sure that you are in the project where the infobase is located.

2. Create a service user with the S3 User role and access to the project where the bucket will be created.

3. Create a bucket in S3. Take into account the bucket limitations and recommendations.

4. Open the page of the created bucket → Access Policy tab.

5. Click Create access policy.

6. Add a rule for the service user:

   • in the Access field, select Allow;
   • in the Users field, select Authorized and add the service user you created in step 2;
   • in the Action set field, select Editor.

7. Add a rule for control panel users:

   • in the Access field, select Allow;
   • in the Users field, select Authorized and add the user who will attach the storage to the 1C cluster;
   • in the Action set field, select All.

8. Click Save.

9. Issue S3 keys to the service user.

Prepare an existing bucket

1. Make sure that the bucket meets the bucket limitations and recommendations.

2. Make sure that you are in the project where the infobase and S3 bucket are located.

3. Create a service user with the S3 User role and access to the project where the bucket is located.

4. Go to the section S3 → Buckets.

5. Open the page of the created bucket → Access Policy tab.

6. Click Create access policy.

7. Add a rule for the service user:

   • in the Access field, select Allow;
   • in the Users field, select Authorized and add the service user you created in step 3;
   • in the Action set field, select Editor.

8. Add a rule for the user:

   • in the Access field, select Allow;
   • in the Users field, select Authorized and add the user who will attach the storage to the 1C cluster;
   • in the Action set field, select All.

9. Click Save.

10. Issue S3 keys to the service user.

2. Create backup storage

1. In the control panel, in the top menu, click Products and select Cloud for 1C.

2. Go to the Backups section.

3. Click Create backup storage.

4. Select the region and pool where the backup storage will be created. The pools of the infobase and backup storage must match.

5. Select the backup storage creation method — Manually.

6. Select the region and pool where the bucket is located.

7. In the Bucket field, select the bucket that you prepared earlier.

8. In the Prefix field, specify the prefix for the simulated folder (directory) where the backups will be stored.

   If you need to create a new folder, specify its name according to the Amazon S3 bucket naming rules. The folder will be created automatically when creating the backup storage.

   If backups are to be stored in the bucket root, leave the field empty.

9. In the S3 keys block, specify the Access key and Secret key for the service user that you created when preparing the bucket.

10. Click Create.