Amazon web services – Automated Elastic Beanstalk deployment of dotnet application fails on both CodePipeline and GitHub Actions, but works manually

I’m trying to set up automated deployment of my .NET Core API application to an existing EB environment. I’m currently deploying manually via the AWS Toolkit (Publish to AWS) extension for Visual Studio, which works completely fine. But every time I try to set up seemingly any CI/CD pipeline, I get this exact same ERROR message after the "Added instance [i-0adf163e55a825fa9] to your environment." stage:

06:10:39 ERROR: Error occurred during build: Command hooks failed
06:10:44 ERROR: [Instance: i-0adf163e55a825fa9 ConfigSet: Infra-EmbeddedPreBuild, Hook-PostInit, Hook-PreAppDeploy, Infra-EmbeddedPostBuild, Hook-EnactAppDeploy, Hook-PostAppDeploy, Infra-WriteVersionOnStartup] Command failed on instance. Return code: 1 Output: null.
06:10:44 INFO: Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
06:10:44 ERROR: Unsuccessful command execution on instance id(s) 'i-0adf163e55a825fa9'. Aborting the operation.
06:10:44 ERROR: Failed to deploy application.
06:10:45 ERROR: Deployment failed! Current State: Version: v-638557011188113073, Health: Yellow, Health Status: Warning

I’ve tried looking at the last 100 lines of logs in the EB dashboard, as well as comb through my S3 bucket, but nothing in those logs match up with the date and time of when I receive the error messages (trying to take timezones into account too). I think I’ve gone through 12 different guides on how to setup a pipeline specifically for ASP.NET Core applications and they’ve all failed, mostly because they’re all outdated and do not match with AWS’ current interface. What am I missing?

GitHub Workflow file:

name: Deploy to Elastic Beanstalk

on:
  push:
    branches:
      - main

jobs:
  build-and-deploy:
    runs-on: windows-2019
    steps:
      - name: Checkout Code
        uses: actions/checkout@v3

      - name: Setup .NET
        uses: actions/setup-dotnet@v3
        with:
          dotnet-version: '6.0.x'

      - name: Build and Publish
        working-directory: ./API
        run: dotnet restore && dotnet publish -c Release -o publish --self-contained "true"

      - name: Create Deployment Package
        uses: thedoctor0/[email protected]
        with:
          type: 'zip'
          filename: 'API.zip'
          path: |
            APIpublish

      - name: Deploy to Elastic Beanstalk
        uses: einaregilsson/beanstalk-deploy@v22
        with:
          aws_access_key: ${{ secrets.AWS_ACCESS_KEY_ID }}
          aws_secret_key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
          application_name: AppName
          environment_name: EnvironmentName
          version_label: ${{ github.sha }}
          region: ${{ secrets.AWS_REGION }}
          deployment_package: API.zip

–EDIT:

As Delta George suggested, I tried deploying through AWS CLI. It’s worth mentioning that my API project is located in my repo as a separate folder inside of my overall repository. My project structure looks therefore as follows:

Repo  
│
└── API
│   │   API.csproj
|   |   API.sln
│   │   appsettings.json
|   |   aws-beanstalk-tools-defaults.json
|   |   web.config
|   |   etc.
│
└── Frontend project

With that in mind, I ran the following commands individually to try an deploy my API project to my EB environment using AWS CLI (v2):

dotnet publish -c Release -o ./publish

cd .publish

zip -r ../API.zip *

cd ..

aws s3 cp API.zip s3://my-s3-bucket-name/Backend/

aws elasticbeanstalk create-application-version --application-name EBAppName --version-label 1234567890 --source-bundle S3Bucket="my-s3-bucket-name",S3Key="Backend/API.zip"

aws elasticbeanstalk update-environment --environment-name EBAppNameEnv --version-label 1234567890

All commands run successfully. But checking the EB "events" output during deployment, I can eventually see the same handful of error messages show up as mentioned at the top of this post.