Skip to content

Frequently asked questions

Yes: the missions were made for that, and steps 1 to 3 of each one work without an account. Create the account only when you want to go further.

Use the interactive menu. If you are still unsure, start with A bill without surprises: the spending alert is useful before anything else.

In missions 1 and 2, no: you just copy commands and edit some text. Mission 3 uses a 3-line Python function, and understanding the error is the goal.

The one you already have. The prompts work in any assistant. In Kiro and other IDEs, you can connect the kit so the AI guides you.

The steps without an account are free. In the account, regular Budgets have no cost, CloudShell has no additional cost, and Lambda and Amplify have a free tier for a test this size. Check your own account, because values and plans change. Each mission lists its sources, with the date they were checked.

No. It warns you, but it does not turn anything off. If an email arrives, look at the bill right away.

Run the commands in the Cleanup section of the mission. They can be run at any time. Then look at the Billing console to check.

Delete the resource first and open a case with AWS Support, explaining what happened. The result cannot be guaranteed, but it is the official path.

Because the value is in what you tested and saw, and a model did not run that test. Also, you are responsible for the text: you need to be able to explain every claim.

To ask questions, understand errors, compare options and review clarity and organization. If it helped, say how in the article.

Great, and checking is still worth it. In the real examples, the AI got a lot right. You only know that because you checked.

They may be out of date. Ask for the source, open the link and check the date. Treat a number without a source as a hypothesis.

Do not paste keys, passwords, account IDs, or personal or customer data. Use made-up data, like the data in the missions, or remove anything sensitive.

The AI asked for my access key. What do I do?

Section titled “The AI asked for my access key. What do I do?”

Do not hand it over. No mission needs it: you run the commands in your own CloudShell session.

Avoid it day to day. Create your own user and turn on MFA following the IAM documentation.

That is part of the mission. Paste the error into the AI with the tutoring prompt from mission 3, read it and write it down in your evidence log.

The identity you are using does not have that permission. Check with aws sts get-caller-identity and ask the AI to explain which permission is missing, without widening access blindly.

My Amplify site shows “Access Denied”.

Section titled “My Amplify site shows “Access Denied”.”

Almost always, you zipped the folder instead of its contents. Create the .zip with index.html at the root.

Open a report. It is the most useful contribution right now.

Independent community project by Fernando Azevedo, AWS Community Builder. Not official AWS material, and not endorsed by AWS. AWS and related names are trademarks of Amazon.com, Inc. or its affiliates. MIT license.