amplify-category-api icon indicating copy to clipboard operation
amplify-category-api copied to clipboard

Published 20 hours ago • verified publisher icon aws-amplify

Deploy Fails due to OpenSearchStreamingLambdaIAMRoleDefaultPolicy exceeding policy size limit

Open MtthwBrwng opened this issue 2 years ago • 1 comments

How did you install the Amplify CLI?

npm

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

v16.18.1

Amplify CLI Version

v10.2.3

What operating system are you using?

Windows 10

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

No manual changes made

Describe the bug

When deploying my schema of about 51 models using @searchable it fails due to Maximum policy size of 10240 bytes exceeded for role on the OpenSearchStreamingLambdaIAMRoleDefaultPolicy

Expected behavior

I'd expect it to work. Currently the only error that the CLI reports back is Resource is not in the state stackUpdateComplete, nothing else. Making this issue initially very difficult to debug, it'd be nice if there were better errors associated with exceeding the policy size.

Reproduction steps

  1. Attempt to deploy with a schema with > 50 models using @searchable directive.

Project Identifier

ca840755b7c0c4fb9c6de6aef7a9ff72

Log output

# Put your logs below this line

Additional information

I'm hoping to find out if there is a way to specify my own policy for the OpenSearchStreamingLambdaIAMRoleDefaultPolicy as I'd be able to use wildcards and reduce the size. Currently my development is blocked.

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.

MtthwBrwng avatar Dec 31 '22 22:12 MtthwBrwng