Connect a GCS archive bucket
This guide shows you how to configure a Google Cloud Storage (GCS) bucket to archive your Coralogix telemetry data in the US3 (us-central1) environment. For AWS environments, see Connect an S3 archive bucket.
Note
GCS archiving is currently available for the US3 environment only (us3.coralogix.com, region: us-central1). Contact your Coralogix representative for availability in other environments.
What you need
- A GCP project with the Cloud Storage API active.
- Permission to create buckets and manage Identity and Access Management (IAM) policies in your GCP project.
Step 1. Create a bucket
In the Google Cloud Console, navigate to Cloud Storage, then Buckets, and create a bucket with the following settings:
Enter a name for your bucket (for example, my-company-cx-logs). Bucket names must be globally unique.
Under Location type, select Region.
Under Region, select us-central1 (Iowa). The bucket region must match your Coralogix domain.
Under Default storage class, keep the default: Standard.
Warning
Do not use Nearline, Coldline, or Archive storage classes. These incur retrieval fees every time Coralogix queries your archive.
Under Access control, leave Uniform selected and keep Enforce public access prevention enabled.
Click Create.
Step 2. Grant bucket permissions to Coralogix
Coralogix needs Storage Object Admin access to write and read archive data. This is a cross-project IAM grant if Coralogix runs in a different GCP project than your bucket — GCP supports this natively.
In the GCP Console, open your bucket and select the Permissions tab.
Click Grant Access.
In the New principals field, enter the Coralogix archive service account for the US3 environment: coralogix-archive-us3@coralogix-prod-saas-service.iam.gserviceaccount.com.
Under Assign roles, select Storage Object Admin (roles/storage.objectAdmin).
Click Save. The bucket is now ready to use.
Step 3. Connect the bucket in Coralogix
In Coralogix, select Data Flow, then click Setup Archive.
Choose from two bucket options: one for logs & traces (CX data) and one for metrics. You cannot use the same bucket for both.
Enter the name of your GCS bucket.
Click Save. This activates your archive storage. Find out more here.
How authentication works
Coralogix authenticates with GCS using GKE Workload Identity through the GCS S3-compatible API. The service account coralogix-archive-us3@coralogix-prod-saas-service.iam.gserviceaccount.com - no keys or credentials are exchanged. Granting this service account access in Step 2 is everything you need to do.
Storage costs
Use Standard storage class to avoid retrieval fees. If you use a different storage class, GCS charges a retrieval fee each time Coralogix reads archive data.
GCS Class A and Class B API operations are also billed to your GCP project. See GCS pricing for details.