Wehre can I find my .NET Core deployment on Elastic Beanstalk?

[Yossi Geretz]

I'm using this pipe to deploy my application to Elastic Beanstalk.

atlassian/aws-elasticbeanstalk-deploy:0.2.3

Everything succeeds, but after the deployment when I SSH into the EC2 server I can't -

a. Find the project deployment files

b. See my application running as a service.

There is a .NET application running on the server but it is NOT my application, rather it's the stock AWS Elastic Beanstalk page -

Welcome to Your Elastic Beanstalk Application

Congratulations! Your .NET Core application is now running on your own dedicated environment in the AWS Cloud.

OK, great, so I've got A .NET Core application running on that server, but where is MY .NET Core application?

[Yossi Geretz · Accepted solution]

The problem is COMMAND: 'deploy'. That is invalid. The correct syntax is COMMAND: 'all'.

(It would be nice if the pipeline execution would indicate that the command is invalid, but it doesn't. It just doesn't do anything.)

[Yossi Geretz]

This isn't an answer, but I didn't see any way to edit my original question.

Here are the pipeline steps which I am using to deploy my application. (Sorry for the lack of indentation. I couldn't see any way to preserve the indentation on the paste.)

custom:

staging-deployment:
- step: # Create the deployment zip file
name: "Agent API Deployment Zip"
caches:
- dotnetcore
script:
- apt-get update && apt-get install --yes zip
- export PROJECT_NAME=AgentAPI/AgentAPI.csproj
- dotnet restore $PROJECT_NAME
- dotnet build $PROJECT_NAME --configuration Release
- dotnet publish $PROJECT_NAME --configuration Release -r linux-x64 --self-contained true -o ./publish
- zip -r application.zip ./publish/*
artifacts:
- application.zip

- step: # Upload the zipped Admin API and deploy to EB
name: "Upload to S3 Bucket and Deploy to EB"
script:
- pipe: atlassian/aws-elasticbeanstalk-deploy:0.2.3
variables:
AWS_ACCESS_KEY_ID: ${AWS_ACCESS_KEY_ID}
AWS_SECRET_ACCESS_KEY: ${AWS_SECRET_ACCESS_KEY}
AWS_DEFAULT_REGION: ${AWS_DEFAULT_REGION}
APPLICATION_NAME: 'claravox-api-stage'
ENVIRONMENT_NAME: 'claravox-api-stage-env'
VERSION_LABEL: 'claravox-api-stage-$BITBUCKET_BUILD_NUMBER-$BITBUCKET_COMMIT'
COMMAND: 'deploy'
ZIP_FILE: 'application.zip'
S3_BUCKET: 'claravox-eb-deployment'
WAIT: 'true'