lobo/aws-sdk-for-zig
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
AWS SDK for Zig
140 Commits 7 Branches 2 Tags 20 MiB
Zig 99.9%
Makefile 0.1%
e66c82468a
Go to file
Emil Lerch e66c82468a
All checks were successful
continuous-integration/drone/push Build is passing
Details
most requests working (see below) 
rest_json_1_work_with_lambda seems to fail
STS-generated keys not working
there might be an intermittent signature failure
2022-01-19 19:29:58 -08:00
codegen upgrade to zig 0.9.0 2022-01-03 08:06:14 -08:00
smithy upgrade to zig 0.9.0 2022-01-03 08:06:14 -08:00
src most requests working (see below) 2022-01-19 19:29:58 -08:00
.drone.yml fix build 2022-01-12 18:25:53 -08:00
.gitignore initial cut of VersionStep - implementation TBD 2022-01-12 12:21:28 -08:00
build_test.zig add build_test/VersionStep 2022-01-12 16:52:45 -08:00
build.zig initial cut of VersionStep - implementation TBD 2022-01-12 12:21:28 -08:00
CopyStep.zig dig out aws crt. project no longer builds 2022-01-10 21:49:59 -08:00
GitRepoStep.zig dig out aws crt. project no longer builds 2022-01-10 21:49:59 -08:00
LICENSE first thing that actually works 2021-04-27 11:24:01 -07:00
Makefile first thing that actually works 2021-04-27 11:24:01 -07:00
README.md update readme 2022-01-11 11:19:40 -08:00
VersionStep.zig fix build 2022-01-12 18:25:53 -08:00
zfetch_deps.zig dig out aws crt. project no longer builds 2022-01-10 21:49:59 -08:00

README.md

AWS SDK for Zig (zig-native branch)

Build Status

WARNING: This branch is in development, with builds currently failing!

This SDK currently supports all AWS services except EC2 and S3. These two services only support XML, and zig 0.8.0 and master both trigger compile errors while incorporating the XML parser. S3 also requires some plumbing tweaks in the signature calculation, which is planned for a zig version (probably self-hosted 0.9.0) that no longer has an error triggered. Examples of usage are in src/main.zig.

This is designed to be built statically using the aws_c_* libraries, so we inherit a lot of the goodness of the work going on there. Current executable size is 9.7M, about half of which is due to the SSL library. Running strip on the executable after compilation (it seems zig strip only goes so far), reduces this to 4.3M. This is for x86_linux, (which is all that's tested at the moment).

Building

zig build should work. It will build the code generation project, run the code generation, then build the main project with the generated code. There is also a Makefile included, but this hasn't been used in a while and I'm not sure that works at the moment.

First time build should use zig build -Dfetch to fetch dependent packages (zfetch and friends).

Running

This library mimics the aws c libraries for it's work, so it operates like most other 'AWS things'. main.zig gives you a handful of examples for working with services. For local testing or alternative endpoints, there's no real standard, so there is code to look for AWS_ENDPOINT_URL environment variable that will supersede all other configuration.

TODO List:

  • Implement credentials provider
  • Implement sigv4 signing
  • Implement jitter/exponential backoff. This appears to be configuration of aws_c_io and should therefore be trivial
  • Implement timeouts and other TODO's in the code
  • Switch to aws-c-cal upstream once PR for full static musl build support is merged (see Dockerfile)
  • Implement AWS restXml protocol. Includes S3. Total service count 4. This may be blocked due to the same issue as EC2.
  • Implement AWS EC2 query protocol. Includes EC2. Total service count 1. This is currently blocked, probably on self-hosted compiler coming in zig 0.9.0 (January 2022) due to compiler bug discovered. More details and llvm ir log can be found in the XML branch.
  • Implement sigv4a signing

Compiler wishlist/watchlist: