Forem: Kosuke ENOMOTO

AWS Security Fundamentals with AWS BuilderCards Security Expansion Pack

Kosuke ENOMOTO — Sun, 30 Nov 2025 15:27:48 +0000

TL;DR

Let’s learn the Security pillar of the AWS Well-Architected Framework by using AWS security services to prepare for mischief caused by threat actors—depicted here as adorable “pet actors”—and the security incidents they trigger.

drawn by @komakichidev

$ whoami

My name is coosuke (Kosuke Enomoto). Some people call me Kosuke, others Koske.

{
    "Name":"Kosuke Enomoto",
    "Bio":"https://linktr.ee/coosuke",
    "Job":"PO of Global CCoE",
    "SNS":[
          {
              "LinkedIn":"https://www.linkedin.com/in/kosuke-enomoto/",
              "X (formerly Twitter)":"@coosuke",
              "mixi2":"@coosuke",
              "Instagram":"@coskenomoto"
          }
      ],
    "Communities":[
        "Organizer, JAWS-UG Chiba Chapter",
        "AWS Community Builder",
        "AWS BuilderCards Japanese Edition Developer"
    ],
    "My Family":[
        "Wife","Black cat(5yo)","Kid(4yo)"
    ],
    "Hobbies":[
        "Sauna","Cooking","Photography"
    ]
}

You can find all my social links here—let’s connect!

https://linktr.ee/coosuke

What This Post Covers (and What It Doesn’t)

This post covers:

Why AWS BuilderCards is awesome
Why the AWS BuilderCards Security Expansion Pack is even more awesome

This post does not cover:

Deep explanations of AWS security services or implementation details
Detailed rules of the BuilderCards base game

Introduction

In this post, I’ll introduce the new AWS BuilderCards Security Expansion Pack, which I contributed translation and localization for the Japanese edition.

At AWS re:Invent 2025 in Las Vegas, the BuilderCards booth is open again this year.

AWS BuilderCards Booth at AWS re:Invent 2025

📍 Location: Caesar’s Forum (alcove, below the escalators)
🕐 Opening Hours:
- Sun, Nov 30 — 10 AM–6 PM
- Mon, Dec 1 — 9 AM–5 PM
- Tue, Dec 2 — 9 AM–5 PM
- Wed, Dec 3 — 9 AM–5 PM
- Thu, Dec 4 — 9 AM–4 PM
Japanese-speaking AWS SAs will be available at the booth!

If you’re attending re:Invent, you may already have visited the booth and picked up the cards. In this article, I’ll introduce the new expansion pack from the perspective of a BuilderCards translator and contributor—who is, admittedly, not a hardcore security expert.

What Is the AWS Well-Architected Framework?

Before diving into the expansion pack, let’s briefly revisit what the AWS Well-Architected Framework is.

AWS Well-Architected Framework

In my view, the Well-Architected Framework is essentially a collection of cloud best practices—guidance that remains universal regardless of company size, team structure, or workload type. While not mandatory, following it leads to higher ROI and more resilient architectures.

(And yes, Google Cloud and Azure also provide their own Well-Architected frameworks. Comparing them is fascinating!)

The Six Pillars of the AWS Well-Architected Framework

Operational Excellence
Security
Reliability
Performance Efficiency
Cost Optimization
Sustainability

This year’s new expansion pack focuses on learning the Security pillar.

The Security Pillar

Before we jump into the cards themselves, let’s briefly walk through what the Security pillar of the AWS Well-Architected Framework actually says.

In the official documentation, it is organized into:

7 security design principles
6 focus areas (best practices)

These form the mental model behind the AWS BuilderCards Security Expansion Pack.

7 Security Design Principles

These principles are high-level guidelines for how to think about cloud security.

Implement a strong identity foundation

Apply the principle of least privilege and enforce separation of duties.

Prefer role-based and temporary credentials instead of long-lived, user-bound access keys.
Enable traceability

Monitor, alert on, and audit all actions and changes in your environment.

Centralize logs and metrics so you can investigate issues in (near) real time.
Apply security at all layers

Don’t rely only on a perimeter firewall.

Use defense in depth across VPCs, subnets, load balancers, instances, operating systems, and applications.
Automate security best practices

Manage security controls as code (IaC) and keep them in version control.

Automation reduces human error and helps you scale securely as your workloads grow.
Protect data in transit and at rest

Classify data by sensitivity, then protect it with encryption, tokenization, and access control.

Consider both live data and backups, as well as internal and external access paths.
Keep people away from data

Minimize direct human access to production data.

Use tools, workflows, and automation so operations can be performed without engineers touching raw data, reducing the risk of mistakes and leaks.
Prepare for security events

Define and document an incident response process.

Regularly run simulations or game days to validate that your detection, investigation, containment, and recovery steps actually work and are fast enough.

6 Focus Areas (Best Practices)

The pillar also breaks security down into concrete implementation categories.

Security Foundations
- Understand the shared responsibility model so you know what AWS secures vs. what you must secure.
- Structure your AWS accounts (for example, multiple accounts per workload) and manage them centrally with services like AWS Organizations.
Identity and Access Management (IAM)
- Manage identities for both humans and machines in a consistent, centralized way.
- Enforce least privilege so every identity only has the permissions it needs, only when it needs them.
Detection
- Turn on services such as AWS CloudTrail (API activity), AWS Config (configuration changes), and Amazon GuardDuty (threat detection).
- Build alerting so the right teams are notified automatically when suspicious activity occurs.
Infrastructure Protection
- Protect your networks using VPCs, security groups, network ACLs, AWS WAF, and related services.
- Protect your compute layer with OS patching, vulnerability scanning, and container security controls.
Data Protection
- Classify data (for example: public, internal, confidential, highly confidential).
- Encrypt data at rest and in transit using services like AWS KMS, and protect backups with the same level of care as production data.
Incident Response
- Prepare: Establish runbooks, playbooks, communication channels, and tools in advance.
- Operate: Use automated playbooks to move quickly from detection to containment and recovery.
- Learn: Run post-incident reviews (post-mortems) and improve your processes and controls based on what you learned.

There is also a cross-cutting area of Application Security, which means:

Building security into the entire software development lifecycle (“shift left”)
Running regular security testing such as SAST/DAST and other application-focused assessment

The Four + One Key Concepts of Security Implementation

After reading the Security Pillar, I believe the essential points of cloud security can be summarized into 4+1:

Access Management — Authentication & authorization based on least privilege
Defense — Multi-layered protection across networks, data, and applications
Detection — Monitoring and logging to identify anomalies
Response — Processes to contain and recover from incidents
Learning — Post-incident reviews and continuous security testing　*This is "+1" because this should be the different aspect than the others 4.

Simulating failures Chaos Engineering–style is valuable—but doing it in production could be career-ending! Even staging environments require careful preparation.

But with AWS BuilderCards, you can simulate this safely—right at the table.

What Is AWS BuilderCards?

AWS BuilderCards is a board-game-style learning tool for the Well-Architected Framework.
There are two categories:

Base game
Expansion packs

Base Game

The base game teaches cloud migration and architecture design using Well-Architected principles. Both 1st and 2nd editions exist—the 2nd edition is available at re:Invent, and amazon.com in some countries!

Expansion Packs

Expansion packs add new learning themes on top of the base game. They cannot be played alone.
Past expansions include:

Generative AI (for 1st edition)
Resilience (for 2nd edition)

This article introduces the Security Expansion Pack, the brand-new expansion.

Another expansion pack, Builder’s Galore, also debuts at re:Invent—a "strong-and-new-game" style experience focused purely on cloud-native architectures.

Why We Created the Japanese Edition

BuilderCards was originally created by David Heidt, Game Tech Solutions Architect at AWS Germany. After it was showcased at re:Invent 2023, AWS Heroes and community members collaborated to localize it into Japanese.

Learn more from AWS Hero Yamaguchi’s article:

楽しみながら学べる AWS BuilderCards の遊び方、そして日本語化に込めた思い *Japanese

Here is my past blog how we localize BuilderCards into Japanese.
AWS BuilderCards Japanese Edition for JAWS DAYS

Learn more from an interview with David-how he inspired BuilderCards, develop and spread it.
The unexpected game designer: how a happy coincidence sparked a popular AWS card game

Learning AWS Security Fundamentals with the Security Expansion Pack

Thanks for reading this far—we’re finally at the main topic!

The Security Expansion Pack is designed around the 4+1 concepts introduced earlier.

Understand Security Threats

Threat actors are represented as “pet actors”—cute animals that “attack” the AWS environment players build.

Polly Packet (Bird) — Network & Infrastructure

As former companion of a network engineer, Polly learned all about protocols by listening to countless troubleshooting calls. Now she uses that knowledge to probe network defenses, repeating packets instead of phrases. Known for saying "Pretty payload!" while launching DDoS attacks. Believes that sometimes you need to overwhelm a network to show its weakness.

Zero-Day Raccoon — Applications & Runtime

Originally started by digging through developers' discarded code printouts in dumpsters, Zero-Day Raccoon discovered a talent for finding vulnerabilities others missed. Works at night, testing applications and leaving behind detailed bug reports along with scattered coffee cups and keyboard crumbs. It's called trash can - not trash can't!

Inside Cat — Data & Databases

Started her career as a data center cat catching mice, but became more interested in catching data instead. Specialized in quietly sitting between systems, proving that if she can intercept the data, so can others. Known for leaving "gifts" of exposed data on doorsteps. Favorite napping spot: Right on top of the most critical servers.

Bad Doggo — Identity & Access Management

After years of watching security guards use weak passwords and share credentials "just this once", Bad Doggo couldn't take it anymore. Originally trained as a security K-9 unit, he now specializes in breaking authentication systems to prove how easily treats... err, threats... can get in. Is it his fault, that humans always trust a friendly face with a wagging tail? His motto: "Who's a bad doggo? I am, but for he right reasons!"

These pet actors represent threats targeting access management and defense, the first two of the 4+1.

Detect & Respond Using AWS Security Services

AWS provides many security services for:

DETECTION — Discovering threats
RESPONSE — Taking corrective action

Both are essential.

The expansion pack includes BuilderCards representing these AWS security services.
Whether a threat is mitigated depends on whether your built architecture includes the relevant security cards.

Example: Pet Actor Mischief – How Detection and Response Change the Outcome

In the Security Expansion Pack, pet actor mischief is triggered when a player buys a Well-Architected Point card during the Cloud-Adoption (purchase) phase.

Event cards include some sections:

Event name
Description
DETECTION
RESPONSE
IMPACT based on whether detection/response conditions are met

If you fail both detection and response → you receive a PWNED card, which deducts one Well-Architected point.

The image above shows an example of a mischief event caused by Polly Packet. In the Security Expansion Pack, these kinds of incidents are represented as Event Cards.

Each Event Card is structured as follows (from top to bottom):

Event name
Event description – what kind of “mischief” is happening
DETECTION
RESPONSE
IMPACT

The most important parts to pay attention to are the bottom three: DETECTION, RESPONSE, and IMPACT.

Earlier, I wrote that in both the real world and in the Security Expansion Pack, resolving a threat (a pet actor’s mischief) requires both detection and response. The card text reflects exactly that: whether you can mitigate the incident depends on whether your built architecture includes the services listed under DETECTION and/or RESPONSE.

Using this Event Card as an example:

To detect this event (DETECTION), you need Amazon CloudWatch.
To respond to this event (RESPONSE), you need any one of the following:
- AWS Shield Advanced
- AWS Network Firewall
- Amazon EventBridge + AWS Lambda

Some notation rules:

A bulleted list under RESPONSE means OR (any one is enough).
A “+” sign means AND (you need those services together).

In other words, whether you have zero, one, or both of DETECTION and RESPONSE implemented will change the outcome described in IMPACT.

Let’s look at the IMPACT section of this Event Card and see what happens when Polly Packet attacks:

❌ If you have neither DETECTION nor RESPONSE

→ You must take 1 PWNED card.
⚠️ If you have only one of DETECTION or RESPONSE (not both)

→ On your next turn, your hand size is reduced to 4 cards (instead of the usual 5).
✅ If you have both DETECTION and RESPONSE

→ You may perform the Cloud-Adoption (purchase) action one more time.

In this way, the game rewards architectures that are designed to both see incidents and act on them.

What Does “PWNED” Mean? And What Is the Penalty?

pwn is a term commonly used in CTF (Capture the Flag) competitions—a category of security challenges where you exploit vulnerabilities in an application or system to “take over” a target and capture a flag.

There’s also another meaning of pwn in online gaming slang: “to beat or dominate someone.”

In either sense, being PWNED means “you got owned” or “you were defeated.”

In the Security Expansion Pack, if you fail to both detect and respond to an event, you receive a PWNED card as a penalty.

Each PWNED card you hold reduces your total Well-Architected Points by 1.
Some events are severe enough that you may have to take 2 PWNED cards at once.

So, as you can imagine, ignoring detection and response is costly—not just in real-world security, but even in this tabletop simulation.

Learn Without Risking Your Real Environment

This corresponds to the final “+1” of the 4+1: learning.

BuilderCards Is Not Just a Game—It’s a Learning Tool

The base game teaches Well-Architected concepts; expansion packs teach deeper technical domains.

For the Security Expansion Pack, I recommend learning foundational AWS security concepts first (Level 200–300).

Resources I personally recommend:

https://dev.classmethod.jp/articles/aws-summit-japan-2024-community-stage-security/

https://business.ntt-east.co.jp/content/cloudsolution/ihcm_column-04.html

https://www.shoeisha.co.jp/book/detail/9784798190853

Security Expansion Pack Rulebook (Japanese)

Created by JAWS-UG Chiba:

https://drive.google.com/file/d/1EZ2A2ixkde1GoalvvUanH7TpTcDhXzI3/view?usp=sharing

Can You Get BuilderCards in Japan?

Short answer: Not on Amazon Japan, but you may receive them at JAWS-UG BuilderCards workshops.

Follow these accounts for event information:

X: @jawsdays
JAWS-UG Event Calendar: https://jaws-ug.jp/calendar/
AWS Community Manager Numaguchi-san’s note: https://note.com/s_numaguchi

Wrap up my 2024 ~Contribute to the Community, and make MIRACLE!~

Kosuke ENOMOTO — Sat, 28 Dec 2024 07:42:05 +0000

TL;DR

This blog encourage you to contribute to the Community you are participating, and your contribution makes miracle to the globe.

$whoami

I am Kosuke, who is an active AWS Community Builder since 2021, is working as a Cloud Architect and PO in the Global CCoE team based in Tokyo, a husband, a friend of a black cat "Komachi" and a father of a 3yo kid.

Click here for my social networks and feel free to connect with me!

Wrap up 2024 as an AWS Community Builder

Here are my contribution to the AWS communities in Japan and in the world.

As one of JAWS-UG Chiba chapter organizers, I co-hosted 6 workshops or meetups this year, 5 out of them were workshops in-person, and the other one was online from Philadelphia, PA during AWS re:Inforce was there.
Published 2 Japanese versions of AWS BuilderCards, the previous one was distributed 200 sets among AWS communities in Japan(JAWS-UG), and the latest one was disclosed at re:Invent 2024 and the distribution is TBD(I WISH IT WILL BE EARLIER 2025!!). See AWS News Blog by Jeff Barr for more detail about the second edition of AWS BuilderCards.
Offered 3 presentations in person, first one was at AWS Summit Japan on June 20, presented together with JAWS-UG Chiba organizers. The second was at AWS Community Day Taiwan on September 28 in Taipei, and the other was at JAWS-UG Tokyo meetup on December 16. Go on to my Speaker Deck to refer my presentations.
Published 7 blog posts regarding AWS related activities of mine, 3 were related to the BuilderCards, others 2 were for JAWS DAYS 2024, and other 1 was for AWS Summit Japan and the last one for AWS CBs. In total I published 10 blog posts and 30 short notes in note.com/coosuke, Qiita.com/coosuke, and sizu.me/coosuke... Except for this article!!

3 most impressive outputs

AWS BuilderCards localization project. This year I dedicated most of my CB activities to this project. Not only translation the card game to Japanese, but I worked together with my folks to enhance learning effectiveness and developer experience through the game experience. Thank you very much folks, especially much appreciated to David Heidt, Shigeru Numaguchi both from AWS, and co-organizers of JAWS-UG Chiba. This project cannot achieve such a miracle as we are at this time without our collaboration and working together.
Throughout the BuilderCards project, I was so fortunate to offer presentations at AWS Summit Japan and AWS Community Day Taiwan, where I spoke our dedicated effort to this project. These 2 were the opportunities I had never have before, as Summit was so big AWS conference in Japan and the others was my first opportunity to present in English. They were challenging but I could have a good time both.
I cannot ignore the impression of my 3rd presentation, that I presented at JAWS-UG Tokyo and I spoke how to be an AWS Community Builder. My slide earned 2.9k PVs in recent 2 weeks, while my blog post regarding the same topic earned over 700 PVs. They are incredible impressions I had never experienced, who are typically earn around 100-200 PVs each output.

Want to make miracle? Apply the CBs program

AWS Community Builders accepts applications from developers once a year, most recently in January. While there are no required criteria to become a CB, your application will be reviewed by AWS to determine if you will be accepted as a new CB member.

Metric your outputs and its impressions, this is what you must do before you apply.

The upcoming application for CB will open on January 6, 2025, as Jason Dunn, the Global AWS CB Program Manager in AWS announced in his LinkedIn post.

Catch up about CBs program? Go on to AWS Community Builders on AWS Websites, set up your AWS Builder ID(IF you do NOT have the one yet), and add your name to the waitlist.

AWS BuilderCards Japanese Edition for JAWS DAYS

Kosuke ENOMOTO — Thu, 29 Feb 2024 16:17:56 +0000

TL;DR

Hi, I would like to introduce AWS BuilderCards and my contribution to produce Japanese edition of the card.

What are AWS BuilderCards?

AWS BuilderCards is a kind of trading card game in general words.

AWS BuilderCards is a fun and educational trading card deck building game designed to teach how different AWS services work together to build well-architected workloads.

Here describes the introduction of BuilderCards.
AWS BuilderCards

Disclaimer

This article focuses on the story of the production of the Japanese version of BuilderCards. You can see many blogs around the world, in your mother tongue, that describe what is the cards and how to play them in detail.
This article is original in Japanese and translated by DeepL.

How we produced the Japanese Edition

Background

The background of the AWS BuilderCards Japanese edition (hereafter referred to as "the Japanese edition") is described in detail in a note by JAWS-UG @jawsdays.

【日本語版登場】AWS BuilderCards 体験コーナーのご紹介 by JAWS-UG Blog

AWS BuilderCards の日本語化を山口(@kinunori)さん、吉江(@typhon666_death)さんが企画し、翻訳作業を山口(@kinunori)さん、榎本さん(@coosuke)が行いました。

翻訳者の山口さんからコメントを頂戴しています。
「日本語化にあたっては AWS BuilderCardsの原作者 David Heidt さんに大きなご支援を頂きました。実際、日本語化したAWS BuilderCardsを日本に届けてくれたのはDavidさんです。ありがとうございました。
そして、Davidさんへ日本語化企画の打診などを対応していただいた AWSコミュニティマネージャーの沼口さん、いつも私たちの活動に協力して下さりありがとうございます。
最後に、参加者のみなさま、ぜひJAWS DAYS 2024会場で AWS BuilderCards を体験してみてください！」

(Translate by DeepL)
AWS BuilderCards was translated into Japanese by Yamaguchi (@kinunori) and Yoshie (@typhon666_death), and translated by Yamaguchi (@kinunori) and Enomoto-san (@coosuke).

The translator, Mr. Yamaguchi, commented on the translation.
We are grateful to David Heidt, the original author of AWS BuilderCards, for his great support in translating the AWS BuilderCards into Japanese. In fact, it was David who delivered the Japanese version of AWS BuilderCards to Japan. Thank you very much.
And to Mr. Numaguchi, AWS Community Manager, who approached David to help us with the Japanese version, thank you very much for always cooperating with us in our activities.
Finally, to all the participants, please try AWS BuilderCards at JAWS DAYS 2024!

My work

Mr. Yamaguchi asked me to help with the translation work. Together with Mr. Yamaguchi and David, the developer of BuilderCards (who lives in Germany and is a Solution Architect at AWS in the gaming field), we mainly worked on the following tasks

Translation of the cards (mainly to check if the Japanese was correct)
Card binding review (checking the appearance of the Japanese text when it is printed on the cards to make sure that there are no errors in the notation, etc.)
Communication with David regarding the above two tasks (in English)

Digest until completion

When I joined the project, the first draft of the Japanese version (version 0.0.1 or so lol) had already been submitted, and I was trying to make sure that the translation from English to Japanese would be consistent with all the cards (47 cards in total, is the number correct?) one by one.
It took 4 days from the participation to this point.

Next, we gave him feedback on the review results and asked him to revise and update the Japanese version for a couple of days. The Japanese version is now up to version 0.1.0 (...let's say! lol) and is handed over to David.

From here, we reviewed the binding created by David, who manufactured the cards. Specifically, I reviewed it from the perspective of whether there had been any line breaks in odd positions in the Japanese, and whether it had been something that could be read smoothly by Japanese people. I repeated this process over and over again.

For example, here is what David's binding (let's call this version 0.1.5) looked like.

And my feedback with the version was,

The horizontal notation is correct, but please turn the letters 90 degrees to the right. As it is, we will have to tilt our heads to the left to read, which I think will stiffen our shoulders lol.

That's how we created version 0.99.99. About 10 days had passed since I joined the project when David told us, "I submitted it successfully! Thank you very much for your help!"

As mentioned in the JAWS-UG's blog introduced at the beginning of this article, the Japanese edition was delivered successfully in Japan at the end of this month.

What we focused on when producing the Japanese version

Localize, not translate, the BuilderCards.

The contents of BuilderCards are broadly classified into three types of cards.

Starter Cards ・・・ Ten cards distributed at the beginning of the game. They have a picture of on-premise systems.
BuilderCards ・・・ Cards with AWS services listed on them. The best part of the game is to buy these cards from the Marketplace and build your AWS architecture.
AWS Well-Architected Card ・・・ Score Card. Ultimately, the player who collects the most points on this card wins.

Of these, the most work time was actually spent translating the starter cards. In contrast, translating the builder cards and the AWS Well-Architected cards were not as difficult a task. It was just a steady cycle of translation, review, revision, binding, review, and revision.

For the purpose of English to Japanese translation, you can use translation services such as DeepL, Google Translate, or more recently ChatGPT to translate and correct English by setting prompts. Many of you who read this blog come into contact with English documents on a regular basis, and I am sure many of you are familiar with these tools (I am one of them!). However, since I was fortunate enough to assist in the production of the Japanese edition, I decided beforehand that I would not simply produce a translation into Japanese, but rather produce cards localized for Japan. This is the reason why I wrote "Japanese edition" instead of "translated (into Japanese) version" in this blog. Then, I turned my attention to the starter cards.

My obsession

If you have played the English version of BuilderCards, you have probably seen some kind of poop written in English on the starter card. I realized that these are actually English proverbs or English versions of so-called "system operations" jokes that, if you read them carefully, can be a bit funny. I looked that it would not be funny to translate these sentences directly into Japanese, so I decided to give the starter card a uniqueness as a Japanese version. From here, the days of searching for a Japanese version of the starter card began.

For example, when there is an English proverb, there may be a corresponding Japanese proverb. In this case, we adopted the Japanese proverb. This solved most of the problems, but there remained a couple of cards that just did not translate well into Japanese. For these, rather than translating them seriously, we dug up sayings that were popular in the Japanese IT community and incorporate them into the starter cards.

We'll let you know what kind of sayings were engraved on the starter cards until the BuilderCards experience corner on the day of JAWS DAYS 2024....

// Detect dark theme var iframe = document.getElementById('tweet-1762501262615187882-699'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1762501262615187882&theme=dark" }

Summary

So, the Japanese version has been successfully completed and will be unveiled at JAWS DAYS 2024 on 2nd of March. I hope you all look forward to the day. If you share your impressions on your SNS, I will be very happy to hear from you.

JAWS DAYS 2024

Build a R&R app with PartyRock and Bedrock!

Kosuke ENOMOTO — Sat, 25 Nov 2023 00:02:39 +0000

TL;DR

You can easily build a Generative AI app with PartyRock!

Intro to Bedrock and PartyRock

Are you a GenAI enthusiast? Do you want to learn it with AWS Bedrock? Yes you are, and you can easily build a generative AI app running on Bedrock. This is PartyRock.

What is Amazon Bedrock?

Amazon Bedrock is generative AI platform provided by AWS as a full-managed-service. This is generally available since September 2023 and provides the capability to build Generative AI on AWS.
Here is an announcement from AWS.
Amazon Bedrock Is Now Generally Available – Build and Scale Generative AI Applications with Foundation Models

And What is PartyRock?

PartyRock.aws is also provided by AWS. You can build a mini app, share with friends, experiment and learn all about prompt engineering.
Build AI apps with PartyRock and Amazon Bedrock

Let's build a Rock'n Roll app with PartyRock

As you can see, both Bedrock and PartyRock include the phrase "ROCK". And I love Rock music. My duty is to build an app something relates to ROCK...

So I decided to build an app that recommends the rock music per your input. Let's start.

Sign up

First, go on to PartyRock.aws. Click "Sign in" on your right-top.

You can sign up PartyRock account with your social, Google, Apple or Amazon. No AWS account is required in case you just want to use PartyRock.

Signed up! And you can set up your username, gio information, and submit.

Build an app in seconds

After you succeeded to sign up, go back to the top, and then click "Build your own app". You can see the app builder. Fill the description with 2-3 sentences just like the screenshot. I would like to build a recommendation app so I typed "Rock Recommendation App recommends users the rock music with YouTube link".
ARE YOU READY? Then click "Generate app".

After a while, not so long! it was just a minute later, you will see your app!! Input your favor in Input field and the app recommends you a couple of rock music.

Enjoy your app!!

Play the app

Now you can see your app, let's play!!

I made a prompt like this,

Could you please recommend a couple of metal music? I am so busy recently due to both my business and private, and feel a bit got tired. I would like to listen to metal that cheers me up. 

# Condition
- Verify YouTube link is correct, validated and the streaming is available
- The more up beat, the more I can cheer me up!

And here is the output from my app.

Here are a couple upbeat metal songs that may help lift your spirits:

Song: "Thunderstruck" by AC/DC Artist: AC/DC Link: https://www.youtube.com/watch?v=v2AC41dglnM

This classic hard rock song by AC/DC is pure fun and energy from start to finish. Brian Johnson's vocals and the guitars will have your head banging and stress melting away. AC/DC always knows how to lift your mood with their catchy, no nonsense rockers.

Song: "You Give Love a Bad Name" by Bon Jovi Artist: Bon Jovi Link: https://www.youtube.com/watch?v=KrZHPOeOxQQ

One of the most iconic arena rock anthems ever, "You Give Love a Bad Name" by Bon Jovi is guaranteed to get your blood pumping. From the opening riff to the singalong chorus, it's simply a blast to listen to. Jon Bon Jovi's charismatic performance and the band's signature sound make it the perfect high energy pick me up.

I chose upbeat, classic hard rock/metal songs from iconic bands that should provide an endorphin boost to help lift your spirits during your busy time. Let me know if you'd like any other recommendations!

Very good, they recommended 2 rock!
Click the thumbnails, and you can go on to YouTube.

"Thunderstruck" by AC/DC
"You Give Love a Bad Name" by Bon Jovi

Share your app with friends

Yes, you can share your own app with friends! Here is the procedure.

You can see "Make public and Share" on your right-top. Yes, you can just click there.

Your app is now public! Click "Copy link to clipboard, and share the link with friends.

