AWS Amplify Gen 2 Environment Setup
Setting up the operating environment for AWS Amplify Gen 2. I already have the development folder and am starting from the sandbox launch. These past few days, I've been verifying the synchronization between this local sandbox environment and CloudFormation. That is, confirming that the content written in files like backend.ts and the resource.ts files within resources such as auth and data inside the amplify folder are reflected in CloudFormation.
So far, I haven't been able to confirm this reflection (although, when the sandbox launches, the local configuration is correctly built in CloudFormation).
I was able to confirm that DynamoDB is initialized for the first time when using the data resource. Previously, it was only Cognito with the auth resource.
One tip I've learned is that while I previously used Gemini or technical blog posts as a reference for configuration file content (or rather, copied and pasted it), copying and pasting the sample code from the official AWS website is what ultimately worked.
In my experience, AI often provides incorrect information regarding AWS configuration, which frequently leads to being stuck. This is likely because there are many updates to the configuration methods, making it difficult for the AI to keep up with the latest information.
Going forward, since I haven't yet memorized how to write these Amplify files, I will use technical blogs as a reference to learn. The workflow will be: write the configuration, check if it's updated within CloudFormation, and then verify if the application in the development environment performs the intended action.
Looking slightly ahead, the goal is to be able to quickly iterate through the cycle of idea generation, development, production deployment, and improvement. Using Amplify should allow me to do this quickly. I aim to complete this environment setup, ideally by around the end of November. For what I'm doing now, I'm documenting the steps as thoroughly as possible.
Top comments (0)