- Add
logs_bucket_force_destroyandmetrics_bucket_force_destroyvariables to allow force destroy the bucekts.
- Added an option to include metrics from source accounts linked to the monitoring account in the Firehose CloudWatch metric stream.
- Introduced the
include_linked_accounts_metricsvariable to control the inclusion of linked account metrics for Firehose. - Updated example configurations to demonstrate usage of the
include_linked_accounts_metricsvariable in Firehose metric streams.
- Fixed ecs-ec2 module, adjusted cdot image command to
--config env:OTEL_CONFIG - Removed latest flag from ecs-ec2 module example.
- Removed deprecated logging exporter from ecs-ec2 module otel configs.
- Added pprof extension to default ecs-ec2 otel configurations.
- Remove deprecated modules: cloudwatch-logs, S3 and kinesis
- Add AP3 region to the list of regions
- Added custom naming for global resources
- Added ability to import global resources (s3 & iam)
- For firehose-logs & firehose-metrics, Update variables:
coralogix_regionvalues regions from [Europe, Europe2, India, Singapore, US, US2] to [EU1, EU2, AP1, AP2, AP3, US1, US2] - Update variables:
private_keyrenamed toapi_keywith typestringinstead ofany.
- Update coralogix role from
arn:aws:iam::<account-id>:role/msk-access-<region>toarn:aws:iam::<account-id>:role/coralogix-archive-<region> - allow the module to run in AP3 region
- Allow the module to be deployed in AP3
- Allow the module to be deployed in ap-southeast-3 region
- Add AP3 region to the list of regions
- Added custom naming for global resources
- Added ability to import global resources (s3 & iam)
- Update variables:
private_keyrenamed toapi_keywith typestringinstead ofany.
- Add new module
msk-data-stream, the module will create msk with public access, and a role to allow coralogix to stream data to his topics.
- Update lambda runtime from nodejs18 to nodejs20
- Update variables:
collect_aliasesandcreate_secretto be typeboolinstead ofstring.
- Add new parameter runtime, to allow users to specify lambda run time, possible options:
provided.al2023orprovided.al2
- Allow to specify multiple api_key when using the parameter integration_info
- Remove the creation of an SNS topic for lambda failure in case the user didn't set up notification_email
- Add new variable create_endpoint to allow users to choose if they want to create an endpoint in case they are using a private link and store their ApiKey in secret.
when using integration_info varialbe will now need to specify the api_key as parameter in the mapping of integration_info instead of in the modules body itself example
- Add delete permissions to the archive buckets
- replace ap1 region with ap2 in the aws_role_region mapping
- Added validation using operator route to default otel config for ecs-ec2 config
- Add support for DLQ
- Add log_group_prefix variable to avoid limitation of number of log groups
- Update versions for github actions to avoid node.js 16 issue
- [cds-1198] set default type parameter to CloudWatch_Metrics_OpenTelemetry070_WithAggregations
- add README description for aggregation
- Update the lambda runtime to Amazon 2023, the lambda module version to 7.2 and the terraform version to 5.32
- Add new variables custom_csv_header and custom_metadata
- Update permissions for lambda when using private link
- Update permissions for EcrScan integration
- [cds-1099] set default force_flush_period parameter to 0 for ecs-ec2 otel filelog receiverπ‘
- [cds-1099] add recombine operator to default configuration for opentelemetry ecs-ec2 integration
- allow MSK integration to get multiple topic names as a trigger
- Create lambda-manager module
- [cds-1050] add support for x86 to template
- ECS-EC2 module, set log level to warn by default for otel configurations
- fixes ecs-ec2 bugs from v1.0.87
- ECS CDOT restrict hostfs mount scope security fix; OTEL config batch fix; README improvement.
- ECS CDOT update region codes Terraform interface.
- Add support for Ecr
- Add support for MSK and Kafka
- Fix a bug that won't allow you to use more than one s3 integration on 1 terraform configuration file
- Split main.tf file, every integration resource will be in its file.
- Add support for CloudFront Access logs
- Support for adding metadata to logs (bucket_name, key_name, stream_name)
- Update the role for the metrics bucket
- Missing resource instance key
- Add option to use Kinesis stream
- Update the role to the s3 bucket
- Add option to use Sqs with out without s3 bucket
- Allow log group with a dot in the name to be a trigger for lambda
- Add variable lambda_name to allow users to specify the name of the lambda that gets created by the module
- Use unique resource names - this will allow the deployment of the service multiple times on the same cluster (for configuration tests for example) and to maintain separate definitions within the same account/region
- [optionally] Allow tagging
- [optionally] Reuse task definition for multiple service deployments
- Reduce Secret Manage IAM permissions
- Fix bug related to attach_async_event_policy in the lamabda module
- Fix examples with correct module name and source
- Fix examples with correct module name and source
- Update the Coralogix Region list to be the same as the list in the website
- Change default loglevel to WARN
- Option to specify a retention time of the CloudWatch log group that is created by the lambdas
- Add submodule for the coralogix-aws-shipper
- Add lambda function filtering in resource-metadata
- Remove CloudWatch_Metrics_JSON from metrics integrationTypes
- Refactoring the module to use 'for_each' instead of 'count' to avoid unnecessary changes in terraform plans and applies, when there was any change to the log_groups variable
- Option to specify a retention time of the CloudWatch log group that is created by the lambdas
- firehose submodule will be deprecated in favor of two separate submodules firehose-metrics and firehose-logs
- remove dynamic_metadata_logs, applicationNameDefault and subsystemNameDefault in following the changes made on firehose logs documentation
- Add submodule for the ecs-ec2
- Migrate Lambda transformation runtime
- changed applicationNameDefault and subsystemNameDefault in following the changes made on firehose logs documentation.
- added lambda_processor_enable variable to enable/disable lambda transformation processor
- add secret_manager_enabled variable to integrations
- Added subsystem value to common attributes of firehose metrics
- Added override_default_tags to allow users to override the default tags we set
Change the SSM option name to be SM (Secret Manager).
- Remove the IAM role named Default - there is no need for this role and it can cause a conflict.
- change coralogix_region to aws_region
- add validation for aws_region variable
- Add support to US2 region
- Add option to use custom coralogix arn
- Add an option for a user to use an existing secret instead of creating a new one with ssm
- Remove the ssm_enabled variable.
- fix duplicate IAM issue
- standardizing variable naming and description
- add buffer and cache configurations to fix firehose lag
- Add submodule for the lambda-secretLayer
- Add support for govcloud, by adding custom_s3_bucket variable.
- Add support to use a private link with coralogix by adding subnet_id and security_group_id variable
- Update examples removing ssm_enable and layer_arn
- Add new region US2 to the integrations
- Change submodule location to be under Provisioning section
- Add submodule for the s3-archive
- raise semantic-release-action and semantic_version
- update default for integration_type_metrics to be CloudWatch_Metrics_OpenTelemetry070