Where Rock Recommendation App?

Here you go!! Enjoy Rock Music!!
Rock Recommender by Kosuke

I will publish another blog when I update the app...

Thank you very much for reading, here is my social account.
LinkTree - coosuke

AWS APAC Community Summit 2022 -From the Serverless Perspective-

Kosuke ENOMOTO — Sun, 09 Oct 2022 03:58:26 +0000

TL;DR

This is a blog report for my attendance to AWS APAC Community Summit 2022 hosted by AWS between Sep. 14th and 16th in Bangkok, Thailand.

$ whoami

Hello! Thank you for visiting my blog! I'm Kosuke from Japan, who is a Product Owner of IoT platform in a water and housing product manufacturer.
My SNS list is here -> Linktree and please feel free to follow me!

What is AWS APAC Community Summit?

AWS APAC Community Summit is hosted by Amazon Web Services, and for AWS influencers from APACJ region such as

AWS Heroes
AWS Community Builders
Leaders from AWS User Groups
AWS Alliances

I hear AWS hosted the APAC regional community leader summit several times before COVID-19 but the summit was the first in-person and APAC regional summit after COVID.

I was invited the summit as one of the Community Builders so I went to Bangkok and attend it.

Serverless & Containers Feedback Session

The summit was sooooo impressive as I posted in LinkedIn,

Kosuke Enomoto on LinkedIn: I am pleased I could attend to AWS APAC Community Summit here in Bangkok…

I am pleased I could attend to AWS APAC Community Summit here in Bangkok, Thailand. Hard to express my emotion in a short sentence but these 2 days conference…

linkedin.com

and it is too hard for me to pick up one or two sessions...
However I am a Serverless Community Builder, so I decided to focus on the sessions regarding Serverless.

In Day 1, I joined a breakout session that was called Serverless & Containers Feedback Session and 3 lightening talks and panel discussion delivered.

Build better with Step Functions with SDK integrations by Jones

The first talk was delivered by Jones Zachariah Noel from India who is a Serverless Community Builder. His talk focused on Step Functions with SDK Integrations.

Why SDK Integrations?

How to implement the integrations

From his talk I learned that Step Functions with SDK integrations makes us more productive and efficient.

How our team embraced EventBridge for our event-driven serverless architecture by Raphael

The second talk was delivered by Raphael Jambalos who is also a Serverless Community Builder from Philippines. His talk focused on EventBridge and how he converted from a monolith application on EC2 to microservices with EventBridge.

Customer Painpoint

Scenario

He brought throughout the talk that

How he worked on decoupling to microservices and building event-driven(serverless) architecture
What issues occurred and how he resolved them
- Payload too big
- Destination unreachable
- Steps must be done sequentially

Serverless Web Hosting Strategy For Modern Front-end Application by Takahiro

The third talk was delivered by Takahiro Horike who is a Serverless Hero from Japan.
// Detect dark theme var iframe = document.getElementById('tweet-1570281011610791936-657'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1570281011610791936&theme=dark" }

Single Page Application has changed front-end landscape

Evolution never stops!

First he mentioned that Single Page Application, Server-Side Rendering and Static Site Generation has been the game-changer on front-end strategy. And he also mentioned the key consideration to follow Well-Architected Framework as follows;

Grasping the front-end design pattern(SPA, SSR, SSG etc)
CI/CD workflow and optimization that fit the design pattern
Leveraging managed service for efficient infrastructure

To satisfy the consideration he explained some options

Load balancing and virtual machines (EC2 or Fargate)
Serverless (S3 bucket, API Gateway + Lambda or CloudFront)
built-in CI/CD workflow solutions (Amplify Hosting or App Runner)
Full-stack develop environment (Amplify Studio)

And he concluded that with leveraging AWS serverless platform like them we could maximize our work efficiently.

Panel Discussion

Then 3 presenters joined the panel discussion hosted by @FarrahC32 and @donnieprakoso from AWS.
The interesting fact is... // Detect dark theme var iframe = document.getElementById('tweet-1570286314590969857-846'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1570286314590969857&theme=dark" }

Anyway, the panel discussion was so impressive!

Serverless - past, present and future - by Kameda-san

In the same day, @kameoncloud who is a Senior Evangelist in AWS Japan delivered another Serverless session.

He presented the history of back-end of AWS serverless architecture... How it was architected in the past, how it is improved at the present.
Here are the remarks;

AWS Lambda is born in 2014
- Event = S3, Kinesis and DynamoDB only
- Up to 1GB memories, 5mins duration, 25 invocations
- Lambda worker were running on EC2 instances
Improvement
- Nitro System = Nitro Controller + Nitro Hypervisor(light-weighted KVM)
- Nitro System could run w/o EC2 instances, Containers
- Firecracker = fast to launch micro VMs
- Cold Start will become faster
- Relational Database access - VPC
- AWS Hyperplane and V2N(VPC to VPC NAT) made true Lambda access to RDB
Who will invoke Lambda function?
- Synchronous : API Gateway
- Asynchronous : Just put event (put object into S3, DynamoDB) to internal queue
- Event Source Mapping : Synchronous under the hood
- Dynamic resource allocation(Lambda) vs Stateful(Fargate)

// Detect dark theme var iframe = document.getElementById('tweet-1570321077733322756-341'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1570321077733322756&theme=dark" }
// Detect dark theme var iframe = document.getElementById('tweet-1570321834343813121-81'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1570321834343813121&theme=dark" }

Conclusion

All the serverless session were AWeSome. I am a Serverless Community Builder as well but not familiar with Step Functions and EventBridge. I was lucky to listen to the experience regarding those services. And 2 Japanese talks were also impressive. I had tons of lessons learned from those sessions.

