Skip to main content

Connect S3 to 1C server cluster

Last update:

S3 is a service for storing and distributing unlimited data.You can connect S3 to your 1C server cluster to save media files such as images and documents there.This will allow you to:

  • reduce the number of requests to the database cluster — requests for actions with files will be addressed to the storage buckets;
  • increase the reliability of media file storage — data in S3 is replicated to three independent servers in different racks;
  • edit and replace media files in the baket in the control panel or using the storage tools.

Principle of operation

You connect the storage to the 1C server cluster in the control panel, then configure the media storage method in the 1C configuration menu.

New media files will then start to be sent to the storage.Existing media files will not be automatically moved to the storage, you can move them after you connect.

Once connected and configured, you will be able to work with media files both through 1C and storage — files will be created, modified and deleted in storage, their current state will be displayed in 1C.

S3 has a flat address structure — there are no folders and hierarchy in the storage, but you can create and view simulated folders (directories) for convenience. The folder name is a prefix in the object name.

You cannot connect parent and child directories in the same bucket at the same time. For example, if the directory example/images is connected, you cannot connect its parent directory example or child directory example/images/photos, but you can connect the directory example/documents.

Two ways to connect the S3 are available:

  • automatically — you can connect an existing bucket or create a new one. The service user and access policies for working with the baquette will be created automatically;
  • manually — you can connect an existing bucket. You must create the service user and access policies yourself.

Limitations and recommendations for baquettes

Only buckets can be connected to a cluster of 1C servers:

For optimum performance, we recommend choosing buckets:

  • with a private type;
  • in the region and pool where the 1C server cluster is located.

Cost

Storage of files in the baket is charged under the S3 payment model and pricing.

When deleting a cluster of 1C servers, files from connected buckets are not deleted and continue to be charged — to stop charging , delete the buckets.

Connect the bucket to the cluster automatically

The default buckets will be created and configured when connected:

  • GO1C_SERVICE_USER service user;
  • access policy for service user GO1C_POLICY;
  • access policy for the current control panel user ALL_OTHER.

A user with the Account Owner role and users with role combinations can automatically connect the buckets:

  • Account Administrator and User Administrator;
  • Project Administrator and User Administrator.

It is possible to connect the bucket only to a cluster of 1C servers in ACTIVE status.

:::dangerWhen changing, deleting a service user or access policies, the connection to the 1C server cluster may be severed, but the connection status in the control panel will not change.::::

  1. In the control panel, in the top menu, click Products → 1C Ready Cloud → 1C Server Clusters section.

  2. Open the cluster page → Storage tab.

  3. Click Connect.

  4. Select the connection type — Automatic.

  5. In the Region and Pool fields, select the region and pool in which the bucket will be created. We recommend to create a bucket in the same region and pool as the 1C server cluster.

  6. Select New S3 buckets in the Buckets field. A private bucket with Virtual-Hosted addressing and standard storage class will be created.

  7. In the Bucket name field, specify the name of the new bucket. For compatibility with the S3 API, the name of the bucket must be unique within S3 and comply with Amazon S3 bucket naming rules, see the Bucket naming rules in the Amazon documentation.

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

    To create a new folder, name the folder according to the Amazon S3 buckets naming rules. The folder will be created automatically.

    If the media files will be stored in the baket root, leave the field blank.

  9. Click Create Connection.

Connect the buckets to the cluster manually

It is possible to connect the bucket only to a cluster of 1C servers in ACTIVE status.

:::dangerWhen changing, deleting a service user or access policies, the connection to the 1C server cluster may be severed, but the connection status in the control panel will not change.::::

  1. Prepare the tank for connection.
  2. Connect the baquette.

1. Prepare the tank for connection

  1. Make sure you are in a project that hosts a cluster of 1C servers.

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

  3. Create a baquette at S3. Observe restrictions and recommendations for the bucket.

  4. Go to 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 account:

    • 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.

  8. Add a rule for control panel users:

    • in the Access field, select Allow;
    • in the Users field select Authorized and add a control panel user who will connect the storage to the 1C cluster;
    • in the Action Set field, select All.

  9. Click Save.

  10. Issue S3 keys for the service user.

2. Connect the tank

  1. In the control panel, in the top menu, click Products → 1C Ready Cloud → 1C Server Clusters section.

  2. Open the cluster page → Storage tab.

  3. Click Connect.

  4. Select the connection type — Manual.

  5. In the Region and Pool fields, select the region and pool where the bucket is located.

  6. In the Bucket field, select the bucket you prepared earlier.

  7. In the Prefix field, specify a prefix for the simulated folder (directory) where the media files will be stored.

    To create a new folder, name the folder according to the Amazon S3 buckets naming rules. The folder will be created automatically.

    If the media files will be stored in the baket root, leave the field blank.

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

  9. Click Create Connection.

Shut down the baquette

You can disconnect a bucket only from a cluster of 1C servers in the ACTIVE status.When disconnecting a bucket from the cluster, the service user's S3 key and the access policy rule for the service user that were created for this bucket will be deleted.

  1. In the control panel, in the top menu, click Products → 1C Ready Cloud → 1C Server Clusters section.
  2. Open the cluster page → Storage tab.
  3. In the baquette line, click .
  4. Enter the name of the bacta to confirm the deletion.
  5. Click Disconnect. If the bucket is no longer needed, delete it.