| app_name | Name of the Elastic Beanstalk application. If it doesn't exist, it will be created. | yes | — |
| aws_access_key_id | AWS Access Key ID. May instead be specified via the AWS_ACCESS_KEY_ID environment variable. | — | — |
| aws_region | AWS region. May instead be specified via the AWS_REGION environment variable. | — | — |
| aws_secret_access_key | AWS Secret Access Key. May instead be specified via the AWS_SECRET_ACCESS_KEY environment variable. | — | — |
| aws_session_token | AWS session token for using temporary credentials. May instead be specified via the AWS_SESSION_TOKEN environment variable. | — | — |
| blue_env | Name of the blue environment. | — | — |
| create_environment | Whether to create a new environment during deployment if the target environment doesn't exist. | — | true |
| deploy | Whether to deploy to the target environment. | — | false |
| disable_termination_protection | Whether to disable termination protection for the target environment's CloudFormation stack before attempting to terminate it. | — | false |
| enable_termination_protection | Whether to enable termination protection for the target environment's CloudFormation stack after deployment. | — | false |
| green_env | Name of the green environment. | — | — |
| minimum_health_color | Minimum health color (Green, Yellow, Red, or Grey) required for the target environment to be considered healthy. | — | Green |
| option_settings | Path to a JSON file consisting of an array of option settings to use when updating an existing evironment or creating a new environment. | — | — |
| platform_branch_name | Name of the platform branch to use. When creating a new environment, it will be launched with the latest version of the specified platform branch. To see the list of available platform branches, run the `aws elasticbeanstalk list-platform-branches` command. | — | — |
| production_cname | CNAME prefix for the domain that serves production traffic when performing a blue/green deployment. | — | — |
| send_command | Command to send to the target environment after (optional) deployment. Specify a shell script or series of commands to run. Useful for running tasks related to deployment, such as swapping environment variables before promoting an environment to production. | — | — |
| single_env | Name of a single environment to deploy. If specified, the blue/green environments and production/staging CNAMEs must not be provided. | — | — |
| single_env_cname | CNAME prefix to use for a single-environment deployment. | — | — |
| source_bundle | Path to the source bundle to deploy. If not specified, the sample application will be used. | — | — |
| staging_cname | CNAME prefix of the staging environment for a blue/green deployment. | — | — |
| swap_cnames | Whether to swap the CNAMEs of the blue and green environments. | — | false |
| template_name | Name of an Elastic Beanstalk configuration template to use when creating a new environment. | — | — |
| terminate_unhealthy_environment | Whether to terminate an unhealthy target environment. If set to false, the action will fail if the target environment is unhealthy. | — | false |
| update_environment | Whether to update an existing environment during deployment. | — | true |
| update_listener_rules | When set to true, the action will update any elbv2 listener rules on the environments' SharedLoadBalancer tagged with a `bluegreenbeanstalk:target_cname` key, whose value is equal to an environment's CNAME prefix, so that it forwards to the corresponding target group.
For example, you can tag a listener rule that matches the host `my-domain.com` with a tag containing `bluegreenbeanstalk:target_cname` as its key and `my-prod-cname` as its value, and the action will update the listener rule to point to the same target group as the environment with the CNAME `my-prod-cname`.
The listener rules are updated after the CNAMEs are swapped, so this keeps the listener rules in sync with the CNAMEs.
The port of the process may be specified by another tag with the key `bluegreenbeanstalk:target_port` whose value is the port number. If no such tag is found, the default port of 80 will be used.
If you'd only like to update the listener rules for a certain CNAME, you can set this input to the CNAME prefix you'd like to update.
| — | false |
| use_default_option_settings | Whether to use default option settings when creating a new environment. | — | true |
| version_description | Description to use for the new application version. | — | — |
| version_label | Version label to use for the new application version. | — | — |
| wait_for_command | Whether to wait for the send_command execution to complete. | — | true |
| wait_for_deployment | Whether to wait for the deployment to complete. | — | true |
| wait_for_environment | Whether to wait for the target environment to be ready before deployment. If set to false, the action will fail if the target environment is not ready. | — | true |
| wait_for_termination | Whether to wait for an environment to be terminated. If set to false, the action will fail if the target environment is terminating. | — | true |