I attended the JAWS-UG Yokohama #102 AWS Service Termination Memorial LT Event and performed a memorial service for the AWS services that couldn't pass on to the afterlife #jawsug #jawsugyokohama

I attended the JAWS-UG Yokohama #102 AWS Service Termination Memorial LT Event and performed a memorial service for the AWS services that couldn't pass on to the afterlife #jawsug #jawsugyokohama

I gave a memorial service for the AWS services that couldn't pass on peacefully at "JAWS-UG Yokohama #102 AWS Service Discontinuation Memorial LT Session."
2026.07.17

This page has been translated by machine translation. View original

I'm Oguri, who absolutely loves whiskey, cigars, and pipes.

I gave a presentation at the 102nd JAWS-UG Yokohama study session "AWS End-of-Service Memorial LT Meeting," so I'd like to share the content of my presentation.

https://jawsug-yokohama.connpass.com/event/397635/

AWS Services That Can't Rest in Peace ~Today, We Hold a Memorial for Three~

The honorable departed we are memorializing today are as follows.

  • First spirit: EC2-Classic
    • Has passed on. However, the belongings have not been tidied up.
  • Second spirit: SDB
    • Still living. However, currently in the process of end-of-life activities.
  • Third spirit: SBS
    • The funeral is over. However, the heart is still beating.

Kumokai-in Koten Heimon-koji EC2-Classic

2006 − 2023 (Died at age 17)

The Life of EC2-Classic

  • August 2006: Amazon EC2 beta launch.
  • August 2009: Amazon VPC introduced.
  • March 2013: Default VPC introduced.
  • December 2013: New accounts became fully VPC-only. New use of EC2-Classic ended.
  • October 2021: Announcement of EC2-Classic retirement (EOL notice)
  • August 15, 2022: EC2-Classic sales ended. All instances in Classic environments were stopped.

Although sales ended on August 15, 2022, Dr. Werner Vogels issued a completion certificate for EC2-Classic one year later. You might wonder why one year later, but...

farewell-ec2-classic-certificate

But I knew the reason. On July 25, 2023, I witnessed the final moments of EC2-Classic.

image (11)のコピー

However —— The belongings have not been tidied up

Settings still remain in the Management Console. There are no VPC IDs or subnet IDs, and errors occur when displaying security groups.

スクリーンショット 2026-07-17 14.52.27

スクリーンショット 2026-07-17 14.50.07

Lesson One

Even when a service dies, the configuration does not

This Is Not an Obituary: Amazon SDB

2007− (Still living)

Everyone's beloved SDB

SBD = SimpleDB

The Journey of SimpleDB (Still Living)

  • December 2007: Amazon SimpleDB private beta launch.
  • December 2008: Amazon SimpleDB GA.
  • January 2012: Amazon DynamoDB GA. The NoSQL protagonist changes.
  • July 2024: New use of Amazon SimpleDB ended
  • March 2026: A surprising new feature addition ← New!

By the way, it went 18 years without ever appearing in the Management Console

A new feature at year 18

  • New APIs: GetExport, ListExports, StartDomainExport
  • New CLI namespace: simpledbv2
  • No additional charge for the export itself; charges apply for S3 data transfer and storage usage

https://dev.classmethod.jp/articles/amazon-simpledb-domain-export-to-s3/

Lesson Two

The addition of an export feature is the packing up of belongings in preparation for closure

Utakata-in Kannō Bakushu-koji SBS

2015 − 2024 (GitHub archived)

Naturally Beloved SBS

sbslogo

SBS = Simple Beer Service🍺

  • Cloud-connected beer server made by awslabs (2015)
  • Flow rate, temperature, humidity, volume, proximity sensors → AWS IoT → Dashboard
  • Final release v5.0 was in 2016. Buried (archived) in 2024.

https://aws.amazon.com/blogs/startups/internet-of-beer-introducing-simple-beer-service/

Up to here, it's a typical end-of-service story. However——

The electrocardiogram is moving

スクリーンショット 2026-07-17 15.29.08

The graphs are moving in New York and San Francisco!!!

The site is still operational. At some locations, sensor data continues to flow in real time

In other words, at this very moment, somewhere on Earth, a beer server that no one is taking care of may still be sending data to AWS.

Frightening, isn't it? Terrifying, isn't it?

Lesson Three

Serverless, if you forget to stop it, lives forever (maybe?)

Summary

AWS end-of-service events follow a "pattern"

  1. Close the entrance —— Stop new registrations (No new customers accepted)
  2. Prepare the exit —— Export and migration support (The moving boxes arrive)
  3. End quietly —— Take 2 years from announcement (EC2-Classic style)
  4. Traces remain —— Configuration is forever (The belongings are never tidied up)

After Today's Memorial Service

What truly needs memorializing——

May be that test environment still running in your account.

Finally

I was reminded once again that cleanly ending a service is difficult. You may all face the end of services you are involved with someday. I hope there's no need to face it, but I hope this serves as a reference just in case.

Share this article

AWSのお困り事はクラスメソッドへ