aws-amplify / aws-amplify/amplify-hosting

Build Process for Manual deployment of Amplify Console

Open
#2,112 2 comments 0 reactions 0 assignees View on GitHub
feature-request
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
As a developer, I want to trigger build when I manually deploy so that I can ship my application withiout Git provider.

**Describe the solution you'd like**
Add an option to build frontend or backend in a manual deployment app, and manual deployment should run settled build process.

**Additional context**
I heard from developers that they needed to use Amplify without Git provider because of the following three reasons:

- Required highly secured development environment
- Cost
- Less time for POC

But, it seems that currently manual deployment feature only allows us to deploy the built artifact, and build process does not run on Amplify.
Thus, they cannot set build process without git provider and hard to use Amplify for their development.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by reviewing the manual deployment flow and its current built-artifact boundary, then define how frontend and backend builds should be configured and what a successful build-and-deploy should produce.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
build-system, ci-cd, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.