Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit on the number of resources in a single stack operation exceeded when enable flag "DynamoDBEnablePointInTimeRecovery" #1357

Open
2 tasks done
simoneagostinelli opened this issue Mar 16, 2023 · 2 comments
Assignees
Labels
bug Something isn't working duplicate This issue or pull request already exists graphql-transformer-v1 p3 transferred

Comments

@simoneagostinelli
Copy link

How did you install the Amplify CLI?

npm

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

14.17.0

Amplify CLI Version

10.3.2

What operating system are you using?

Ubuntu

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

I have a lot of tables (175), when i enable the flag "DynamoDBEnablePointInTimeRecovery" in the api parameters json to enable bynamo point in time recovery, during the amplify push i get back the error

Embedded stack arn:aws:cloudformation:eu-west-1:280063554922:stack/amplify-aim-packagesaim-common-dev-153939-apiaim-5A0SAA8IK3WC-ConnectionStack2-TPDPMYES9Q41/fa5bb4c0-43ad-11ec-8962-06dd6ae7ce0f was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: Limit on the number of resources in a single stack operation exceeded

image

Expected behavior

dynamoBD tables should be migrated corrtly with no errors

Reproduction steps

  1. enter in amplify/backend/api/<api-name>/parameters.json
  2. add parameter "DynamoDBEnablePointInTimeRecovery": "true"
  3. run amplify push
  4. get back the error

Project Identifier

report-1678963964036.zip

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@josefaidt josefaidt assigned josefaidt and unassigned josefaidt Mar 21, 2023
@josefaidt josefaidt transferred this issue from aws-amplify/amplify-cli Mar 21, 2023
@AnilMaktala AnilMaktala self-assigned this Mar 21, 2023
@AnilMaktala
Copy link
Member

Hey @simoneagostinelli, Thank for your raising this. A similar issue has been reported on #32. We suggest referring to the [comment] (#32 (comment)) to check if it can assist in resolving the issue you reported.

@AnilMaktala AnilMaktala added pending-response duplicate This issue or pull request already exists and removed pending-triage labels Apr 10, 2023
@simoneagostinelli
Copy link
Author

Hi Anil Maktala,
No that issue can't help me, I have the V1 transformer at the moment, and I already use the transform.conf.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists graphql-transformer-v1 p3 transferred
Projects
None yet
Development

No branches or pull requests

5 participants