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

After removing cloudFront (Hosting endpoint information is not updated). #402

Closed
rizerzero opened this issue Nov 6, 2018 · 5 comments · Fixed by #6041
Closed

After removing cloudFront (Hosting endpoint information is not updated). #402

rizerzero opened this issue Nov 6, 2018 · 5 comments · Fixed by #6041
Assignees
Labels
bug Something isn't working hosting Issues tied to hosting category

Comments

@rizerzero
Copy link

Hi,
After removing cloudfront i noticed that the endpoint information is never updated when i use amplify status command even after making a push or a publish.
even if my amplify publish is uploading the files to the S3 and not to cloudflare it still shows the cloudflare endpoint.

Steps to reproduce the behavior:

  1. amplify publish ( publish to s3 bucket check status to see the hosting endpoint)
  2. amplify hosting configure to add cloudfront
  3. amplify push
  4. amplify status (you can see that the endpoint now is cloudflare endpiont
  5. amplify hosting configure to remove cloudfront
  6. apmify push
  7. amplify status (you can see that the endpoint is still cloudflare and not the dev s3 bucket)
    this information is false ( i can not relay on the git status to be sure i'm pushing to S3 or to cloudFlare

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

image

Desktop (please complete the following information):

  • OS: windows 10
  • Browser chrome
  • Version :70
@rizerzero rizerzero changed the title After removing cloudFront (Endpoint information is not updated). After removing cloudFront (Hosting endpoint information is not updated). Nov 6, 2018
@mlabieniec mlabieniec transferred this issue from aws-amplify/amplify-js Nov 6, 2018
@UnleashedMind
Copy link
Contributor

UnleashedMind commented Nov 6, 2018

Thanks for the feedbacks, this is a known issue.

@UnleashedMind UnleashedMind added the bug Something isn't working label Nov 6, 2018
@rizerzero
Copy link
Author

rizerzero commented Nov 13, 2018

By the way i think that the command amplify status should be added to the workflow on the documentation to me it's clear that the right process should be :

  1. Make a change
  2. Push
  3. Check with "status" that everything is ok and the that the correct destiniation is configured (prod/dev)
  4. Publish
    👌

@kaustavghosh06 kaustavghosh06 removed their assignment Mar 22, 2019
@nirvdrum
Copy link

Is there a workaround? Is manually modifying the amplify config files to point at the S3 bucket an acceptable solution?

@UnleashedMind
Copy link
Contributor

@nirvdrum
There's no workaround at the moment, the urls are in the amplify/backend/amplify-meta.json file, as "CloudFrontSecureURL", "WebsiteURL", but of course the CloudFrontSecureURL is no longer working after the CloudFront is removed.

@kaustavghosh06 kaustavghosh06 added the hosting Issues tied to hosting category label Mar 11, 2020
UnleashedMind pushed a commit to UnleashedMind/amplify-cli that referenced this issue Dec 1, 2020
correct hosting meta output after CloudFront removal

fix aws-amplify#402
UnleashedMind pushed a commit to UnleashedMind/amplify-cli that referenced this issue Dec 1, 2020
fix the hosting output when CloudFront is removed

fix aws-amplify#402
UnleashedMind pushed a commit to UnleashedMind/amplify-cli that referenced this issue Dec 2, 2020
fix hosting category output after CloudFront is removed

fix aws-amplify#402
jhockett pushed a commit that referenced this issue Jan 22, 2021
fix(#402) hosting category output after CloudFront is removed
@github-actions
Copy link

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

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working hosting Issues tied to hosting category
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants