This tutorial demonstrates how to configure an S3 bucket to send your telemetry data to Coralogix.
Use your archive buckets to store all of your data as long as you need, on your own S3 bucket, for infinite retention. Your logs & traces archive bucket can be stored in CX data format. Metrics archive bucket stores Prometheus index blocks.
STEP 3. [Optional] Add KMS keys to the buckets with logs_kms_arn and metrics_kms_arn variables.
STEP 4. Create the archive buckets by saving the file and running the following commands:
STEP 1. Create an S3 bucket for configuration with default parameters.
STEP 2. Search S3 in your AWS search bar and select this service.
STEP 3. Locate and select the bucket of choice for storing the archive.
STEP 4. Navigate to the Permissions tab. Edit the Bucket policy.
STEP 5. Paste the following code and update the name of your bucket. The following provides both a logs and metrics archive bucket configuration snippet. Note that the configuration snippet for metrics contains an additional delete permission.
The configuration snippet for metrics contains an additional delete permission.
For all configured snippets, you are required to input the ACCOUNT_ID associated with your Coralogix domain and region.
STEP 7. Copy and save the name of the archive for your Coralogix platform setup.
KMS Encrypted Bucket (Optional)
If your bucket needs to be encrypted and you are using KMS, you will need to grant Coralogix permission to use the specific key to encrypt and decrypt the data when we store it on your bucket. Only those keys that are ‘Customer Managed’ may have their policy modified.
STEP 1. Access KMS and choose the key used for encryption. Note: The key must be in the same region as your archive bucket.
STEP 2. Edit the Key Policy and add the highlighted section below to your KMS key policy or copy the code in full to also give your root user full access.