Type of Issue:
Issue Creator Checklist
Background
Currently, Serverless uses the default configuration for bucket creation, resulting in a single bucket per service. With the existing services, that results in 8 serverless deployment buckets being created per branch. A high number of development branches has caused us to exceed the default S3 bucket limit in AWS.
Proposed Approach
Implement Serverless Deployment Bucket by default, pointing each service to a single deployment bucket
Value
Reduction in AWS S3 overhead, and we would be enabled to have more open branches without requiring a S3 limit increase
AC:
New branches created with macpro-quickstart-serverless will have 1 deployment bucket per branch, rather than bucket for each branch + service.
Type of Issue:
Issue Creator Checklist
Background
Currently, Serverless uses the default configuration for bucket creation, resulting in a single bucket per service. With the existing services, that results in 8 serverless deployment buckets being created per branch. A high number of development branches has caused us to exceed the default S3 bucket limit in AWS.
Proposed Approach
Implement Serverless Deployment Bucket by default, pointing each service to a single deployment bucket
Value
Reduction in AWS S3 overhead, and we would be enabled to have more open branches without requiring a S3 limit increase
AC:
New branches created with macpro-quickstart-serverless will have 1 deployment bucket per branch, rather than bucket for each branch + service.