Amazon EventBridge and AWS Step Functions announce integration with private APIs

Amazon EventBridge and AWS Step Functions now support integration with private APIs powered by AWS PrivateLink and Amazon VPC Lattice, making it easier for customers to accelerate innovation and simplify modernization of distributed applications across public and private networks, both on-premises and in the cloud. This allows customers to bring the capabilities of AWS cloud to new and existing workloads, achieving higher performance, agility, and lower costs.

Enterprises across industries are modernizing their applications to drive growth, reduce costs, and foster innovation. However, integrating applications across siloed VPCs and on-premises environments can be challenging, often requiring custom code and complex configurations. With fully-managed connectivity to private HTTPS-based APIs, customers can now securely integrate their legacy systems with cloud-native applications using event-driven architectures and workflow orchestration, allowing them to accelerate their innovation on AWS while driving higher security and regulatory compliance. These advancements allow customers to achieve faster time to market by eliminating the need to write and maintain custom networking or integration code, enabling developers to build extensible systems and add new capabilities easily.

Integration with private APIs in Amazon EventBridge and AWS Step Functions are now generally available in Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), South America (Sao Paulo), US East (N. Virginia), US East (Ohio), US West (N. California), and US West (Oregon). You can start using private APIs with Amazon EventBridge and AWS Step Functions from the AWS Management Console or using the AWS CLI and SDK. To learn more, please read the launch blog, Amazon EventBridge user guide and AWS Step Functions documentation.
 

Source:: Amazon AWS