Amplify Fusion updates deliver high-performance protocol support and critical security enhancements for hybrid integration flows.
Fusion now officially supports the gRPC protocol. The new gRPC Client connector supports server streaming APIs, while a new feature allows for calling gRPC back-end services over RESTful APIs by ingesting proto descriptor files.
The SFTP client now supports larger file uploads. Additionally, the connector now offers Public Key Authentication and supports "Stream" as a configurable input file type for MGet and MPut operations to optimize resource usage.
Added support for OAuth 2.x Client Credentials combined with mTLS, providing a highly secure mechanism for service-to-service authentication.
The Crypto component has been upgraded to support asymmetric signing using RSA and Elliptic Curve (EC) algorithms for JSON Web Tokens (JWT). Verification now also supports EC-based signatures.
Fusion now supports the generation of JSON Web Encryption (JWE) tokens using symmetric keys, compliant with RFC 7516.
Users can now perform message signing and verification using Fusion-managed keys as an alternative to external HSM connections.
The HTTP Client now reuses persistent connections even when "Override Connection" is selected, provided core security settings remain unchanged. Similarly, the system now evaluates overridden properties to reuse cached tokens whenever applicable, reducing redundant authentication calls.
Fusion now supports configurable rate limits directly on each data plane, allowing customers to protect back-end services with throttling at the month, week, day, hour, minute, and second levels.
Enhanced WIF support includes a redesigned UI that groups identity provider, Google STS, and Google IAM fields for more intuitive configuration and validation.
Logs in both Studio and the Fusion data plane are now presented in JSON format by default, simplifying integration with modern log management stacks.
The Monitor dashboard now provides separate tabs for API Transactions versus general transactions, improving visibility into specific traffic patterns.
Full support for OpenTelemetry (OTel) using Fluent Bit as an exporter, enabling unified observability across the enterprise integration landscape.