endoflife.ai
EOL Checker Products EOL Watch Get Support

Five AWS Services End October 7, 2026 — and One Deletes Your Data

By Scott Bissett  ·  Published: September 22, 2026  ·  EOL Watch — deadline coverage  ·  Every date read from AWS's own documentation

Cloud retirements are usually reported one service at a time, which is how five of them landing on the same day goes unnoticed. On October 7, 2026, AWS ends support for Amazon FinSpace, Amazon Lookout for Equipment, AWS IoT Greengrass V1, AWS Proton and AWS WAF Classic. They are not related products and they do not share a team. They share a date because AWS announced all five on October 7, 2025 and gives sunset services a standard twelve-month window.

Quick answer: five AWS services reach end of support on the same day, October 7, 2026. The one that behaves differently from the rest is AWS Proton: its own FAQ says all data is deleted after the date, where the others remove access. There is no extended-support option for any of them — a managed service has no third party who can keep it running — so migration is the only route past the date.

Key Dates at a Glance

Facing an end-of-life deadline?
Tell us which product and we’ll reply with vetted extended-support options and pricing guidance — free, no obligation. Vendors don’t pay for placement.

Free · No obligation · Independent · dates verified against vendor sources · Not urgent? Follow the EOL radar or see the 2026 EOL calendar →

What AWS actually publishes

All five appear in one place: the Services in Sunset table in the AWS General Reference. That table is the vendor's primary lifecycle surface for retiring services, and its preamble states the rule plainly — sunset services have a sunset timeline, typically twelve months, and the sunset date is the date AWS ends operations and support.

ServiceAnnouncedEnd of supportWhat AWS says stops
Amazon FinSpaceOctober 7, 2025October 7, 2026Access to the Dataset Browser and Managed kdb Insights
Amazon Lookout for EquipmentOctober 7, 2025October 7, 2026Operations and support for the service
AWS IoT Greengrass V1October 7, 2025October 7, 2026Operations and support for the V1 line
AWS ProtonOctober 7, 2025October 7, 2026Console and resource access — and all data is deleted
AWS WAF ClassicOctober 7, 2025October 7, 2026Operations and support for the Classic line

Two of the five have dedicated end-of-support pages of their own, which is where the useful detail lives. The other three exist only as rows in that table plus a migration link, so the table is the whole notice.

AWS Proton: the one that deletes

Proton is the service to read carefully, because its retirement behaves differently from the others. AWS's deprecation and migration guide states that support ends on October 7, 2026, that new customers were blocked a year earlier, from October 7, 2025, and, in its FAQ, answers the question “How long will my data be retained?” with a retention date and then a deletion: until October 7, 2026, and after that date all data will be deleted.

The good news, which AWS states clearly, is that the blast radius is narrower than it first appears. Proton is a delivery service, not a runtime: the CloudFormation stacks it deployed and the resources those stacks manage keep running untouched. What goes away is the templating, the environments and the pipelines — the ability to change the infrastructure through Proton, and the template data describing how.

Who this catches: platform teams that used Proton to give developers self-service environments. Your running services are fine. Your ability to update them through the mechanism your developers know is not, and the templates encoding the standards are what gets deleted. Export before the date, not after.

AWS names four alternatives in its own guide: CloudFormation Git sync for teams that want a GitOps workflow, AWS CodePipeline with CodeBuild for maximum flexibility, Harmonix on AWS for an internal developer portal built on Backstage, and GitHub Actions for smaller teams already on GitHub. It is candid about the trade-offs — Git sync has no concept of environments, and Harmonix is a partner solution rather than an AWS-maintained service.

Amazon FinSpace: two capabilities, one date

FinSpace went generally available on May 3, 2021 as an analytics service for financial-services firms, and later gained Managed kdb Insights. Its end-of-support page says that after October 7, 2026 both the Dataset Browser and Managed kdb Insights become inaccessible. AWS points Dataset Browser users at its data catalog, Spark and SageMaker AI Studio, and gives kdb customers a documented export path via pyKX to Amazon S3 before standing kdb up themselves on their own compute.

