Kethan sai

Hey👋 thanks for raising this! I'm going to transfer this over to our JS repository for better assistance 🙂

Hey,👋 thanks for raising this! I'm going to transfer this over to our Amplify JS repository for better assistance 🙂

Hey @ahsan2hashmi, thank you for reaching out. wanted to get some additional information on the issue. > the auth folder was also nested in some other folders and not in...

Hey @InfoPrince21, does the user profile have [AdministratorAccess-Amplify](https://docs.aws.amazon.com/amplify/latest/userguide/security-iam-awsmanpol.html#security-iam-awsmanpol-AdministratorAccess-Amplify) attached?

Hey @imortkz, thank you for reaching, marking this as feature-request to upgrade the default python runtime. From https://github.com/aws-amplify/amplify-cli/blob/6340adbb6f02e139128c712719d8054d8fab5ad1/packages/amplify-python-function-runtime-provider/src/util/buildUtils.ts#L10 you should be able to update the runtime in the CloudFormation template...

@imortkz the information is currently documented here: https://docs.amplify.aws/react/build-a-backend/functions/configure-options/#updating-the-runtime you will need to ensure the python version is installed locally as well for the push to build the function

Hey @mahimc367, thank you for reaching.Tried reproducing the issue using the following but did observe the references being populated. ```ts const dependencies: AmplifyDependentResourcesAttributes = AmplifyHelpers.addResourceDependency( this, amplifyResourceProps.category, amplifyResourceProps.resourceName, [ {...

Hey @mahimc367, was the Lambda resource pushed before adding the dependancy in the custom cdk resource? tried reproducing the issue on the latest Amplify CLI version but did not observe...

Hey @raphaelgrau, thank you for reaching out. The issue appears to similar to https://github.com/aws-amplify/amplify-cli/issues/13124. Refer to the comment https://github.com/aws-amplify/amplify-cli/issues/13124#issuecomment-1761930499 providing information on opening a support case on the AWS console.

@raphaelgrau thank you for the update. The behavior is currently occurring on the account which the support team should be able to assist you on this.