OpenID Connect (OIDC) is a simple identity layer on top of the OAuth 2.0 protocol. It allows clients to verify the identity of a user or an application based on the authentication performed by an Authorization Server. This will enable you to securely interact with 3rd party applications like your cloud provider. Now with env0, each deployment can have an integration with OIDC and provides an OIDC short-lived token (JWT) for you to authenticate to any other 3rd party application.

Splunk, Datadog, and Logz.io are not enough? Add Coralogix to that list!
Centralized log systems have been around for a long time, and in today's world, they are more than just log aggregators. Metrics, traces, analytics, and other valuable tools are all rolled up into logging systems.
Today we've added integration between env0 and Coralogix — to forward all of your infrastructure deployments from env0, giving you the ability to monitor, track and analyze logs with the power of a great tool like Coralogix.

We're happy to announce that from today, CloudFormation joins Terraform, Terragrunt, Pulumi, and Kubernetes as a core IaC tool supported in env0! AWS CloudFormation lets you model, provision, and manage AWS and third-party resources by treating infrastructure as code. With CloudFormation, you declare all your resources and dependencies in a template file. The template defines a collection of resources as a single unit called a stack. CloudFormation creates and deletes all member resources of the stack together and manages all dependencies between the resources for you.

Self-hosted agents allow you to run your env0 deployment workloads on your own infrastructure. This gives you the ability to isolate your infrastructure as code deployments in a more secure way, within your private network. This also allows you to manage your secrets in your preferred secret manager. Today you can also store those secrets natively inside Hashicorp Vault, and give your agent the ability to resolve those secrets for each deployment automatically.

env0 supports a wide variety of IaC platforms, including Terragrunt, but up until now it lacked the support for running multiple modules at the same deployment, a feature that is supported by Terragrunt's run-all command. Another advantage is the ability to define dependencies between Terraform modules in code. Today we are proud to deliver this support out of the box with env0!

Managing software versions of your Infrastructure as code framework is one of the basic aspects when managing your deployment and code. Now you can specify the exact Pulumi CLI version you want your IaC to run with and avoid version incompatibility issues and have full control over what versions update and backward compatibilities issues.

One of the advantages of env0 is the ability to monitor the actual cost of your environments based on your Infrastructure as code resources. This feature is available due to our beloved open source project, Terratag. As of today, it officially supports Terragrunt code, giving our env0 platform the ability to show you cost over time for your Terragrunt based environments and correlate them with your deployment. Together with these cost estimation capabilities, you can have full control of your cloud spending.

env0 lets you create a managed self-service inside your organization, empower your developers and R&D teams to spin up, update and destroy an environment with one click, and easily track environment status or deployment history. To manage those environments and make sure no resources wasted, env0 lets you create TTL policies. The Organization administrator can limit the environment's time-to-live, but often, the same settings don't fit the needs of different projects in the organization. Now we allow overriding organization TTL policy on a project basis.

A production app’s infrastructure consists of many different resources. As those resources grow, managing and deploying them requires more thought and effort. We tend to look at managing resources as we do with code - split them into smaller manageable pieces (env0 Environments) where each piece is cohesive and loosely coupled. In theory, this textbook solution sounds great because each environment is independent and can be deployed at any time, but in the real world, we have dependencies - deploying all those env0 Environments simultaneously is impractical.

There are many ways to interact with the env0 platform that requires an API key for authentication and authorization. Our public API, env0 Terraform provider, and the env0 CLI. Now, with our new non-admin API key, you can provide members of your team with the ability to use API keys, while maintaining your organization's RBAC. A user API key can be created with specific project permissions, assigned to a team, and basically treated like any other user in the system.