How to split Amplify project into multiple stacks. Error - Limit on the number of resources in a single stack operation exceeded

[BBopanna]

How did you install the Amplify CLI?

npm

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

v18.17.1

Amplify CLI Version

12.0.3

What operating system are you using?

Mac

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

NO

Describe the bug

We are getting this error on an amplify project - "Limit on the number of resources in a single stack operation exceeded".

Question is simple - How to split Amplify project into multiple stacks. Are there any documentation with references/examples ?

Expected behavior

References/Documentation on - "How to split Amplify project into multiple stacks"

Reproduction steps

Create an amplify project with AppSync GraphyQL API with 50+ entities and add around 6+ custom resource which build around 30 custom resolvers and try to amplify push to get the error - "Limit on the number of resources in a single stack operation exceeded"

Project Identifier

No response

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.

[ykethan]

Hey @BBopanna, thank you for reaching out. Currently, GraphQL API does provides support for splitting resolvers into custom named stack; documentation.

[BBopanna]

Thankyou - problem seems to be around large number of custom resources added in amplify cdk - https://docs.amplify.aws/react/build-a-backend/graphqlapi/modify-amplify-generated-resources/#place-appsync-resolvers-in-custom-named-stacks

Is there a way to break custom resources added via amplify cdk into multiple stacks ?

[ykethan]

@BBopanna , it is currently not supported to split the custom resource. From the number of resources provided on custom, the issue may be due to the number of resolvers on the GraphQL API.

[BBopanna]

Is there a way to create a new stack in the cdk part of amplify ?

This documentation talks about it when working entirely using cdk - https://docs.aws.amazon.com/cdk/v2/guide/stack_how_to_create_multiple_stacks.html

Is this possible in cdk part of amplify ?

Also use dependOn (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-dependson.html) - may be ?

stack1.node.addDependency(stack2)

[ykethan]

@BBopanna tried creating nested and creating a dependOn with a new stack but i have not been able to split the resource.

Examples tried:

const nst = new NestedStack(this, "nstsk", {});
this.node.addDependency(nst);

class NestedStack extends cdk.NestedStack {
  constructor(scope: Construct, id: string, props?: cdk.NestedStackProps) {
    super(scope, id, props);

    // Define resources for the nested stack here
    new cdk.aws_s3.Bucket(this, "MyBucket");
  }
}

push ran into TemplateURL must be a supported URL.

also tried

this.node.addDependency(cdkStack1);

export class cdkStack1 extends cdk.Stack {
  constructor(
    scope: Construct,
    id: string,
    props?: cdk.StackProps,
    amplifyResourceProps?: AmplifyHelpers.AmplifyResourceProps
  ) {
    super(scope, id, props);
    /* Do not remove - Amplify CLI automatically injects the current deployment environment in this input parameter */
    new cdk.CfnParameter(this, "env", {
      type: "String",
      description: "Current Amplify CLI env name",
    });

    const amplifyProjectInfo = AmplifyHelpers.getProjectInfo();
    const sqsQueueResourceNamePrefix = `sqs-queue-stack1test`;
    const queue = new sqs.Queue(this, "sqs-queue-stack1", {
      queueName: `${sqsQueueResourceNamePrefix}-${cdk.Fn.ref("env")}`,
    });
  }
}

If the use case requires creating custom resources, I would suggest Amplify Gen 2 or using pure cdk with Amplify GraphQL API construct as an workaround.

[BBopanna]

Thankyou @ykethan for trying it out and sharing few more valuable resources - We are on Amplify Gen 1 - what are the possible ways we could go about now that you have mentioned that attempting to add new stack in amplify cdk is not working out ? Please advise.