Creating API models - is not authorized to perform: apigateway:GET

[RAISERALEX21]

Before creating a new issue, please confirm:

• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.

Which UI component?

Liveness

Gradle script dependencies

I'm working with AMPLIFY-UI-ANDROID/samples/liveness and following the setup guide ->
// amplify-ui-android/samples/liveness/README.md

To the above, I do not understand well what would be needed within my permissions or if I need to make another change from the aws console., I hope for your comments.

Environment information

Welcome to Gradle 8.2.1!

Here are the highlights of this release:

• Kotlin DSL: new reference documentation, assignment syntax by default
• Kotlin DSL is now the default with Gradle init
• Improved suggestions to resolve errors in console output
• Reduced sync memory consumption

For more details see https://docs.gradle.org/8.2.1/release-notes.html

---

Gradle 8.2.1

Build time: 2023-07-10 12:12:35 UTC
Revision: a38ec64d3c4612da9083cc506a1ccb212afeecaa

Kotlin: 1.8.20
Groovy: 3.0.17
Ant: Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM: 1.8.0_311 (Oracle Corporation 25.311-b11)
OS: Mac OS X 10.16 x86_64

Please include any relevant guides or documentation you're referencing

https://github.com/aws-amplify/amplify-ui-android/blob/main/samples/liveness/README.md

Describe the bug

The following screenshot shows the error:

But within my AWS console, I've added permissions to authorize my user. I'll attach a screenshot ->

Reproduction steps (if applicable)

where I'm encountering an issue within the step:
Provision Backend API -> 3. Once finished, run amplify push to publish your changes.

next -> amplify push -> error!!

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

amplifyconfiguration.json

{
"UserAgent": "aws-amplify-cli/2.0",
"Version": "1.0",
"auth": {
"plugins": {
"awsCognitoAuthPlugin": {
"UserAgent": "aws-amplify-cli/0.1.0",
"Version": "0.1.0",
"IdentityManager": {
"Default": {}
},
"CredentialsProvider": {
"CognitoIdentity": {
"Default": {
"PoolId": "us-east-1:9923229d-e322-4d23-bbf8-b22c8ed3a2c7",
"Region": "us-east-1"
}
}
},
"CognitoUserPool": {
"Default": {
"PoolId": "us-east-1_k4H5NZqDH",
"AppClientId": "5nhoomrfgc2visru2stud45bct",
"Region": "us-east-1"
}
},
"Auth": {
"Default": {
"OAuth": {
"WebDomain": "liveness70a2b540-70a2b540-dev.auth.us-east-1.amazoncognito.com",
"AppClientId": "5nhoomrfgc2visru2stud45bct",
"SignInRedirectURI": "myapp://callback/",
"SignOutRedirectURI": "myapp://signout/",
"Scopes": [
"phone",
"email",
"openid",
"profile",
"aws.cognito.signin.user.admin"
]
},
"authenticationFlowType": "USER_SRP_AUTH",
"socialProviders": [],
"usernameAttributes": [],
"signupAttributes": [
"EMAIL"
],
"passwordProtectionSettings": {
"passwordPolicyMinLength": 8,
"passwordPolicyCharacters": []
},
"mfaConfiguration": "OFF",
"mfaTypes": [
"SMS"
],
"verificationMechanisms": [
"EMAIL"
]
}
}
}
}
}
}

Additional information and screenshots

AMPLIFY VERSION :
12.11.1
DEVICE:
macOS - version 12.7.4

[mattcreaser]

Although this was encountered while setting up the Liveness sample, this error occurs when executing amplify push with the CLI and is not related to the UI component itself.

Transferring to the CLI repo for triage.

[ykethan]

Hey @RAISERALEX21, from the error message it appears this occurring on a IAM permission boundary set on the user the Amplify CLI is utilizing. Refer to this post providing additional information. I would suggest checking the boundary permissions and enable apigateway:GET to mitigate this behavior.

[RAISERALEX21]

I've been trying to enable the permission as shown in the images... but so far, I haven't been successful, and I don't really have much experience with AWS IAM. Could you specify the steps I would need to follow to enable it?

I share my console settings in IAM.. ->

[ykethan]

@RAISERALEX21 The permission boundary is a additional layer of security in IAM, the allow permission need to exist on both.
Refer to documentation on permission boundary.

The permissions boundary should be below the permissions policies section where you can add the necessary permmissions.

[RAISERALEX21]

I have been able to finish the setup now... but I have another issue. I think I will open another ticket... and thank you very much!!, you helped me a lot.

[ykethan]

@RAISERALEX21 Glad to hear I was able to assist you. Do reach out if you are experiencing any issue. Closing the issue.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.