Thai-incorporated startups now sit on top of a domestic AWS region — ap-southeast-7 (Bangkok) launched in 2025 — with ap-southeast-1 (Singapore) at roughly 30ms as the long-standing fallback for services not yet present in Bangkok. The Activate credit stack is unchanged in eligibility mechanics, but the Thai context reshapes how applications are scoped: PDPC supervision under PDPA Thailand (2019), BOT (Bank of Thailand) supervision for fintech, NIA (National Innovation Agency) signal substituting for tier-1 venture capital where it is absent, and Thai-language Bedrock POCs that anchor consistently at the upper end of the inference-funding range. This page covers every credit pool a Thai startup qualifies for in 2026, the ap-southeast-7 region mechanics, the BOT and PDPC regulatory builds that fund Build for Startups, and the typical $100K–$150K stack for a Thai Series-A.
The AWS Activate program is globally identical in its eligibility mechanics — the credit tracks, the partner-filing path, the Portfolio funding signal requirement. What changes in Thailand is the shape of the institutional capital base, the role of corporate venture relative to independent venture, the way the "Thailand 4.0" national strategy interacts with NIA credibility signaling, and the very recent arrival of ap-southeast-7 as a domestic region that changes the regulatory-residency calculus.
The Thai institutional venture base is materially smaller and more corporate-concentrated than the Singapore base 30ms away. Independent venture firms operate in Thailand — 500 TukTuks is the most active by deal count, with cohorts dating to 2015 — but the deeper capital pools sit inside corporate venture arms. Beacon Venture Capital (Kasikornbank), AddVentures by SCG (Siam Cement Group), KASIKORN Investment, Krungsri Finnovate (Krungsri / Bank of Ayudhya), AIS-D Venture Capital (AIS / Advanced Info Service), Bualuang Ventures (Bangkok Bank), True Digital (True Corporation), and InVent (Intouch Holdings) collectively deploy more Series-A and Series-B capital into Thai startups than the independent venture firms do. For AWS Portfolio applications, corporate VC vouches carry the same eligibility weight as independent venture vouches — reviewers do not down-weight CVC backing. The strategic implication for a Thai founder: a Beacon Venture Capital or Krungsri Finnovate vouch is functionally equivalent to a 500 TukTuks vouch on the Portfolio gate.
NIA (National Innovation Agency) is the central government innovation body and operates the "Thailand 4.0" program — the national strategy launched in 2016 to move Thailand from a middle-income manufacturing economy toward a value-added innovation economy through deep-tech, biotech, agritech, smart electronics, and digital-services sectors. NIA recognition — through the Startup Thailand network, the Innovation Hub program, or NIA-backed grant tracks — sits as a credibility signal in AWS partner-filed credit applications. The pattern is parallel to DPIIT recognition in India and EDB / Enterprise Singapore engagement in Singapore: not a substitute for institutional venture capital at the Portfolio tier, but a meaningful credibility uplift at the partner-filed Founders tier and a useful supplementary signal in the Build for Startups scoping narrative.
The Thai government supports the startup ecosystem through several adjacent programs alongside NIA: depa (Digital Economy Promotion Agency) operates digital-economy-focused grants and Smart City initiatives; the Board of Investment (BOI) offers tax holidays and import duty exemptions for qualifying startups including specific incentives for digital and software development companies; the Eastern Economic Corridor (EEC) framework provides regional tax and visa benefits for startups operating in the EEC provinces (Chonburi, Rayong, Chachoengsao). For AWS credit applications, BOI tax status and EEC engagement do not directly affect credit gating but appear in partner-filed application narratives as supplementary context that anchors the operational seriousness of the entity.
The shape of Thai startup AWS spend differs from regional peers. A Thai Series-A B2B SaaS company typically runs USD $3K–$9K/month of AWS spend (~THB 105K–315K), slightly lower than the Singapore equivalent because the Thai cost base for engineering talent is lower and engineering teams tend to be smaller at equivalent revenue scale. A Thai Series-A fintech runs USD $6K–$14K/month (~THB 210K–490K) due to regulatory infrastructure overhead. A $100K Portfolio pool covers roughly 11–28 months of runway at this burn — comfortably within the 12-month initial validity window with room to extend through the Bedrock POC 24-month validity layer.
A consequence of the four factors: Thailand is a market where the partner-filed full stack ($100K–$150K) is reachable but not as automatic as Singapore. The corporate venture concentration means Portfolio applications need to clearly cite the CVC vouch and the corporate venture's direct AWS engagement path; NIA recognition opens the partner-filed Founders track to startups still pre-Series-A; and the recently-arrived ap-southeast-7 region creates new architectural options that earlier reference material does not yet cover. The strategically right play for most Thai Series-A founders is to file the full partner-filed stack — Portfolio + Build for Startups + Bedrock POC — rather than defaulting to the self-serve $5K tier surfaced in the AWS Activate console.
AWS announced the Asia Pacific (Bangkok) region — ap-southeast-7 — in 2022 and launched in 2025. For Thai-incorporated startups, the region calculus changed materially with the launch: workloads previously defaulting to ap-southeast-1 (Singapore) at ~30ms RTT from Bangkok can now run primary in ap-southeast-7 at sub-2ms RTT for Bangkok users. The catch in 2026 is service catalog parity: ap-southeast-7 carries a narrower service catalog than ap-southeast-1 and will continue to converge over the next 12–24 months.
ap-southeast-7 (Bangkok) as of mid-2026 carries the mainstream service catalog necessary for most general-purpose workloads: EC2 across the M, C, R, T, and I instance families (the P, Inf, and Trn ML accelerator families are partial or absent); RDS with PostgreSQL, MySQL, MariaDB (Aurora MySQL and PostgreSQL are available; Oracle and SQL Server are not at launch); ElastiCache for Redis and Memcached; Lambda; ECS, EKS, and Fargate; App Runner; S3 with Object Lock; DynamoDB; SQS, SNS, EventBridge; Step Functions; the core security primitives including IAM, KMS with customer-managed keys, CloudTrail, CloudWatch with X-Ray and ADOT, GuardDuty, Inspector, Security Hub, and AWS Config; AWS Backup; and the data migration tooling (DMS, DataSync, Snowball). Bedrock in ap-southeast-7 carries a partial model catalog: Anthropic Claude Haiku 3 and 3.5, Amazon Titan Text and Embeddings, Amazon Nova Lite and Nova Micro are present; Claude Sonnet 3.5 and 4, Llama 3.1 and 3.3, and Mistral Large 2 are not yet in Bangkok as of the May 2026 review. Bedrock Agents and Bedrock Knowledge Bases are not available in ap-southeast-7; OpenSearch Serverless is not available; SageMaker Studio is available but with a reduced instance-family selection. Workloads requiring the absent services need to run those components in ap-southeast-1 (Singapore) with cross-region traffic patterns documented in the credit application.
ap-southeast-1 (Singapore) remains the regional service-complete hub for SEA workloads and the natural fallback for Thai workloads on the unsupported services in Bangkok. ap-southeast-1 carries the full Bedrock model catalog (Claude Sonnet, Llama 3.3, Mistral Large, Nova, Titan), Bedrock Agents and Knowledge Bases, OpenSearch Serverless, the full ML accelerator family, and the broader specialized services. Cross-region traffic from ap-southeast-7 to ap-southeast-1 runs at ~28–34ms RTT in mid-2026, with established AWS backbone routing on the Bangkok-Singapore path.
Latency profile from major Thai metros to each region: Bangkok users see sub-2ms RTT to ap-southeast-7 and ~28–34ms to ap-southeast-1; users in suburban Bangkok and the broader BMR (Bangkok Metropolitan Region — Pathum Thani, Nonthaburi, Samut Prakan) see ~3–7ms to ap-southeast-7 and ~30–36ms to ap-southeast-1; Chiang Mai users see ~12–18ms to ap-southeast-7 and ~38–46ms to ap-southeast-1; Chiang Rai users see ~16–22ms to ap-southeast-7 and ~42–50ms to ap-southeast-1; Phuket users see ~14–20ms to ap-southeast-7 and ~32–40ms to ap-southeast-1; Hat Yai (deep south) users see ~18–24ms to ap-southeast-7 and ~22–28ms to ap-southeast-1 (the south of Thailand is geographically closer to Singapore than to Bangkok and the latency reflects this); Khon Kaen and Udon Thani users see ~14–20ms to ap-southeast-7 and ~38–44ms to ap-southeast-1; Pattaya users see ~5–10ms to ap-southeast-7 and ~30–36ms to ap-southeast-1. For workloads serving a primarily Thai user base, ap-southeast-7 is now the unambiguous primary on latency grounds — the service-catalog gap is the only constraint.
For cross-border SEA reach from a Bangkok primary: ap-southeast-1 (Singapore) at ~28–34ms, ap-southeast-3 (Jakarta) at ~32–40ms, ap-northeast-1 (Tokyo) at ~92–105ms, ap-south-1 (Mumbai) at ~88–98ms. CloudFront edge locations within Thailand are deployed in Bangkok (multiple) and Chiang Mai; static-content delivery from CloudFront is region-agnostic and typically lands sub-15ms for Thai metro users. CloudFront cache miss origins falling back to ap-southeast-7 add the minimal regional latency on the miss path; for workloads primarily serving the Thai user base, the operational target for CloudFront cache hit ratio is 88–92% on dynamic SaaS and above 95% for content-heavy workloads.
For workloads requiring multi-region resilience and disaster recovery, the natural Thai pairing is ap-southeast-7 primary with ap-southeast-1 (Singapore) as the DR target — the cross-region RTT is low, the AWS backbone path is stable, and the service catalog at ap-southeast-1 fully covers anything available in Bangkok. Some Thai fintech entities under BOT supervision elect to pair instead with ap-southeast-2 (Sydney) for regulatory-distant DR — both work, with the choice driven by operational team distribution rather than technical considerations.
CloudRoute's working defaults for Thai applications in mid-2026: for any Thai-incorporated SaaS or fintech workload primarily serving Thai customers, default to ap-southeast-7 (Bangkok) as the primary region with ap-southeast-1 (Singapore) as the fallback for the AI inference tier (Claude Sonnet, Mistral Large) and any other unsupported services (Bedrock Agents, Bedrock Knowledge Bases, OpenSearch Serverless). This split-region pattern is the dominant Thai architecture as the Bangkok region matures. Document the architectural split explicitly in the credit application narrative so reviewers understand the cross-region pattern.
For Thai-incorporated workloads with cross-border customers in Vietnam, Indonesia, the Philippines, or elsewhere in SEA, default to ap-southeast-7 for the Thai data residency layer (PDPA Thailand classified personal data) and ap-southeast-1 for the regional API tier serving cross-border users — this minimizes latency for the SEA neighbor markets while preserving Thai data residency. Cross-region replication patterns document the data flow for the PDPA audit trail.
For BOT-supervised fintechs specifically, the architectural posture typically requires the regulated payment-system data path to remain in Thailand — meaning ap-southeast-7 as the primary store for the payment data layer. The BOT IT Notice (more on this below) is not a strict data-localization mandate in the same sense as the RBI Storage of Payment System Data circular in India, but the BOT supervisory expectation for resilience and incident response strongly favors a domestic primary region. Pair ap-southeast-7 with ap-southeast-1 for DR, document the regulatory boundary in the credit application, and the Build for Startups scope frames cleanly.
Credits land in your AWS account independent of region — they apply to consumption across any region. The region choice does not affect the credit balance, only the operational latency, service availability, and the regulatory data-residency posture for your specific customer mix.
The Activate program tracks are globally identical in eligibility mechanics. The Thailand-specific framing is in how each track maps to the corporate venture vouching pattern, the BOT and PDPC regulatory scope, and the Thai-language and cross-border SEA Bedrock use cases that anchor the AI track funding.
A Thai founder reading this for the first time should know: the AWS Activate console surfaces only the $5K self-serve Founders tier. Everything above that — partner-filed Founders through Activate Portfolio, Build for Startups, and Bedrock POC funding — is gated to partner submission via the ACE (APN Customer Engagements) program or to VC submission via the AWS Portfolio Sub-Program. CloudRoute's routing handles the partner-filed path; many of the Thai corporate venture arms (Beacon Venture Capital, Krungsri Finnovate, AddVentures by SCG, AIS-D, Bualuang Ventures) have direct AWS engagement at the parent corporation level that can supplement the partner-filed path through joint VC + partner attestation.
Use case in Thailand: pre-seed and early-seed companies before institutional Series-A capital arrives, NIA-recognized startups, depa-supported deep-tech startups, True Digital Park resident companies, KX (Knowledge Exchange for Innovation) cohort graduates, and bootstrapped Thai SaaS startups that have not yet raised institutional rounds.
Coverage: $5K floor (self-serve, available directly through the AWS Activate console), $25K ceiling (partner-filed via ACE).
Timeline: 12–16 days from partner ACE submission. Slightly faster for NIA-recognized companies because the reviewer-side credibility signal is documented through the partner narrative.
Common Thai pattern: a Bangkok-incorporated B2B SaaS startup running on a mix of DigitalOcean and self-hosted Thai data center infrastructure (some Thai startups still use the legacy True IDC, CAT Telecom, or 3BB IDC colocation patterns), with founders coming out of the True Digital Park ecosystem, raised a THB 20M–60M ($570K–$1.7M USD at ~THB 35/USD) seed round, ready to migrate to a production AWS posture on ap-southeast-7. The partner-filed Founders track lands at $20K–$25K with the NIA and depa vouches cited in the ACE record.
Use case in Thailand: seed-with-institutional-VC or Series-A companies where the funding signal is clear. 500 TukTuks-backed, Beacon Venture Capital-backed, AddVentures by SCG-backed, KASIKORN Investment-backed, Krungsri Finnovate-backed, AIS-D-backed, Bualuang Ventures-backed, True Digital Ventures-backed, InVent-backed, and Peak XV-backed companies all qualify on funding signal alone. Cross-border investment from Singapore-anchored VCs (Peak XV, Lightspeed SEA, Insignia, Wavemaker, Jungle) into Thai entities is increasingly common and also qualifies.
Coverage: $50K–$75K typical for Thai seed with institutional VC; $75K–$100K typical for Thai Series-A. The Thai Portfolio award skews slightly lower than the Singapore equivalent because projected AWS spend at typical Thai burn rates ($3K–$9K/month for B2B SaaS) supports the $75K–$100K range cleanly within the 12-month validity window without leaving meaningful surplus.
Timeline: 14–22 days partner-filed; 12–32 days VC-filed depending on VC operational responsiveness. Thai corporate venture operations teams (Beacon, AddVentures, Krungsri Finnovate, AIS-D) typically respond on a 10–18 day cadence; 500 TukTuks operations runs on the global 500 Global timeline of 5–10 days.
Validity: 12 months from issue on the initial Portfolio award; the Bedrock POC layer typically carries a 24-month validity that extends the effective burndown horizon.
Common Thai pattern: Bangkok-incorporated Series-A B2B fintech serving Thai SMEs with a cross-border arm extending into Vietnam and the Philippines, raised THB 350M–700M ($10M–$20M USD) led by Beacon Venture Capital with 500 TukTuks and Krungsri Finnovate participation. Projected AWS spend THB 280K–490K/month ($8K–$14K USD). Portfolio approves at $100K with the Beacon vouch cited; the cross-border expansion narrative supports the upper-end approval.
Use case in Thailand: the canonical Thai Build for Startups workload is a BOT-aligned regulatory build for fintech — implementing the BOT IT Risk Management notice technical controls, the Payment Systems Act 2017 controls expected of licensed payment institutions, or the operational resilience controls for digital lending license holders under the BOT Digital Lending framework. For non-fintech workloads, PDPA Thailand cross-border transfer scaffolding, PDPC-aligned data subject rights infrastructure, migration-from-third-party-host engagements (off legacy Thai IDC infrastructure or off DigitalOcean / Linode / Vultr regional VPS), and the architecture work for BOI-qualifying digital-services tax-status companies are the other dominant scoping anchors.
Other Thailand-relevant Build for Startups scenarios: implementing the technical controls expected for SEC Thailand digital asset license holders (the Securities and Exchange Commission Thailand supervises the Thai digital asset and crypto perimeter); building Thai + English + cross-border SEA-language inference pipelines on Bedrock + SageMaker for regional customer-service automation; implementing the technical controls for OIC (Office of Insurance Commission) insurtech licensing; migrating from legacy Thai-IDC-hosted infrastructure to production AWS as a discrete project; and building the NIA Innovation Hub-recognized deep-tech infrastructure scope where applicable.
Coverage: $25K. Validity 12 months. Stacks with Portfolio without conflict when the scope is distinct — reviewers approve Portfolio + Build for Startups when the two records describe non-overlapping workloads. "Portfolio funds the SaaS infrastructure broadly; Build for Startups funds the BOT IT Risk Management implementation specifically." Same-workload double-files get downgraded; non-overlapping files approve cleanly.
What works in Thailand specifically: Build for Startups applications that explicitly cite BOT IT Risk Management Notice sections, the Payment Systems Act 2017, PDPA Thailand sections 26–29 (cross-border transfers), or the SEC Thailand digital asset technical control framework tend to approve at the $25K ceiling rather than the mid-range. The named-regime specificity is what reviewers anchor against; vague "Thai compliance work" framing lands lower in the $10K–$15K range.
Use case in Thailand: Bedrock POCs that anchor consistently at the upper end of the range scope around Thai-language inference (Thai is a tonal language with a distinct script and well-documented model-evaluation difficulties — POCs scoped around Thai-language fluency, sentiment, and intent recognition demonstrate substantive evaluation work) or cross-border SEA inference (Thai + Vietnamese + Bahasa Indonesia + Tagalog evaluation for cross-border e-commerce or customer service). The canonical Thai Bedrock POC: a customer-service automation product that handles Thai and English for the domestic Thai customer base and adds Vietnamese, Bahasa Indonesia, and Tagalog for the cross-border SEA expansion, evaluated against held-out test sets sampled from each language.
Coverage: $10K–$20K floor at Thai seed stage, $25K–$40K typical at Series-A, $50K ceiling for substantial inference budgets with documented evaluation methodology covering Thai-language-specific benchmarks. The Thai-language scoring on Bedrock POC funding has improved notably through 2025 as reviewer familiarity with Thai-language evaluation methodology has built up; Thai-language-only POCs no longer get the discount they did pre-2024.
Timeline: 14–28 days. The POC plan needs to be specific: model selection (Claude Sonnet in ap-southeast-1 cross-region, given the absence of Sonnet from ap-southeast-7 as of this writing, or Claude Haiku and Amazon Nova for in-region inference), evaluation methodology with reference benchmarks (the Thai-language benchmarks expected include ThaiQA for Thai question answering, Wisesight Sentiment Thai for sentiment, XNLI-Thai for cross-lingual inference, and FLORES-200 Thai for translation quality), projected monthly inference budget, and decision criteria for production graduation.
What works in Thailand specifically: Bedrock POCs scoped against Thai-language customer service automation, cross-border SEA marketplace fraud detection, automated PDPA Thailand data subject access request fulfillment, AI-driven cross-border KYC for Thai fintechs serving SEA neighbor markets, Thai-language regulatory document classification for BOT and SEC Thailand reporting, and Bedrock-driven Thai-language insurance claims processing all land favorably. The cross-border SEA framing — where the Thai entity's Bedrock workload serves a regional customer base across multiple SEA languages — is one of the most reviewer-recognized Thai patterns and consistently anchors at $35K–$50K.
Thailand's regulatory landscape covers the major supervisory pillars expected of a mid-tier APAC financial market. BOT (Bank of Thailand) supervises licensed payment institutions, e-money operators, digital lending platforms, and the broader bank-adjacent fintech perimeter. PDPC (Personal Data Protection Committee) supervises personal data processing under PDPA Thailand. SEC Thailand (Securities and Exchange Commission) supervises capital markets and the Thai digital asset perimeter. OIC (Office of Insurance Commission) supervises insurance and insurtech. Each regime translates into specific technical controls on AWS workloads, and the Build for Startups track funds the implementation work.
For most Thai startups, only a subset of these regimes is in scope at any given moment. A B2B SaaS startup not handling personal data of regulated classes may face only PDPA Thailand. A licensed payment institution faces the BOT IT Risk Management Notice + the Payment Systems Act 2017 technical controls + PDPA Thailand. A SEC Thailand-licensed digital asset business operator (DABO) operates under the SEC Thailand digital asset notification series + PDPA Thailand + selective BOT requirements where the business model crosses payment functionality. Each regime maps to specific AWS-service architectural patterns, and partner-experienced ACE filings encode this mapping into the credit application scope.
The BOT IT Risk Management Notice — the central guidance for technology risk management at BOT-supervised institutions — defines the technical risk management expectations the central bank holds for licensed payment institutions, e-money operators, and the broader BOT-regulated fintech perimeter. For AWS workloads, BOT IT Risk Management compliance typically translates to: a multi-account AWS Organization structure with production / non-production / log-archive segregation; customer-managed KMS keys with documented key lifecycle management; CloudTrail with multi-year retention in a dedicated log-archive account; GuardDuty for ongoing threat detection; Inspector for vulnerability scanning; Security Hub for centralized compliance reporting; AWS Config rules for BOT-mandated control state tracking; AWS Backup for documented RPO / RTO posture; and a documented incident response runbook with named BOT reporting thresholds. The Payment Systems Act 2017 layered on top adds the licensing-specific operational controls — KYC/AML integration with the payment flow, transaction monitoring infrastructure, customer fund segregation patterns for e-money operators.
CloudRoute's data: Thai BOT-supervised fintechs filing Portfolio + Build for Startups stack typically approve at $75K–$100K + $25K = $100K–$125K total, with the Build for Startups scope explicitly cited against the BOT IT Risk Management Notice and the Payment Systems Act 2017 sections. The BOT-anchored scope is the most reviewer-recognized Build for Startups frame for Thai applications.
PDPA Thailand was enacted in 2019 and fully enforced from June 2022 after multiple postponements. It is the central personal data protection regime for any business processing personal data of individuals in Thailand, structured broadly parallel to GDPR with adaptations for Thai legal context. PDPA Thailand establishes Data Controllers and Data Processors, mandates explicit consent (or specified lawful bases) for processing personal data, requires sensitive personal data (health, biometrics, genetics, religious beliefs, criminal records, political opinions, sexual orientation) to be processed under heightened conditions, and creates Data Subject rights to access, correction, and erasure under PDPC supervision.
Cross-border transfers of personal data out of Thailand are governed by PDPA Thailand sections 26–29. Transfers are permitted where the recipient country has been determined adequate by PDPC, where the data subject has explicitly consented after being informed of the inadequacy, or under specified safeguards including binding corporate rules, standard contractual clauses, or PDPC-approved certification schemes. For AWS architectural purposes: workloads processing Thai personal data and replicating to ap-southeast-1 (Singapore) or any non-Thai region must include cross-border transfer documentation, logging of the data classes transferred, and Data Subject notification mechanisms where applicable.
For AWS workloads, PDPA Thailand compliance typically translates to: Amazon Cognito for consent capture and Data Subject identity management; AWS KMS with customer-managed keys for encryption of sensitive personal data at rest; Amazon Macie for ongoing scanning and classification of sensitive personal data across S3; AWS CloudTrail with extended retention for processing-activity audit logs; Amazon S3 with Object Lock for retention compliance; Lambda + Step Functions for Data Subject access request fulfillment workflows; SNS or Amazon Pinpoint for Data Subject notification flows; AWS Config for compliance state tracking. This scope typically lands at $20K–$25K Build for Startups when scoped distinctly from the underlying SaaS infrastructure, particularly where the architecture includes the cross-border transfer audit trail for the ap-southeast-7 to ap-southeast-1 path explicitly.
SEC Thailand supervises capital markets and the Thai digital asset business operator perimeter under the 2018 Royal Decree on Digital Asset Business and subsequent SEC Thailand notifications. The digital asset business operator licenses — Digital Asset Exchange, Digital Asset Broker, Digital Asset Dealer, Digital Asset Fund Manager, and Digital Asset Advisory Service — each carry specific technical control expectations. SEC Thailand notifications cover IT security, custody arrangements (including cold storage and key management), client asset segregation, transaction monitoring, and incident reporting.
For AWS workloads, SEC Thailand digital asset compliance typically translates to: hardware security module (HSM) integration via AWS CloudHSM for private key custody; multi-account AWS Organization with hard segregation for the custody plane; customer-managed KMS keys for all client data; CloudTrail with multi-year retention; GuardDuty + Security Hub + Detective for threat detection and investigation; and the BOT IT Risk Management Notice technical controls where the business model crosses into BOT-supervised payment functionality. SEC Thailand-supervised Build for Startups applications consistently land at the $25K ceiling when scoped against the specific notification series.
OIC (Office of Insurance Commission) supervises Thai insurance, including the insurtech segment that has grown materially through 2023–2026. OIC technical control expectations are less elaborated than BOT's but are increasingly substantive for digital-native insurtech licensees. For AWS workloads, OIC-aligned scope typically includes the standard regulatory technical controls — customer-managed KMS, CloudTrail audit, GuardDuty, multi-account segregation — supplemented by insurance-specific data architecture (claims data segregation, policy data retention with Object Lock, regulatory reporting infrastructure). The Build for Startups application scoped for insurtech compliance lands at the same $25K ceiling as the BOT-scoped fintech equivalent when the partner files the application with specific OIC notification references.
The Thai SEC Thailand-supervised securities crowdfunding licensees, the Ministry of Digital Economy and Society (MDES) supervised digital service providers (under the Royal Decree on Electronic Service Tax / VAT for foreign digital service providers), and the depa-supervised Smart City service providers each carry distinct but overlapping technical control vocabularies. The Build for Startups track can address any of these scopes where the technical work is substantive and distinct from the underlying SaaS infrastructure funded by Portfolio.
Thailand's institutional capital base is structurally bifurcated between independent venture firms (most notably 500 TukTuks, the Thai brand of the 500 Global franchise) and corporate venture arms attached to the major Thai banks, conglomerates, and telecommunications carriers. Each carries varying degrees of AWS reviewer recognition; partner-filed applications cite the relevant institutional signal in the ACE record to anchor the credibility assessment.
The institutional capital base relevant to Thai Portfolio applications. 500 TukTuks is the Thai brand of the 500 Global venture firm (formerly 500 Startups), founded in 2015 with deal activity across SEA and concentrated portfolio activity in Thailand. 500 TukTuks portfolio companies qualify for Activate Portfolio at parity with other 500 Global portfolio companies — the funding signal is recognized directly. Peak XV Partners (the successor brand to Sequoia Capital India and SEA) has a smaller but growing Thai investment book through the SEA practice; Peak XV-backed Thai entities qualify on the same global recognition as Peak XV-backed Singapore or Indonesian entities. Lightspeed, Insignia, Wavemaker, and Jungle Ventures invest into Thai entities from their Singapore-anchored SEA practices; each carries global-recognized institutional signal.
The Thai corporate venture arms collectively deploy the larger share of institutional capital into Thai Series-A and Series-B rounds. Beacon Venture Capital — the corporate venture arm of Kasikornbank (one of the major Thai commercial banks) — was founded in 2017 and operates an active investment book across fintech, deep-tech, and B2B SaaS. AddVentures by SCG — the corporate venture arm of Siam Cement Group, one of Thailand's largest industrial conglomerates — invests in deep-tech and industrial-adjacent ventures. KASIKORN Investment is a separate Kasikornbank-affiliated investment vehicle distinct from Beacon. Krungsri Finnovate — the corporate venture arm of Krungsri / Bank of Ayudhya (the Mitsubishi UFJ Financial Group-affiliated Thai commercial bank) — focuses on fintech and adjacent ventures. AIS-D Venture Capital — the corporate venture arm of AIS (Advanced Info Service, the largest Thai mobile network operator) — invests in telco-adjacent, IoT, and deep-tech ventures. Bualuang Ventures is the corporate venture arm of Bangkok Bank. True Digital Ventures and InVent (the Intouch Holdings venture vehicle) round out the major corporate VC roster.
For VC-filed Portfolio applications (the route alongside partner-filed via ACE), the VC submits directly through the AWS Portfolio Sub-Program. 500 TukTuks has direct Portfolio Sub-Program access through the global 500 Global framework. Peak XV, Lightspeed, Insignia, Wavemaker, and Jungle Ventures all have direct access through their global firm relationships. The Thai corporate venture arms have varied AWS engagement — Beacon Venture Capital, Krungsri Finnovate, AddVentures, and AIS-D have established partner relationships through the Kasikornbank, Krungsri, SCG, and AIS parent corporations' AWS commercial engagements; portfolio companies under these CVCs benefit from the parent corporation's existing AWS relationship in the Portfolio funding signal validation.
Partner-filed applications via CloudRoute-routed partners run consistently in the 14–22 day window for Thai applications and are the more reliable path for time-sensitive credit applications, particularly where the CVC parent corporation's direct AWS engagement timing is uncertain.
NIA operates the central government innovation framework under the "Thailand 4.0" national strategy. NIA-recognized startups — through the Startup Thailand network, the NIA Innovation Hub program, or NIA-backed grant tracks (the SME / Startup Voucher, the Open Innovation Grant, the Thematic Innovation Grant) — carry an AWS-reviewer-recognized credibility signal. The signal is parallel to DPIIT recognition in India: not a substitute for institutional venture capital at the Portfolio tier, but a meaningful uplift in the partner-filed Founders track. CloudRoute's data: partner-filed Founders applications referencing NIA recognition typically land at $20K–$25K, against a baseline of $10K–$15K for applications without it.
depa (Digital Economy Promotion Agency) operates digital-economy-focused grants and Smart City initiatives. depa-supported startups appear in partner-filed applications as supplementary credibility signal. The BOI (Board of Investment) software development and digital-services tax-status companies appear as operational seriousness signal but do not directly affect credit gating.
True Digital Park (Bangkok), opened in 2018 by True Corporation, is the largest tech-focused mixed-use campus in Thailand and the geographic and ecosystem center for the Bangkok startup base. True Digital Park residency or graduation status appears in partner-filed Founders applications as ecosystem signal. The KX (Knowledge Exchange for Innovation) at KMUTT (King Mongkut's University of Technology Thonburi) and the CU Innovation Hub at Chulalongkorn University fill out the university-attached incubator side of the Bangkok ecosystem.
For Chiang Mai-headquartered startups in the remote-first and digital-nomad-adjacent SaaS segment, the ecosystem is more distributed but anchored by the CMU (Chiang Mai University) innovation programs and the broader Punspace / CAMP / The Wall / Maya coworking ecosystem. AWS reviewer recognition of the Chiang Mai ecosystem is weaker than Bangkok recognition; Chiang Mai startups in CloudRoute's routed pipeline tend to scope applications around the operational pattern (remote-first global team, Bangkok or Singapore commercial entity, international customer base) rather than the geographic origination.
YC, Techstars, and 500 Global are tier-1 accelerator signals globally — including for Thai-incorporated startups. YC-backed Thai companies receive direct Activate Portfolio access regardless of subsequent VC funding status; the YC + AWS integration path runs through the AWS Activate console. 500 TukTuks is the Thai brand of 500 Global and carries the same direct Portfolio recognition.
Bangkok has positioned through 2022–2026 as a regional fintech hub serving the broader Mekong-region SEA market. The pitch: Thai-incorporated entities operating from Bangkok as the regional headquarters, with cross-border product extension into Vietnam, Indonesia, the Philippines, and increasingly Cambodia, Lao PDR, and Myanmar (where regulatory complexity is higher). This positioning shapes how Series-A and Series-B Thai credit applications scope, what regions get cited in the architectural narrative, and how the cross-border SEA Bedrock POC funding lands.
The structural case for Bangkok as regional fintech hub: a Thai-incorporated entity benefits from a relatively mature BOT supervisory framework with documented technical control expectations, an English-speaking commercial layer in Bangkok specifically (across the major Thai banks, the corporate venture arms, and the tier-1 service providers), a domestic market of 70M+ consumers and 3M+ SMEs that supports scale within Thailand alone, a domestic engineering talent base concentrated in Bangkok with cost positioning below Singapore and slightly below Jakarta, and direct geographic and ecosystem proximity to the Vietnamese, Indonesian, and Philippine markets for cross-border expansion. The cross-border SEA pitch is increasingly common in Thai Series-A and Series-B funding narratives.
For AWS credit applications, the cross-border SEA narrative scopes naturally across three Activate tracks: Portfolio for the consolidated SaaS infrastructure across the Thai parent and operating subsidiaries; Build for Startups for the regulatory technical builds that cover BOT and PDPC for the Thai entity plus the cross-border data transfer architecture for the SEA neighbor markets; and Bedrock POC for the multilingual SEA inference layer that supports cross-border customer service and KYC. The combined stack reaches $100K–$150K for Thai Series-A applications that explicitly frame the cross-border SEA positioning.
The architectural pattern: ap-southeast-7 (Bangkok) primary for the Thai customer-facing product and Thai PDPA-classified personal data; ap-southeast-1 (Singapore) for the regional API tier serving Vietnamese, Indonesian, and Philippine users plus the AI inference layer that depends on Claude Sonnet, Mistral Large, Bedrock Agents, or Bedrock Knowledge Bases (the services not yet in ap-southeast-7 as of this writing); CloudFront edge globally for static content delivery; and where Indonesian PDP-classified personal data is in scope, ap-southeast-3 (Jakarta) as the Indonesian data residency layer with documented cross-region replication for the audit trail.
The credit math at the cross-border SEA pattern: the $75K–$100K Portfolio + $25K Build for Startups + $25K Bedrock POC stack covers 11–28 months of consolidated AWS spend across the Thai parent and the operating subsidiaries. For a Series-A cross-border Thai fintech burning $10K–$18K/month (~THB 350K–630K) of AWS, the $150K stack covers 8–15 months of runway. For a Thai Series-A SaaS company without the fintech regulatory overhead, burning $4K–$10K/month (~THB 140K–350K) of AWS, the $125K–$150K stack covers 12–30 months.
For fintech entities operating across multiple SEA jurisdictions, the regulatory scope multiplies — BOT for the Thai entity, SBV (State Bank of Vietnam) for Vietnamese operations, OJK (Otoritas Jasa Keuangan) for Indonesian operations, BSP (Bangko Sentral ng Pilipinas) for Philippine operations. The Build for Startups scope can address the multi-jurisdiction technical controls as a single architectural build serving multiple regulatory regimes; this typically scopes at the $25K ceiling because the technical work is substantial. Where the cross-border footprint extends to MAS (Singapore) supervision through a Singapore subsidiary, the build complexity increases and the partner typically files the Build for Startups scope to explicitly cover the technical controls overlapping BOT and MAS expectations.
The Thai startup ecosystem outside Bangkok concentrates in two secondary clusters with distinct profiles. Chiang Mai is the center for remote-first, digital-nomad-adjacent SaaS companies — both Thai-incorporated entities founded by Thai or expatriate founders and Singapore- or Delaware-incorporated entities with operational teams based in Chiang Mai. Phuket carries a smaller but growing hospitality-tech and Web3 cluster oriented around the tourism economy and the broader Phuket Sandbox digital nomad ecosystem.
Chiang Mai-anchored SaaS companies in CloudRoute's Thai routed pipeline tend to scope AWS credit applications around the global operating pattern rather than the geographic origination. The dominant Chiang Mai pattern: a small SaaS company (typically 6–18 engineers) building B2B SaaS for international customers, distributed engineering team with a Chiang Mai operational hub, Singapore or Delaware incorporation for the commercial entity with a Thai operating subsidiary, AWS workloads running primary in us-east-1 (us customer base) or ap-southeast-1 (SEA customer base) rather than ap-southeast-7 (Thai customer base is incidental, not primary). For Thai-incorporated Chiang Mai SaaS — less common but present — the credit application scopes naturally against ap-southeast-7 as primary with the global CloudFront edge pattern.
Phuket's hospitality-tech cluster — booking platforms, property management SaaS for the short-term rental market, restaurant tech, tourism marketplaces — typically files credit applications scoped around the seasonal demand pattern of the Thai tourism economy. The architectural narrative covers elastic capacity for the high-season demand spikes (November through April for the dominant Western tourism cycle, plus the Chinese New Year and Songkran festival peaks), CloudFront edge for the international booking traffic, and Bedrock-driven multilingual customer service across English, Mandarin, Russian, Thai, and increasingly the Middle East languages reflecting the diversification of the Phuket tourism base.
The Phuket Web3 cluster is smaller and concentrated around the Phuket Sandbox digital nomad community plus a handful of Singapore- or Cayman-incorporated entities with Phuket operational presence. AWS credit applications for this segment scope against the global infrastructure pattern rather than the Thai-domestic pattern; ap-southeast-7 has limited relevance for the Web3 workloads that typically run primary in us-east-1 or eu-central-1.
For both Chiang Mai and Phuket-anchored Thai entities, the NIA recognition signal still applies — NIA operates nationally rather than Bangkok-specifically — and the partner-filed Founders track at $20K–$25K is reliably accessible. The Portfolio tier at $50K–$100K depends on the institutional capital signal, which is more likely to be sourced from Bangkok-based or Singapore-based investors rather than locally-anchored capital in Chiang Mai or Phuket.
A practical mechanic that matters for Thai-incorporated companies: AWS invoices Thai customers in USD by default through the AWS Asia Pacific operating entity, with the THB-equivalent settlement happening at the Thai bank when the invoice is paid. The THB-USD rate has fluctuated between THB 33 and THB 37 per USD through 2024–2026, with a reference rate of approximately THB 35 per USD used in this document.
AWS accounts registered in Thailand are typically under the AWS Asia Pacific operating entity, billed in USD. Thai corporate tax treatment of the AWS invoice runs through the standard Thai input/output VAT mechanics — Thai VAT applies at the prevailing rate (7% as of 2026), with input VAT recoverable for VAT-registered businesses. The credit pool reduces the USD-denominated service charge before VAT application; practical effect: $100K of credits applied to a Thai AWS account reduces the USD cost by $100K, which translates to roughly THB 3.5M of THB-denominated spend offset at the reference rate.
For Thai-incorporated entities with cross-border revenue exposure (Thai parent serving Vietnamese, Indonesian, or Philippine customers), the AWS account typically remains a single consolidated Thai-billed account with cross-border traffic patterns managed through the architectural region selection rather than billing entity selection. This simplifies the credit application — Portfolio attaches to the Thai parent entity, regardless of where the cross-border traffic terminates.
| Track | Typical Thai award | Filed by | Time-to-balance | Thailand-specific gate |
|---|---|---|---|---|
| Activate Builders (self-serve) | $1K | You | 24 hours | None — universal |
| Activate Founders (self-serve) | $5K | You | 3–7 days | None — universal |
| Activate Founders — partner-filed | $10K–$25K | Partner via ACE | 12–16 days | NIA / depa / True Digital Park vouch helps |
| Activate Portfolio (partner or VC-filed) | $50K–$100K | Partner via ACE or VC direct | 14–22 days | 500 TukTuks / Beacon / Krungsri Finnovate / AddVentures / AIS-D / Bualuang Ventures funding |
| Build for Startups — BOT / Payment Systems Act | +$25K | Partner via ACE | 14–21 days | BOT-supervised scope; discrete compliance build |
| Build for Startups — PDPA Thailand / PDPC | +$25K | Partner via ACE | 14–21 days | PDPA cross-border or PDPC certification scope |
| Build for Startups — SEC Thailand digital asset | +$25K | Partner via ACE | 14–21 days | Digital Asset Business Operator license scope |
| Bedrock POC — Thai-language / cross-border SEA | +$25K–$50K | Partner via ACE | 14–28 days | Thai-language or multilingual SEA inference; defined POC plan |
| Build for AWS | Partner labor subsidy (variable) | Partner | 21–42 days | Subsidizes partner work, not founder credits |
A typical engagement for a Thai-incorporated startup, from initial inquiry to credits applied to the AWS account. Wall-clock timing pulled from CloudRoute's Thai routed pipeline through 2025–2026.
Day 0 — Inquiry submitted to CloudRoute (3 minutes). Three questions: company name, funding stage, AWS use case (one sentence). Thailand-specific: noting whether BOT supervision, PDPA Thailand cross-border, SEC Thailand digital asset, or NIA recognition applies routes the inquiry to a partner with the relevant regional regulatory experience. Routing happens within 24 hours.
Day 1–2 — 30-minute discovery call for non-regulated SaaS; 60 minutes for BOT-supervised fintech where the partner walks through the regulatory build scope. Partner confirms Thai incorporation status (Private Limited Company under the Civil and Commercial Code is the cleanest), identifies whether Portfolio is standalone or whether to stack Build for Startups + Bedrock POC, and assesses VC or CVC vouch availability.
Day 3–5 — Founder provides company info, DBD (Department of Business Development) registration details, AWS account ID (or guides creation), use case description (1–2 paragraphs), and 8–10 slide deck. If BOT IT Risk Management or PDPA Thailand scope is in play, the partner provides a scoping template covering the architectural components.
Day 5–7 — Partner files ACE records: Founders track or Portfolio (whichever applies based on funding signal), Build for Startups (if applicable), Bedrock POC (if AI workload in scope). For Thailand-specific applications, the partner explicitly names BOT IT Risk Management Notice sections, Payment Systems Act 2017 references, PDPA Thailand sections 26–29 for cross-border transfer scope, target region (ap-southeast-7 default with ap-southeast-1 fallback noted), and any DR region.
Day 10–16 — AWS reviewer queue assigns. Thai applications with 500 TukTuks / Beacon Venture Capital / Krungsri Finnovate funding signal, NIA recognition citation, and named regulatory scope typically clear at the upper end of the range. The reviewer may ask one clarifying question about region selection (specifically about the ap-southeast-7 / ap-southeast-1 split), cross-border SEA scope, or Bedrock POC methodology; partner responds within 24 hours.
Day 14–21 — Credits applied to the Thai-billed AWS account, visible in the Billing and Cost Management dashboard under "Promotional credits." The credit balance is USD-denominated; it reduces the USD-equivalent service charge before THB settlement and VAT application.
Total founder time: ~60 minutes across the engagement for non-regulated SaaS; ~3 hours for BOT-supervised fintech where regulatory counsel is involved in the Build for Startups scoping. Total wall-clock: 14–21 days from inquiry to credits applied. Total cost: $0 — AWS funds the partner via APN Funding and ACE attribution; the partner pays CloudRoute commission from its own AWS-funded revenue.
Mistake 1: Applying for self-serve $5K only and not stacking Build for Startups or Bedrock POC. The self-serve $5K is the default surfaced in the AWS Activate console, and many Thai founders stop there. The partner-filed stack at $75K–$150K is structurally available for Thai Series-A applicants — most APAC-experienced partners file the full stack routinely. The fix: confirm with the partner before settling for self-serve only.
Mistake 2: Filing Portfolio without explicitly citing the corporate venture vouch and the parent corporation's AWS engagement. For Beacon Venture Capital, Krungsri Finnovate, AddVentures, AIS-D, and Bualuang Ventures-backed startups, the parent corporation (Kasikornbank, Krungsri, SCG, AIS, Bangkok Bank) often has a direct AWS commercial engagement that strengthens the Portfolio signal validation. Filing Portfolio with only the CVC name cited without the parent corporation reference underutilizes the funding signal. The fix: scope the CVC parent corporation's AWS engagement into the partner-filed narrative.
Mistake 3: Defaulting to ap-southeast-7 (Bangkok) for all services without checking the service catalog gap. ap-southeast-7 launched in 2025 and as of 2026 lacks several services that may be load-bearing for AI-heavy workloads — Claude Sonnet, Mistral Large, Bedrock Agents, Bedrock Knowledge Bases, OpenSearch Serverless. Filing a Bedrock POC scoped around Claude Sonnet for in-region inference without recognizing the ap-southeast-1 cross-region requirement creates reviewer-side confusion that delays approval. The fix: scope the ap-southeast-7 / ap-southeast-1 split explicitly from the start.
Mistake 4: Filing a vague Bedrock POC without Thai-language-specific evaluation methodology. Thai Bedrock POCs scoped as "we will evaluate Claude for our Thai customer service use case" land at the $15K–$20K floor. The same use case scoped as "we will evaluate Claude Sonnet 4 in ap-southeast-1 (with cross-region traffic from ap-southeast-7) against held-out test sets sampled from Thai customer interactions, benchmarked against ThaiQA and Wisesight Sentiment Thai for in-language quality, plus FLORES-200 Thai for translation pairings to English / Vietnamese / Bahasa Indonesia / Tagalog for the cross-border SEA expansion, with monthly inference budget of $X" lands at $35K–$50K. The fix: invest 30 minutes in the evaluation methodology before the partner files.
Mistake 5: Confusing the Thai parent entity with a Thai operating subsidiary on the ACE record when a foreign holding company exists. Some Thai startups operate with a Singapore or Cayman holding company that holds the institutional VC funding, with a Thai operating subsidiary that runs the day-to-day commercial operations. The AWS credit application files against the entity that holds the institutional VC funding — the foreign holding company in this structure. Filing against the Thai operating subsidiary introduces queue-routing inconsistency because the funding signal does not match the entity. The fix: confirm on day 1 which entity holds the cap table and file against that entity.
The biggest predictors of credit ceiling for Thai applications are the regulatory scope, the corporate venture or independent VC vouch, and the cross-border SEA architecture. Plain SaaS lands around the partner-filed Founders / lower Portfolio range; fintech with BOT regulatory work stacks higher; cross-border SEA expansion with multilingual Bedrock use cases reaches the $150K stack ceiling consistently.
| Variable | Thai SaaS (no regulatory) | Thai BOT fintech | Thai cross-border SEA + Bedrock |
|---|---|---|---|
| Typical credit pool | $25K–$75K | $100K–$150K | $100K–$150K |
| Portfolio approval likelihood | Moderate (depends on VC) | High (CVC + BOT scope) | High (CVC + cross-border) |
| Build for Startups stack? | Sometimes (PDPA-only scope) | Always (BOT IT Risk Management) | Often (multi-jurisdiction) |
| Bedrock POC fit? | Depends on use case | Often (anomaly detection, doc AI) | Always (multilingual SEA + Thai) |
| Region selection | ap-southeast-7 default | ap-southeast-7 + ap-southeast-1 (AI tier) | ap-southeast-7 + ap-southeast-1 (regional API + AI) |
| Application length | 12–16 days | 14–21 days | 14–21 days |
| Founder time | ~45 min | ~3 hours (incl. regulatory counsel) | ~2 hours |
| Cost to founder | $0 | $0 | $0 |
Situation: Bangkok-incorporated B2C marketplace serving Thai consumers (domestic core) with a cross-border arm extending into Vietnam through a Ho Chi Minh City operating subsidiary. NIA-recognized. PDPA Thailand cross-border architecture required for the Vietnam operating subsidiary's personal data layer; PDPC supervisory expectation for data subject rights infrastructure built out before scale. Roadmap included Bedrock-driven multilingual customer service automation (Thai + Vietnamese for launch, Bahasa Indonesia and Tagalog for the planned 2027 expansion into the broader SEA marketplace footprint) and Bedrock-driven marketplace fraud detection. Pre-engagement architecture ran on a mix of DigitalOcean (legacy Bangkok presence) and a Vercel + Supabase stack for the Vietnam expansion, with growing concerns about Bangkok-to-Vietnam cross-region traffic costs and PDPA cross-border audit trail gaps.
What CloudRoute did: Routed within 22 hours to a Bangkok-headquartered APAC Advanced-tier partner with documented BOT-adjacent and PDPC engagement track record (7 prior Thai engagements, including 3 PDPA Thailand cross-border builds for cross-SEA fintech and marketplace clients). Discovery call ran 70 minutes including the Thai partner regulatory counsel for the PDPC-side scoping. Partner filed three ACE records: Portfolio ($85K, Beacon Venture Capital + 500 TukTuks + KASIKORN Investment funding cited with explicit reference to Kasikornbank parent AWS engagement) on day 4 for the consolidated marketplace SaaS infrastructure; Build for Startups ($25K, PDPA Thailand sections 26–29 cross-border transfer scope with Cognito + KMS + Macie + CloudTrail + Step Functions architecture, plus the Vietnam-side cross-border data flow with documented PDPC audit trail) on day 5; Bedrock POC ($40K, Claude Sonnet 4 in ap-southeast-1 for Thai + Vietnamese customer service automation with cross-region traffic from ap-southeast-7, evaluation methodology citing ThaiQA, Wisesight Sentiment Thai, FLORES-200 Thai-to-Vietnamese, and held-out marketplace conversation samples) on day 6.
Outcome: Total credits approved by day 20: $150K (~THB 5.25M). Production AWS architecture delivered over 9 weeks. Production AWS Organization in ap-southeast-7 (Bangkok) primary for the Thai marketplace and PDPA Thailand-classified personal data, ap-southeast-1 (Singapore) for the AI inference tier (Claude Sonnet 4 cross-region for the multilingual customer service) and the Vietnamese-customer-facing API tier, with CloudFront edge globally. Latency to Bangkok users <2ms; to Ho Chi Minh City users 8–14ms via ap-southeast-1; to Chiang Mai users 14–18ms via ap-southeast-7. Bedrock POC delivered the Thai + Vietnamese multilingual customer service automation into pilot by week 11. PDPA Thailand cross-border audit trail live before the credit balance fully applied. Effective AWS spend covered through month 18 at the post-Series-A scaled burn rate. CloudRoute commission paid by the partner from AWS engagement funding. Customer cost: $0.
engagement window: 11 weeks · founder time: ~14 hours · credits secured: $150K · cost to customer: $0
CloudRoute routes within 24 hours to APAC-queue-experienced partners with BOT IT Risk Management, PDPA Thailand cross-border, ap-southeast-7 / ap-southeast-1 split-region, and Thai-language Bedrock scoping vocabulary. Credits applied in 14–21 days. Customer pays $0.