Oh do you want to see more about the summit?
OK, go on to the tweet gathering #AWSCommunityAPAC

AWS APAC Community Summit - Togetter [トゥギャッター]

2022年にタイで開催されたAWS APAC Community Summit のタグまとめです

togetter.com

P.S.

日本語の振り返り記事は、別途執筆中で後日公開予定です。

Let's say "Hello World" with Lambda Function URLs

Kosuke ENOMOTO — Thu, 07 Apr 2022 20:17:34 +0000

TL;DR

Briefly tested Lambda Function URLs that AWS announced yesterday.

Introduction

Hi everyone! I am Kosuke who is working as a Product Owner based in Japan and one of the members of AWS Community Builders for Serverless.

My SNS are;

Twitter -> @coosuke
LinkedIn -> Kosuke Enomoto
Blog(Japanese) -> note

What is "Lambda Function URLs" ?

On Apr/06/2022 AWS announced a new feature that makes it easier to invoke functions through an HTTPS endpoint as a built-in capability of the AWS Lambda service. You can see details at AWS blog.
Announcing AWS Lambda Function URLs: Built-in HTTPS Endpoints for Single-Function Microservices

Let's say hello with Lambda Function URLs!!

I briefly tested that new feature within a half hours.
Here are the procedures.

Log on to AWS Console and go on to AWS Lambda > Functions.
Click "create function" on the upper right.
Choose "Author from scratch"
name the Function name(helloWorldUrlTest), choose Runtime(Node.js 14.x) and Architecture(x86_64). Permission can stay as default(as chosen Create a new role with basic Lambda permissions).
Open Advanced settings, check Enable function URL and you will see some more settings, Auth type to NONE and check Configure cross-origin resource sharing(CORS).
Click Create function button on the bottom.
Here you created the function!
You can see the function URL. Click it and you will see "Hello from Lambda!" That's it!

Closing remarks

It took only just a few minutes to see "Hello world" in the browser.
The codes just returns simple JSON including HTTP status code 200 and body "Hello from Lambda!".

{
  "statusCode": 200,
  "body": "\"Hello from Lambda!\""
}

The AWS blog offers sample codes to deep dive into the function URLs feature, so you just build and test it!

Thank you very much for reading! See you next time!!

Can Amazon Connect integrate to EventBridge and SNS?

Kosuke ENOMOTO — Wed, 15 Sep 2021 09:15:53 +0000

TL;DR

I am wondering if Amazon Connect could integrate with Amazon EventBridge, Step Functions, and Short Notification Service (SNS).

Who am I?

Hi, My name is Kosuke and I work as a product owner of an Internet of Thing (IoT) product at a manufacturing firm based in Tokyo. I also start to work recently as a second job, as a Cloud engineer.
My recent interests are AWS, serverless, IoT, and Product Management.

Twitter --> @coosuke
LinkedIn --> kosuke-enomoto

What do you build?

As a Cloud engineer, I am considering building an automated telephone system / answering machine using AWS Serverless services such as Amazon Connect, Amazon EventBridge, Step Functions, and Short Notification Service (SNS).

Here is the wishlist of what the customer wants

[Must] Build the Answering Machine, Notification, Recording, and Transcription

If somebody calls the phone number of the customer, then Amazon Connect acts as an answering machine.
Amazon Connect records the voice mail from somebody who is calling and store it on a bucket in S3.
Amazon Connect notifies the customer that somebody calls, which uses EventBridge, SNS, and Chatbot connecting to Slack.
EventBridge calls Amazon Transcribe to transcript the voice mail. (It might need to use Lambda)
The customer can review the voice mail or the transcription later on their device

[Should / Nice to have] Build the automated telephone system

Conditional branch works as the caller pushes during the call

I would describe the [MUST] cases later.

Why do you build?

To provide an automated answering machine system so that the customer could reduce the workload to address with an anonymous call

How do you build?

Here is the overview of this architecture. Please note that this is a very rough architecture and there might be some misunderstandings because I am NOW studying Amazon Connect!!

Here are my assumptions for each step.

If somebody calls the phone number of the customer, then Amazon Connect works as an answering machine.

This is a first step and a simple process because I have to set up the instance and phone number on Amazon Connect.

Amazon Connect records the voice mail from somebody who is calling and store it on a bucket in S3.

This is on the 2nd floor. Amazon Connect can record the call in itself and I shall transfer the record to the S3 bucket for further process.

Amazon Connect notifies the customer that somebody calls, which uses EventBridge, SNS, and Chatbot connecting to Slack.

3rd floor. Amazon Connect can integrate with EventBridge and I shall do it so to avoid coding. I concern if this could come true because I am not sure of any reference regarding this process...

EventBridge calls Amazon Transcribe to transcript the voice mail. (It might need to use Lambda)

EventBridge or Step Functions calls a lambda function to trigger Amazon Transcribe and transcript the recordings.

The customer can review the voice mail or the transcription later on their device

OK, I am almost reaching the goal but I need to build so that the customer could review the recordings or the transcription.

Any Concern?

I have read some references in Japanese to build a similar environment but I am still not sure if we can build the notification from Amazon Connect to Slack via EventBridge, SNS, and Chatbot.
Any feedback or comments are welcome! Thank you for reading this article!!

AWS Community Buildersへの道アウトプットせよ、されば開かれん How to become an AWS Community Builder in Nihongo(Japanese)

Kosuke ENOMOTO — Wed, 25 Aug 2021 13:33:37 +0000

TL;DR

This article describes "How to become an AWS Community Builder" for Japanese speakers in Nihongo.
For English speakers, please refer to an original article

この記事は、 How to become an AWS Community Builderの日本語版です。

How to become an AWS Community Builder

