GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Announcements about S3 BitTorrent discontinuation shouldn't be buried in the commit history · Issue #27 · awsdocs/amazon-s3-userguide

This repository was archived by the owner on Jun 28, 2023. It is now read-only.
This repository was archived by the owner on Jun 28, 2023. It is now read-only.

Announcements about S3 BitTorrent discontinuation shouldn't be buried in the commit history #27

Copy link
Copy link
Closed
Closed
Announcements about S3 BitTorrent discontinuation shouldn't be buried in the commit history#27
Copy link
Assignees
aws-alan
Labels
archived

Description

@alexwlchan
alexwlchan
opened on Jun 8, 2021
Issue body actions

Commit 0d17598 (13 May) announced the deprecation plan for S3 BitTorrent:

# doc_source/S3Torrent.md
+ As of April 29, 2021 Amazon S3 is discontinuing the S3 BitTorrent feature and it will no
+ longer be available to enable\. AWS will support customers currently using the
+ S3 BitTorrent feature for 12 months\. After April 29, 2022, BitTorrent clients will
+ no longer connect to Amazon S3\.

The entire page was then removed in commit 7a83e40 (19 May).

At present, the discontinuation notice doesn't appear anywhere in the S3 documentation; all mention of BitTorrent has been completely removed. If somebody is wondering if this feature is still supported or for how much longer it'll be available, that's pretty difficult to find right now.

It would be helpful if there was a page with this warning as part of the S3 documentation, so people could find this information more easily than poking through the commit history.

Reacted by Gerben van der Stouwe, Ian Mckay, Albert, Harish Ved, Conrad Lara, Max Turck and Scottpedia

Activity

  1. aws-alan
    self-assigned this
    on Jun 8, 2021
  2. scottpedia commented on Sep 23, 2021

    @scottpedia
    scottpedia
    on Sep 23, 2021
    More actions

    @alexwlchan

    Hello

    But it seems to me that still the official docs site doesn't cover the deprecation at all. In addition, there is a misleading article that talks about how to get the torrent for a specific object, which you can find here. We need to remove similar misleading articles and possibly add permanent notice on the site to tell developers not to use this deprecated service.

  3. scottpedia commented on Sep 24, 2021

    @scottpedia
    scottpedia
    on Sep 24, 2021
    More actions

    @alexwlchan

    Is it possible that the AWS changed its mind between May 13 and 19, and retracted the announcement?

  4. alexwlchan commented on Sep 26, 2021

    @alexwlchan
    alexwlchan
    on Sep 26, 2021
    Author
    More actions

    there is a misleading article that talks about how to get the torrent for a specific object, which you can find here. We need to remove similar misleading articles

    I don't think that's too misleading, it's describing how to use the S3 BitTorrent APIs – which will presumably continue to work until next April.

    and possibly add permanent notice on the site to tell developers not to use this deprecated service.

    Yes, that's what I'm asking for.

    Is it possible that the AWS changed its mind between May 13 and 19, and retracted the announcement?

    I'd be very surprised if they did, and if they did, I'd expect them to have restored the feature page for S3 BitTorrent.

  5. joshbean
    added
    archived
    on Jun 28, 2023
  6. joshbean commented on Jun 28, 2023

    @joshbean
    joshbean
    on Jun 28, 2023
    Contributor
    More actions

    Closing this issue or pull request in advance of archiving this repo. For more information about the decision to archive this repo (and others in the "awsdocs" org), see the announcement on the AWS News Blog.

  7. joshbean
    closed this as completedon Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @aws-alan
    aws-alan

Labels

archived

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.