Description
I just got this from the IAM Documentation team (first time I learned there is such a team!)
We chatted a while back about your Policy Sentry code in GitHub that scrapes the IAM Actions, resources, and condition keys documentation. We will delete those pages in 30 days and redirect traffic to the matching page in the new Service Authorization Reference.
Action item: Within the next 30 days, we recommend that you review the policy_sentry code and update it to scrape the new pages. The content format of these new pages and the HTML file names have not changed. If your code supports server redirects, then it should not be affected at all. However, we still recommend that you use the new URL.
Today:
- The existing Actions, resources, and condition keys pages include a new “Tip” box at the top of the page. The link in that paragraph takes you to the same page in the new guide. https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_actions-resources-contextkeys.html
- The new guide includes the same structure, file names, and content as the IAM User Guide. However, the table of contents (TOC) structure of the guide is different above the page. The IAM User Guide content is located at Reference > Policy reference > Actions, resources and condition keys. The new Service Authorization Reference content is located in Reference > Actions, resources and condition keys.
- You can begin testing your code using the new URL: https://docs.aws.amazon.com/service-authorization/latest/reference/reference.html.
On November 16:
- The AWS Docs server will begin permanently redirecting customers from the old page to the matching page in the new guide.
- The IAM User Guide TOC will still include the high-level Actions, resources, and condition keys page. Choosing that TOC entry redirects you to the new guide.
- On or before that date, we will remove the existing Actions, resources, and condition keys pages from GitHub.
If you have any questions or recommendations for documentation improvements, please let us know.
Thanks,
IAM Documentation
FYI - @aidansteele, @0xdabbad00