Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment error (next.js) for a new AWS account (free) #3704

Open
12evgen opened this issue Mar 12, 2024 · 3 comments
Open

Deployment error (next.js) for a new AWS account (free) #3704

12evgen opened this issue Mar 12, 2024 · 3 comments

Comments

@12evgen
Copy link

12evgen commented Mar 12, 2024

Following the instructions (https://docs.sst.dev/start/nextjs), I'm trying to set up the SST for the next.js application
I created a new AWS account (free), set up an AIM account according to the instructions (https://docs.sst.dev/advanced/iam-credentials#loading-from-a-file).

After the npx create-sst@latest command, I see the changes in my repository. And after that I run npx sst dev. My application is starting.
image

Now I am trying to deploy my application and I get an error: "Access denied for operation 'AWS::CloudFront::Distribution: Your account must be verified before you can add new CloudFront resources. To verify your account, please contact AWS Support"
image

How can this problem be solved?

@jayair
Copy link
Contributor

jayair commented Mar 12, 2024

Hmm have you tried contacting AWS support about this?

@12evgen
Copy link
Author

12evgen commented Mar 13, 2024

@jayair Yes, I contacted support but I haven't received a response yet.
However, such a bug was noticed in this issue - #3429

@yarabramasta
Copy link

Welp, can confirm this also. I am trying to delete my dev stage resources and deploy the prod one. I think it has something to do with resources, sst creating many resources for NextjsSite stack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants