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

Hosting using Amazon CloudFront and S3 is already enabled - during adding at the new environment #13448

Closed
2 tasks done
biloshkurskyi-ss opened this issue Dec 3, 2023 · 2 comments
Labels
pending-triage Issue is pending triage

Comments

@biloshkurskyi-ss
Copy link

How did you install the Amplify CLI?

No response

If applicable, what version of Node.js are you using?

v20.5.0

Amplify CLI Version

12.8.2

What operating system are you using?

Mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Describe the bug

Can't add hosting to the prod environment from the command: amplify add hosting after choosing Amazon CloudFront and S3.
Screenshot 2023-12-03 at 13 25 06

Expected behavior

The hosting resource should be added to this environment.

Reproduction steps

  1. The project has e few environments.
  2. Add hosting to the staging environment ✅
  3. Try to do the same in the prod environment. (switch to it)
  4. Run the amplify add hosting
  5. obtain an error 🛑 Hosting using Amazon CloudFront and S3 is already enabled.
  6. Env info:
    Screenshot 2023-12-03 at 13 34 00
    Screenshot 2023-12-03 at 13 34 09

Project Identifier

Project Identifier: 690951cba13dc8a658cc92f297ef4740

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@biloshkurskyi-ss biloshkurskyi-ss added the pending-triage Issue is pending triage label Dec 3, 2023
@biloshkurskyi-ss
Copy link
Author

Not an issue. Need to do amplify pull after switching from a different env.

Copy link

github-actions bot commented Dec 3, 2023

⚠️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.

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

No branches or pull requests

1 participant