aws-sdk
serverless
aws-sdk | serverless | |
---|---|---|
10 | 24 | |
64 | 2,217 | |
- | - | |
3.9 | 0.0 | |
3 months ago | 3 months ago | |
TypeScript | ||
GNU General Public License v3.0 or later | MIT 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.
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
serverless
- Using Flask for API development
- Where can I find examples of cloud architectures ?
-
Confused around serverless trends and need opinion on the architecture.
I don't know any tutorials that cover all of these, but check out: https://cdkpatterns.com/ for 1) https://docs.aws.amazon.com/cdk/v2/guide/cdk_pipeline.html for 2) 3) and 5) https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-cdk-testing.html for 4)
-
Why are pulumi examples repo not showing good re-useable design patterns
I would like to see re-useable design patterns advocated similar to the terraform/terragrunt modules concepts. Encouraging pulumi.ComponentResource definitions multi environment structure, best practices. The cdk guys have something similar https://cdkpatterns.com/.
- Lambda best approach
-
Building a Flutter application (for Web) with AWS Lambda Function URL backend using AWS CDK Pipelines (written in Java)
While writing this post, the four stacks combined are 129 lines of source code. With the help of the CDK Constructs that are being used this translates to over 1k lines of code in CloudFormation. We are only using L2 constructs here β there is way more constructs available that you can use in the Constructs Hub and also a lot of guidance regarding the usage of CDK over at CDKPatterns.
-
In a serverless architecture, is it best to handle all API methods of a single entity in one lambda function with one API endpoint, or create an API endpoint for each and a lambda as a result?
I use the "Lambda-lith" pattern, primarily because I am using Rust and deploying via CI/CD (codepipeline).
-
Learning Lambda
Here is a read of common lambda design pattern https://github.com/cdk-patterns/serverless/blob/main/the-lambda-trilogy/README.md
- Makefile to manage containers ?
-
What Are AWS CDK Constructs, Stacks and How To Use Them
Level 3 constructs are opinionated units of reusable code which often deliver a service. Open source level 3 constructs are available from AWS Solutions Constructs - an extension to the CDK, CDK Patterns - a library of well-architected patterns, Construct Hub - a library of open-source constructs and some even come out of the box with the CDK - these are appended with 'patterns' to make them identifiable. Two examples are shown below:
What are some alternatives?
botocore - The low-level, core functionality of boto3 and the AWS CLI.
nx-serverless - π The Ultimate Monorepo Starter for Node.js Serverless Applications
amazonka - A comprehensive Amazon Web Services SDK for Haskell.
lift - Expanding Serverless Framework beyond functions using the AWS CDK
amazon-sagemaker-examples - Example π Jupyter notebooks that demonstrate how to build, train, and deploy machine learning models using π§ Amazon SageMaker.
terraform-aws-appsync - Terraform module to create AWS AWS AppSync resources πΊπ¦
serverless-haskell - Deploying Haskell applications to AWS Lambda with Serverless
terraform-aws-next-js - Terraform module for building and deploying Next.js apps to AWS. Supports SSR (Lambda), Static (S3) and API (Lambda) pages.
aws-route53 - A Haskell AWS Route53 client library
sst-start-demo - A simple SST app to demo the new `sst start` command
aws-genomics-workflows - Genomics Workflows on AWS
aws-sam-typescript-layers-example - Example project for developing AWS Lambda functions on TypeScript with all goodies: local development, tests, debugging, shared layers (3rd party and your own), and deploy.