Replies: 2 comments
-
I agree with Holi0317. We have a large stack, and our combined size of all lambdas is about 500 Mb. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hey @Holi0317 - it's not possible to do it on an externally owned bucket because that flag also controls how the bucket is going to be created - if it's provisioned by serverless, proper settings for S3 acceleration are also set on the bucket. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am planning to manage the deployment bucket in terraform externally so we only have 1 deployment bucket instead of a dozen created by serverless on-the-fly. During the migration, I got the following error:
Digging into serverless code brings me to generate-core-template.js, which brings me to deprecation warning of S3_TRANSFER_ACCELERATION_ON_EXISTING_BUCKET on sls v3.
The change is committed on 04b921a. Is there any reason behind this change? There is no reasoning written for this change in the changelog or migration guide right now.
We want to enable transfer acceleration because our ci runs on us-east-1 while our deployment region is in eu and ap. Our lambda zip is around 50MB so enabling transfer acceleration should help with the deployment time.
Beta Was this translation helpful? Give feedback.
All reactions