SIsitole·Feb 13, 2026Submission
AWS Adds support for nested virtualization
304 points · Open discussionaws
aws-sdk-go-v2
Go2022–2026
aws / aws-sdk-go-v2
aws-sdk-go-v2
AWS SDK for the Go programming language.
10Distinct people
11Mentions
0Explicit recommenders
3.7KGitHub stars
What to know before exploring
What it is
AWS SDK for the Go programming language.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year11 dated mentions
Observed mentions: 2022-01-22 20:25:47 UTC to 2026-02-13 00:07:57 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
11 sourcesYou may already know these things, but for others who may not: the AWS SDK for Go suffers from shockingly bad discoverability.
For example, take the S3 library, github.com/aws/aws-sdk-go-v2/service/s3. If you have an s3.Client and you look at e.g. the ListObjectsV2 method, you might have no idea that there is a ListObjectsV2Paginator which makes it much easier to use, because nowhere in the method docs is it mentioned. Indeed, most operations that paginate have more ergonomic paginators, but none of them tell you this.
But that isn't even the worst of it. Say you want to download or upload a file to S3. If you haven't worked with AWS for other languages, you might think that you just do GetObject and PutObject. And yes, for small files, that's generally fine. But for large files you want to use resumable downloads and multipart uploads. S
Read the rest
o you look and lo, there is no simple way to do this in the AWS SDK for Go. But actually, there is! It's in a totally unrelated and unlinked package, called github.com/aws/aws-sdk-go-v2/feature/s3/manager.
Now you're getting some religion, so you ask "what are the other so-called 'feature' packages?" and you try to browse pkg.go.dev at the github.com/aws/aws-sdk-go-v2/feature level but nope, that's not a Go module so there's nothing to see there. In fact, you can't even browse the other s3 features, never mind find out what other services have features. Fortunately, you can browse their GitHub repo at least: https://github.com/aws/aws-sdk-go-v2/tree/main/feature
It's quite clear that they use poorly thought-out cross-language codegen for this, which partly explains the lack of ergonomics, but also shows that they don't much care whether you use their stuff properly.
> That may be what S3 is like, but what the S3 API is is this: https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/s3
> My browser prints that out to 413 pages with a naive print preview. You can squeeze it to 350 pretty reasonably with a bit of scaling before it starts getting to awfully small type on the page.
idk why you link to Go SDK docs when you can link to the actual API reference documentation: https://docs.aws.amazon.com/AmazonS3/latest/API/API_Operatio... and its PDF version: https://docs.aws.amazon.com/pdfs/AmazonS3/latest/API/s3-api.... (just 3874 pages)
In MinIO is now in maintenance-modeThat may be what S3 is like, but what the S3 API is is this: https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/s3
My browser prints that out to 413 pages with a naive print preview. You can squeeze it to 350 pretty reasonably with a bit of scaling before it starts getting to awfully small type on the page.
Yes, there's a simple API with simple capabilities struggling to get out there, but pointing that out is merely the first step on the thousand-mile journey of determining what, exactly, that is. "Everybody uses 10% of Microsoft Word, the problem is, they all use a different 10%", basically. If you sat down with even 5 relevant stakeholders and tried to define that "simple API" you'd be shocked what you discover and how badly Hyrum's Law will bite you even at that scale.
In MinIO is now in maintenance-modeSurely there's github.com/aws/aws-sdk-go-v2 ?
In MinIO stops distributing free Docker imagesThese are different AWS partitions. They are completely separate from each other, requiring separate accounts and credentials.
There's one for China, one for the AWS government cloud, and there are also various private clouds (like the one hosting the CIA data). You can check their list in the JSON metadata that is used to build the AWS clients (e.g. https://github.com/aws/aws-sdk-go-v2/blob/1a7301b01cbf7e74e4... ).
In AWS multiple services outage in us-east-1I got bit by this a month ago.
You can disable the new behavior by setting 2 environment variables
export AWS_REQUEST_CHECKSUM_CALCULATION=when_required
export AWS_RESPONSE_CHECKSUM_CALCULATION=when_required
or adding the following 2 lines to a profile in ~/.aws/config
request_checksum_calculation=when_required
response_checksum_validation=when_required
Or just pin your AWS SDK to version before the following.
<https://github.com/aws/aws-sdk-go-v2/blob/release-2025-01-15...>
<https://github.com/boto/boto3/issues/4392>
<https://github.com/aws/aws-cli/blob/1.37.0/CHANGELOG.rst#L19>
<https://github.com/aws/aws-cli/blob/2.23.0/CHANGELOG.rst#223...>
<https://github.com/aws/aws-sdk-java-v2/releases/tag/2.30.0>
<https://github.com/aws/aws-sdk-net/releases/tag/3.7.963.0>
<https://github.com/aws/aws-sdk-php/releases/tag/3.337.0>
and wai
Read the rest
t for your S3 Compatible Object store to add a fix to support this.
fix: delete go.sum, change go.mod:
github.com/aws/aws-sdk-go-v2 latest
github.com/aws/aws-sdk-go-v2/config latest
github.com/aws/aws-sdk-go-v2/credentials latest
github.com/aws/aws-sdk-go-v2/service/iot latest
github.com/aws/aws-sdk-go-v2/service/iotdataplane latest
go mod tidy
go build
In AWS Golang 11/15/23 updates are incompatibleAWS Golang 11/15/23 updates are incompatible
1 points · Open discussionThe Go vs Rust debate is really tiring. Beyond releasing around the same time, they're languages built for extremely different purposes.
Instead, I'm going to lament about a few things I think would take Go from an extremely good language, to one of the best languages out there:
* Context. Context-creep is really annoying; similar to async in JS, it becomes something that over time absorbs your codebase and dirties function signatures beyond recognition [1]. Unlike promises in JS; for surprisingly low benefit. I don't for sure know what a better solution looks like, but my initial thought: the language runtime should have globals like setContext() and getContext(), which can set and get a goroutine-local context. If you want to pass a context between goroutines, just do it like you'd do it today.
* Enums. I will die on this hill: proper e
Read the rest
nums (think typescript and rust) are one of the most powerful programming paradigms in typed languages. Go not having them is one of its largest gaps; and leads to really weird obviously-should-be-an-enum things that instead get shoved into a set of constants with a common prefix [2]. What do you lose out on? So. Much. Beyond the obvious [3]; one of the coolest features of enum-prioritizing languages like Rust is exhaustive switch/casing; this is a huge feature in application development, and that's what Go is great at; except for this gap.
* Pointer-to-interface shenanigans, and how that oftentimes interacts with custom error handling. This is the WILDEST part of Go, and I am convinced that even extremely seasoned Go devs run into this, know that it does happen, try to avoid it, but can't explain why it happens. "Oh yeah, uh, nil, when coalesced into an interface, is nil, but, uh, also isn't, uh, nil, uh, when it comes to, uh, checking if its nil" [4] WHAT. There's no excuse for this; this isn't a feature, this is a bug, end of story. Its a bug that, for some reason, has lasted years; in the same breath that defenders explain why it happens they also say "oh, but, Go is industrial scale, its for large engineering teams"; this is not industrial, this is brittle.
[1] https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/s3
[2] https://pkg.go.dev/net/http#pkg-constants
[3] https://go.dev/play/p/mc-0m_fakfJ
[4] https://go.dev/play/p/lIEmO9tG4iQ
I found go compiler isn't very efficient in not linking in the dead code.
I ran into it by switching from aws-sdk-go to aws-sdk-go-v2 and the binary jumped from 27Mb to 66Mb [1]
Granted fully featured app will likely use all of the module's code so it's not a factor.
[1] https://github.com/aws/aws-sdk-go-v2/discussions/1532
In MicroShift