FEATURE RELEASE

Ambassador Edge Stack API Gateway 1.3 Available

Flexibility with the Edge Policy Console, built-in support for Authentication, and other new features and bug fixes

We’re releasing Ambassador Edge Stack 1.3 and Ambassador API Gateway 1.3 today. In this release, we focused on continuing to improve the Ambassador Edge Stack for ease-of-use and configurability. The Ambassador Edge Stack is a complete superset of the Ambassador API Gateway (open-source) with integrated support for rate limiting, authentication, filter management, and more. The Ambassador Edge Stack installs in minutes in any Kubernetes cluster.

Flexibility with Edge Policy Console

(Available for Ambassador Edge Stack 1.3)
The Edge Policy Console is a UI feature available in the Ambassador Edge Stack 1.0 that supports self-service giving developers the ability to easily configure, manage, and visualize edge policies.

In 1.3, we are giving Ambassador Edge Stack users the ability to disable the console if desired. The Edge Policy Console can be fully disabled with the diagnostics.enable element in the ambassador module.

Built-in Support for Authentication

(Available for Ambassador Edge Stack 1.3)
We’ve added the Password grant type to our included authentication, allowing users to authenticate by supplying their username and password in headers with requests. This is actually a lot like the Client Credentials grant, but Password uses an existing username and password rather than a special client ID and secret, so it can be easier to use, especially when migrating. And under the hood, it uses the Resource Owner Password Credentials OAuth2 flow.

The Ambassador Edge Stack will use the provided username and password to authenticate with your Identity Provider (IdP) using the Resource Owner Password Credential flow. Keep in mind that not all IdPs support grant_type=password.

Additional Bug Fixes and Enhancements
The following additional fixes and enhancements apply to the Ambassador Edge Stack 1.3:

• Feature: edgectl install provides better feedback for clusters that are unreachable from the public Internet
• Feature: edgectl install supports KIND clusters (thanks, @factorypreset!)
• Feature: edgectl intercept supports HTTPS
• Feature: Ambassador Edge Stack Docker image is ~150MB smaller
• Feature: aes-plugin-runner now allows passing in docker run flags after the main argument list.
• Bugfix: Ambassador Edge Stack doesn’t crash if the Developer Portal content URL is not accessible
• Bugfix: edgectl connect does a better job handling clusters with many services
• Bugfix: The Plugin Filter now correctly sets request.TLS to nil/non-nil based on if the original request was encrypted or not.
• Change: There is no longer a separate traffic-proxy image; that functionality is now part of the main AES image. Set command: ["traffic-manager"] to use it.

Installing and Upgrading to 1.3

Installing and Upgrading to 1.3

To install the Ambassador Edge Stack, follow the quick start.

To upgrade from your current version of the Ambassador Edge Stack to 1.3, please follow the instructions here.

Get Started Today

The Ambassador Edge Stack is a complete superset of the Ambassador API Gateway (open-source), with integrated support for rate limiting, authentication, filter management, Swagger, and more. The Edge Stack installs in minutes in any Kubernetes cluster. Get started here

And, if Ambassador is working well for you, we’d love to hear about it. Drop us a line in the comments below, or @ambassadorlabs on Twitter.