DEV Community: Kenichiro Wada

A Vibe Coding Beginner Tried Making a Game with Amazon Q CLI

Kenichiro Wada — Fri, 20 Jun 2025 03:02:03 +0000

The header image is for illustrative purposes only and is not related to the main text.

This text is a translation of the content from the following article using Amazon Nova Premier.

https://zenn.dev/keni_w/articles/e95dda34d32ae8

An event called "Create a game with Amazon Q CLI and get a T-shirt" was being held, and many people were challenging it. Also, after hearing about AI development the other day, I thought I should try Vibe Coding... so I gave it a try.

About the event (until June 30, 2025)
https://aws.amazon.com/jp/blogs/news/build-games-with-amazon-q-cli-and-score-a-t-shirt/

What is Vibe Coding?

I set the model to Amazon Nova Pro in Amazon Bedrock and asked about Vibe Coding.

Vibe Coding is an innovative approach that combines sensitivity and atmosphere with traditional programming paradigms. In this method, developers not only implement functions but also express emotions and visions through code.
Vibe Coding deeply considers team dynamics, culture, and the final user experience. Developers are encouraged to write code that reflects the overall atmosphere and emotional tone of the project, resulting in more personalized and intuitive software solutions.
Vibe Coding emphasizes not only technical accuracy but also creativity and empathy, making the development process more inclusive and human-friendly. This approach is particularly effective in creative industries and fields that prioritize user experience.

Setup

Set up by looking at the explanation pages and articles by pioneers.

https://zenn.dev/showm001/articles/2025-06-12-01

https://zenn.dev/kumao/articles/61d2f8bca89eb1

https://dev.classmethod.jp/articles/q-developer-cli-game-cbs/

https://community.aws/content/2vlITBGRfv8slpeU1UlTrpT4bBI/vibe-coding-in-practice-building-a-super-mario-game-with-amazon-q-developer-cli

Install the following on your development PC:

Amazon Q CLI
pygame

After installation, start Q CLI with the q chat command.

% q chat
To learn more about MCP safety, see https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-mcp-security.html


    ⢠⣶⣶⣦⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣤⣶⣿⣿⣿⣶⣦⡀⠀
 ⠀⠀⠀⣾⡿⢻⣿⡆⠀⠀⠀⢀⣄⡄⢀⣠⣤⣤⡀⢀⣠⣤⣤⡀⠀⠀⢀⣠⣤⣤⣤⣄⠀⠀⢀⣤⣤⣤⣤⣤⣤⡀⠀⠀⣀⣤⣤⣤⣀⠀⠀⠀⢠⣤⡀⣀⣤⣤⣄⡀⠀⠀⠀⠀⠀⠀⢠⣿⣿⠋⠀⠀⠀⠙⣿⣿⡆
 ⠀⠀⣼⣿⠇⠀⣿⣿⡄⠀⠀⢸⣿⣿⠛⠉⠻⣿⣿⠛⠉⠛⣿⣿⠀⠀⠘⠛⠉⠉⠻⣿⣧⠀⠈⠛⠛⠛⣻⣿⡿⠀⢀⣾⣿⠛⠉⠻⣿⣷⡀⠀⢸⣿⡟⠛⠉⢻⣿⣷⠀⠀⠀⠀⠀⠀⣼⣿⡏⠀⠀⠀⠀⠀⢸⣿⣿
 ⠀⢰⣿⣿⣤⣤⣼⣿⣷⠀⠀⢸⣿⣿⠀⠀⠀⣿⣿⠀⠀⠀⣿⣿⠀⠀⢀⣴⣶⣶⣶⣿⣿⠀⠀⠀⣠⣾⡿⠋⠀⠀⢸⣿⣿⠀⠀⠀⣿⣿⡇⠀⢸⣿⡇⠀⠀⢸⣿⣿⠀⠀⠀⠀⠀⠀⢹⣿⣇⠀⠀⠀⠀⠀⢸⣿⡿
 ⢀⣿⣿⠋⠉⠉⠉⢻⣿⣇⠀⢸⣿⣿⠀⠀⠀⣿⣿⠀⠀⠀⣿⣿⠀⠀⣿⣿⡀⠀⣠⣿⣿⠀⢀⣴⣿⣋⣀⣀⣀⡀⠘⣿⣿⣄⣀⣠⣿⣿⠃⠀⢸⣿⡇⠀⠀⢸⣿⣿⠀⠀⠀⠀⠀⠀⠈⢿⣿⣦⣀⣀⣀⣴⣿⡿⠃
 ⠚⠛⠋⠀⠀⠀⠀⠘⠛⠛⠀⠘⠛⠛⠀⠀⠀⠛⠛⠀⠀⠀⠛⠛⠀⠀⠙⠻⠿⠟⠋⠛⠛⠀⠘⠛⠛⠛⠛⠛⠛⠃⠀⠈⠛⠿⠿⠿⠛⠁⠀⠀⠘⠛⠃⠀⠀⠘⠛⠛⠀⠀⠀⠀⠀⠀⠀⠀⠙⠛⠿⢿⣿⣿⣋⠀⠀
 ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⠛⠿⢿⡧

