Amplience incident

Unable to publish in DAM and Dynamic Content

Critical Resolved View vendor source →

Amplience experienced a critical incident on September 5, 2023 affecting Content Hub and Dynamic Content, lasting 21m. The incident has been resolved; the full update timeline is below.

Started
Sep 05, 2023, 03:52 PM UTC
Resolved
Sep 05, 2023, 04:14 PM UTC
Duration
21m
Detected by Pingoru
Sep 05, 2023, 03:52 PM UTC

Affected components

Content HubDynamic Content

Update timeline

  1. identified Sep 05, 2023, 03:52 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Sep 05, 2023, 04:14 PM UTC

    This incident has been resolved.

  3. postmortem Sep 07, 2023, 09:57 AM UTC

    # **Summary** On Tuesday, September 5th, we experienced a failed deployment of an SSL certificate which impacted our platform. This caused our customers to experience difficulties generating an authentication token alongside being unable to publish or preview content # **Root Cause** We carried out a standard change \(pre-authorized and low-risk\) of renewing our certificate. However, the intermediate certificate was missing during the process, which meant our internal services couldn’t connect to [auth.amplience.net](http://auth.amplience.net/) to get a token. The certificate was redeployed on our infrastructure to restore the service # **Corrective and Preventive Measures** Internally, we are exploring ways to automate and upgrade our services so we can avoid this issue going forward ‌ If you would like to discuss this further, please contact your customer success manager \([[email protected]](mailto:[email protected])\)