Amplify-cli: Amplify Publish Not Reflecting Changes

Created on 16 May 2019  路  1Comment  路  Source: aws-amplify/amplify-cli

Describe the bug
A clear and concise description of what the bug is.
I have Amplify Setup in my application which is working previously.
Now Yesterday I made change and did amplify publish...Everything is successfully but changes didn't got reflected in the live website.

Debuging: So to debug myself I went to the bucket in s3 and looked at the files manually and it's updated files with the changes...Then I went to the bucket hosting "Properties" then "Static Website Hosting" then clicked on the endpoint "http://courselabz-prod-release-redstone.s3-website-us-west-2.amazonaws.com" which is working and have all the changes inside it. So I want to know why even though s3 bucket and s3 bucket url is having updated changes why not my amplify hosted cloudfront url doesnt have my changes? "https://d19v75l5red964.cloudfront.net"
To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://d19v75l5red964.cloudfront.net' (No changes)
  2. Click on 'http://courselabz-prod-release-redstone.s3-website-us-west-2.amazonaws.com'(changes working)
    No Error Was thrown during the amplify publish command [I tried publish multiple times still no change]
    Screen Shot 2019-05-16 at 10 40 08 AM
hosting question

Most helpful comment

@jmandivarapu1 Cloudfront doesn't immediately invalidate it's cache. If you want to immediately invalidate the cache, you would want to use the -c flag with the amplify publish command.

>All comments

@jmandivarapu1 Cloudfront doesn't immediately invalidate it's cache. If you want to immediately invalidate the cache, you would want to use the -c flag with the amplify publish command.

Was this page helpful?
0 / 5 - 0 ratings