Stephen Sennett for AWS Community Builders ・ Aug 17 '21

#aws #career #cloud

はじめに

はじめまして。エノモトです。
AWS Community Builderとして、dev.toに初めて投稿しました。
普段は東京に本社がある製造業で、IoTを活用した新規事業開発をミッションとしている部門の、プロダクトオーナーをしています。

私のSNSは以下です。フォローしていただけますと、ピョンピョン喜びます。

Twitter: @coosuke
LinkedIn: kosuke-enomoto
Blog: note: COOSUKE

今日はAWS Community Buildersというプログラムを紹介したいと思います。

AWS Community Builders is 何？

皆さんはご存知でしょうか？
AWS Community Buildersは、Amazon Web Servicesがグローバルで提供している、AWSエンジニア向けのプログラムで、AWSの開発チーム、AWS Heroesや世界中のエンジニアとのネットワーキングだったり、AWSから技術面でのサポートやメンタリングが利用できます。

Throughout the program, subject matter experts will provide mentorship and share insights, including information about the latest services, as well as best practices for creating technical content, increasing reach, and sharing AWS knowledge across online and in-person communities.

AWS Community Buildersへ参加するには？

年に2回、応募を受け付けているようです。

2023年2回目となるCommunity Builders公募開始！

2023年になりまして2回目の公募が、受付開始となりました。
〆切は、2023/7/13 23:59(米国太平洋時間)です。日本時間ですと、翌7/14 15:59頃が〆切となります。
2023年2回目の応募フォームはこちら → Link

AWS Community Buildersへの参加資格はあるの？

明確な参加資格はありません。ただし、応募フォームの中で、これまでにAWSコミュニティへどれだけ貢献したか、を問われる質問があります。

AWSコミュニティへ貢献って何すればいいの？

コミュニティへ貢献… と書くと少し大事に捉えられる方もいらっしゃるかもしれません。
では、具体的に何で貢献すればいいか？！ですが、大きく分けると2つです

AWSコミュニティへ参加する
ひたすらアウトプットする

AWSコミュニティへ参加する

まず、AWSコミュニティへ参加することが、はじめの一歩となります。
日本国内であれば、

AWS Japanが提供するセミナーやTechブログなどの各種コンテンツ
国内のAWSユーザーコミュニティ

が主なAWSコミュニティで、毎週のように何かしらの活動が展開されています。
コミュニティに参加することで、継続してAWSの最新情報をインプットし続ける習慣をつけましょう。

ここでは、後者のAWSユーザーコミュニティについて詳しく記述します。
日本国内には、

などが有名なAWSユーザーコミュニティとして活動されています。これらのコミュニティはSNSで積極的に情報提供しているので、SNSをフォローしたり、コミュニティが主催されるミートアップに参加することが肝心です。

私の場合は、JAWS-UGを中心に活動していますので、JAWS-UGを中心に説明します。
JAWS-UGは全国各地に約70の支部が活動しており、私はX-Tech JAWSやJAWS-UG 千葉支部という2つのJAWS-UG支部の運営をお手伝いしつつ、他のJAWS-UG支部のミートアップにも参加させて頂いたりしています。
JAWS-UGのミートアップの情報は、JAWS-UGのツイッター(@jawsdays)や、AWS Japanでコミュニティプログラムマネージャーをご担当されている沼口さんの note:「JAWS-UG活動のまとめ」などを、フォローされると良いと思います。

ひたすらアウトプットする

日本には「参加することに意義がある」という名言(?)があります。
もちろん、仕事やプライベートの合間に、こうしたコミュニティへ参加されること自体、とても尊いことだと思います。

しかしながら、一方で、日本のITコミュニティでは、「アウトプットしないのは知的な便秘」であるという言葉もあります。

出典：ssmjp

つまり、コミュニティに参加することで得たインプットを、アウトプットとして他者へ情報拡散することを通じて、自らもまたインフルエンサーとしてコミュニティに貢献することこそが、コミュニティに参加すること以上に、尊ばれることなのです。

アウトプットする方法はたくさんあります。

Twitterでつぶやく

最も手っ取り早くアウトプットする方法は、Twitterでつぶやくことです。JAWS-UGに限らず多くのコミュニティでは、ハッシュタグを用いて積極的に情報拡散することを推奨されていることが多くなりました。
またAWSに限らず、多くのコミュニティがTwitterで情報発信されているので、Twitterはインプットの場であり、同時にアウトプットの場であると考えます。

ブログにまとめる

次に、ブログでアウトプットする方法もあります。
私の場合はnoteでブログを書いていて、自分が運営しているミートアップの開催レポートだけではなく、参加したミートアップのメモもブログに残して、読み返すこともあります。
ちなみに私のブログはこちらです → note|coosuke

登壇する

コミュニティや、あるいは業務の中で得られたインプットや成果を、ミートアップに登壇して発表するのも、有効はアウトプット手段です。
私は登壇した数はそれほど多くはないですが、過去のスライドはSlideshareに公開してあります。

ミートアップやコミュニティを運営する

これは自分がアウトプットするというよりも、アウトプットする場を提供する、ということです。
私の場合は、上述したJAWS-UG支部の運営に加えて、昨年9月にJAWS-UGが開催した24時間イベントである「JAWS SONIC & MIDNIGHT JAWS 2020」や「JAWS DAYS 2021」の実行委員としても活動して、ミートアップを運営する側も経験しました。

まとめ

いかがでしたでしょうか。AWS Community Builderへの道は、まずはコミュニティに参加することから始まります。そして、参加するだけではなく積極的にアウトプットを拡散していきましょう。
コミュニティに参加すれば、人生は変わります。
次は、あなたの人生が変わるのを、楽しみに見守っております。