Backend Environments Tab in Amplify Console is Empty

[jhoffmcd]

** Please describe which feature you have a question about? **

The tab in Amplify that is supposed to show Backend Environments seems to be empty in my project, even though we have definitlely have two declared environments.

** Provide additional details**

What is actually supposed to show here? We have two environments that do seem to work other than what we see in this tab. Here is what we are seeing in the tab:

However, we do see environments when we use the CLI tool or when we try to connect a branch:

Is there a way to connect these two so I can see what value this tab section brings to my team?

[ganipcanot]

@jhoffmcd Does your application only have a front-end? Or does it also have a back-end? Also could you provide your app-id (app ARN) in order to assist you further? Thanks!

If your application has only deployed a front-end then you wouldn't see a backend environment.

[jhoffmcd]

It does also have a backend (auth/cognito) component.

App ARN: arn:aws:amplify:us-west-2:059525859496:apps/d2zqif4mv6lhdb

[ihao8]

Hi @jhoffmcd , this is a known issue for us. We are still investigating a fix to pass custom parameters when creates backend env. The current workaround is here: #206 (comment)

[jhoffmcd]

Thanks for the update @Joycehao19, I'm glad to hear the team is on it. I can probably wait of a true fix to this, the work around looks to be a bit bulky and we are able to survive with out it for a while longer I think.

Also, we are not using social federation, would this fix still apply if we wanted to look into it? Is there a specific part of this shell script that provides the workaround that you can point out?

[ihao8]

@jhoffmcd what version of the CLI are you using?

[jhoffmcd]

Looks like 4.13.1

[jhoffmcd]

An update on this, I added a 3rd env, "staging" and that did show up in the console, but the other two environments are still lost to the ether... :(

[ihao8]

@jhoffmcd To clarify your issue, do you mean that: you created 2 env by amplify cli, then amplify push, but didn't see any backend env. Then you added 3rd env, "staging", then amplify push. The app only has 1 backend "staging". In your team-provider-info.json, it contains all 3 env.

If you re-create a new project, add env (amplify init + your custom setting), do amplify push, do you have the same issue?

I can't reproduce your issue. I did amplify init (create env abc) + amplify add auth + amplify auth update + amplify init (create env prod) + amplify push, I got 2 backend env on my console..

[jhoffmcd]

@Joycehao19 correct, we had 2 for a long time, which never showed up in the console, we just added a third one (which did add to the team-provider-info.json).

I can try to do this in a brand new project. It should be worth noting that the first two environments were created around 10 months ago, and this new one was created a few days ago. Maybe older environments are not setup to show in the console?

[ihao8]

@jhoffmcd That might be the reason. We launched the front-end and back-end list in recent 4 months. The new back-end environments would be showed on console.

[jhoffmcd]

So for these old environments, is there nothing we can do to get the console to read those correctly? We don't want to reset everything because we would have to migrate users to the new user pools created by the CF template.

[jhoffmcd]

Just an update, I ran aws amplify list-branches to see the output of what I have in this project. The older dev and master branches do not have the following property set:

"backendEnvironmentArn"

However, my new staging env branch does have that property set to what looks like some internal env ARN

Not sure if that is the missing piece or not as to why these older environments aren't showing up in the tabs in the console. I hope that helps give a little more info on this issue.

[H6]

That might be the reason. We launched the front-end and back-end list in recent 4 months. The new back-end environments would be showed on console.

Hi @Joycehao19 . And old ones will never be visible here?

I have an old amplify project. And I just migrated to the current CLI and was also wondering, that the backend tab was empty.

[swaminator]

@jhoffmcd @H6 are you still facing this issue?

[H6]

@jhoffmcd @H6 are you still facing this issue?

Yes, my backend tab is still empty in the console.

[jhoffmcd]

@swaminator I don't work on that project anymore so I can't say for sure.

[RossWilliams]

I still have the issues with multiple apps. They became duplicated in the console, and the “active” app has an empty backend tab.

[dylan-westbury]

I am facing this issue for a next.js frontend, for a react native and reactjs frontend it is fine.

Even after running amplify init --appId xxxxx and pushing

[lucafronterotta]

Hello all,I'm having the same problem, my backend console is empty even if the services I configured (analytics, notifications, pinpoint) are working well.

The strange thing I see is that:

• if I create everything from my personal AWS account with administration rights everything is ok and I can see the backend in the Amplify console;
• if I create everything from my Company account where I have limited rights services works well but backend in Amplify is missing, but I get no errors while doing all the configurations.

What I do is:

• create a react native app
• amplify init (creating a single environment)
• amplify add notifications
• amplify add analytics
• amplify push

Could it be a rights problem (missing policies?!?) on my Company account?
Is it possible to have a list of rights mandatory to use Amplify CLI and push everything to the cloud?

Thanks in advance.

[lucafronterotta]

I solved the problem requesting amplify:* permissions on my AWS Company account; it seems that the Amplify web console, when permissions are missing, simply tells that you have no backend instead of saying something like "You have no right to do this task"

[ganipcanot]

Resolving this issue based on the update to permissions on your end.

Feel free to re-open if still experiencing issues.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.