DevOps Articles

Keeping up with your dependencies: building a feedback loop for shared libr

This enables teams to work independently of each other, helps to reduce wait times and decreases coupling between services.

Although it’s vital to offer an opt-out of those libraries (namely, use your own code to address the cross-cutting-concern, such as when there is no version for a given language), shared libraries also provide the benefit of better governance and time savings.

This is why I sometimes use low-level AWS CloudFormation constructs or even use the provided escape hatches to use AWS CloudFormation constructs directly.

To do this I create roles for cross account access from the producer account in the consumer account as described here.

You might want to replace the AWS Fargate portion with a Lambda-only solution and use AWS Step Functions for better error handling.