amazonka
amazonka
| amazonka | amazonka | |
|---|---|---|
| 1 | 7 | |
| 0 | 589 | |
| - | - | |
| 9.9 | 9.5 | |
| over 2 years ago | 28 days ago | |
| Haskell | ||
| GNU General Public License v3.0 or later | Mozilla Public License 2.0 |
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
-
Amazonka 2.0.0-rc1 is ready for testing
Yes, I believe it is, even with 9.2. There was a branch for the 1.x series with GHC 9.0 support, but it was deleted. I have a backup at https://github.com/ysangkok/amazonka/tree/release/1.7.0
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
What are some alternatives?
aws-ec2 - Now maintained by: See https://github.com/memcachier/aws-ec2
amazonka-s3-streaming - Provides a conduit based interface to uploading data to S3 using the Multipart API
aws - Amazon Web Services for Haskell
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
aws-lambda - Haskell bindings for AWS Lambda
loup - Simple Workpools
aws-cloudfront-signer - Haksell library package for signing URL requests to the AWS CloudFront service
ec2-unikernel - Tool for uploading unikernels into EC2
serverless-haskell - Deploying Haskell applications to AWS Lambda with Serverless
minio-hs - Minio Client SDK for Haskell
aws-sdk - AWS SDK for Haskell