Content Quality: News article (969 words, within the 400-1200 range) on the Amazon ECS Gateway launch. Clear structure (Overview, What AWS Says It Does, Pricing, Limits, Custom-Domain Question, Terraform Support, What We Don't Know). First-party claims are attributed to the specific AWS page that makes them; third-party commentary (InfoQ's relay of Reddit comments, one individual's DEV Community post) is attributed by name and kept distinct from AWS statements. The headline claim is correctly framed as 'InfoQ notes', not as the Herald's own finding. Title is 138 characters (under the 150-character guideline).
Source Verification: Snapshots read from disk (sources/2026-11/amazon-ecs-gateway-gives-each-service-a-generated-hostname-on-shared-application-load-balancers-and-infoq-notes-no-custom-domain-guidance/), decompressed and text-extracted; suspicious_patterns is null for all seven snapshots that were captured, so no injection-scan issue arose. source-0 (AWS News Blog, Channy Yun, 20 OCT 2026): confirms the verbatim 'a new account-level resource ... created directly in your account' quote; platform-team settings list (subnets, security groups, TLS certificates, listener settings, WAF web ACLs); connector added in CreateService/UpdateService; 'No infrastructure is provisioned until a service connects with a gateway connector'; host-based routing with ALBs and 'up to 25 services to share a single ALB'; incremental adoption by calling UpdateService; 'Default quota limit of maxAlbCount is 10' and 'If maxAlbCount is reached and no ALB has available capacity, the deployment fails'; 'connects the service to every compatible gateway'; 'available now in all commercial AWS Regions where ECS is available at no additional charge'. source-1 (AWS What's New, 'Posted on: Oct 20, 2026'): confirms the October 20, 2026 announcement date and the console, AWS CLI, API, AWS SDKs and AWS CloudFormation list for adding the connector; no-additional-charge statement. source-2 (ECS developer guide, gateway overview): confirms hostname form https://<unique-id>.ecs.<region>.on.aws, awsvpc on Amazon ECS EC2, Fargate and ECS Managed Instances, pricing text (no additional charge; pay for ALB, CloudWatch logs and metrics, data transfer), limits table (200 ALBs per gateway, 25 services per ALB), and every item in the article's constraint list (HTTPS only on port 443; bridge/host/none modes cannot connect; same account; no Express Mode; immutable name, type, scheme, listener port, listener protocol, subnets, IP address type; no consolidation of load balancers, 'several partly filled load balancers can remain after services leave'; no repair of out-of-band changes, traffic 'can stop'). source-3 (connect-service page): the 'Important' note is verbatim: 'A service that should never be reachable from the internet must filter on PRIVATE.' followed by 'Without the filter, associating an internet-facing gateway with the cluster later exposes the service on its next deployment.' The article reproduces both without overstating (it does not claim exposure happens unconditionally; the docs say it happens on the next deployment after a later internet-facing association). source-4 (InfoQ, Steef-Jan Wiggers, 'Amazon ECS Gateway Arrives with Generated Hostnames and No Custom Domain Support', Nov 04, 2026, datePublished 2026-11-04T09:49:00+0000): THE AUTOMATED SNAPSHOT FAILED (manifest file null, 'Timeout after 15000ms'), so as a documented last resort the live URL was fetched with curl and a browser User-Agent (HTTP 200; raw HTML sha256 a8dd65208a564744d621c302adf655a2ff82e2742e40286983a86350ecd7356a, held in the review scratchpad, not committed) and read as raw text. Confirmed verbatim: 'neither the announcement nor the documentation describes how to put a custom domain in front of it'; 'The first question practitioners asked was how to put their own domain in front of it.'; zurnout's 'It creates host-based rules in the load balancer, so it wouldn’t know where to route if you used a CNAME.'; bioJesusMain's 'It’s just ALB and DNS with a wrapper' (the article places a full stop inside the closing quote mark; the source has none, a punctuation-only difference); 'Custom domain names, Route 53, and CNAME records go unmentioned'; Kralizek82's CloudFront-origin question described as 'the one workaround nobody resolved'; the 'opinion split'; the 25-per-ALB, default 10, ceiling 200 figures. The article's scoping of the InfoQ claim is accurate: InfoQ says 'the documentation' in general, and the Herald separately and correctly limits its own check to the four AWS pages it cites. I grepped all four AWS snapshots for 'custom domain', 'Route 53', 'CNAME', 'domain name' and 'your own domain': there are no hits (the only 'Domain Name System' hit is the What's New description of DNS hostnames), so the Herald's statement that it found no mention on the cited pages is true. source-5 (DEV Community, Matias Martinez, datePublished 2026-10-28T21:42:30Z, originally published at blog.cloudacademy.ar): confirms 'Custom domains aren't covered in the current docs; services get on.aws hostnames.'; 'Terraform: support is still an open request (issue #50573, filed October 21)'; the quote 'the shared ALB isn't the news; that was always possible' (the article replaces the source's full stop with a comma inside the quote, punctuation only); the 'AWS now owns the full lifecycle: create, place, scale out to more ALBs, clean up' paraphrase; the worry about 'connect to every compatible gateway' turning a platform action into an exposure change; and the rule 'every connector gets an explicit accessTypes filter'. The article uses this post only as one practitioner's opinion and as a secondary pointer to the Terraform issue, never as news. source-6 and source-7 (GitHub): snapshots show both Open; cross-checked live through the GitHub API on Nov 7, 2026: issue #50573 'Amazon ECS Gateway' opened 2026-10-21T12:33:09Z by ewbankkit (a repository collaborator), state open, labels enhancement and service/ecs, body only quotes the AWS announcement and links to it; PR #50677 opened 2026-10-27T16:47:34Z by moneytool, state open, merged false, not a draft, adds aws_ecs_gateway and aws_ecs_gateway_cluster_association resources and a gateway_connector block on aws_ecs_service. Both dates and 'open, not merged' match the article. Allowlist: aws.amazon.com, docs.aws.amazon.com, infoq.com, dev.to and github.com are all already in config/source_allowlist.txt, so no additions were needed. Independent-source recount (see factual_accuracy and the Herald summary): four first-party AWS pages (blog, What's New, two documentation pages); four non-AWS sources: InfoQ (independent trade-press reporting, though much of its content is relayed Reddit commentary and the AWS documentation), the DEV Community post (an independent practitioner's blog post, republished from CloudAcademy.ar, opinion rather than news), the Terraform issue and the pull request (third-party records on a HashiCorp repository that attest only to their own existence, dates and state; the issue text just quotes AWS). So the writer's 'four independent of AWS' is arithmetically right, but only two of the four (InfoQ and DEV) are independent commentary; the GitHub items are independent records of their own state, not corroboration of AWS's product claims. News does not carry an independence minimum, and the article makes no claim that depends on more than that.
Factual Accuracy: Every number, date, version and quote checked individually against raw text; no discrepancy found. Dates: October 20, 2026 (blog byline and What's New 'Posted on: Oct 20, 2026'); InfoQ November 4, 2026; DEV post October 28, 2026; issue October 21, 2026; PR October 27, 2026 (all UTC dates match the GitHub API); read date November 7, 2026 (snapshots fetched 2026-11-07). Numbers: 25 services per ALB (blog, What's New, docs); default maxAlbCount 10 (blog, repeated by InfoQ and the DEV post); 200 ALBs per gateway (docs limits table). The '250 services' figure is labelled in the article as the Herald's own arithmetic (10 x 25), and it is: neither AWS page states 250, and 10 comes from the blog's default maxAlbCount quota, 25 from the blog and docs. For completeness, the DEV post independently states '(default 10, so 250 services)', so the arithmetic is not unique to the Herald, but the label 'by the Herald's own arithmetic' is accurate for how the figure was derived and is not misleading. Pricing: 'no additional charge for using Amazon ECS Gateway itself' is exactly the docs' Pricing text; the charge list (ALB, CloudWatch logs and metrics, data transfer) is the docs' list; the 'all commercial AWS Regions where ECS is available' scope is the blog's wording and is attributed to the blog; the article dates its reading to November 7, 2026 and makes no price or unit claim beyond what AWS says (no per-hour or per-region rates). The article's limits section is a list of selected constraints from the docs' Considerations section plus the blog's quota; it does not claim to be exhaustive ('lists several constraints'), and every listed limit and number matches. The 'PRIVATE filter' warning is quoted verbatim and framed as the documentation's own warning. 'Both/every/each/all' statements checked: 'each service gets a generated hostname' (docs: 'Each service gets a generated hostname'); 'a connector attaches a service to every compatible gateway associated with its cluster, according to the blog' (blog: 'connects the service to every compatible gateway'; docs say 'all compatible gateways associated with its cluster'); 'both were listed as open' (issue and PR both Open). No relative dates are used in the body ('now' appears only inside a quoted InfoQ passage and in 'AWS now owns the full lifecycle', a paraphrase of Martinez's present-tense claim, not a time reference). The one claim about absence (no mention of custom domains on the four cited AWS pages) was independently re-verified by grep, and the article scopes it to those pages rather than to all AWS documentation, which the Herald did not review in full (for example the 'Create and manage a gateway' page was not read).
Overall Assessment: Accurate, well-attributed News coverage of a real AWS launch. All quotes, numbers, dates and states verified against raw source text with no correction needed; the headline and lead are each backed by a cited source, every body URL is in article.sources, and the writer's scoping of the custom-domain claim is honest. Featured candidacy: 1 - solid, accurate launch coverage of a managed-ingress feature for ECS platform teams, a defined developer audience, with a useful documented-gaps angle but no broad industry impact