╭─────────────────────────────── Did you know? ────────────────────────────────╮
│                                                                              │
│      Set a default model by running q settings chat.defaultModel MODEL.      │
│                          Run /model to learn more.                           │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

/help all commands  •  ctrl + j new lines  •  ctrl + s fuzzy search
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🤖 You are chatting with claude-3.7-sonnet

> /model

✔ Select a model for this chat session · claude-4-sonnet

 Using claude-4-sonnet

What I Made

When thinking about what to create, meteorite drop and colony drop came to mind.
Influenced by a certain anime that peaks on Tuesday late nights in June 2025... So, a shooting game where you shoot down falling objects from the ground?

I started Q CLI and gave the following instructions:

地球に落下してくる物体をレーザー砲を発射して、破壊するゲームを作ります。
プレイヤーは、地球連邦軍のガーディアン部隊の隊員です。
地上に向かって落下してくる物体をレーザー砲を操作して破壊するミッションを日々行なっています。
レーザー砲は、左右で移動、スペースキーで発射します。
落下してくる物体は以下の物体があり、それぞれに耐久度と報酬が設定されています。
耐久度はその物体を破壊するためにレーザー砲を何発当てる必要があるかの数値です。
報酬はその物体を破壊するもらえるスコアです。破壊するたびにスコアがプラスされていきます。
物体が地上に落下すると、その物体のポイントでスコアがマイナスされていきます。
スコアがマイナス10000になるとゲームオーバーです。
落下してくる物体は以下です。左から、名前,耐久度,報酬になります。
壊れた衛星,1,10
火球,1,20
UFO,1,50
スペースプレーン,1,-10000
UFO母艦,10,100
スペースコロニー,20,1000
小惑星,50,10000

1回のゲームは120秒間で終了します。
UFO母艦、スペースコロニー、小惑星は最後の30秒から出現させてください。

ただし、スコアが-10000になるとその時点でゲームオーバーです。
ゲームはguradianというディレクトリの中に作ってください。

(Sorry Japanese Only.)

The basic game was completed with these instructions. Surprisingly, it took about 3 hours to finish development.

The completed game screen looks like this.
As you can see from the repository, it consists of just one HTML and one JavaScript file.

(Forgetting to take a screenshot during development was a big mistake.)

The basic gameplay involves shooting down objects falling from space (top) with a laser cannon from the ground (bottom).
The laser cannon is tricolor, which is an homage to a certain anime (I specifically instructed to make the laser cannon tricolor).

Various Updates

As I mentioned earlier, something close to completion was made initially, but upon trying it out, I found various points for improvement, which I then instructed to be improved.
Even when I gave vague instructions, it properly responded with "I'll do this," which I thought was really amazing.
Sometimes errors occurred, but it recovered properly, and I was truly impressed, thinking, This is seriously amazing.

