Kaspersky Security Center 13.1

Working in Google Cloud

This section provides information about work with Kaspersky Security Center in a cloud environment provided by Google.

In this section

Creating client email, project ID, and private key

Working with Google Cloud SQL for MySQL instance

See also:

Scenario: Deployment for cloud environment

Page top
[Topic 193319]

Creating client email, project ID, and private key

Expand all | Collapse all

You can use the Google API to work with Kaspersky Security Center in Google Cloud Platform. A Google account is required. Please refer to the Google documentation at https://cloud.google.com for more information.

You will need to create and provide Kaspersky Security Center with the following credentials:

  • Client email

    Client email is the email address that you used for registering your project at Google Cloud.

  • Project ID

    Project ID is the ID that you received when you registered your project at Google Cloud.

  • Private key

    Private key is the sequence of characters that you received as your private key when you registered your project at Google Cloud. You might want to copy and paste this sequence to avoid mistakes.

See also:

Scenario: Deployment for cloud environment

Page top
[Topic 204070]

Working with Google Cloud SQL for MySQL instance

You can create a database in Google Cloud and use this database for Kaspersky Security Center.

Kaspersky Security Center works with MySQL 5.7 and 5.6. Other versions of MySQL have not been tested.

To create and configure a MySQL database:

In your browser, go to https://cloud.google.com/sql/docs/mysql/create-instance#create-2nd-gen and follow the instructions provided.

When configuring a MySQL database, use the following flags:

  • sort_buffer_size 10000000
  • join_buffer_size 20000000
  • innodb_lock_wait_timeout 300
  • max_allowed_packet 32000000
  • innodb_thread_concurrency 20
  • max_connections 151
  • tmp_table_size 67108864
  • max_heap_table_size 67108864
  • lower_case_table_names 1

See also:

Scenario: Deployment for cloud environment

Page top
[Topic 204066]