gemstone-nexus · Phase 6
DOC-AWS-SMS-Recovery
Metadata
| id | doc_id | title | category | source_path | summary | content_hash | indexed_at |
|---|---|---|---|---|---|---|---|
| 4 | DOC-AWS-SMS-RECOVERY | DOC-AWS-SMS-Recovery | reference | DevResources/docs/DOC-AWS-SMS-Recovery.md | Agent “text me” uses **Amazon SNS SMS**. The account is still in the **SNS SMS sandbox**. Destination `+14193063078` is stuck **Pending** (OTP never completed). US carriers often filter SNS sandbox short-code OTPs. **Delete/recreate of that sandbox number is blocked for 24h after create** — do not keep resending doomed OTPs to the same number. | b607e823d17035102c3ad26624dda9951f19470b | 2026-07-22 18:33:18 |
Content
# DOC-AWS-SMS-Recovery **Account:** `209457336992` · **Region:** `us-east-1` · **Updated:** 2026-07-22 **Policy:** Never Twilio. Prefer SES email notify until SMS production path works. Do not take down `gemstone.dataright.net`. ## Root cause (why SMS lingered) Agent “text me” uses **Amazon SNS SMS**. The account is still in the **SNS SMS sandbox**. Destination `+14193063078` is stuck **Pending** (OTP never completed). US carriers often filter SNS sandbox short-code OTPs. **Delete/recreate of that sandbox number is blocked for 24h after create** — do not keep resending doomed OTPs to the same number. Parallel path **AWS End User Messaging (EUM) toll-free** `+18447531062` is **PENDING** because registration `registration-19835bd2d54e4914893a45181f098dd3` (`US_TOLL_FREE_REGISTRATION`) is **REQUIRES_UPDATES** after denied **v3**. **SES email notify works** (verified recipients include `mfuriate@nex-tech.biz`, `mfuriate@gmail.com`). Use email until SMS is fixed. ## EUM denial (exact) | Version | Status | Reason | |---------|--------|--------| | v1 | DENIED | Missing conditional field | | v2 | DENIED | Missing required field | | v3 | DENIED | **Business Registration Document Required** | | v4 | **DRAFT** (opened 2026-07-22) | Not submitted — waiting on Mark | ### v3 denial (carrier) > Your company identification number could not be independently verified by the carrier. To resolve this, upload an official business registration document (such as Articles of Incorporation, Certificate of Formation, or equivalent government-issued document) in the **Business Registration Document** field of the Company Info section, or update your company identification number if it was entered incorrectly. After making your changes, resubmit your registration. Docs: [Registering your toll-free number](https://docs.aws.amazon.com/sms-voice/latest/userguide/registrations-tfn-register.html) ### Field gaps vs what AWS wants | Field path | Status on denied v3 / draft v4 | Action | |------------|--------------------------------|--------| | `companyInfo.businessRegistrationDoc` | **Missing** (required by denial) | Mark uploads PDF/PNG/JPEG Articles / Certificate of Formation | | `companyInfo.taxId` | **Missing** (never successfully set; v1 had empty/denied) | Mark sets correct EIN | | `companyInfo.taxIdAuthority` | **Missing** | Set `EIN` | | `companyInfo.taxIdCountry` | **Missing** | Set `US` | | `companyInfo.businessType` | Was `SOLE_PROPRIETOR` on v3 (wrong for LLC) | **Fixed on draft v4 → `PRIVATE_PROFIT`** | | Company / contact / use-case / samples / opt-in image | Present on draft v4 (restored from v3) | Review; tweak only if inaccurate | **CLI cannot finish resubmit** without Mark’s EIN and business registration document file. Do not invent tax IDs or upload placeholder docs. ### Draft v4 (agent prep done) - Registration ID: `registration-19835bd2d54e4914893a45181f098dd3` - Toll-free phone ID: `phone-c8c26941520647f8ad840e9a54c1c589` (`+18447531062`, PENDING) - Opt-in attachment already uploaded: `attachment-9c98f8e16ee748e4ab8c47bbc76518ea` After Mark supplies EIN + registration PDF: ```powershell # Upload doc (example paths — Mark provides file) aws pinpoint-sms-voice-v2 create-registration-attachment --region us-east-1 --attachment-body fileb://C:\path\to\CertificateOfFormation.pdf # Then put fields (use returned attachment id; never echo taxId in chat logs) aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxIdAuthority --select-choices EIN --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxIdCountry --text-value US --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.taxId --text-value "<EIN>" --region us-east-1 aws pinpoint-sms-voice-v2 put-registration-field-value --registration-id registration-19835bd2d54e4914893a45181f098dd3 --field-path companyInfo.businessRegistrationDoc --registration-attachment-id attachment-XXXXXXXX --region us-east-1 aws pinpoint-sms-voice-v2 submit-registration-version --registration-id registration-19835bd2d54e4914893a45181f098dd3 --region us-east-1 ``` Or complete the same fields in console: **AWS End User Messaging → Configurations → Registrations** → open the REQUIRES_UPDATES registration → edit draft → submit. ## SNS sandbox → production - `get-sms-sandbox-account-status` → `IsInSandbox: true` - Sandbox destination `+14193063078` → **Pending**; opt-out **false** - There is **no CLI** to exit the SMS sandbox. Support API requires Premium Support (not enabled). Console creates the case. ### Console path (Mark) 1. https://console.aws.amazon.com/sns/v3/home?region=us-east-1#/mobile/text-messaging 2. Under **Account information** → **Exit SMS sandbox** (opens Support / Service quota increase). 3. Form answers for **DataRight agent alerts** (transactional, low volume): | Field | Recommended answer | |-------|-------------------| | Service | SNS Text Messaging | | Website / app | https://dataright.net (OmniFlowCRM / DataRight agent status alerts) | | Message type | **Transactional** (not promotional) | | Region | **us-east-1** | | Countries | United States | | Opt-in | Internal operator (Mark) explicitly requests SMS notify for agent/job completion; not marketing blast; STOP/HELP supported where applicable | | Message templates | `DataRight: Ready — <short status one-liner>` / `DataRight agent: <blocker one-liner>` | | Use case detail | Low-volume transactional alerts from Cursor/DataRight ops agents to an authenticated operator phone; expected volume tens–low hundreds SMS/month | | New limit | Request production access / raise monthly SMS spend as needed | **Note:** AWS docs also expect at least one **Verified** sandbox destination and a successful test SMS before approval. With `+141******3078` stuck Pending, either wait out delete cooldown and re-verify, or add a **second** sandbox number Mark provides (agent must not invent a number). ### Related quota (submitted 2026-07-22) - Service Quotas request **SMS Message Spending in USD** `L-BCD4AAF3`: **$1 → $10**, status **CASE_OPENED**, case `178473400100660`. - This raises spend ceiling; it is **not** the same as exiting the SMS sandbox. Mark still must run **Exit SMS sandbox** in console. ## Delivery logging (done 2026-07-22) Enabled SNS SMS delivery status → CloudWatch Logs: - IAM role: `arn:aws:iam::209457336992:role/SNSSuccessFeedback` - Attributes: `DeliveryStatusIAMRole` set; `DeliveryStatusSuccessSamplingRate=100`; `MonthlySpendLimit=1` (until quota increase approved) Inspect after next SMS attempt: CloudWatch log groups `sns/us-east-1/.../DirectPublishToPhoneNumber` (success/failure). Carriers can delay log appearance up to ~72h. ## Secrets (names only) `DATARIGHT_DEV_SECRETS`: `AWS_EUM`, `AWS_EUM_SMS_NUMBER`, `AWS_EUM_SMS_PHONE_ID`, `AWS_SNS_REGION` (+ `SES_FROM_EMAIL` for email path). Never print values. ## Mark actions (ordered) 1. **Use SES email** for agent notify until SMS works (`mfuriate@nex-tech.biz` / `mfuriate@gmail.com`). 2. **EUM v4:** Provide EIN + official business registration PDF → put `taxId` / `taxIdAuthority=EIN` / `taxIdCountry=US` / `businessRegistrationDoc` → **submit** draft v4. 3. **SNS Exit SMS sandbox** via console form (answers above); optionally reply on spend case `178473400100660`. 4. **Sandbox number:** Do **not** keep OTP-spamming `+141******3078` while delete cooldown blocks reset. After cooldown, delete + recreate **or** give agent a **second** E.164 to verify. 5. After production / verified destination: send one short test SMS; confirm CloudWatch delivery logs. 6. Only then point agent notify / secrets at a working origination path (SNS production and/or registered EUM toll-free). ## Never - Twilio - Print secret values or full tax IDs in chat/logs - Spam SMS / marketing - Treat EUM PENDING toll-free as working agent SMS path - Take down production GemStone hosts for SMS work