MarlonJD
commented
6 months ago I think I fixed this, I can fix this by adding these codes to backend.ts:
// Get the first resolver
const amplifyData = amplifyDataStack[0];
// Get resolvers from the first resolver
const connectionStack = amplifyData.node.children.filter((child) =>
child.node.id.includes("ConnectionStack")
);
// If the connectionStack has more than 500 resources
if (connectionStack[0].node.children.length > 500) {
console.log("All Resources Count:", connectionStack[0].node.children.length);
// Crete new nestedStacks every nestedStacks can hold 200 resources, each.
// connectionStack[0].node.children.length / 200 = number of nestedStacks
const nestedStacksCount = Math.ceil(
connectionStack[0].node.children.length / 200
);
console.log("Splitting, Nested Stacks Count:", nestedStacksCount);
for (let i = 0; i < nestedStacksCount; i++) {
const nestedStack = new NestedStack(
connectionStack[0],
`ConnectionStackSplit${i}`
);
// Get items with start i * 200 to (i + 1) * 200 resources
const startIndex = i * 200;
const endIndex = (i + 1) * 200;
// Add the resources to the nestedStack
connectionStack[0].node.children
.slice(startIndex, endIndex)
.forEach((child) => {
nestedStack.node.addDependency(child.node);
});
amplifyData.node.addDependency(nestedStack);
}
// Remove stack from the data stack
connectionStack[0].node.children.forEach((child) => {
connectionStack[0].node.tryRemoveChild(child.node.id);
});
}I'm still doing some tests, I'll let you know about news
AnilMaktala
LukaASoban
vinothj-aa
thomasoehri
How did you install the Amplify CLI?
nem
If applicable, what version of Node.js are you using?
v18.20.2
Amplify CLI Version
1.0.1
What operating system are you using?
MacOS
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Describe the bug
I have 60 models. I'm trying to migrate to Gen 2.
npx ampz sandboxcommand tried to push, then got this warning:then I tried to test reach limit and got error like this:
So, I was able to fix this limit issue by creating custom stacks for some resolvers like in documents, Place AppSync Resolvers in Custom-named Stacks. And I could fix template size limit issue by doing
amplify push --minifyI couldn't do these in Gen 2. So how can we fix this?
Just info: I saw this example to splitting stack with cdk, it may help this article I saw people could solve this issue when they're using
aws-cdkandserverless (framework)by using split-stacks.Expected behavior
Should update stack
Reproduction steps
Creating big schema will give this error. I added some test models like this. If models have much relations, it will started to increase resource counts quickly.
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm: