Filter
Exclude
Time range
-
Near
Jun 11
Reduce Next.js SSR cold-start latency on AWS Amplify with scheduled warmups. A lightweight Lambda triggered by EventBridge can periodically hit a health endpoint and keep server-side compute ready after idle periods. Read more 👉 u11d.com/blog/nextjs-amplify… #NextJS #AWSAmplify #AWSLambda #EventBridge
1
16
cursorのclaud agentが便利すぎたので布教を兼ねて自分が導入した時の手順を纏めといた。 まだまだ試してみたいことが山のようにあって追いつかん。 #Cursor #CursorCloudAgent #AWSAmplify #AmplifyGen2 #個人開発
2
8
476
【AWS Amplify導入で、ECS運用からGitプッシュだけで完了するデプロイへ移行】 #AWSAmplify #findy_tools 🔗findy-tools.io/products/aws-…
1
5
723
フロントエンドのインフラ構築負荷を劇的に軽減したAWS Amplify。Gitプッシュだけでデプロイ完了、プレビュー環境自動生成でレビュー効率を向上させた株式会社ispecのAWS Amplify活用事例をご紹介 #AWSAmplify #findy_tools findy-tools.io/products/aws-…
2
482
Congratulations 🙌 you build amazing tools which we used day to day work. Amplify is one of the tool I love it. Kiro is still evolving. Looking forward to what you will build there.
2
29
📬Career update: After nearly a decade building developer tools at AWS — @AWSAmplify and @kirodotdev — I'm joining @NVIDIAAI to lead their Developer Experience. Most developers think of NVIDIA as a hardware company. My job is to help them see everything else. The software stack is deeper than most realize: discover and experiment with models at build.nvidia.com, build agents with NemoClaw, Nemotron, and NIMs, deploy to production via cloud partners or on-prem GPUs. I own the front door to all of it — NVIDIA Console, CLI, MCP, and access management. My north star: work backwards from developers to solve real pain points. When I joined Amazon, I had spent years avoiding AWS entirely — @Heroku and @digitalocean were my comfort zone. That blank slate turned out to be a blessing in disguise. I'm bringing that same fresh eyes approach to NVIDIA. Excited to step into a new world again. 🚀
1
4
162
Deploying Next.js on AWS just got a lot easier!! I know aspects around this are a bit polarizing , but overall this is really neat to see and glad I was apart of it from the @AWSAmplify side! Kudos to @feedthejim and team :)
Mar 26
Next.js 16.2 introduces a stable Adapter API, built with Netlify, Cloudflare, OpenNext, AWS, and Google Cloud. But the API is only part of the story. Next.js is used by millions of developers across every major cloud, and making it work well everywhere is on us. Here are our commitments. nextjs.org/nextjs-across-pla…
1
8
643
Replying to @nextjs
I really hope that Aws can get their stuff together with @AWSAmplify , it’s pretty much been abandoned for a big while.
2
4
4,880
This is what I was hoping @AWSAmplify pushed with Kiro.
We’re launching a brand new, full-stack vibe coding experience in @GoogleAIStudio, made possible by integrations with the @Antigravity coding agent and @Firebase backends. This unlocks: — Full-stack multiplayer experiences: Create complex, multiplayer apps with fully-featured UIs and backends directly within AI Studio — Connection to real-world services: Build applications that connect to live data sources, databases, or payment processors and the Antigravity agent will securely store your API credentials for you — A smarter agent that works even when you don't: By maintaining a deeper understanding of your project structure and chat history, the agent can execute multi-step code edits from simpler prompts. It also remembers where you left off and completes your tasks while you’re away, so you can seamlessly resume your builds from anywhere — Configuration of database connections and authentication flows: Add Firebase integration to provision Cloud Firestore for databases and Firebase authentication for secure sign-in This demo displays what can be built in the new vibe coding experience in AI Studio. Geoseeker is a full-stack application that manages real-time multiplayer states, compass-based logic, and an external API integration with @GoogleMaps 🕹️
1
5
551
【フロントエンドのインフラ運用をやめたら開発速度が上がった — AWS Amplify導入記】 #AWSAmplify #findy_tools 🔗findy-tools.io/products/aws-…
36
9,629
Amplify Gen2のスキーマ定義でGSIの投影(projection)対象属性を指定できるようになった。属性が多いテーブルでは必要なキーのみを指定することでコスト削減が見込めそう docs.amplify.aws/react/build… #aws #AWSAmplify
3
10
1,471
It's interesting....I wonder if it's driving more usage of @AWSAmplify Hosting
I used to think Vercel would win the AI era. They're AI native and dev-friendly But now Claude one-shots AWS deploys from CLI, for 10-100x cheaper hosting
1
3
540
Don’t be a "safe" coder. It's a trap. I spent half day debugging @AWSAmplify config only to realize that process env NEXT_PUBLIC works, but process?.env?.NEXT_PUBLIC returns undefined because the Next.js compiler doesn't recognize the pattern. @vercel why you do this to me? 🤡
1
2
56
Amplify Gen2 VSCode拡張のv0.15.0をリリースしました🚀リソースツリーから論理IDやリソースタイプで検索&フィルタリングして表示できるようになりました!ぜひ、お試しください。 Open VSXでも公開しているのでKiro IDEでも使えます! github.com/fossamagna/amplif… #AWSAmplify #aws

2
11
389
@AWSAmplify Backend VSCode v0.13.0でBedrock AgentCoreに対応しました。 みのるんさん紹介のAmplify&AgentCoreをsandbox開発する時になんかに便利です!ぜひ使ってみてください。 marketplace.visualstudio.com…
2
3
8
983
Developers using @AWSAmplify, this one is for you! I know many of you have been waiting for a migration tool to migrate to Gen 2! Now you can do it! 🎉🎉 Check out the documentation here: bit.ly/gen1-gen2-migration-g… Do you have feedback or ideas to make your experience better? ->
2
4
243
First I was an idea guy. Then I was a skills issue developer. Then I was vibe coder. Now I am apparently discussing github branching strategies as I migrate off @AWSAmplify to a self-hosted Lightsail vps. Sooooo, yeah - just start. You can just do and build things and you will probably learn something along the way.
1
3
236