API Scheme: IAM deprecated warning, but documentation is not updated

[bergmorten]

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

12.7.1

What operating system are you using?

windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Nope

Describe the bug

When pushing amplify we get warning that our scheme is using IAM, but this is the method which is documented at amplify website.

⚠️ WARNING: Schema is using an @auth directive with deprecated provider 'iam'. Replace 'iam' provider with 'identityPool' provider.

You need to update documentation and enum AuthProvider at e.g. https://docs.amplify.aws/gen1/javascript/build-a-backend/graphqlapi/customize-authorization-rules/#how-it-works

Expected behavior

Documentation should not use deprecated auth methods

Reproduction steps

Make a scheme like the documentation suggest and push

Project Identifier

No response

Log output

``` # Put your logs below this line ```

Additional information

No response

Before submitting, please confirm:

• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• [X] I have removed any sensitive information from my code snippets and submission.

[ykethan]

Hey👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

[rickyadriell]

Any update on this? I'm encountering the same issue but couldn't find the update on Documentation.

Amplify version 12.12.0

[DanieleMoschiniMac]

Same here ✋

[sanderkollerie]

Same here

[chirpavel]

Agree, what does it mean? What to do? Migrating?

[SamsterJam]

Same here, I'm using IAM for lambda calling access and the userpool for user access, is this no longer supported and if so what is the alternative?