elastic beanstalk environment does not appear in console
I am struggling with an AWS problem. I login to the AWS web console with master creds. I create a user with admin role (arn:aws:iam::aws:policy/AdministratorAccess) using IAM, and from that user I get access_id and access_key.
I run eb init using the CLI, and put in the access_id/access_key. I then try to run eb deploy to the one existing environment and it says the environment doesn't exist:
ERROR: InvalidParameterValueError - No Environment found for
EnvironmentName = 'xxx'.
So I create a new environment with eb create and then I run eb deploy and it works. But the new env does not show up in the console!...and I get a 502 Gateway error when I use eb open.
My only hypothesis is that somehow I am logged in with the wrong creds? If I open ~/.aws/config it shows the expected access_id and access_key and no other relevant env vars should be overriding that.
amazon-web-services amazon-elastic-beanstalk aws-elasticbeanstalk
asked Nov 10 at 5:54
Alexander Mills
17.9k31150301
add a comment |
I am struggling with an AWS problem. I login to the AWS web console with master creds. I create a user with admin role (arn:aws:iam::aws:policy/AdministratorAccess) using IAM, and from that user I get access_id and access_key.
I run eb init using the CLI, and put in the access_id/access_key. I then try to run eb deploy to the one existing environment and it says the environment doesn't exist:
ERROR: InvalidParameterValueError - No Environment found for
EnvironmentName = 'xxx'.
So I create a new environment with eb create and then I run eb deploy and it works. But the new env does not show up in the console!...and I get a 502 Gateway error when I use eb open.
My only hypothesis is that somehow I am logged in with the wrong creds? If I open ~/.aws/config it shows the expected access_id and access_key and no other relevant env vars should be overriding that.
amazon-web-services amazon-elastic-beanstalk aws-elasticbeanstalk
asked Nov 10 at 5:54
Alexander Mills
17.9k31150301
add a comment |
I am struggling with an AWS problem. I login to the AWS web console with master creds. I create a user with admin role (arn:aws:iam::aws:policy/AdministratorAccess) using IAM, and from that user I get access_id and access_key.
I run eb init using the CLI, and put in the access_id/access_key. I then try to run eb deploy to the one existing environment and it says the environment doesn't exist:
ERROR: InvalidParameterValueError - No Environment found for
EnvironmentName = 'xxx'.
So I create a new environment with eb create and then I run eb deploy and it works. But the new env does not show up in the console!...and I get a 502 Gateway error when I use eb open.
My only hypothesis is that somehow I am logged in with the wrong creds? If I open ~/.aws/config it shows the expected access_id and access_key and no other relevant env vars should be overriding that.
amazon-web-services amazon-elastic-beanstalk aws-elasticbeanstalk
asked Nov 10 at 5:54
Alexander Mills
17.9k31150301
I am struggling with an AWS problem. I login to the AWS web console with master creds. I create a user with admin role (arn:aws:iam::aws:policy/AdministratorAccess) using IAM, and from that user I get access_id and access_key.
I run eb init using the CLI, and put in the access_id/access_key. I then try to run eb deploy to the one existing environment and it says the environment doesn't exist:
ERROR: InvalidParameterValueError - No Environment found for
EnvironmentName = 'xxx'.
So I create a new environment with eb create and then I run eb deploy and it works. But the new env does not show up in the console!...and I get a 502 Gateway error when I use eb open.
My only hypothesis is that somehow I am logged in with the wrong creds? If I open ~/.aws/config it shows the expected access_id and access_key and no other relevant env vars should be overriding that.
amazon-web-services amazon-elastic-beanstalk aws-elasticbeanstalk
amazon-web-services amazon-elastic-beanstalk aws-elasticbeanstalk
asked Nov 10 at 5:54
Alexander Mills
17.9k31150301
asked Nov 10 at 5:54
Alexander Mills
17.9k31150301
edited Nov 10 at 6:36
asked Nov 10 at 5:54
Alexander Mills
17.9k31150301
asked Nov 10 at 5:54
Alexander Mills
17.9k31150301
asked Nov 10 at 5:54
Alexander Mills
17.9k31150301
17.9k31150301
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Ok so yeah the reason why the environment I created at the command line wasn't appearing the console is because I was in the wrong region in the web console:
in the top right corner of the console, there is region dropdown. Search the relevant regions - your environments are only visible in the right region apparently. (I wish there was a number next to the region in the dropdown - the number of envs in that region).
I assume that the error at the command line - ERROR: InvalidParameterValueError - No Environment found for EnvironmentName = 'xxx', occurred because the wrong region was assumed? That seems weird, but it's my best guess.
answered Nov 10 at 8:09
Alexander Mills
17.9k31150301
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236370%2felastic-beanstalk-environment-does-not-appear-in-console%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ok so yeah the reason why the environment I created at the command line wasn't appearing the console is because I was in the wrong region in the web console:
in the top right corner of the console, there is region dropdown. Search the relevant regions - your environments are only visible in the right region apparently. (I wish there was a number next to the region in the dropdown - the number of envs in that region).
I assume that the error at the command line - ERROR: InvalidParameterValueError - No Environment found for EnvironmentName = 'xxx', occurred because the wrong region was assumed? That seems weird, but it's my best guess.
answered Nov 10 at 8:09
Alexander Mills
17.9k31150301
add a comment |
Ok so yeah the reason why the environment I created at the command line wasn't appearing the console is because I was in the wrong region in the web console:
in the top right corner of the console, there is region dropdown. Search the relevant regions - your environments are only visible in the right region apparently. (I wish there was a number next to the region in the dropdown - the number of envs in that region).
I assume that the error at the command line - ERROR: InvalidParameterValueError - No Environment found for EnvironmentName = 'xxx', occurred because the wrong region was assumed? That seems weird, but it's my best guess.
answered Nov 10 at 8:09
Alexander Mills
17.9k31150301
add a comment |
Ok so yeah the reason why the environment I created at the command line wasn't appearing the console is because I was in the wrong region in the web console:
in the top right corner of the console, there is region dropdown. Search the relevant regions - your environments are only visible in the right region apparently. (I wish there was a number next to the region in the dropdown - the number of envs in that region).
I assume that the error at the command line - ERROR: InvalidParameterValueError - No Environment found for EnvironmentName = 'xxx', occurred because the wrong region was assumed? That seems weird, but it's my best guess.
answered Nov 10 at 8:09
Alexander Mills
17.9k31150301
Ok so yeah the reason why the environment I created at the command line wasn't appearing the console is because I was in the wrong region in the web console:
in the top right corner of the console, there is region dropdown. Search the relevant regions - your environments are only visible in the right region apparently. (I wish there was a number next to the region in the dropdown - the number of envs in that region).
I assume that the error at the command line - ERROR: InvalidParameterValueError - No Environment found for EnvironmentName = 'xxx', occurred because the wrong region was assumed? That seems weird, but it's my best guess.
answered Nov 10 at 8:09
Alexander Mills
17.9k31150301
answered Nov 10 at 8:09
Alexander Mills
17.9k31150301
answered Nov 10 at 8:09
Alexander Mills
17.9k31150301
answered Nov 10 at 8:09
Alexander Mills
17.9k31150301
17.9k31150301
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236370%2felastic-beanstalk-environment-does-not-appear-in-console%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
