Manually deploy Amplify Gen2 project

[Bradley-Cooley]

Is this related to a new or existing framework?

No response

Is this related to a new or existing API?

No response

Is this related to another service?

Amplify Hosting

Describe the feature you'd like to request

I'd like to deploy a new Amplify Gen2 project without using the Amplify UI in the AWS Console to connect to a git provider. My project is in self-hosted Gitlab and there is no external access.

Describe the solution you'd like

I'd like to docs to provide a description of how to perform a first-time deploy of a Gen2 project without connecting to an external git provider, whether it is fairly easy via npx amplify or more difficult via AWS SDK.

Describe alternatives you've considered

I have considered temporarily putting my code on a different service provider in order to deploy - however, if I did so, I am unsure how I would change the configuration to only go back to manual deploys afterwards.

Additional context

No response

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

[nadetastic]

Hi @Bradley-Cooley thanks for opening this issue. I'm transferring this FR over to the backend repo for better assistance.

[swaminator]

@Bradley-Cooley the instructions are here: https://docs.amplify.aws/gen2/deploy-and-host/fullstack-branching/custom-pipelines/

[Bradley-Cooley]

So it seems that what I'm looking to do isn't possible yet. Correct me if I'm wrong -

1. According to the docs, you must use the web console to create an Amplify gen2 project the first time. I tried a few options for creating a gen2 project using aws amplify CLI and was unsuccessful - I was not able to create a gen2 project via the aws cli, only a gen1 project. That's fine, as a workaround I temporarily put my code into a private repo on github to create the gen2 project and then disabled auto-build. Via the aws cli I can create new branches as needed on that project and trigger backend deployments via amplify pipeline-deploy. It would be nice to not need to do this step though, and I'd imagine other people are more constrained and do not have the option to start a gen2 project by creating a git repo outside of their self-hosted solution.
2. It seems frontend deploys are not supported unless the repo is accessible. The docs point to webhooks as the solution for frontend builds and there does not seem to be an equivalent to amplify publish in the new amplify cli. I'd imagine the workaround here would again be usage of the aws cli to manually or via script upload the frontend build artifacts to S3 and use aws amplify create-deployment and aws amplify start-deployment pointing to the S3 bucket. This seems a fairly large burden to take on for custom pipelines. Is there currently any plan to support frontend deployments with amplify hosting for gen2?

[anbraten]

We are having the same issue with a private gitlab instance. We would somehow need a command that does a similar setup to what the "Connect to Github / Gitlab repo" button is doing.

What is the current state of this issue? Are there any plans to support manual creation of projects?

[moleCuleFFF]

+1 This is a blocker for me to upgrade from Gen 1 to Gen 2.

[abarke]

Really need this issue solved or GitLab EE support... either would suffice. Right now im using my sandbox for building the app locally then host manually on Amplify. At least that works 😅

Here are a few suggestions/thoughts: #2056 (comment)

[fireflysemantics]

Same here. Please also support the old workflow where we could run amplify publish against a local git branch.

[abarke]

So this is still not fixed? AWS Team, wake up guys and girls! You are pushing developers away by not supporting manual deployments or integration with GitLab EE. At least provide a workaround!? API access to automate deployments using any tool?

This issue is labelled as feature request 🤔 sounds like a serious bug/incident to me. Meanwhile, switching back to Supabase.