033-ses-gs: requires real email verification (cannot be non-interactive)

Open
#78 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
aws
Domain
cloud

Research direction

Review README and REVISION-HISTORY.md alongside the SES sandbox constraints described in the issue. Decide which of the four listed options the tutorial should adopt; done means the chosen handling is documented and the tutorial’s non-interactive expectations match it.

Written by the indexing model from the issue text.

Description

Problem

SES in sandbox mode requires real email verification via inbox click. The read prompts that wait for verification are intentional — there is no API to auto-verify.

Current state

  • Removed from non-interactive PR
  • Documented in REVISION-HISTORY.md

Options

  1. Accept that this tutorial requires human interaction (document in README)
  2. Move SES out of sandbox (requires support case)
  3. Use SES v2 API with email identity verification via DNS (no inbox click needed)
  4. Skip the verification steps and only test the non-verification parts
Dominant language
Shell
Stars
176
Forks
43
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/sample-developer-tutorials

All issues in aws-samples/sample-developer-tutorials

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.