Update legacy documentation links (#4722)

* Update legacy botocore documentation links

* Update legacy boto3 documentation links

* Update fragment based links to new URL structure

Author: alexgromero

.changes/1.4.0.json

@@ -26,7 +26,7 @@
   }, 
   {
     "category": "s3", 
-    "description": "Port ``s3.transfer`` module to use ``s3transfer`` package. Please refer to `Upgrading Notes <https://boto3.amazonaws.com/v1/documentation/api/latest/guide/upgrading.html>`_ when upgrading. In porting the logic over, various performance issues and bugs were fixed.", 
+    "description": "Port ``s3.transfer`` module to use ``s3transfer`` package. Please refer to `Upgrading Notes <https://docs.aws.amazon.com/boto3/latest/guide/upgrading.html>`_ when upgrading. In porting the logic over, various performance issues and bugs were fixed.",
     "type": "bugfix"
   }, 
   {

.changes/1.9.0.json

@@ -11,12 +11,12 @@
   }, 
   {
     "category": "Events", 
-    "description": "[``botocore``] This migrates the event system to using sevice ids instead of either client name or endpoint prefix. This prevents issues that might arise when a service changes their endpoint prefix, also fixes a long-standing bug where you could not register an event to a particular service if it happened to share its endpoint prefix with another service (e.g. ``autoscaling`` and ``application-autoscaling`` both use the endpoint prefix ``autoscaling``). Please see the `upgrade notes <https://botocore.amazonaws.com/v1/documentation/api/latest/index.html#upgrade-notes>`_ to determine if you are impacted and how to proceed if you are.", 
+    "description": "[``botocore``] This migrates the event system to using sevice ids instead of either client name or endpoint prefix. This prevents issues that might arise when a service changes their endpoint prefix, also fixes a long-standing bug where you could not register an event to a particular service if it happened to share its endpoint prefix with another service (e.g. ``autoscaling`` and ``application-autoscaling`` both use the endpoint prefix ``autoscaling``). Please see the `upgrade notes <https://docs.aws.amazon.com/botocore/latest/#upgrade-notes>`_ to determine if you are impacted and how to proceed if you are.",
     "type": "feature"
   }, 
   {
     "category": "Events", 
-    "description": "This migrates the event system to using sevice ids instead of either client name or endpoint prefix. This prevents issues that might arise when a service changes their endpoint prefix, also fixes a long-standing bug where you could not register an event to a particular service if it happened to share its endpoint prefix with another service (e.g. ``autoscaling`` and ``application-autoscaling`` both use the endpoint prefix ``autoscaling``). Please see the `upgrade notes <https://boto3.amazonaws.com/v1/documentation/api/latest/guide/upgrading.html>`_ to determine if you are impacted and how to proceed if you are.", 
+    "description": "This migrates the event system to using sevice ids instead of either client name or endpoint prefix. This prevents issues that might arise when a service changes their endpoint prefix, also fixes a long-standing bug where you could not register an event to a particular service if it happened to share its endpoint prefix with another service (e.g. ``autoscaling`` and ``application-autoscaling`` both use the endpoint prefix ``autoscaling``). Please see the `upgrade notes <https://docs.aws.amazon.com/boto3/latest/guide/upgrading.html>`_ to determine if you are impacted and how to proceed if you are.",
     "type": "feature"
   }
 ]

CHANGELOG.rst

@@ -18710,8 +18710,8 @@ AWS Marketplace OfferSets support for opportunities
 
 * api-change:``logs``: [``botocore``] Update logs client to latest version
 * api-change:``config``: [``botocore``] Update config client to latest version
