amazonka VS aws-sdk

Compare amazonka vs aws-sdk and see what are their differences.

amazonka

A comprehensive Amazon Web Services SDK for Haskell. (by brendanhay)

aws-sdk

Landing page for the AWS SDKs on GitHub (by aws)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
amazonka aws-sdk
7 10
587 63
- -
9.7 3.9
about 1 month ago 2 months ago
Haskell
GNU General Public License v3.0 or later GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

Posts with mentions or reviews of amazonka. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-09.
  • Getting Amazonka S3 to work with localstack
    2 projects | /r/haskell | 9 Dec 2023
    This is perhaps not as obvious as it could be. A penny for your thoughts? https://github.com/brendanhay/amazonka/issues/968
  • stack
    7 projects | /r/haskell | 17 Jul 2022
    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
  • Amazonka 2.0.0-rc1 is ready for testing
    2 projects | /r/haskell | 28 Nov 2021
  • Haskell ghost knowledge; difficult to access, not written down
    13 projects | /r/haskell | 24 Jan 2021
    amazonka is a bit of a minefield despite being listed as the only AWS library by SOTU

aws-sdk

Posts with mentions or reviews of aws-sdk. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-03.
  • AWS SDK v3 + DAX
    2 projects | /r/aws | 3 May 2023
    From this GitHub issue and this one from 2021 it seems like AWS just doesn't care about this - so, asking here if anyone knows of a workaround (other than "just keep using v2"... that's not a long-term solution), or if any AWS devs can shed some light on the situation.
  • Amazon ECS Exec to access your Windows containers on Amazon EC2 and AWS Fargate
    2 projects | dev.to | 16 Sep 2022
    Please note that ECS Exec is supported via AWS SDKs, AWS CLI, as well as AWS Copilot. In the future, we will enable this capability in the AWS Console. Also, this feature only supports Linux containers (Windows containers support for ECS Exec is not part of this announcement).
  • Using AWS for Text Classification Part-1
    2 projects | dev.to | 27 Aug 2022
    Set up the AWS CLI and AWS SDKs.
  • Tips for scalable workflows on AWS
    3 projects | dev.to | 1 Jul 2022
    One common pattern to integrate with AWS from a workflow job is to call additional services using the AWS CLI. Overall, this works well, but there are a few considerations one should note when doing so. First and foremost, a workflow job needs to know where the AWS CLI installed and how to use it. You can do this by either installing the AWS CLI on the host compute and bind mounting it into the container job, or including the AWS CLI as part of the container image. That said, see my notes above on keeping container images small for associated caveats. Second, while the AWS CLI is great for scripting, for more complex operations direct integration via the AWS SDK is a better fit.
  • Waiting for things to happen and paginating responses with boto3
    2 projects | dev.to | 17 Jun 2022
    I like how you can imagine what the Python implementation that uses this looks like from this structure. If there are no waiters for what you need, you can create an Issue in the AWS SDK repository because the service teams provide those. I tried that for DynamoDB Streams, and I'm curious to see how long it will take them to add that.
  • Sending Emails with SES, Terraform and TypeScript
    4 projects | dev.to | 24 Apr 2022
    Amazon Simple Email Service (SES) is a serverless service for sending emails from your applications. Like other AWS services, you can send emails with SES using the AWS REST API or the AWS SDKs. In this article, I want to look at how to send emails using SES with TypeScript specifically.
  • The Evolution of AWS from a Cloud-Native Development Perspective: Serverless, Event-Driven, Developer-Friendly, Sustainable
    6 projects | dev.to | 18 Mar 2022
    In 2002, Jeff Bezos's so-called API Mandate forced all Amazon teams to expose their data and functionality through service interfaces. Amazon has built AWS around the same principles: every service is programmatically controllable, from starting a virtual machine to accessing a satellite. While this is an essential property of an effective cloud platform, it is not necessarily developer-friendly. By now, AWS has incrementally and significantly improved in this space. Besides using their APIs, we can control services and infrastructure with a unified Command Line Interface (CLI), Software Development Kits (SDK), CloudFormation, and, since July 2019, the AWS Cloud Development Kit (CDK). The CDK had a massive impact on developer productivity and satisfaction. While teams could already access and control services and infrastructure using the AWS SDK and their favorite programming language, infrastructure was primarily defined using incredible amounts of mostly punctuation marks and whitespace, also known as YAML or JSON. CDK — initially only flavored TypeScript and Python — finally gave developers an AWS-native means to define Infrastructure as actual Code. Since its introduction, AWS has added support for more languages, like Java, C#, and Go.

What are some alternatives?

When comparing amazonka and aws-sdk you can also consider the following projects:

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.

botocore - The low-level, core functionality of boto3 and the AWS CLI.

hs-GeoIP - Haskell bindings to the MaxMind GeoIPCity database

aws-lambda - Haskell bindings for AWS Lambda

loup - Simple Workpools

ec2-unikernel - Tool for uploading unikernels into EC2

aws-cloudfront-signer - Haksell library package for signing URL requests to the AWS CloudFront service

serverless-haskell - Deploying Haskell applications to AWS Lambda with Serverless

minio-hs - Minio Client SDK for Haskell