aws-sdk-go
s5cmd
aws-sdk-go | s5cmd | |
---|---|---|
34 | 11 | |
8,548 | 2,339 | |
0.2% | 2.2% | |
9.4 | 7.3 | |
2 days ago | about 2 months ago | |
Go | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aws-sdk-go
- my first go project, a CLI application to store IP addresses
-
Go 1.21 will (probably) download newer toolchains on demand by default
I'm... really not sure I agree with this, from a philosophical point of view. It feels like this is making "eh, we'll just upgrade our Go version next quarter" too easy; ultimately some responsibility toward updating your application's Go version to work with what new dependencies require should fall on Us, the application developers. Sure, we're bad at it. Everyone's lived through running years-old versions of some toolchain. But I think this just makes the problem worse, not better.
Its compounded by the problem that, when you're setting up a new library, the `go` directive in the mod file defaults to your current toolchain; most likely a very current one. It would take a not-insignificant effort on the library author's part to change that to assert the true-minimum version of Go required, based on libraries and language features and such. That's an effort most devs won't take on.
I'd also guess that many developers, up-to this point if not indefinitely because education is hard, interpreted that `go` directive to mean more-of "the version of go this was built with"; not necessarily "the version of go minimally required". There are really major libraries (kubernetes/client-go [1]) which assert a minimum go version of 1.20; the latest version (see, for comparison, the aws-sdk, which specifies a more reasonable go1.11 [2]). I haven't, you know, fully audited these libraries, but 1.20 wasn't exactly a major release with huge language and library changes; do they really need 1.20? If devs haven't traditionally operated in this world where keeping this value super-current results in actually significant downstream costs in network bandwidth (go1.20 is 100mb!) and CI runtime, do we have confidence that the community will adapt? There's millions of Go packages out there.
Or, will a future version of Go patch a security update, not backport it more than one version or so, and libraries have to specify the newest `go` directive version, because manifest security scanning and policy and whatever? Like, yeah, I get the rosy worldview of "your minimum version encodes required language and library features", but its not obvious to me that this is how this field is, or even will be, used.
Just a LOT of tertiary costs to this change which I hope the team has thought through.
[1] https://github.com/kubernetes/client-go/blob/master/go.mod#L...
[2] https://github.com/aws/aws-sdk-go/blob/main/go.mod
- How to get better on golang
-
Send an Email through AWS SES with GoLang
This email was sent with " + "Amazon SES using the " + "AWS SDK for Go.
-
Looking for library recommendations: Django -> Golang port
I figured I'd ask the community for some recommendations for the following capabilities that Django + python stack is giving me at the moment: 1. Amazon SES Mailing (considering - aws-sdk-go) 2. Django Admin (considering go-admin 3. Django Signals (considering syncsignals 4. Celery (No contenders here)
-
S3 upload with progress
I've been trying to implement some logging of progress when uploading objects to S3. My code is building on this example and can be found here.
-
Background process in Lambda using SQS
Now that you have everything you need, let’s install the AWS SDK for Go library.
- Node.js 18 support in Lambda added to Go SDK
- Node.js 18 Runtime support added to Golang SDK
-
AWS and its complicated shit needs to die
Counterpoint 2: Amazon is bad and should feel bad for making this an internal and embedding it in the Credentials struct.
s5cmd
-
GitHub issues from top Open Source Golang Repositories that you should contribute to
s5cmd - Extended character support for s3 compatible backend
-
Migrate 5 TB S3 bucket from one AWS account to another
I've used a tool in the past called s5cmd to copy millions of objects, and it was strikingly fast: https://github.com/peak/s5cmd
-
Those using AWS, have you ever tried to use AWS Transfer Family to transfer files into an S3 bucket? Can I use python to make these uploads, and if so how do I set it up in aws?
Some folks say https://github.com/peak/s5cmd is faster than the two options above.
- Gcloud storage: up to 94% faster data transfers for Cloud Storage
- Faster way to empty S3 buckets?
-
A Dockerfile for Perl 5.36 / Alpine, with working SSL
RUN mkdir /tmp/output && cd /tmp/output RUN wget --no-check-certificate https://github.com/peak/s5cmd/releases/download/v1.2.1/s5cmd_1.2.1_Linux-64bit.tar.gz RUN tar xvzf s5cmd_1.2.1_Linux-64bit.tar.gz && mv s5cmd /usr/bin/s5cmd && rm -rf /tmp/output && rm s5cmd_1.2.1_Linux-64bit.tar.gz
-
DataSync Vs AWS S3 sync?
Not that I’ve seen but you might checkout https://github.com/peak/s5cmd
-
S3/100gbps question
I like to use https://github.com/peak/s5cmd
-
Downloading files from S3 with multithreading and Boto3
Excellent walkthrough, love boto. We’ve recently been using s5cmd which we’ve found is ridiculously faster than boto without any extra boto tricks.
https://github.com/peak/s5cmd
- How to download millions of files from S3? (AWS CLI stops working after 1st million)
What are some alternatives?
minio-go - MinIO Go client SDK for S3 compatible object storage
rclone - "rsync for cloud storage" - Google Drive, S3, Dropbox, Backblaze B2, One Drive, Swift, Hubic, Wasabi, Google Cloud Storage, Azure Blob, Azure Files, Yandex Files
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
s4cmd - Super S3 command line tool
botocore - The low-level, core functionality of boto3 and the AWS CLI.
s3-proxy - S3 Reverse Proxy with GET, PUT and DELETE methods and authentication (OpenID Connect and Basic Auth)
twitter-scraper - Scrape the Twitter frontend API without authentication with Golang.
s3-benchmark - Measure Amazon S3's performance from any location.
cachet - Go(lang) client library for Cachet (open source status page system).
kool - From local development to the cloud: web apps development with containers made easy.
goamz
aptly - aptly - Debian repository management tool