-* feature:Events: [``botocore``] This migrates the event system to using sevice ids instead of either client name or endpoint prefix. This prevents issues that might arise when a service changes their endpoint prefix, also fixes a long-standing bug where you could not register an event to a particular service if it happened to share its endpoint prefix with another service (e.g. ``autoscaling`` and ``application-autoscaling`` both use the endpoint prefix ``autoscaling``). Please see the `upgrade notes <https://botocore.amazonaws.com/v1/documentation/api/latest/index.html#upgrade-notes>`_ to determine if you are impacted and how to proceed if you are.
-* feature:Events: This migrates the event system to using sevice ids instead of either client name or endpoint prefix. This prevents issues that might arise when a service changes their endpoint prefix, also fixes a long-standing bug where you could not register an event to a particular service if it happened to share its endpoint prefix with another service (e.g. ``autoscaling`` and ``application-autoscaling`` both use the endpoint prefix ``autoscaling``). Please see the `upgrade notes <https://boto3.amazonaws.com/v1/documentation/api/latest/guide/upgrading.html>`_ to determine if you are impacted and how to proceed if you are.
+* feature:Events: [``botocore``] This migrates the event system to using sevice ids instead of either client name or endpoint prefix. This prevents issues that might arise when a service changes their endpoint prefix, also fixes a long-standing bug where you could not register an event to a particular service if it happened to share its endpoint prefix with another service (e.g. ``autoscaling`` and ``application-autoscaling`` both use the endpoint prefix ``autoscaling``). Please see the `upgrade notes <https://docs.aws.amazon.com/botocore/latest/#upgrade-notes>`_ to determine if you are impacted and how to proceed if you are.
+* feature:Events: This migrates the event system to using sevice ids instead of either client name or endpoint prefix. This prevents issues that might arise when a service changes their endpoint prefix, also fixes a long-standing bug where you could not register an event to a particular service if it happened to share its endpoint prefix with another service (e.g. ``autoscaling`` and ``application-autoscaling`` both use the endpoint prefix ``autoscaling``). Please see the `upgrade notes <https://docs.aws.amazon.com/boto3/latest/guide/upgrading.html>`_ to determine if you are impacted and how to proceed if you are.
 
 
 1.8.9
@@ -19985,7 +19985,7 @@ AWS Marketplace OfferSets support for opportunities
 * bugfix:Session: Fixed Session.__repr__ region argument name.
 * feature:s3: Add managed copies to S3 client, Bucket, and Object.
 * feature:s3: Add managed downloads to file-like objects in the S3 client, Bucket, and Object.
-* bugfix:s3: Port ``s3.transfer`` module to use ``s3transfer`` package. Please refer to `Upgrading Notes <https://boto3.amazonaws.com/v1/documentation/api/latest/guide/upgrading.html>`_ when upgrading. In porting the logic over, various performance issues and bugs were fixed.
+* bugfix:s3: Port ``s3.transfer`` module to use ``s3transfer`` package. Please refer to `Upgrading Notes <https://docs.aws.amazon.com/boto3/latest/guide/upgrading.html>`_ when upgrading. In porting the logic over, various performance issues and bugs were fixed.
 * feature:s3: Add ``io_chunksize`` parameter to ``TransferConfig``
 
 

CONTRIBUTING.rst

@@ -1,5 +1,5 @@
 For more information, please see the official docs at
-https://boto3.amazonaws.com/v1/documentation/api/latest/index.html
+https://docs.aws.amazon.com/boto3/latest/
 
 Contributing Code
 -----------------

README.rst

@@ -29,7 +29,7 @@ For more information on deprecations, see this
 `blog post <https://aws.amazon.com/blogs/developer/python-support-policy-updates-for-aws-sdks-and-tools/>`__.
 
 .. _boto: https://docs.pythonboto.org/
-.. _`doc site`: https://boto3.amazonaws.com/v1/documentation/api/latest/index.html
+.. _`doc site`: https://docs.aws.amazon.com/boto3/latest/
 .. _`Amazon Web Services`: https://aws.amazon.com/what-is-aws/
 .. |Python| image:: https://img.shields.io/pypi/pyversions/boto3.svg?style=flat
     :target: https://pypi.python.org/pypi/boto3/
@@ -87,7 +87,7 @@ Then, set up a default region (in e.g. ``~/.aws/config``):
    [default]
    region = us-east-1
 
-Other credential configuration methods can be found `here <https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html>`__
+Other credential configuration methods can be found `here <https://docs.aws.amazon.com/boto3/latest/guide/credentials.html>`__
 
 Then, from a Python interpreter:
 

boto3/docs/service.py

@@ -50,8 +50,7 @@ def __init__(self, service_name, session, root_docs_path):
         ]
         self._root_docs_path = root_docs_path
         self._USER_GUIDE_LINK = (
-            'https://boto3.amazonaws.com/'
-            'v1/documentation/api/latest/guide/resources.html'
+            'https://docs.aws.amazon.com/boto3/latest/guide/resources.html'
         )
 
     def document_service(self):

boto3/session.py

@@ -307,7 +307,7 @@ def client(
             over environment variables and configuration values, but not over
             a region_name value passed explicitly to the method. See
             `botocore config documentation
-            <https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html>`_
+            <https://docs.aws.amazon.com/botocore/latest/reference/config.html>`_
             for more details.
 
         :type aws_account_id: string
@@ -416,7 +416,7 @@ def resource(
             user_agent_extra is specified in the client config, it overrides
             the default user_agent_extra provided by the resource API. See
             `botocore config documentation
-            <https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html>`_
+            <https://docs.aws.amazon.com/botocore/latest/reference/config.html>`_
             for more details.
 
         :return: Subclass of :py:class:`~boto3.resources.base.ServiceResource`

docs/README.rst

@@ -1,6 +1,6 @@
 Boto3 Documentation
 ~~~~~~~~~~~~~~~~~~~
-Documentation for boto3 can be found `here <https://boto3.amazonaws.com/v1/documentation/api/latest/index.html>`_.
+Documentation for boto3 can be found `here <https://docs.aws.amazon.com/boto3/latest/>`_.
 
 Generating Documentation
 ~~~~~~~~~~~~~~~~~~~~~~~~

docs/source/guide/clients.rst

@@ -161,4 +161,4 @@ General Example
         with ThreadPoolExecutor(max_workers=8) as executor:
             futures = [executor.submit(do_s3_task, s3_client, task) for task in my_tasks]
 
-.. _Botocore Events: https://botocore.amazonaws.com/v1/documentation/api/latest/topics/events.html
+.. _Botocore Events: https://docs.aws.amazon.com/botocore/latest/topics/events.html

docs/source/guide/configuration.rst

@@ -24,13 +24,13 @@ This option is for configuring client-specific configurations that affect the be
 
 * ``region_name`` (string) - The AWS Region used in instantiating the client. If used, this takes precedence over environment variable and configuration file values. But it doesn't overwrite a ``region_name`` value *explicitly* passed to individual service methods.
 * ``signature_version`` (string) - The signature version used when signing requests. Note that the default version is Signature Version 4. If you're using a presigned URL with an expiry of greater than 7 days, you should specify Signature Version 2.
-* ``s3`` (related configurations; dictionary) - Amazon S3 service-specific configurations. For more information, see the `Botocore config reference <https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html>`_.
+* ``s3`` (related configurations; dictionary) - Amazon S3 service-specific configurations. For more information, see the `Botocore config reference <https://docs.aws.amazon.com/botocore/latest/reference/config.html>`_.
 * ``proxies`` (dictionary) - Each entry maps a protocol name to the proxy server Boto3 should use to communicate using that protocol. See :ref:`specify_proxies` for more information.
 * ``proxies_config`` (dictionary) - Additional proxy configuration settings. For more information, see :ref:`configure_proxies`.
 * ``retries`` (dictionary) - Client retry behavior configuration options that include retry mode and maximum retry attempts. For more information, see the :ref:`guide_retries` guide.  
 
 
-For more information about additional options, or for a complete list of options, see the `Config reference <https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html>`_.
+For more information about additional options, or for a complete list of options, see the `Config reference <https://docs.aws.amazon.com/botocore/latest/reference/config.html>`_.
 
 To set these configuration options, create a ``Config`` object with the options you want, and then pass them into your client.
 
@@ -89,7 +89,7 @@ Alternatively, you can use the ``HTTP_PROXY`` and ``HTTPS_PROXY`` environment va
 
 Configuring proxies
 '''''''''''''''''''
-You can configure how Boto3 uses proxies by specifying the ``proxies_config`` option, which is a dictionary that specifies the values of several proxy options by name.  There are three keys in this dictionary: ``proxy_ca_bundle``, ``proxy_client_cert``, and ``proxy_use_forwarding_for_https``. For more information about these keys, see the `Botocore config reference <https://botocore.amazonaws.com/v1/documentation/api/latest/reference/config.html#botocore.config.Config>`_.
+You can configure how Boto3 uses proxies by specifying the ``proxies_config`` option, which is a dictionary that specifies the values of several proxy options by name.  There are three keys in this dictionary: ``proxy_ca_bundle``, ``proxy_client_cert``, and ``proxy_use_forwarding_for_https``. For more information about these keys, see the `Botocore config reference <https://docs.aws.amazon.com/botocore/latest/reference/config.html#botocore.config.Config>`_.
 
 .. code-block:: python