For example, there are final boss-like objects such as the UFO mothership, space colony (influenced by a certain anime), and asteroids (also influenced by a certain anime).
However, they were falling at the same size and speed as the others, so I thought I'd increase their size and adjust their falling speed.
I gave instructions like this:

> UFO母艦、スペースコロニー、小惑星はサイズを4倍にして、他に比べて1/4のスピードで落下するようにしてください。
UFO母艦、スペースコロニー、小惑星のサイズを4倍にし、落下速度を1/4にして、より迫力のある強敵にします。

〜中略〜

修正が完了しました！🚀

## 🔄 変更内容

### 大型敵の強化
• **サイズ**: 4倍に拡大
  • UFO母艦: 50px → 200px
  • スペースコロニー: 60px → 240px  
  • 小惑星: 80px → 320px

• **落下速度**: 1/4に減速
  • 通常敵: 1-3px/フレーム
  • 大型敵: 0.25-0.75px/フレーム

### ゲームバランスの調整
• **出現制限**: 大型敵がいる時は同時出現数を1体に制限
• **視覚効果**: 大型敵に影と光るエフェクトを追加
• **HP表示**: 大型敵のHP数値を明確に表示

### 戦略性の向上
1. 時間管理: 大型敵は時間をかけて倒す必要がある
2. 位置取り: 巨大なサイズで回避が困難
3. 集中攻撃: 高耐久力で連続攻撃が必要
4. リスク管理: 大型敵出現時は他の敵が出にくい

### 視覚的インパクト
• **迫力**: 巨大なサイズで圧倒的な存在感
• **エフェクト**: 影と光で立体感を演出
• **情報表示**: HP数値で戦況を把握しやすく

これで、最後の30秒に出現する大型敵が真の脅威となり、ゲームのクライマックスがより緊張感のあるものになりました！大型敵は画面の大部分を占めるため、プレイヤーは慎重な位置取りと集中的な攻撃が求められます。

(Sorry Japanese Only.)

With these instructions, I made them gigantic to give a final boss feel.

As an aside, I asked to make the space colony circular, like the so-called O'Neill cylinder type space colony.

> スペースコロニーを円形にして、アイコンもシリンダーっぽいものにしてください。
スペースコロニーを円形にして、シリンダーっぽいアイコンに変更します。

〜中略〜

 ⋮ 
 ● Completed in 0.0s
スペースコロニーの円形デザインが完成しました！🏭

## 🔄 変更内容

### 視覚的変更
• **形状**: 四角形 → 円形
• **アイコン**: 🏗️ → 🏭（シリンダーっぽい工場アイコン）
• **グラデーション**: 中心が白く、外側に向かって黄色のグラデーション
• **枠線**: 黄色の円形枠線で強調

### 技術的改善
• **描画**: arc() を使用した円形描画
• **影効果**: 円形の影エフェクト
• **当たり判定**: 円と点の距離計算による正確な当たり判定

### デザインの特徴
1. シリンダー効果: 放射状グラデーションで立体感を演出
2. 工業的外観: 🏭アイコンで宇宙コロニーの工業施設感を表現
3. 視認性: 円形で他の四角い敵との区別が明確
4. リアリズム: 実際のスペースコロニー（O'Neill型）に近い円筒形

### ゲームプレイへの影響
• **当たり判定**: より正確な円形当たり判定
• **視覚的識別**: 独特な形状で瞬時に識別可能
• **戦略性**: 円形のため角を狙う戦術が不要
• **美観**: より宇宙的で未来的な外観

### 宇宙コロニーの表現
• **O'Neill型**: 円筒形の回転する宇宙居住施設
• **工業施設**: 🏭で製造・居住複合施設を表現
• **規模感**: 240pxの大きさで巨大構造物を演出

これで、スペースコロニーがより現実的で視覚的に魅力的な円形デザインになりました！宇宙空間に浮かぶ巨大な円筒形居住施設として、ゲームの世界観がより豊かになります。

(Sorry Japanese Only.)

I didn't specifically mention it, but I was a bit moved when it came out with Realism: Close to an actual space colony (O'Neill type) cylindrical shape.

Conclusion

I completed it for now and committed it to GitHub. The README files were created based on the resources generated by Q CLI.

https://github.com/Kenichiro-Wada/amazon-q-developer-games/tree/main/guardian

"By the way, it says Multilingual support (7 languages), but while the in-game explanations have been changed, the surrounding descriptions and such remain the same, so it's in a half-done state."

Example of French notation

By the way, even if you exit with /quit, you can resume by giving instructions like this:

> 地球防衛ゲーム「ガーディアン」を改良しようと思います。
地球防衛ゲーム「ガーディアン」の改良について、まずは現在のプロジェクト構造を確認させてください。


🛠️  Using tool: fs_read (trusted)
 ⋮ 
 ● Reading directory: . with maximum depth of 0
 ⋮ 
 ● Completed in 0.0s
guardianディレクトリがありますね。その中身を確認してみましょう。


🛠️  Using tool: fs_read (trusted)
 ⋮ 
 ● Reading directory: ./guardian with maximum depth of 0
 ⋮ 
 ● Completed in 0.0s
ガーディアンゲームのファイル構成が確認できました。どのような改良を考えていますか？

現在のゲームの状況を把握するために、まずはREADMEファイルを確認してみましょう：


🛠️  Using tool: fs_read (trusted)
 ⋮ 
 ● Reading file: ./guardian/README_jp.md, all lines
 ⋮ 
 ● Completed in 0.0s
現在のゲームの状況がよく分かりました。どのような改良を考えていますか？例えば：

• **新しい敵の種類**を追加
• **パワーアップシステム**の実装
• **効果音や音楽**の追加
• **新しいゲームモード**の追加
• **ビジュアルエフェクト**の強化
• **モバイル対応**の改善
• **リーダーボード機能**の追加

具体的にどの部分を改良したいか教えてください。現在のゲームコードも確認して、最適な改良方法を提案します。

(Sorry Japanese Only.)

Well, that's convenient.

How to Play

To play the game, you can check out the following repository and open guardian/index.html in your browser to start playing.
(Confirmed to work in Google Chrome.)

https://github.com/Kenichiro-Wada/amazon-q-developer-games/

As mentioned before, the author is not good at shooting games, so I can't get a very high score, but I think skilled players could achieve quite high scores.
(Note: Spaceplanes are allies, so don't shoot them down)

Impressions

When I first came up with the idea, I had a rough image of what it would be like, but I was surprised that something close to it, including the UI, was created in the initial stage.

Just by giving instructions to Q CLI, I didn't write any code, including the README. The points to be modified in the code were shown each time, so I could see how it was changed by looking at them (though I can't call it confirmation), but I was really just watching.

Amazon Q Developer is truly amazing.

This was a great experience, and I plan to continue practicing Vibe Coding in the future.

Feel free to check out the repository and try the game. Enjoy!

Lambda's loop detection after it became compatible with loops triggered by S3.

Kenichiro Wada — Sun, 22 Dec 2024 13:59:04 +0000

Regarding the detection and stopping of Lambda loops introduced in 2023, in October 2024, the long-awaited (I think) detection and stopping of loops with S3 triggers has been supported!

https://aws.amazon.com/jp/about-aws/whats-new/2024/10/aws-lambda-detects-stops-recursive-loops-lambda-s3/

During the 2023 update, I wrote verification articles in the following post.

https://dev.to/aws-builders/i-created-a-lambda-loop-detection-verification-environment-with-aws-cdk-and-verified-it-5883

As a continuation of that, or rather, since S3 triggers were not a target for detection and stopping at that time, and I wrote that I would be happy if they were updated in the future,I re-verified the S3 triggers after the update. (Two months late... sorry)
I will also update the past articles later.

https://dev.to/aws-builders/i-created-a-lambda-loop-detection-verification-environment-with-aws-cdk-and-verified-it-5883

For the runtime of the verification Lambda, I am using the one I created last time.

https://github.com/Kenichiro-Wada/aws-lambda-recursion-detection

It works as is, but the following have been addressed:

