New features:

• Liveness tests with many headers. You can define multiple HTTP headers for any HTTP(S) liveness test configuration using the API and user interface.

• Disable liveness tests. You can use the API or a checkbox in the user interface to disable a liveness test, which directs the GTM service to cease running the test and effectively treat the test as no longer existing.

• Static property types. You can use the API to configure static answers, such as an A record value for GTM properties, to deliver static record responses.

• Apex properties. You can configure properties at the apex record of a domain, which eliminates the need to create a subdomain of a GTM domain with only one property. The API and user interface display the apex record with an @ symbol.

• Terraform Provider. You can use Terraform Provider to minimize the activity required to manage and configure GTM domains and properties.

New features:

• Force zone deletes. You have the option to force zone deletions in cases when safety checks previously prevented it. The user interface alerts you to the risks of the deletion and requires your confirmation before the zone is deleted.

• Zone transfer status from Zone list. Zone list includes icons that display the status of many zone transfers in a single view. Green indicates a successful zone transfer, yellow indicates that one or more zone transfers have issues, and red indicates a zone transfer failure. You can click the icons to view additional status details for each zone.

• Terraform Provider. You can use Terraform Provider to minimize the activity required to manage and configure Fast DNS zones and record sets, especially in organizations that use multiple authoritative DNS providers.

Enhancements in Identity and Access Management Application

• OPEN API clients for which the owner is no longer a user on Akamai Control Center will now be shown on the Identity and Access Management application. The owner of the API client will appear as [X] in the “User ID/Client Owner” column on the application list page. To find the original owner of the API client you can click on the API client and see the details page. You can transfer ownership of this API client to a new owner in the system.

New Features:

• Origin Failover for AMD: This lets you configure an Origin Failure Recovery Policy for AMD to recognize certain errors and connection timeout situations as failure scenarios. You also configure associated Origin Failure Recovery Methods to address the different failure scenarios. A recovery method can either redirect a failed request to a backup origin or return a custom HTTP status code to the end-user. Origin Failover use is covered in the AMD - Implementation Guide.
• Mixed Mode Configuration for AMD: This lets you apply the various use case-based behaviors (Client Characteristics, Content Characteristics, Origin Characteristics, and Segmented Media Delivery Mode) outside the default rule in an AMD property configuration. This way, you can define different match criteria for different instances of these behaviors, in order to optimize delivery for unique use cases. Instructions on its use are covered in Mixed Mode Configuration for AMD.

Enhancements:

• Support for Origin-assist Prefetching for Azure URLs: We have incorporated metadata changes to support Azure URLs for HLS and DASH format media. Currently, CMAF format manifests and manifests that have KEY frames are not supported. (A DOS does not occur for these formats, they are just not supported. Content is still fetched, just not in prefetch mode.)

The latest update for API Gateway includes the following features and enhancements:

New features:

• JSON web token validation now support the use of an ‘iat’ claim.
• JWKS support allows for more seamless key rotations.
• Cache prefreshing is available for both RESTful and GraphQL-based APIs.

Enhancements:

• The API Endpoint Definition API returns only documented parameters.
• The ‘Reset to API settings’ button does not reset all of the settings in API privacy.
• The JWT public key validation includes a restriction to accept only the PKCS#8 format.

New Features: 

• Akamai Cloud Embed (ACE) map expansion. This lets us use the Akamai edge map without restrictions and we expect it will improve performance for subcustomers. ACE policy activations now take longer to complete (eight minutes versus one minute), but this update provides marked benefits for safety and performance (improvement in throughput, latency, and time to first byte (TTFB)).
• Live delivery optimizations. This feature provides optimizations for live streaming to ACE partners and their customers. This is available as a new option, “streaming-video-live” in the existing “content-characteristics” behavior. See the ACE - Implementation Guide for full usage instructions.
• Prefetching of streaming content. Prefetching positions target media content at the Edge in anticipation of requests by end users. This reduces the time to deliver that content. The origin housing content needs to be configured to support the origin-assist model, and prefetching is supported for use with DASH, HLS, and Smooth streaming formats. Complete usage is also explained in the ACE - Implementation Guide.
• Origin failover. This feature identifies primary origin connection failures based on a type you specify and marks that origin as “bad” after connections to all its IPs fail repeatedly. Rather than issuing a redirect to the end user, requests are failed over to a backup origin you call out. You can add this support for subcustomers via a new behavior in the ACE API.

Enhancements

• HTTPS orchestration. We’ve made improvements to certification selection logic.

The latest update for the support home release includes:

• New training videos available in the training video section of the support home page. Older videos have been removed.
• Standard bug fixes.

Enhancements in Identity and Access Management Application

• If the account administrator updates the account’s password policy to a more restrictive one, existing users whose passwords could expire immediately (according to this new policy) will be given an extension of 21 days to be able to rotate their Akamai Control Center passwords.
• After a user is deleted from IDM all escalation contacts data for that user, along with Email advisories, is also deleted.
• The CSV file that can be downloaded from the Identity & Access Management screen will now include information on whether the users are locked.

The latest update to mPulse includes the following bug fixes:

• Fixed an issue related to filters set in the dashboard property panel. Previously, the “do not display” filter setting did not persist on subsequent sessions.
• Fixed the animation of the Globe legend and resolved some issues that occasionally caused the Globe to crash on initial load.

The latest update to mPulse includes a change in frequency for uploading raw beacon data to Amazon S3, from 3 minutes to 5 minutes. This is a temporary measure we’re taking during holiday season in order to ensure real-time data in mPulse’s Waterfall tool.