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.

Release Notes:  Property Manager

New Features:

• Pending Certificates.  When adding enhanced TLS hostnames you will now see pending certificates in the certificate selection step.  This means you no longer have to wait for enhanced TLS certificates to be fully deployed before adding Property Manager hostnames/edge-hostnames.  Note that you still need to wait for the certificate, edge hostname, and Property Manager configuration to all be active before you CNAME over any production traffic.
• Push to Sandbox.  For customers with Sandbox on their contract, you can now push a Property Manager configuration directly to your sandbox via the button in Property Manager.

Bug Fixes:

• Smaller Activation Emails.  In order to make the Property Manager activation notification emails smaller, the emails will no longer include all the warnings.
• Miscellaneous bug fixes and performance improvements.

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.

We’re approaching the completion of Test Center 2.0 which will add the functional testing capabilities to the application. You will hear more about the Test Center 2.0 beta release closer to the release date. This release introduces the new UI framework which will support the future features.

The latest update for Test Center includes:

• Updated homepage navigation.    

  • The Detect unexpected behavior menu is now called Comparative testing.    

  • The Dashboard menu is now called Home.  

  • Recent activity: 30 days is now called Last 30 days activity.  

  • The Runs & results tab in the left menu is moved below Comparative testing.  

• Updated configuration of test runs.   

  • The new interactive window provides the following options:  

    • Select objects to test.  

    • Select environment.  

    • Enter notes.  

    • Choose if you want to have the results emailed.  

• Updated the results page layout.  

  • The runs in the master list have a progress and status indicator.  

  • Notes are displayed while the tests are running.  

  • The readability of test run results is improved. The summary is hierarchical and there’s the new View details link that opens up a window with the results.  

• Updated notification email content.  

  • More in line with the UI results.  

• Improved application performance.  

• Implemented various stability improvements and fixed bugs.  

The latest update to mPulse includes the following enhancement:

• mPulse Lite customers can now see and use the Dimensions dashboard.

The latest update to mPulse includes the following bug fixes:

• Fixed a chart permissions error that states: “Current user/tenant does not have permission to read object”. Previously, this error occurred if the widget permission was set higher than the dashboard level permission.
• Waterfall dashboard can now correctly filter beacons for synthetic browser values.
• mPulse Alert emails now include an image when that option is selected in alert Attributes.