aws-samples / aws-samples/aws-serverless-saas-workshop
ServerlessSaaSLayers Copies
- Dominant language
- Python
- Stars
- 163
- Forks
- 82
- Avg merge
- 10d 5h
- Merged PRs (30d)
- 1
Description
I see copies of ServerlessSaaSLayers created - once for shared services, once for pooled tenants, once for each siloed tenant.
I like how the LambdaInsightsExtension layer is 'global'.
What changes need to happen to make ServerlessSaaSLayers also 'global' and thus a single copy?
Contributor guide
Research direction
Locate the definitions and deployment references for ServerlessSaaSLayers and LambdaInsightsExtension, then compare how their scope is configured. Determine the changes needed for ServerlessSaaSLayers to be provisioned globally as one copy, and verify that shared services, pooled tenants, and siloed tenants all reference that single layer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100