amazonka
aws-sign4
Our great sponsors
| amazonka | aws-sign4 | |
|---|---|---|
| 7 | - | |
| 589 | 4 | |
| - | - | |
| 9.5 | 0.0 | |
| 16 days ago | over 9 years ago | |
| Haskell | Haskell | |
| GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" 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.
amazonka
-
Getting Amazonka S3 to work with localstack
This is perhaps not as obvious as it could be. A penny for your thoughts? https://github.com/brendanhay/amazonka/issues/968
- amazonka 2.0.0-rc2 announced
-
[JOB] Haskell Developer @ Bellroy (Remote)
Most of our tech stack is built on Free and Open Source Software, and we give back wherever we can - either by upstreaming fixes or publishing libraries. In the Haskell world, we’ve open-sourced wai-handler-hal and aws-arn, made significant contributions to amazonka and we have more on the way. If you’re interested, here’s our applications page. If you have questions, you can ask them here or email [[email protected]](mailto:[email protected]).
-
stack
Stack does not clone a copy of a git package for each of a user's projects that uses the package but cabal does. This can be a deal-breaker for cabal when using huge git projects like https://github.com/brendanhay/amazonka that can take forever to git clone. If you have a test/CI setup for a project that uses such packages, cabal's lack of caching can also cause huge delays and more opportunities for failure (from network errors or timeouts). From the proceedings of past issues, I don't think cabal devs are interested in addressing this use case. https://github.com/haskell/cabal/issues/5586
- Usability of smart constructors and large records with required, optional, and default parameters
- Amazonka 2.0.0-rc1 is ready for testing
-
Haskell ghost knowledge; difficult to access, not written down
amazonka is a bit of a minefield despite being listed as the only AWS library by SOTU
aws-sign4
We haven't tracked posts mentioning aws-sign4 yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
aws-ec2 - Now maintained by: See https://github.com/memcachier/aws-ec2
aws-sdk - AWS SDK for Haskell
amazonka-s3-streaming - Provides a conduit based interface to uploading data to S3 using the Multipart API
themoviedb - Simple Haskell library that provides functions for retrieving movie metadata from TheMovieDB
aws - Amazon Web Services for Haskell
oanda-rest-api - Haskell library implementing the OANDA REST API
amazon-emailer - A simple daemon to process messages put into a postgresql table and mail them out using amazons SES.
hs-GeoIP - Haskell bindings to the MaxMind GeoIPCity database
messente - Messente SMS Gateway for Haskell
aws-lambda - Haskell bindings for AWS Lambda