Updates to various modules,
Node.js runtime version upgrade (v18 -> v22)
Added a 5-second wait in the internal process (to prevent it from stopping immediately)
Updated README (mentioning detection and stopping)

Verification of Loop Detection and Notification with S3 Trigger

The verification of detection was done with the following configuration.
To confirm that it was okay, I also checked other detection patterns, but since there were no particular changes in behavior, I will omit them.
If you are interested, please refer to the previous article.

The result is... it stops properly (well, it has to stop, right? lol)

It has also been executed 16 times according to the metrics.

Before the update, it looked like this. ※From the previous verification.

Searching for messages output within Lambda in Cloudwatch Logs showed 16 entries, indicating that it was limited to 16 executions.

The metric for detection and stopping is "Recursive invocations dropped" and one stop has been recorded.

Notifications are also displayed on the AWS Health Dashboard as usual.

Additional Verification Needed

In this loop case, there is no flow to trigger a notification, so I think it might be possible to notify by setting a DLQ for Lambda.
I will try a slightly modified version of the flow. Also, I will additionally verify what happens when S3 and SQS are combined and update the article.

What Not to Forget (I Write This Every Time)

Although the long-awaited implementation for S3 triggers has been made, as I mentioned in a previous article, even though it has been implemented, we should not rely on it.
To begin with,
we should avoid loops.
I will not forget this. With S3 support, I think all cases that might cause an infinite loop have been addressed, but I still believe that avoiding loops in the first place is the most important.

In Case of Intentional Looping...

In cases where looping is intentional, stopping at 16 times becomes a problem, so in such cases,it seems that it can be disabled using the PutFunctionRecursionConfig API.
(I think it used to be raising a support case...) I might try it later...

The End