That kdb migration is the one with real engineering in it. Extracting a historical database and rebuilding the environment is not a configuration change, and the customers running it are capital-markets firms with data volumes that make the export itself a scheduling problem.

AWS IoT Greengrass V1: the fleet problem

Greengrass launched on June 7, 2017 to run Lambda functions and local compute on connected devices. V2 is a separate, supported product, so on paper this is a version migration rather than a service retirement.

In practice it is the hardest of the five, because the software being retired is not in a data centre. It is on devices in factories, vehicles and remote sites, and moving from V1 to V2 means a fleet-wide update on hardware that may be intermittently connected and physically inaccessible. Nine years of deployments is a long tail. If any of that fleet cannot be reached before October 7, 2026, it becomes unsupported edge software running production workloads — the category that turns up in breach reports.

AWS WAF Classic: a rename that hid a deadline

AWS WAF Classic is the original AWS WAF, renamed when AWS shipped a rewritten version of the service in 2019. Anything created before that rewrite is Classic, and Classic is what ends on October 7, 2026. The current AWS WAF is unaffected and is the migration target.

The risk here is specifically one of naming. A team that checks whether “AWS WAF” is supported will find that it is, because it is — the product with that name today is the new one. The question that matters is whether the web ACLs and rules in the account were created under Classic, and that is not visible from the service name alone. Classic rules do not carry across automatically; the migration is a rebuild of the rule set.

Amazon Lookout for Equipment: the quiet one

Lookout for Equipment went generally available on April 8, 2021 to detect abnormal industrial-equipment behaviour from sensor data. It has no dedicated end-of-support page. Its entire published notice is the row in the sunset table and a migration blog post AWS links from it, which is worth knowing if you go looking for an official announcement and cannot find one.

The pattern worth taking away

AWS's sunset window is twelve months from announcement. That means the October 2026 cohort was settled in October 2025, and every cohort after it is already visible in the same table today. Reading that one page twice a year catches these a year ahead instead of a fortnight.

The same table carries two more dates close to this one that are easy to sweep up in the same piece of work: Amazon SageMaker AI – Mechanical Turk ends September 30, 2026, and Amazon Pinpoint ends October 30, 2026. Further out it lists Amazon WorkMail, Amazon RDS Custom for Oracle, Amazon WorkSpaces PCoIP and Thin Client, AWS Managed Services Advanced and several others through 2027.

And the structural point, which applies well beyond AWS: there is no extended-support market for a managed service. When a vendor retires software you install, somebody can keep patching it — that is the whole business that exists around Java, Linux and the older web frameworks. When a vendor retires a service it operates, there is nothing to patch and nobody to sell it. The date is the date.

Frequently asked

Which AWS services end support on October 7, 2026?

Five: Amazon FinSpace, Amazon Lookout for Equipment, AWS IoT Greengrass V1, AWS Proton and AWS WAF Classic. All five carry an announcement date of October 7, 2025 and an end-of-support date of October 7, 2026 in the AWS Services in Sunset table.

Does AWS delete data when a service is sunset?

It depends on the service, and Proton is the one to watch. Its FAQ says data is retained until the date and deleted after it. The others state loss of access rather than deletion, so each service has to be read on its own terms.

Why do so many AWS services retire on the same day?

Because the standard sunset window is twelve months from announcement and these five were announced together. The clustering comes from the announcement date, not from the services having anything to do with one another.

Is there third-party extended support for a retired AWS service?

No. Only AWS operates these services, so there is nothing a third party can patch or host. Migration is the only path past the date, which is why this page recommends no vendor.

Where is the authoritative notice?

The Services in Sunset table at docs.aws.amazon.com/general/latest/gr/sunset_services.html, plus the dedicated end-of-support pages AWS publishes for Proton and FinSpace. Every date on this page is re-checked against those sources at every build.

Related Resources