Open jhoffmcd opened 5 years ago
Hm yeah, I'm just starting with Amplify and I hit this too, not sure why it didn't ask for the project name during amplify init
— but it seems like amplify configure project
will step you through re-editing the config.
This command has some documentation here:
https://aws-amplify.github.io/docs/cli-toolchain/quickstart#multiple-frontends
I know this answer as I too hit this wall of default name of my-aws-project fix after installing before AWS 1 Amplify configure New user (Iam role ) get secret keys and install them 2 next window up will say profile name make sure you use your existing profile then next window up will ask for project name If you just use default it seems to jump past this step and uses my-aws-project
Hope that helps
I just tested this starter out and it works great, however the
amplify init
did not ask for a project name, so the CLI tool provisioned everything asmy-aws-project
. Trying to change the project named seemed to end up in a various states of error.Proposal would be to update the documentation to show where to change that project name before running
amplify init
or linking to documentation from Amplify that shows a step by step how to change project name and reprovision. I was looking for something here but was not able to find something specific: https://aws-amplify.github.io/docs/cli/init#amplify-configure-project