Amazon Elastic Beanstalk deployment provider deploys single artifact to the Elastic Beanstalk application specified.
The packaging of the artifact to deploy depends on the type of project being built:
buildin YAML or check
Package Web Applications for AWS Elastic Beanstalk deploymentcheckbox under
MSBuildtab in the UI, as below.
Elastic Beanstalk packagetype is added in the UI under artifacts section or as below for yaml configuration
artifacts: - path: <path to artifact> type: ElasticBeanstalkPackage
Note: Unlike the AWS Toolkit for Visual Studio which can be used to create an application and environment from within the IDE, AppVeyor Elastic Beanstalk deployment relies on a pre-existing Elastic Beanstalk application and environment.
access_key_id) - AWS account access key.
secret_access_key) - AWS secret access key.
application_name) - Name of application (which should already exist) to update.
environment_name) - Name of the environment which is part of the above application.
region) - AWS region where the application is located.
artifact) - Optional. Name of artifact(s) to use for update.
healthcheck) - Optional. Lets you set path to which ELB sends an HTTP GET request to determine instance health. Default is ‘/healthcheck’
max_error_retry) - Optional. Number of times provider will retry after a failure. Default is
Branch and other deployment conditions can be added as in other deployment providers
deploy: - provider: ElasticBeanstalk access_key_id: secret_access_key: secure: application_name: myEbApp environment_name: myEbApp-env region: us-east-1 healthcheck: /Home max_error_retry: 2 on: branch: main # deploy from master branch only