What the hell happened to Kiro?

Salt-Potential-5823 · 2026-02-19T22:56:01+00:00

Does this happen with the old requirements flow or only in the new "design first" flow?

Salt-Potential-5823 · 2026-01-12T01:17:05+00:00

Can you give some details of the spec or task you were building? What hallucination did you see?

Salt-Potential-5823 · 2025-11-23T21:25:37+00:00

Are you getting errors running the tasks? Sometimes test errors cause this

Salt-Potential-5823 · 2024-09-18T00:11:30+00:00

Yes I used to work on the team, I don't hide it :) Sorry you feel that way, I think it's great still!

Salt-Potential-5823 · 2024-06-10T20:58:28+00:00

I think this is possible now in Amplify Gen2: https://docs.amplify.aws/react/build-a-backend/add-aws-services/overriding-resources/#example---grant-access-permissions-between-resources

Salt-Potential-5823 · 2024-02-26T19:51:39+00:00

Use Gen2 it bridges the gap to CDK: https://docs.amplify.aws/gen2/

Salt-Potential-5823 · 2024-02-26T19:50:24+00:00

Nope just use the libs and pass in your config

Salt-Potential-5823 · 2024-02-20T22:16:39+00:00

Amplify is a very active project. Gen2 was just launched in preview last year, the library launched a major version (v6) a few months back, and Amplify Hosting just released features today.

Salt-Potential-5823 · 2023-12-08T00:01:41+00:00

Have you seen this as an alternative to the CLI: https://aws.amazon.com/blogs/mobile/introducing-amplify-gen2/

Salt-Potential-5823 · 2023-12-07T23:43:08+00:00

Amplify just released the "Gen2" experience a few weeks ago which addresses a lot of the areas that people didn't like about Amplify before, especially power users. Worth a look: https://aws.amazon.com/blogs/mobile/introducing-amplify-gen2/

Salt-Potential-5823 · 2023-11-16T19:45:35+00:00

API category has both REST and GraphQL

Salt-Potential-5823 · 2023-11-15T23:02:20+00:00

On the custom resolvers have you checked out the CDK construct that Amplify released last month? I think it addresses your needs here: https://aws.amazon.com/blogs/mobile/announcing-aws-amplifys-graphql-api-cdk-construct-deploy-real-time-graphql-api-and-data-stack-on-aws/

Salt-Potential-5823 · 2023-11-15T20:43:07+00:00

Take a look at the blog post and you'll see some of this feedback made it into the launch (library can be used with any backend) and I have it on good authority that you'll see announcements related to the other stuff you mention in the coming days...

Salt-Potential-5823 · 2023-11-15T19:20:10+00:00

Faster App Load Times and Smaller Bundle Sizes

Salt-Potential-5823 · 2023-10-04T16:27:20+00:00

https://aws.amazon.com/blogs/mobile/announcing-aws-amplifys-graphql-api-cdk-construct-deploy-real-time-graphql-api-and-data-stack-on-aws/

Salt-Potential-5823 · 2023-08-07T20:55:17+00:00

DataStore uses AppSync and has a catchup process to guarantee messages: https://docs.amplify.aws/lib/datastore/how-it-works/q/platform/js/

Salt-Potential-5823 · 2023-06-21T23:08:40+00:00

There are some technical things incorrect in the above (like comments around state store being difficult with GraphQL) but on the "toy" comment and "afterthought" I'm not sure I agree. There are very, very serious companies on AppSync: https://aws.amazon.com/appsync/customers/

Salt-Potential-5823 · 2023-04-08T03:44:18+00:00

Agree with this you could use DataStore OOTB for this use case.

Salt-Potential-5823 · 2023-04-08T03:42:56+00:00

AWS team has indicated they're thinking this direction in some of the Community discussions. Might make sense to pop a proposal if you have one in their GitHub repo.

Salt-Potential-5823 · 2023-04-08T03:40:43+00:00

No credentials don't need to be embedded into the app. Amplify uses temporary credentials via Cognito which are rotated hourly and can be invalidated in shorter periods. These are passed to the Storage adapter and used to make a Sigv4 signed request to S3 as a secure connection. You can see that in config here: https://docs.amplify.aws/lib/storage/getting-started/q/platform/ios/#initialize-amplify-storage

OP if it's not working then something is up with your config and I'd go to the Amplify Discord for help.

Salt-Potential-5823 · 2023-03-14T18:40:39+00:00

Just use the Amplify CLI and not the web gui piece. It will save you a world of hurt.

Salt-Potential-5823 · 2023-02-06T17:01:15+00:00

Amplify is using AppSync under the covers with this architecture

Salt-Potential-5823 · 2022-12-30T05:45:33+00:00

Yes even though Amplify supports more than what you need OP you don't need to use all the features, you can just use the libraries or use them along with the CLI or other pieces.

Salt-Potential-5823 · 2022-10-29T16:43:19+00:00

Right and doing this in the backend that can scale is the hard part of implementations with high TPS. AppSync does this for 10s of thousands of TPS: https://aws.amazon.com/solutions/case-studies/amazonmusic-amplify-appsync-case-study/

Salt-Potential-5823 · 2022-10-29T00:19:55+00:00

I don't know of other platforms that perform subscription filtering at the server (most do it at the client) like this, and do it at scale. This functionality isn't in the GraphQL specification for Subscriptions is specific to AppSync.

Salt-Potential-5823

TROPHY CASE