Detection & stopping is just a guardrail, I think (it's also mentioned in the guide).
As mentioned above, unless it's intentional,
it's important to avoid loops in the first place, and I will be careful not to do so.

This article is being translated from Japanese to English using Amazon Bedrock and Amazon Nova Pro.
Additionally, the title image is being generated using Amazon Bedrock and Amazon Nova Canvas.

Using Amazon EventBridge Pipes to build an AWS CDK stack to launch ECS Tasks

Kenichiro Wada — Fri, 12 Jan 2024 04:12:01 +0000

A year late, I touched Amazon EventBridge Pipes,
I made this for verification purposes, using Amazon EventBridge Pipes to launch an ECS Task.

I'm a newbie to ECS, so this is the first time for me to make it properly.

Why I made it.

I'm a person who usually uses AWS Lambda to build things,
I usually use AWS Lambda to create various things, but for my work, I had to create a heavy process (batch, yes...) which is a case where containers would be the best choice. I was asked to create a heavy process (batch, yes...).

How do we start the ECS Task?

After finishing the development of the application locally, we started to consider what kind of configuration we should use. And then we started to consider,
The problem was how to start the ECS Task.
The way to do it is,

Call AWS Lambda from SQS to launch ECS Task
ECS Task triggered by Step Functions

In terms of processing, we decided to use SQS triggers. And then, we decided to use SQS to AWS Lambda to launch ECS Task,
Then I thought, Call AWS Lambda from SQS and launch ECS Task?
But I thought that it would be a bit odd to call Lambda just for the purpose of launching the task (my favorite AWS service is AWS Lambda!)... I was thinking..,
I found out that I can use Amazon EventBridge Pipes to launch ECS Tasks, so I decided to build it using Amazon EventBridge Pipes (sorry for being a year late).
I also decided to build it with AWS CDK v2.

About Amazon EventBridge Pipes

Learn more about Amazon EventBridge Pipes.

https://aws.amazon.com/eventbridge/pipes/

Created this time

The following is available to the public.

https://github.com/Kenichiro-Wada/cdk-eventbridge-pipes-ecs-tasks

The required items, etc. are listed in the README.
AWS CDK operation is confirmed with Cloud9 as of 2023/12/21.

In building it, we refer to the following site.

https://dev.to/aws-heroes/aws-cdkv2-stack-for-building-amazon-eventbridge-pipes-sqs-to-cloudwatch-logs-52n9

https://dev.classmethod.jp/articles/cdk-ecs-ecr/
(Sorry, Japanese Only)

We would like to take this opportunity to thank you!

A cautionary tale if you try to run it.

The sample code, needs to be rewritten in two places, please make the changes after checkout.

About VPC

In this requirement, there is a requirement to use an existing VPC, so the sample also specifies the ID, etc. of the existing VPC and imports and uses the information of a Public subnet. (Public Subnet is not in the requirement, but the sample is set to Public.)
Please change the VPC ID to match your environment.

If you want to create a new VPC together..., please refer to the official documentation.

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.Vpc.html

You can create a NAT Gateway by specifying the name and CIDR, but you need to be careful about this because it will create a NAT Gateway for each AZ.
If you want to launch the container itself on a private subnet, you will need a NAT Gateway (NAT instance) or VPC endpoint.

https://zenn.dev/yoshinori_satoh/articles/ecs-fargate-vpc-endpoint
(Sorry Japanese only)

Notes on exporting Pipes logs to Cloudwatch Logs

I am including this because there was an update in November 2023 to support log output to Cloudwatch Logs, etc.

https://aws.amazon.com/about-aws/whats-new/2023/11/amazon-eventbridge-logging-improved-observability/

When I first made it, I got an error, what? Not supported? I threw an issue in a mad rush, but it was nothing, I was using an older version of Typo and aws-cdk-lib, so be careful with Typo. And I'm really sorry.

I've just solved the problem and set it up,
The level is set to Optional in the PipeLogConfigurationProperty, but even if it is not specified, it does not cause an error in the cdk diff, but it causes an error at runtime.

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_pipes.CfnPipe.PipeLogConfigurationProperty.html

Since it is already specified on the sample code, it should not be an error.

I am waiting for Pipes to support L2 for now, because I hope it will set this area well even if it is not set in L2...

Summary

Since the beginning of 2023, I had been thinking that I had to try it! I finally got to try a service I've been meaning to try since the beginning of 2023.

EventBridge Pipes, it's quite useful. I didn't try the filter and enhancement this time, but I will try it when I get a chance.
I would also like to connect other processes.

As for the containers, this is the first time I've touched them properly except for the ones I inherited,
On the other hand, it is quite fun. On the other hand, there are still many things I don't understand, so I would like to continue my study.

At any rate, based on the verification results, I have finished building a batch (yes, it's a batch) that is necessary for business and am testing it to great acclaim. I am sure it will work.

Special Thanks

I created a Lambda loop detection verification environment with AWS CDK and verified it.

Kenichiro Wada — Wed, 20 Sep 2023 13:24:12 +0000

Nice to meet you!
I'm Kenichiro Wada, one of the AWS Comunity Builders in Japan.

This is my first post here.
I hope you will read it, even though it is a rambling article.

This article is a compilation of the following two published in Japanese.

https://zenn.dev/keni_w/articles/acbfd69a2c7dbb

https://zenn.dev/keni_w/articles/ef6e8d39bb055f

I tried "Detecting and stopping recursive loops in AWS Lambda functions" which appeared last month.

AWS Lambda now detects and stops recursive loops in Lambda functions

Those who have looped with Lambda in the past (including me) thought it was a surprise and were slightly disappointed (see "What to Expect in the Future"),
But when I actually tried it, I was impressed because it stopped properly.

For details on how it works, please click here.

Detecting and stopping recursive loops in AWS Lambda functions

However, in the article that I tried to verify, others have already written about it, so I started by building a verification environment using the AWS CDK.

Build a verification environment with AWS CDK

The created resources are available on Github.

https://github.com/Kenichiro-Wada/aws-lambda-recursion-detection

As mentioned in the README,
The following verification environment will be deployed.

Loops in Amazon SQS With Dead Letter Queue
Looping with Amazon SQS Without Dead Letter Queue

Looping with Amazon SNS

Pattern combining Amazon SNS and Amazon SQS

Pattern Combining Amazon SQS and AWS Lambda

Looping with Amazon SQS and AWS Lambda in a Beaded Pattern

Looping with Amazon S3 (this is a bonus)

We prepared two types of Amazon SQS because we wanted to know if the behavior changes depending on whether DLQ is used or not.

As for Amazon S3, it is not included in this project, so it is a complete bonus.
This one does not detect and stop when it is running,

If left unchecked, it will continue to run forever, so be sure to stop it!

The code for the Lambda function was generated by ChatGPT (no charge).
I am someone who has not yet mastered Amazon CodeWhisperer yet. I will try harder.

Verified.

My honest impression is, oh, it properly stops at 16 runs.
The invoke metrics also confirm that it stops at 16 runs.

I tried to display it in console.log in Cloudwatch Log to search for messages and get them out,
For the execution, 16 messages are displayed.

(I should have used the TAIL function.)

Email notifications and Health Dashboard notifications did not appear until about 3 hours later.
Below is the Health Dashboard notification.
The ones that were close to the execution time were guided together.
(Sorry for my Japanese.)

If you want to do this as soon as possible...,
Set up a DLQ and use SQS triggers to notify errors (this is also the case),
(This is also the case.) If you can detect that the system has entered the DLQ, you may be able to notice it as soon as possible. I think so.
I'm sending an email in the case of a DLQ in SQS this time.

In the case of the SQS loop with and without DLQ, the behavior did not change,
In the case of the SQS loop without DLQ, if I left the loop as it was, I received an email and a Health Dashboard message the next day or later.
This is the loop processing (without DLQ) information email received on 2023/08/07 that was executed on 2023/08/05.

It is interesting that it changes with or without DLQ.
I think it is recommended to have a DLQ available when using Queue, so I am guessing that the notification will not appear continuously, as it is not even a recommended setting to begin with, plus don't let it loop.

The extra S3 trigger, though,
When I run it, it looks like this. (Even the person who created it was nervous when moving it.)
I stopped it after about a minute, but still, it was executed 27 times.

This one is not subject to detection, so if you try it,
Please stop it as soon as you run it!

About Amazon SQS and AWS Lambda beaded pattern

I wondered if the following pattern would also stop, and verified it, although the pattern was not specifically stated in the official statement.

(This is an excerpt from a slide, so it is only in Japanese. Sorry.)

At the beginning of the verification, I thought that this case would not be detected and stopped...,
It stopped and stopped properly.

This is the Invocations metric for a Lambda function executed in a Pythagorean switch pattern.
This one also stopped after 16 times. (I was really thrilled...)

You can try this one with the "Loop with Amazon SQS and AWS Lambda in a beaded pattern" mentioned above.

I think this time the mechanism is supposed to detect by entering the same Queue or something else in succession, so I'm thinking it would be no good if it goes through something else.

What to Expect in the Future

I think it would be a very effective mechanism in a configuration using SQS/SNS.

But I've had it happen in the past, too,
I've had several people comment on it,
I think Lambda loops are often triggered by S3 triggers like the following.

※This is a Loop pattern that I have caused in the past.
(This is also extracted from a slide, so it is only in Japanese. Sorry.)

So,
I want it implemented in S3 triggers!
I have come to the conclusion that this is a good idea.
I wonder if it will be difficult... But I hope so.

Don't forget.

One thing to remember. The ability to detect and stop loop execution is only an auxiliary function (last resort).
What we should not forget is,
I think we need to be careful to avoid loops.

In the pattern we were verifying, hey, it's not a loop, is it? I had to review it,
I think it is necessary to construct the process in such a way that it does not become a loop (unless it is intentional).

In addition, it seems that the support case needs to be raised for cases where loops are intentionally created.

Finally.

Sample published on github, S3 trigger case,
If you try it, please stop it immediately after it starts!
If you get charged for it, it's your fault for not stopping it, and we are not responsible for it.
It's all over README.md!

We will continue to implement Event processing to avoid being indebted to this function as much as possible.