Skip to main content

Release Apache APISIX 3.3.0

· 2 min read
Yilia Lin

The Apache APISIX 3.3.0 version is officially released. This version provides better performance in multi-domain matching scenarios.

APISIX 3.3.0 New Features

After a month, the new version came again. APISIX 3.3.0 is the first new version since the LTS version 3.2.0. In the new era of 3.x, we will continue to provide you with more new features.

The version 3.3.0 changes the default route matching mode from radixtree_uri to radixtree_host_uri, which provides better performance in multi-domain matching scenarios. As usual, many features are added to optimize the experience of using APISIX.

New Features

Support for storing routing certificates in secrets manager

APISIX 3.3.0 version supports loading certificates from Vault, which provides better security guarantees.

Step 1: Configure Vault Parameters

$ curl -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
"uri": "",
"prefix": "kv/apisix",
"token" : "root"

Step 2: Use $secret:// syntax on the SSL object to refer to the configuration of the vault-related path, and APISIX will obtain the relevant certificate from the corresponding vault resource path.

$ curl -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -i -d '
"cert": "$secret://vault/test1/ssl/",
"key": "$secret://vault/test1/ssl/",
"sni": ""

Finally, configure the above SSL object on the specific route, and the route certificate can be loaded from the vault.

Support for bypassing Admin API authentication via configuration

By default, APISIX will check X-API-KEY, now you can turn off the admin_key_required configuration item in the configuration file to turn off related checks.

Step 1: Modify the config.yaml configuration file

admin_key_required: false

Step 2: Access resources without using admin key

curl -v

In this way, the complexity of development and debugging can be simplified.

Optimization and more small features

In addition to the several major features mentioned above, this release also includes many changes worth mentioning:

  • Support request header injection in fault-injection plugin
  • Provide support for referencing variables captured by route rewrite in proxy-rewrite plugin in other plugins
  • The limit-count plugin provides username and ssl redis authentication methods

If you are interested in the complete update details of the new release, please refer to the CHANGELOG of the 3.3.0 release.