My development progress yesterday was that I managed to launch the AWS Amplify Gen2 sandbox within my local Next.js project — that part went well. A separate sandbox stack was created in AWS CloudFormation, apart from the CDKToolkit stack, which was good.
But after that, when I updated the local Amplify files, the command line showed that the files had been modified, yet nothing seemed to be reflected in the CloudFormation stack’s resources. Finally, I pressed Ctrl + C to stop the sandbox — it ended on the command line, but the CloudFormation stack was still there.
In other words, it seems like the connection between the local environment and AWS hasn’t been working properly after the initial launch.
Still, there was some progress — I hadn’t realized before that the Amplify sandbox actually keeps watching the local environment while it’s running. So even though I didn’t get it to work yesterday, it was good to learn how that mechanism works and to try it out.
Top comments (0)