aws-sdk
aws-sdk-js-v3
aws-sdk | aws-sdk-js-v3 | |
---|---|---|
10 | 18 | |
64 | 2,864 | |
- | 1.5% | |
3.9 | 9.9 | |
3 months ago | 2 days ago | |
TypeScript | ||
GNU General Public License v3.0 or later | Apache 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.
aws-sdk
-
AWS SDK v3 + DAX
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.
-
The Truth About CloudWatch Pricing
AWS SDKs
-
Amazon ECS Exec to access your Windows containers on Amazon EC2 and AWS Fargate
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
Set up the AWS CLI and AWS SDKs.
-
Tips for scalable workflows on AWS
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
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.
- Will AWS SDKs make Terraform useless in the future?
-
Sending Emails with SES, Terraform and TypeScript
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
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.
-
AWS SSO integration with G suite
Yes, no AWS api to create users/groups: https://github.com/aws/aws-sdk/issues/25
aws-sdk-js-v3
-
AWS SDK v3 + DAX
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.
-
Why and how you should use AWS SDK for JavaScript (v3) on Node.js 18
First class typescript support, but everything is possibly undefined?
-
ts-dynamodb-attributes-transformer - A code transformer of TypeScript object to DynamoDB attributes
I published "ts-dynamodb-attributes-transformer" that transforms the TypsScript object to Amazon DynamoDB attributes (precisely, this attributes type is Record that is defined at aws-sdk-js-v3).
- A New Hope for Object Storage: R2 Enters Open Beta
-
Working with EKS: Using IAM and native K8s service accounts to access AWS S3
Once we have verified the presence of the AWS_WEB_IDENTITY_TOKEN_FILE and AWS_ROLE_ARN environment variables, our pod is ready to connect to and read from S3. The following Typescript snippet illustrates a simple example which fetches the names of all the S3 buckets in our account. It uses the AWS SDK for JavaScript V3
-
Deno in 2021
If you'd like the Amazon JavaScript SDK to support Deno then make your support known on this thread:
https://github.com/aws/aws-sdk-js-v3/issues/1289
-
AWS SDK v2 or v3 - which one should you use?
I really suggest checking out the repo and especially the Upgrading section for more details.
-
AWS management: please add more staff to work on the AWS JS v3 SDK
No CloudFront URL signing - how can v3 SDK be labeled as general release if it doesn't have feature parity with the v2 SDK?
- AWS keeps dropping the ball with their AWS JavaScript v3 SDK
- ZA̡͊͠͝LGΌ causes "Invalid MD5 checksum on messages"
What are some alternatives?
botocore - The low-level, core functionality of boto3 and the AWS CLI.
middy - 🛵 The stylish Node.js middleware engine for AWS Lambda 🛵
amazonka - A comprehensive Amazon Web Services SDK for Haskell.
aws4fetch - A compact AWS client and signing utility for modern JS environments
amazon-sagemaker-examples - Example 📓 Jupyter notebooks that demonstrate how to build, train, and deploy machine learning models using 🧠 Amazon SageMaker.
cfn-diagram - CLI tool to visualise CloudFormation/SAM/CDK stacks as visjs networks, draw.io or ascii-art diagrams.
serverless-haskell - Deploying Haskell applications to AWS Lambda with Serverless
aws-sdk-js - AWS SDK for JavaScript in the browser and Node.js
aws-route53 - A Haskell AWS Route53 client library
jsii - jsii allows code in any language to naturally interact with JavaScript classes. It is the technology that enables the AWS Cloud Development Kit to deliver polyglot libraries from a single codebase!
aws-genomics-workflows - Genomics Workflows on AWS
bref - Serverless PHP on AWS Lambda