Deploying a nodejs app to aws elastic beanstalk fails.

Question

bellow the error message :

An error occurred (InvalidParameterValue) when calling the UpdateEnvironment operation: No Environment found for EnvironmentName = 'prod_env'.

knowing that prod_env is my application's environment in aws elastic beanstalk.

Halyna Berezovska · Answer

Hello, @Adelphe MBATCHI ! Could you try to execute aws cli command update-envronment to debug it? Or just to check it if aws should recognize it: aws elasticbeanstalk describe-environments --application-name "" --environment-names "" --debug If it succeed then you can debug update command. Looking forward hearing back from you. Cheers, Galyna

Adelphe MBATCHI · Answer

build logs : INFO: Updating environment in Elastic Beanstalk... An error occurred (InvalidParameterValue) when calling the UpdateEnvironment operation: No Environment found for EnvironmentName = 'prod_env'.✔ Application version CloudHSE-31 successfully created in Elastic Beanstalk.

Adelphe MBATCHI · Answer

bitbucket-pipelines.yml

image: node:10.20.1
pipelines: 
default: 
- step:
name: "Build and Test"
caches:
- node
script: 
- npm install
- apt-get update && apt-get install -y
- apt-get install zip
- zip application.zip index.js package.json
services:
- mongo
artifacts: 
- application.zip 
- step: 
name: "Deploy to Production" 
deployment: 'Production'
script:
- pipe: atlassian/aws-elasticbeanstalk-deploy:0.6.4 
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID 
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY 
AWS_DEFAULT_REGION: 'us-east-1' 
APPLICATION_NAME: 'cloudhse' 
S3_BUCKET: 'elasticbeanstalk-us-east-1-307150017281'
ZIP_FILE: 'application.zip'
VERSION_LABEL: 'CloudHSE-${BITBUCKET_BUILD_NUMBER}'
ENVIRONMENT_NAME: 'prod_env'
definitions: 
services: 
mongo: 
image: mongo