amplify-cli VS aws-cdk

Bug: Before continuing, we need to add some manual changes to the generated output since there is a bug in the 10.8.1 version of the Amplify CLI. To fix the issue, open the amplify/backend/predictions/identifyText<>/parameters.json file and add the following three key-value pairs to it:

AWS Amplify CLI - GitHub

If this is the first time using Amplify you'll need to install the Amplify CLI. This tool will help us setup and add Amplify's services.

This disconnection between the initial business cases of DynamoDB and Amplify can even be seen within the AWS teams themselves. [4] We don't believe any of them are to blame. The solo Front End Engineer bootstrapping a quick Amplify app for a PoC feels like a way different use case than a team of highly trained data engineers working on their Single Table Design for their micro-service. Amplify rightfully tries to offer an easy way to deal with storing data. And so it follows a standard SQL design with DynamoDB. This though leads to bad performance (original selling point of DynamoDB) or other limitations hard to anticipate.

Overall it is pretty clear and fine that Amplify focuses on PoC projects rather than production ones (with features like Geo-tagging [5] but no way to migrate data). However, when starting to get traction, it is a shame we need to completely eject instead of being able to extend because of lack of (boring but necessary) fundamentals.

[1] https://github.com/aws-amplify/amplify-cli/issues/10164

Unfortunately, and this is a bad look for AWS, Amplify still hasn't migrated to CDK v2, meaning they're still using the maintenance-only CDK v1, which is incredibly easy to break due to incompatible packages, and isn't getting any new features. Further, Amplify's implementation of CDK (I think it's the StackSynthesizer subclass) doesn't even support some of the most productive features of CDK like the ability to create a Lambda image from a Dockerfile. You have to define and push the image separately which misses the point of having the entire app defined within Amplify.

Hi u/recursivebob , can you please submit an issue to the Amplify CLI on Github using this link

Hi all, for a new project I need to create a web app and mobile app and would like to hear your opinion on what would be the right architecture. The architecture has two peculiarities, it needs: - a service for crawling/scraping and writing into a (document) DB - full search text support for the crawled/scraped data Since the budget for running is low and time is tight, I was looking into serverless and BaaS architectures. I like the idea of using a BaaS architecture so I was I thinking if Firebase or AWS Amplify are a good fit. Regarding the full search text, Firestore does not support full text search out of the box, but it is possible to use Elastic, Algolia, Typesense (https://firebase.google.com/docs/firestore/solutions/search). With AWS Amplify it's apparently even more easier - it appears that it can be directly connected to AWS ElasticSearch. Regarding the crawling/scraping, I could use e.g. EC2 instances. Now from the time perspective looks good, but not from the budget perspective. As I found here: https://github.com/aws-amplify/amplify-cli/issues/3860 an ElasticSearch Instance on AWS can cost 70$ for 2 hours!!! This is around the budget for a whole month... So what you guys would advice me? Are there any alternatives? How can I move fast with a minimal cost?

AWS Amplify code is open-sourced and could be found on GitHub at https://github.com/aws-amplify/amplify-cli. We could make use of the NPM packages deployed independently to recreate the functionality offered by the AWS Amplify CLI regarding the GraphQL transformers. The entry point for generating the Appsync resolvers could be found here and the class we are interested in is GraphQLTransform which takes as a parameter all the individual transformers and iterates over them to generate the GraphQL resolvers and the associated CloudFormation stacks for deploying those resolvers.

Can you check that issue: https://github.com/aws-amplify/amplify-cli/issues/6338

AWS Amplify - The AWS Amplify CLI is a toolchain which includes a robust feature set for simplifying mobile and web application development. The CLI uses AWS CloudFormation and nested stacks to allow you to add or modify configurations locally before you push them for execution in your account.

environment: Specifies the environment variable that will be available to our Lambda function. In this case I wrote an environment for RDS Database. Anyway, later I will write about AWS CDK using Python for creating database clusters, etc.

Today, I will show you how to build Amazon Location Service, which allows you to build location-based applications within your AWS environment using AWS Cloud Development Kit (AWS CDK) and AWS CloudFormation. I will also show examples of the recently popular CDK Migrate and AWS CloudFormation IaC generator.

AWS Cloud Development Kit (CDK): is an open-source software development framework to define your cloud application resources using familiar programming languages.

I am not one to build programming languages on a whim. In fact, I've spent the last five years building the AWS CDK, which is a multi-language library that addresses some of the challenges I am talking about by allowing developers to define cloud infrastructure using their favorite programming language.

I recently started exploring SST as an alternative to my favorite full-stack set consisting of Projen, AWS CDK, and React. I have been thoroughly impressed with the experience so far. In this article, I will demonstrate how to create a Next.js App Router S3 Picture Uploader using SST.

AWS CDK

For KMS 🔑, Each key is ~$1/mo, and with CDK, keys are generated on a massive scale, if not centralized.

Here is a github repository containing the code and instructions on how to automate this whole setup using AWS CDK.

Now that you have a working smart contract event listener, we'll deploy the resources to AWS using AWS CDK, which is an Infrastructure as Code (IaC) tool. AWS CDK allows you to configure, deploy, and manage AWS cloud resources using popular programming languages such as TypeScript.

✨ Synthesis time: 14.44s CdkScheduledReportingStack: start: Building f3a91fb0ff1605e49b4b00aa223098d7a9a5307e98027f77aecc36bc05a4c3e7:current_account-current_region CdkScheduledReportingStack: success: Built f3a91fb0ff1605e49b4b00aa223098d7a9a5307e98027f77aecc36bc05a4c3e7:current_account-current_region CdkScheduledReportingStack: start: Publishing f3a91fb0ff1605e49b4b00aa223098d7a9a5307e98027f77aecc36bc05a4c3e7:current_account-current_region CdkScheduledReportingStack: start: Building 517f907ce2318aa1a929b43bc1a0247ed509c92576c23a0a8aadfe1677f2ebd7:current_account-current_region CdkScheduledReportingStack: success: Built 517f907ce2318aa1a929b43bc1a0247ed509c92576c23a0a8aadfe1677f2ebd7:current_account-current_region CdkScheduledReportingStack: start: Publishing 517f907ce2318aa1a929b43bc1a0247ed509c92576c23a0a8aadfe1677f2ebd7:current_account-current_region CdkScheduledReportingStack: success: Published 517f907ce2318aa1a929b43bc1a0247ed509c92576c23a0a8aadfe1677f2ebd7:current_account-current_region CdkScheduledReportingStack: success: Published f3a91fb0ff1605e49b4b00aa223098d7a9a5307e98027f77aecc36bc05a4c3e7:current_account-current_region This deployment will make potentially sensitive changes according to your current security approval level (--require-approval broadening). Please confirm you intend to make the following modifications: IAM Statement Changes ┌───┬────────────────────────────────────────┬────────┬───────────────────────┬────────────────────────────────────────┬───────────────────────────────────────────────┐ │ │ Resource │ Effect │ Action │ Principal │ Condition │ ├───┼────────────────────────────────────────┼────────┼───────────────────────┼────────────────────────────────────────┼───────────────────────────────────────────────┤ │ + │ ${SalesReportFunction.Arn} │ Allow │ lambda:InvokeFunction │ Service:events.amazonaws.com │ "ArnLike": { │ │ │ │ │ │ │ "AWS:SourceArn": "${Rule.Arn}" │ │ │ │ │ │ │ } │ ├───┼────────────────────────────────────────┼────────┼───────────────────────┼────────────────────────────────────────┼───────────────────────────────────────────────┤ │ + │ ${SalesReportFunction/ServiceRole.Arn} │ Allow │ sts:AssumeRole │ Service:lambda.amazonaws.com │ │ ├───┼────────────────────────────────────────┼────────┼───────────────────────┼────────────────────────────────────────┼───────────────────────────────────────────────┤ │ + │ ${SalesReportTopic} │ Allow │ sns:Publish │ AWS:${SalesReportFunction/ServiceRole} │ │ └───┴────────────────────────────────────────┴────────┴───────────────────────┴────────────────────────────────────────┴───────────────────────────────────────────────┘ IAM Policy Changes ┌───┬────────────────────────────────────┬────────────────────────────────────────────────────────────────────────────────┐ │ │ Resource │ Managed Policy ARN │ ├───┼────────────────────────────────────┼────────────────────────────────────────────────────────────────────────────────┤ │ + │ ${SalesReportFunction/ServiceRole} │ arn:${AWS::Partition}:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole │ └───┴────────────────────────────────────┴────────────────────────────────────────────────────────────────────────────────┘ (NOTE: There may be security-related changes not in this list. See https://github.com/aws/aws-cdk/issues/1299) Do you wish to deploy these changes (y/n)?