The following changes are included in this release.

Featuresedit

Update other deployments when updating certificates in DirectTrustRelationships. Introduces simplified certificate rotation and revocation for remote cluster connections to clusters running outside of the current Elasticsearch Service environment. If you have multiple clusters in Elasticsearch Service that trust the same external environment, as defined with a DirectTrustRelationship, updating the certificate for one deployment in this environment will automatically be applied to all other deployments trusting this environment.

Enhancementsedit

Remove storageMultiplier from the list of immutable fields. Allow changes to the storage_multiplier field on existing instance configurations.

Add information to Edit page when tier addition failed but instances still exist. In the case of a failed autoscale attempt to add a new data tier, but with some instances added, the UI now informs you of this situation.

Add usage and creation timestamps to usage records. This PR adds usage_timestamp and creation_timestamp fields to usage records generated by metering CTS tasks. It also deprecates the @timestamp field.

Populate deployment level autoscaling in deployment templates on upgrade. Copies the autoscaling_enabled field from the Elasticsearch plan into the deployment settings for all defined deployment templates.

Add the upgrade button to the UI for each deployment. You can now see a notice and button to upgrade your deployment(s) when a new version is available.

Adding trusted relationship dropdown menu. Added a dropdown of existing trust relationships so that users can select one as a model when creating new Trust Relationships.

Ingest allocator garbage collection logs. This change will ingest allocator garbage collection logs into Elasticsearch logging clusters using Filebeat for longer retention and better search capabilities.

Validate certificate UID consistency. Validates that within the same organization a fingerprint is used with only one trust relationship UID, and enforces that a trust relationship must always have all known valid certificates for the environment.

Bug fixesedit

Compare deployment plans against the previously successful plan, not just the previous plan. Deployment plan activity now correctly compares plans to the previous successful plan rather than just the previous plan.

Set the idle timeout on Elasticsearch connections. Prevents connection leaks from the Container Task Service (CTS).

Breaking changesedit

Append the first six digits of deployment ID to cluster.metadata.display_name. The default Elasticsearch cluster.metadata.display_name has been updated to contain <deployment_name> (<first_6_chars_of_deployment_ID>), instead of simply containing the deployment name.