Better error message on `amplify init`, please.

littlebee commented 1 year ago

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id

NEW_APP

AWS Region

us-west-2

Amplify Hosting feature

Console

Frontend framework

Next.js

Next.js version

13.4.16

Next.js router

App Router

Describe the bug

Hello. I'm a first-time user trying to evaluate Amplify for my next project. I'm carefully following the instructions here: https://docs.amplify.aws/start/getting-started/setup/q/integration/next/

When I get to the amplify init step, after selecting my AWS profile, the command fails like this:

? Enter a name for the project twerk
The following configuration will be applied:

Project information
| Name: twerk
| Environment: dev
| Default editor: Visual Studio Code
| App type: javascript
| Javascript framework: react
| Source Directory Path: src
| Distribution Directory Path: build
| Build Command: npm run-script build
| Start Command: npm run-script start

? Initialize the project with the above configuration? Yes
Using default provider  awscloudformation
? Select the authentication method you want to use: AWS profile

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use default
🛑 We are unable to process your request. Please reach out to your support representative.

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 00c940e9-b1a7-4f4c-a3ee-bbbf26e86c69

Expected behavior

Some error message or log that I can look at to see what is it that failed?

Maybe my key is incorrect or not using the keys from [default] in ~/.aws/credentials (I'm pretty sure it is and those are correct). Maybe the region is incorrect in my ~/.aws/config? How would I know?

Reproduction steps

Follow instructions of this tutorial: https://docs.amplify.aws/start/getting-started/setup/q/integration/next/ up to amplify init step.

Build Settings

I think `init` did not get far enough to generate an amplify.yml.  I don't see one in my project root.

Log output

``` # Put your logs below this line 2023-08-16T16:41:36.709Z|info : amplify init core 2023-08-16T16:41:36.739Z|info : @aws-amplify/amplify-cli-core.banner-message/index.ts.fetch banner messages from https://aws-amplify.github.io/amplify-cli/banner-message.json({} 2023-08-16T16:41:53.867Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileConfig(["default"]) 2023-08-16T16:41:53.868Z|info : amplify-provider-awscloudformation.system-config-manager.getProfiledAwsConfig.profileConfig([{"region":"us-east-1"}]) 2023-08-16T16:41:53.868Z|info : amplify-provider-awscloudformation.system-config-manager.getProfileCredentials(["default"]) 2023-08-16T16:41:53.873Z|info : amplify-provider-awscloudformation.amplify-service-permission-check.checkAmplifyServiceIAMPermission.amplifyClient.listApps([]) 2023-08-16T16:41:54.230Z|info : amplify-provider-awscloudformation.amplify-service-manager.init.amplifyClient.createApp([{"name":"[***]rk","environmentVariables":{"_LIVE_PACKAGE_UPDATES":"[{\"pkg\":\"@aws-amplify/cli\",\"type\":\"npm\",\"version\":\"latest\"}]"}}]) 2023-08-16T16:41:54.709Z|error : We are unable to process your request. Please reach out to your support representative. ProjectInitFault: We are unable to process your request. Please reach out to your support representative. ```

Additional information

No response

ykethan commented 1 year ago

Hey @littlebee, thank you for reaching out. When creating a new application on the AWS Amplify console, do you observe a similar message? we can create a new application by clicking on New app -> Build an app

littlebee commented 1 year ago

From console provides less information:

On Wednesday, August 16, 2023 at 01:01:25 PM PDT, Kethan sai ***@***.***> wrote:

Hey @littlebee, thank you for reaching out. When creating a new application on the AWS Amplify console, do you observe a similar message? we can create a new application by clicking on New app -> Build an app

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

ykethan commented 1 year ago

Hey @littlebee, If you are unable to create a application on the AWS Amplify console as well, this seems to be occurring on the account level. I would suggest reaching out to the AWS Quota increase team. From the following documentation: https://docs.aws.amazon.com/general/latest/gr/amplify.html#service-quotas-amplify noticed the following banner for new accounts.

New AWS accounts have reduced apps and concurrent jobs quotas. AWS raises these quotas automatically based on your usage.

josefaidt commented 1 year ago

Closing due to inactivity

github-actions[bot] commented 1 year ago

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

MaheshLoya commented 1 year ago

same error, noth CLI and UI Console error out

joeyu23 commented 11 months ago

I'm seeing the same issue.

joeyu23 commented 11 months ago

@littlebee were you able to resolve this issue?

littlebee commented 11 months ago

No, I was not.

Sent from my iPhone

On Oct 12, 2023, at 6:57 PM, Joe Yu @.***> wrote:

@littlebee were you able to resolve this issue?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

ykethan commented 11 months ago

@joeyu23 @joeyu23 were you able to reach out to the quota team as the issue is currently occurring on a account level?

if you have a premium support plan, you can open a support case under the Amplify Console Support with a brief explanation with the error and being unable to create resources. if you do not have a support plan and see a Basic Support Plan in the AWS support console,

create a new support case under Account and Billing using the following headings: Service: Account Category: Other Account Issues General Question add a subject line say "Check Account Status - Amplify Console" and describe the issue you are experiencing. Do link the GitHub issue to help track the issue.

Coffeeye commented 9 months ago

@ykethan where is 'Account and Billing' section ? somewhere in Billing and Cost Management ??

aws-amplify / amplify-cli