DX - Host web app vs Create app backend

[omenking]

As a developer I have the following options when using the Amplify Console:

1. Frontend (Just use Amplify Console to host my client-side code)
2. Backend (Admin UI provides a managed backend without requiring me to write back-end code)
3. Frontend + Backend

So I wanted Amplify to take care of everything and wanted the 3rd option. I am presented with two options.

If you had to guess, which one do you think would take care of both the Frontend and the Backend?

I chose "Backend" because the Amplify Console's original offering was just Frontend hosting.
I also clicked into both due to uncertainty and when "Host Web app" asked to connect a repo, that made me think it was only frontend because a Frontend + Backend would be low-code and would not ask me too much upfront.

So I ended up creating the Backend, only to discover I had no Frontend.

There is no way to add a Frontend to a Backend, so then I had to create Hosted web app and had setup all of my Backend again...

[swaminator]

@omenking if you start down the route of creating a backend first, you will be able to then create and connect a new frontend. Were you not seeing a Frontend tab with the ability to connect a branch?

[vic-blt]

@omenking What you need is a fullstack amplify app.
For that, you need to click on Host web app.
Then you select your repository and you deploy it on Amplify.
The thing is, you have to version the file amplify/.config/project-config.json.
You can found an example here #448 (comment)
Otherwise your app won't be detected as fullstack, even if you have a frontend and a backend deployed.

[victorccccc]

Hi, we've improved our backend build feature, you can now configure the Amplify backend across apps. Details can be found here: https://docs.aws.amazon.com/amplify/latest/userguide/reuse-backends.html

Feel free to re-open this issue if you have any question. Thanks!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.