aws-amplify / aws-amplify/amplify-cli

Use s3 transfer acceleration as part of amplify push

Open
#8,386 0 comments 0 reactions 0 assignees View on GitHub
feature-request p4 platform-pull platform-push
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### Is this related to a new or existing Amplify category?

function

### Is this related to another service?

S3

### Describe the feature you'd like to request

amplify push is known to take a long time, and this gets even longer as lambda package sizes get bigger.

If the developer's computer is not near the s3 bucket that amplify uploads and downloads from (and with remote teams that is certainly a possibility), then using s3 transfer acceleration could reduce transfer time. I tested that even with a 5mb file with a desktop connection there is an improvement in speed. You can use also http://s3-accelerate-speedtest.s3-accelerate.amazonaws.com/en/accelerate-speed-comparsion.html to test.

So amplify should perhaps enable s3 transfer acceleration by default on the buckets it uses. And for people concerned about cost, they can turn the feature off - they don't pay anyways in cases where s3 transfer acceleration determines there is no acceleration possible (e.g. ci build in same data center as s3 build).

In general however developer time is more costly than s3 transfer acceleration costs.

### Describe the solution you'd like

Use s3 transfer acceleration when uploading to s3 as part of amplify push.

### Describe alternatives you've considered

No alternative, we are stuck with what amplify supports.

### Additional context

_No response_

### Is this something that you'd be interested in working on?

- [ ] 👋 I may be able to implement this feature request
- [ ] ⚠️ This feature might incur a breaking change

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.