Question 181105 in Amazon Web Sevices Question posted in
The official Amazon Web Services documentation can be found here.

Amazon web services – AWS EB environment deployed with CLI not showing in AWS console

I manage to run eb deploy successfully from the command prompt and get the following:

2023-05-21 21:27:31    INFO    Environment update completed successfully.

And when I run eb list I get as result the name of my environment * simply-dev.

I can run eb status --verbose and see everything looks healthy/green.

Environment details for: simply-dev
  Application name: simply
  Region: us-east-2
  Deployed Version: app-230523_221320835290
  Environment ID: e-rdyf63m2dr
  Platform: arn:aws:elasticbeanstalk:us-east-2::platform/Python 3.8 running on 64bit Amazon Linux 2/3.5.2
  Tier: WebServer-Standard-1.0
  CNAME: exit.us-east-2.elasticbeanstalk.com
  Updated: 2023-05-23 21:17:44.717000+00:00
  Status: Ready
  Health: Green
  Running instances: 1
           i-034a7471b6b368e1b: healthy

However, when I run eb console, the console opened in the internet browser does not show any application or environment and keeps loading endlessly. I also checked I am in the same region and both show the same Account ID. I also tried deploying in other regions with the same result.

AWS EB Error

Any idea of why I cannot see the environment in the AWS console?

I am checking the logs from eb logs --zip but I don’t really understand much. Any idea what to look for?
Logs

The Chrome Developers Tools shows an error but I am not sure if it is related to this:
enter image description here

Tags:

2

Answers


  1. Chosen as BEST ANSWER
    0

    AWS support finally gave me the solution. Basically, it seems I was creating my environment in another account. It seems there are AWS credentials (found at C:/Users/Your_User/.aws/config) but EB cli has its own credentials which are input as part of the eb init command, and can be found at the same .aws/config file with the profile named "eb-cli". The access key credentials here are the ones that are used by default when setting up the environment.

    As an example, once I setup the credentials using aws configure, my output is:

    # cat .aws/config
[default]
 
# cat .aws/credentials
[default]
aws_access_key_id = abc
aws_secret_access_key = 123

    After running eb init command, I have the following credentials:

    # cat .aws/config
[default]
 
[profile eb-cli]
aws_access_key_id = xyz
aws_secret_access_key = 890
 
# cat .aws/credentials
[default]
aws_access_key_id = abc
aws_secret_access_key = 123

    So in my case, somehow my "eb-cli" profile contained valid credentials in another account (how I did that, I don't know). The fix is to navigate to the credentials file and change the access keys for the "eb-cli" profile ones found in the .aws/config.


  2. 0

    have you navigate to EC2 dashboard and make sure there has a running VM instance with ID i-034a7471b6b368e1b?. If it not exist, You better ask AWS technical support regarding to this case

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search