#✅ - Deploy AWS Amplify

18 messages · Page 1 of 1 (latest)

marble stirrup
#

Hey guys, I'm facing this issue with my site's deployment on AWS Amplify. However, I don't have much information about the real problem. Has anyone experienced something similar?

2023-08-10T11:42:25 [INFO]: Skipping deploy of existing file wiki/docusaurus-mdx-guide/table-of-contents/index.html
2023-08-10T11:42:25 [INFO]: Skipping deploy of existing file wiki/docusaurus-mdx-guide/tabs/index.html
2023-08-10T11:42:25 [INFO]: Skipping deploy of existing file wiki/docusaurus-mdx-guide/video/index.html
2023-08-10T11:42:25 [INFO]: Skipping deploy of existing file wiki/index.html
2023-08-10T11:42:25 [INFO]: Skipping deploy of existing file wiki/working-with-docusaurus/index.html
2023-08-10T11:42:25 [INFO]: Updating Edge config
2023-08-10T11:42:26 [ERROR]: Failed to deploy

When I do a manual deployment, that is, when I manually import the package, the deployment is carried out.

2023-08-10T11:43:35 [INFO]: Starting Deployment
2023-08-10T11:43:35 [INFO]: Updating Edge config
023-08-10T11:43:35 [INFO]: Beginning deployment for application dzy01yjm2a62s, branch:eng-197-2-2-0, buildId 0000000012
2023-08-10T11:43:35 [INFO]: Got archive: 25283872 bytes
2023-08-10T11:43:46 [INFO]: Deployment complete
marble stirrup
#

Amazon account # 938552245792
I'm not on the free tier

fathom compass
#

Can you please confirm which type of manual deployment are you using for your app?

  • Drag and drop the folder
  • Drag and drop the zip file of the build artifacts
  • Amazon S3
  • Public URL
marble stirrup
#

my original deployment is using AWS CLI and it doesn't work, however if in the same branch I use Drag and drop the zip file of the build artifacts it works

fathom compass
#

Oh I see, in that case were you running amplify publish via the AWS CLI?

marble stirrup
#

aws amplify start-deployment --app-id $APP_ID_AMPLIFY --branch-name $BRANCH_NAME --source-url $S3_PRESIGN_URL

fathom compass
#

Okay got it, yeah the start-deployment API/CLI uses the source-url or the Public URL method which uses a S3 presigned URL.

#

We are aware of issues with the source-url method of manual deployments and have identified it as a bug.

#

Our recommendation would be to either upload the build artifacts via the zip file or use the Amazon S3 method to deploy your app.

marble stirrup
#

I understand, but all this was done via CI/CD, I'm going to have to change the implementation, but that's ok.

fathom compass
#

I can completely understand John and I am curious to understand your use case of using manual deploys with CI/CD because we do provide a git based worklow for hosting your frontend and backend environments: https://docs.aws.amazon.com/amplify/latest/userguide/deploy-backend.html#step-1-deploy-frontend

Getting started with fullstack continuous deployments - AWS Amplify...

Amplify Hosting enables developers building apps with the Amplify Framework to continuously deploy updates to their backend and frontend on every code commit. With Amplify Hosting, you can deploy serverless backends with GraphQL/REST APIs, authentication, analytics, and storage, created using Amplify Studio, on the same commit as your frontend c...

marble stirrup
#

ah that's due to my GitLab being self-managed and there isn't a flow for that yet.

#

If there is any workaround on how to enable git deployment with GitLab self-managed I would like to know.

fathom compass
#

Gotcha yeah, thanks for sharing that use case. Unfortunately, today we do not support self managed GitLab or GitHub repositories via the CI/CD git deployment but I am definitely going to be sharing this feedback internally with the team.

silent shoalBOT
#

✅ - Deploy AWS Amplify