docs(aws): revamp aws docs + iam role anywhere profile

[sicoyle]

Please follow this checklist before submitting:

• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• Read the contribution guide
• Commands include options for Linux, MacOS, and Windows within codetabs
• New file and folder names are globally unique
• Page references use shortcodes instead of markdown or URL links
• Images use HTML style and have alternative text
• Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:

Description

• Bring changes from docs: update fields as they are optional #4371 to v1.15 docs.

• Revamp AWS docs given the complete refactor of things from the following contrib PRs:
  feat(kafka): iam roles anywhere + assume role auth profiles components-contrib#3606
  feat(postgres): add iam roles anywhere auth profile components-contrib#3604
  feat(iam auth): allow iam roles anywhere auth profile components-contrib#3591
  fix get aws creds from environment components-contrib#3617

• Add new auth profiles for assuming an IAM role and for roles anywhere

Issue reference

#4130

[sicoyle]

is there a way i can view the results of my changes somewhere in the PR @hhunter-ms ?

[hhunter-ms]

quick review - thanks @sicoyle!

[hhunter-ms]

is there a way i can view the results of my changes somewhere in the PR @hhunter-ms ?

@sicoyle there are a couple of ways to preview the docs site with your changes:

• open a PR from upstream instead of your fork. I did this for easier review of the conversation api PR
• if you can't do that, you can build the docs site locally using these instructions

[sicoyle]

do I need to do anything else to get this merged @hhunter-ms ?

[hhunter-ms]

do I need to do anything else to get this merged @hhunter-ms ?

@sicoyle I'm just waiting for a quick review from @msfussell - should be merged today!

[msfussell]

LGTM

[msfussell]

Left a few comments

[msfussell]

Is this comment correct about Dapr v1.17? Do you mean v1.16 the next release?

[hhunter-ms]

@msfussell I left a comment about this too - here's @sicoyle's response: #4456 (comment)

[sicoyle]

yes, so it's 1.17 bc we're deprecating all aws prefixed fields. So, I've marked accessKey and secretKey as not required to help support the transition, so the docs are denoted and the metadata bundle as well to state that it will be required in dapr 1.17 as we rm the duplicate fields that had the aws prefix, and then the accessKey and secretKey fields can become required again.