From 819507840f38ee5a6617c4be8c8dafd3bf0c31af Mon Sep 17 00:00:00 2001
From: Ed Costello <orthanc@users.noreply.github.com>
Date: Sat, 8 Jun 2019 02:59:58 +1200
Subject: [PATCH] Update links to AWS module guidelines to target the devel
 docsite since (#57465)

the GUIDELINES.md has been removed from devel on github.
---
 .../docsite/rst/dev_guide/developing_modules_best_practices.rst | 2 +-
 docs/docsite/rst/dev_guide/developing_modules_checklist.rst     | 2 +-
 docs/docsite/rst/dev_guide/index.rst                            | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst b/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst
index e18a6f36ae3..567642189bf 100644
--- a/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst
+++ b/docs/docsite/rst/dev_guide/developing_modules_best_practices.rst
@@ -160,7 +160,7 @@ Ansible conventions offer a predictable user interface across all modules, playb
 * Implement declarative operations (not CRUD) so the user can ignore existing state and focus on final state. For example, use ``started/stopped``, ``present/absent``.
 * Strive for a consistent final state (aka idempotency). If running your module twice in a row against the same system would result in two different states, see if you can redesign or rewrite to achieve consistent final state. If you can't, document the behavior and the reasons for it.
 * Provide consistent return values within the standard Ansible return structure, even if NA/None are used for keys normally returned under other options.
-* Follow additional guidelines that apply to families of modules if applicable. For example, AWS modules should follow `the Amazon guidelines <https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/amazon/GUIDELINES.md>`_
+* Follow additional guidelines that apply to families of modules if applicable. For example, AWS modules should follow `the Amazon guidelines <https://docs.ansible.com/ansible/devel/dev_guide/platforms/aws_guidelines.html>`_
 
 Module Security
 ===============
diff --git a/docs/docsite/rst/dev_guide/developing_modules_checklist.rst b/docs/docsite/rst/dev_guide/developing_modules_checklist.rst
index 6a3f39b0e7d..04b858d450c 100644
--- a/docs/docsite/rst/dev_guide/developing_modules_checklist.rst
+++ b/docs/docsite/rst/dev_guide/developing_modules_checklist.rst
@@ -40,5 +40,5 @@ Other checklists
 ================
 
 * :ref:`Tips for module development <developing_modules_best_practices>`.
-* `Amazon development checklist <https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/amazon/GUIDELINES.md>`_.
+* `Amazon development checklist <https://docs.ansible.com/ansible/devel/dev_guide/platforms/aws_guidelines.html>`_.
 * :ref:`Windows development checklist <developing_modules_general_windows>`.
diff --git a/docs/docsite/rst/dev_guide/index.rst b/docs/docsite/rst/dev_guide/index.rst
index c7c81cd32a6..9d3620e1043 100644
--- a/docs/docsite/rst/dev_guide/index.rst
+++ b/docs/docsite/rst/dev_guide/index.rst
@@ -24,7 +24,7 @@ Find the task that best describes what you want to do:
    * I want to :ref:`get started writing a module <developing_modules_general>`.
    * I want to :ref:`write a network module <developing_modules_network>`.
    * I want to :ref:`write a Windows module <developing_modules_general_windows>`.
-   * I want to `write an Amazon module <https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/cloud/amazon/GUIDELINES.md>`_.
+   * I want to `write an Amazon module <https://docs.ansible.com/ansible/devel/dev_guide/platforms/aws_guidelines.html>`_.
    * I want to :ref:`write a series of related modules <developing_modules_in_groups>` that integrate Ansible with a new product (for example, a database, cloud provider, network platform, etc.).
 
 * I want to refine my code: