AWS SAM connectors now supports multiple destinations
Serverless application developers can now define multiple destinations when integrating AWS services with AWS Serverless Application Model (AWS SAM) connectors. Previously, SAM customers needed to create a SAM connector definition for every source and destination pair. For example, if a AWS::Serverless::Function needed to interact with three SNS topics using identical permissions, three SAM connectors would need to be defined for each connection from the function to each topic.
Serverless application developers can now define multiple destinations when integrating AWS services with AWS Serverless Application Model (AWS SAM) connectors. Previously, SAM customers needed to create a SAM connector definition for every source and destination pair. For example, if a AWS::Serverless::Function needed to interact with three SNS topics using identical permissions, three SAM connectors would need to be defined for each connection from the function to each topic.
Now, SAM customers can use a single SAM connector to define the permissions that should be granted between a single source resource and multiple destination resources. By defining multiple destinations in a single SAM connector, SAM templates are more readable and easier to update over time.
You can use multi-destination connectors today in your Serverless Application Model (SAM) template. This feature is available in all AWS Regions, including the AWS GovCloud (US) Regions.
To get started, please see documentation on using multiple destinations in your AWS SAM template.