Repository Deprecation | Q4 2024

[andrew-glenn]

Deprecation Notice

❌ A large number of projects are on a path to deprecation in Q4 2024. Affected projects have a README notice cross-referencing to this page. Those wishing to leverage an affected project beyond Q4 should clone the repository into their own S3 bucket(s).

No new production dependencies should be created

Beyond deprecation in 2024

What happens to the repository?

Post-deprecation, this repository will exist in a public/archived state.

It's already public/archived, and it was archived recently. What does that mean?

We added a notice to each repo's README.md file. To do so, in some cases, we needed to unarchive the repo, modify the README.md file, and re-archive. These repos were previously archived and we consider them already deprecated.

What about content in the public S3 buckets?

Content that's currently hosted in S3 buckets matching the following patterns will be unavailable beyond deprecation in Q4 2024.

aws-quickstart
aws-quickstart-<REGION_NAME>

aws-ia
aws-ia-<REGION_NAME>

Where do I direct feedback?

Feedback may be directed to quickstart <at> amazon <dot> com. Please tag your email subject with [Github Project Deprecation].