Action Required: AUI CDN is deprecated and will be shut down 30 Oct 2026

Announcements
, , ,
1

Hi Atlassian Developer Community,

We’re writing to let you know that the AUI CDN (aui-cdn.atlassian.com) is now deprecated and will be shut down after 30 October 2026 (approximately 6 months from this notice).

After this date, any requests to aui-cdn.atlassian.com will fail, which will break apps that haven’t migrated. Please migrate as soon as possible.

What is AUI CDN?

aui-cdn.atlassian.com hosts legacy JavaScript and CSS assets for AUI (Atlassian User Interface) versions 5.2.0 – 6.0.9.

Who is affected?

The AUI CDN is primarily used by Connect apps, so this mostly affects apps not yet migrated from Connect to Forge. Connect has announced its own End of Support late 2026. In some rare cases, AUI CDN is also used by Forge apps.

How to check if you’re affected

Search your app’s source code for any URLs containing aui-cdn.atlassian.com. If you find any references, your app is loading assets from AUI CDN and you need to take action before the shutdown.

Next steps

If you’re affected, see the developer changelog entry for steps to migrate.

If you have questions, please reply to this thread.

Best regards,
The Atlassian Design System Team

2

Hi @LukeUnderwood ,

The AUI CDN is referenced in the Atlassian Connect Express template, which is presumably still used by the majority of Connect apps:

atlassian-connect-express-template$ grep -r aui-cdn .
./views/layout.hbs:  <link rel="stylesheet" href="//aui-cdn.atlassian.com/aui-adg/5.8.12/css/aui.css" media="all">
./views/layout.hbs:  <link rel="stylesheet" href="//aui-cdn.atlassian.com/aui-adg/5.8.12/css/aui-experimental.css" media="all">
./views/layout.hbs:  <!--[if IE 9]><link rel="stylesheet" href="//aui-cdn.atlassian.com/aui-adg/5.8.12/css/aui-ie9.css" media="all"><![endif]-->
./views/layout.hbs:  <script src="//aui-cdn.atlassian.com/aui-adg/5.8.12/js/aui-soy.js" type="text/javascript"></script>
./views/layout.hbs:  <script src="//aui-cdn.atlassian.com/aui-adg/5.8.12/js/aui.js" type="text/javascript"></script>
./views/layout.hbs:  <script src="//aui-cdn.atlassian.com/aui-adg/5.8.12/js/aui-datepicker.js"></script>
./views/layout.hbs:  <script src="//aui-cdn.atlassian.com/aui-adg/5.8.12/js/aui-experimental.js"></script>
./views/unauthorized.hbs:  <link rel="stylesheet" href="//aui-cdn.atlassian.com/aui-adg/5.8.12/css/aui.css" media="all">
./views/unauthorized.hbs:  <link rel="stylesheet" href="//aui-cdn.atlassian.com/aui-adg/5.8.12/css/aui-experimental.css" media="all">
./views/unauthorized.hbs:  <!--[if IE 9]><link rel="stylesheet" href="//aui-cdn.atlassian.com/aui-adg/5.8.12/css/aui-ie9.css" media="all"><![endif]-->

With Connect EOS on December 31 2026, why is this CDN being removed from service two months earlier, on October 30 2026? During this very busy period with Forge migrations, could Atlassian please at least synchronize these dates to give vendors one less thing to worry about?

2 Likes
3

For Connect apps that have migrated to Forge, there is still a long tail of installs that haven’t upgraded (see the many other recent discussion threads here in CDAC on this, I won’t bother linking them all here).

Until the issue is resolved via rolling releases or whatever other mechanism, this represents a ticking time bomb where these installs will break and there is no migration path (the developer has already migrated to Forge).

On the one hand you could say that this is a way of forcing those installs to upgrade, but if it’s because the app suddenly stops working one day for these customers then I’m sure you’ll agree is a very poor experience for those customers, and will create a huge wave of support issues for the vendor.

I get that you want to deprecate AUI, and I get that all of Connect is going EoS; but without solving the issue of bulk upgrading installs (that require admin permission consent) to the newer Forge version, this seems problematic for both customers and vendors.

2 Likes