blocks|key|1479447|text|设置TTL=1小时并替换|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1479448|http://developer.amazonwebservices.com/connect/ann.jspa?annID=655|offset|length|1479449|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1T|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Set TTL=1 hour and replace

<a href="http://developer.amazonwebservices.com/connect/ann.jspa?annID=655" rel="nofollow noreferrer">http://developer.amazonwebservices.com/connect/ann.jspa?annID=655</a>

blocks|key|1264881|text|好消息。亚马逊最终添加了一个失效功能。See+the+API+Reference。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1264882|以下是API参考中的示例请求：|1264883|POST+/2010-08-01/distribution/[distribution+ID]/invalidation+HTTP/1.0
Host:+cloudfront.amazonaws.com
Authorization:+[AWS+authentication+string]
Content-Type:+text/xml

<InvalidationBatch>
+++<Path>/image1.jpg</Path>
+++<Path>/image2.jpg</Path>
+++<Path>/videos/movie.flv</Path>
+++<CallerReference>my-batch</CallerReference>
</InvalidationBatch>|code-block|syntax|javascript|1264884|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.amazonwebservices.com/AmazonCloudFront/latest/APIReference/index.html?Actions_Invalidations.html^0|J|L|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

Good news. Amazon finally added an Invalidation Feature. <a href="http://docs.amazonwebservices.com/AmazonCloudFront/latest/APIReference/index.html?Actions_Invalidations.html" rel="noreferrer">See the API Reference</a>.

This is a sample request from the API Reference:

<pre><code>POST /2010-08-01/distribution/[distribution ID]/invalidation HTTP/1.0
Host: cloudfront.amazonaws.com
Authorization: [AWS authentication string]
Content-Type: text/xml

&lt;InvalidationBatch&gt;
 &lt;Path&gt;/image1.jpg&lt;/Path&gt;
 &lt;Path&gt;/image2.jpg&lt;/Path&gt;
 &lt;Path&gt;/videos/movie.flv&lt;/Path&gt;
 &lt;CallerReference&gt;my-batch&lt;/CallerReference&gt;
&lt;/InvalidationBatch&gt;
</code></pre>

blocks|key|1479502|text|使用无效API，它确实会在几分钟内进行更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1479503|查看PHP+Invalidator。|offset|length|1479504|entityMap|0|LINK|mutability|MUTABLE|url|http://www.subchild.com/2010/09/17/amazon-cloudfront-php-invalidator/^0|0|2|F|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

With the Invalidation API, it does get updated in a few of minutes. 
Check out <a href="http://www.subchild.com/2010/09/17/amazon-cloudfront-php-invalidator/" rel="noreferrer">PHP Invalidator</a>.

blocks|key|1479542|text|Bucket+Explorer现在有一个UI，可以让这一切变得非常简单。下面是操作步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1479543|右键单击您的存储桶。选择“管理分发”。|1479544|右键单击您的发行版。选择[获取Cloudfront失效列表]，然后选择[创建]创建一个新的失效列表。选择要失效的文件，然后单击“失效”。等待5-15分钟。|1479545|entityMap|0|LINK|mutability|MUTABLE|url|http://www.bucketexplorer.com/^0|0|F|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

<a href="http://www.bucketexplorer.com/" rel="noreferrer">Bucket Explorer</a> has a UI that makes this pretty easy now. Here's how:

Right click your bucket. Select "Manage Distributions." 
Right click your distribution. Select "Get Cloudfront invalidation list"
Then select "Create" to create a new invalidation list.
Select the files to invalidate, and click "Invalidate." Wait 5-15 minutes.

blocks|key|1265033|text|如果你已经安装了boto+(不仅仅是python，它还安装了一堆有用的命令行工具)，它提供了一个专门称为cfadmin或'cloud+front+admin‘的命令行util，它提供了以下功能：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1265034|Usage:+cfadmin+[command]
cmd+-+Print+help+message,+optionally+about+a+specific+function
help+-+Print+help+message,+optionally+about+a+specific+function
invalidate+-+Create+a+cloudfront+invalidation+request
ls+-+List+all+distributions+and+streaming+distributions|code-block|syntax|javascript|1265035|您可以通过运行以下命令来使某些内容无效：|1265036|$sam#+cfadmin+invalidate+<distribution>+<path>|1265037|entityMap|0|LINK|mutability|MUTABLE|url|http://boto.s3.amazonaws.com/index.html^0|1G|7|8|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

If you have <a href="http://boto.s3.amazonaws.com/index.html" rel="noreferrer">boto</a> installed (which is not just for python, but also installs a bunch of useful command line utilities), it offers a command line util specifically called <code>cfadmin</code> or 'cloud front admin' which offers the following functionality:

<pre><code>Usage: cfadmin [command]
cmd - Print help message, optionally about a specific function
help - Print help message, optionally about a specific function
invalidate - Create a cloudfront invalidation request
ls - List all distributions and streaming distributions
</code></pre>

You invaliate things by running:

<pre><code>$sam# cfadmin invalidate &lt;distribution&gt; &lt;path&gt;
</code></pre>

blocks|key|1265085|text|在ruby中，使用fog+gem|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1265086|AWS_ACCESS_KEY+=+ENV['AWS_ACCESS_KEY_ID']
AWS_SECRET_KEY+=+ENV['AWS_SECRET_ACCESS_KEY']
AWS_DISTRIBUTION_ID+=+ENV['AWS_DISTRIBUTION_ID']

conn+=+Fog::CDN.new(
++++:provider+=>+'AWS',
++++:aws_access_key_id+=>+AWS_ACCESS_KEY,
++++:aws_secret_access_key+=>+AWS_SECRET_KEY
)

images+=+['/path/to/image1.jpg',+'/path/to/another/image2.jpg']

conn.post_invalidation+AWS_DISTRIBUTION_ID,+images|code-block|syntax|javascript|1265087|即使失效，在所有amazon边缘服务器上处理和刷新失效仍然需要5-10分钟|1265088|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In ruby, using the fog gem

<pre class="lang-rb prettyprint-override"><code>AWS_ACCESS_KEY = ENV['AWS_ACCESS_KEY_ID']
AWS_SECRET_KEY = ENV['AWS_SECRET_ACCESS_KEY']
AWS_DISTRIBUTION_ID = ENV['AWS_DISTRIBUTION_ID']

conn = Fog::CDN.new(
 :provider =&gt; 'AWS',
 :aws_access_key_id =&gt; AWS_ACCESS_KEY,
 :aws_secret_access_key =&gt; AWS_SECRET_KEY
)

images = ['/path/to/image1.jpg', '/path/to/another/image2.jpg']

conn.post_invalidation AWS_DISTRIBUTION_ID, images
</code></pre>

even on invalidation, it still takes 5-10 minutes for the invalidation to process and refresh on all amazon edge servers

blocks|key|1479750|text|一个非常简单的方法就是文件夹版本化。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1479751|例如，如果您的静态文件有数百个，只需将它们全部放入一个由year%2Bversioning命名的文件夹中即可。|1479752|例如，我使用一个名为2014_v1的文件夹，里面有我所有的静态文件……|1479753|因此，在我的HTML中，我总是放入对文件夹的引用。(当然，我有一个PHP+include，我在其中设置了文件夹的名称。)因此，通过在一个文件中进行更改，它实际上在我所有的PHP文件中都会发生更改。|1479754|如果我想要完全刷新，我只需将文件夹重命名为2014_v2，并在php+include中更改为2014_v2。|1479755|所有HTML自动更改并询问新路径，cloudfront未命中缓存并将其请求到源。|1479756|示例:+SOURCE.mydomain.com是我的源代码，cloudfront.mydomain.com是云前端的分发版。|1479757|所以PHP将这个文件命名为cloudfront.mydomain.com/2014_v1/javascript.js，当我想要完全刷新时，我简单地将源文件中的文件夹重命名为"2014_v2“，并通过将文件夹设置为"2014_v2”来更改PHP包含。|1479758|像这样，没有失效的延迟，也没有成本！|1479759|这是我在stackoverflow上的第一篇文章，希望我做得很好！|1479760|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|14|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|U|$]]

one very easy way to do it is FOLDER versioning.

So if your static files are hundreds for example, simply put all of them into a folder called by year+versioning.

for example i use a folder called 2014_v1 where inside i have all my static files...

So inside my HTML i always put the reference to the folder. ( of course i have a PHP include where i have set the name of the folder. ) So by changing in 1 file it actually change in all my PHP files..

If i want a complete refresh, i simply rename the folder to 2014_v2 into my source and change inside the php include to 2014_v2

all HTML automatically change and ask the new path, cloudfront MISS cache and request it to the source.

Example: 
SOURCE.mydomain.com is my source, 
cloudfront.mydomain.com is CNAME to cloudfront distribution.

So the PHP called this file
cloudfront.mydomain.com/2014_v1/javascript.js 
and when i want a full refresh, simply i rename folder into the source to "2014_v2" and i change the PHP include by setting the folder to "2014_v2".

Like this there is no delay for invalidation and NO COST !

This is my first post in stackoverflow, hope i did it well !

blocks|key|1479810|text|如果你正在使用AWS，你可能也会使用它的官方CLI工具(迟早)。AWS+CLI+version+1.9.12或更高版本支持使文件名列表无效。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1479811|完全公开:这是我做的。玩得开心!|1479812|entityMap|0|LINK|mutability|MUTABLE|url|http://aws.amazon.com/releasenotes/CLI/4500602791571312^0|W|M|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

If you are using AWS, you probably also use its official CLI tool (sooner or later). <a href="http://aws.amazon.com/releasenotes/CLI/4500602791571312" rel="nofollow">AWS CLI version 1.9.12</a> or above supports invalidating a list of file names.

Full disclosure: I made this. Have fun!

blocks|key|1265291|text|当前的AWS+CLI支持预览模式下的失效。在控制台中运行以下命令一次：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1265292|aws+configure+set+preview.cloudfront+true|code-block|syntax|javascript|1265293|我使用npm部署我的web项目。我的package.json中有以下脚本|offset|length|style|CODE|1265294|{
++++"build.prod":+"ng+build+--prod+--aot",
++++"aws.deploy":+"aws+s3+sync+dist/+s3://www.mywebsite.com+--delete+--region+us-east-1",
++++"aws.invalidate":+"aws+cloudfront+create-invalidation+--distribution-id+[MY_DISTRIBUTION_ID]+--paths+/*",
++++"deploy":+"npm+run+build.prod+&&+npm+run+aws.deploy+&&+npm+run+aws.invalidate"
}|1265295|准备好上述脚本后，您可以使用以下方法部署您的站点：|1265296|npm+run+deploy|1265297|entityMap^0|0|0|I|C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

current AWS CLI support invalidation in preview mode. Run the following in your console once:
<pre class="lang-sh prettyprint-override"><code>aws configure set preview.cloudfront true
</code></pre>
I deploy my web project using npm. I have the following scripts in my <code>package.json</code>:
<pre class="lang-json prettyprint-override"><code>{
 &quot;build.prod&quot;: &quot;ng build --prod --aot&quot;,
 &quot;aws.deploy&quot;: &quot;aws s3 sync dist/ s3://www.mywebsite.com --delete --region us-east-1&quot;,
 &quot;aws.invalidate&quot;: &quot;aws cloudfront create-invalidation --distribution-id [MY_DISTRIBUTION_ID] --paths /*&quot;,
 &quot;deploy&quot;: &quot;npm run build.prod &amp;&amp; npm run aws.deploy &amp;&amp; npm run aws.invalidate&quot;
}
</code></pre>
Having the scripts above in place you can deploy your site with:
<pre class="lang-sh prettyprint-override"><code>npm run deploy
</code></pre>

blocks|key|1265396|text|转到CloudFront。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1265397|单击您的ID/分发。|1265398|单击Invalidations。|1265399|单击创建无效。|1265400|在巨大的示例框中键入*，然后单击无效|1265401|完成|1265402|​|1265403|📷|atomic|offset|length|1265404|1265405|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/ba961ab7abb25b0c243ef17a9fa0fbb7.png|imageAlt^0|0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|19|8|@]|9|@$Q|1A|R|1B|1|1C]]|A|$]]|$1|S|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10|11|-4]]]]

Go to CloudFront.

Click on your ID/Distributions.

Click on Invalidations. 

Click create Invalidation. 

In the giant example box type * and click invalidate

Done 

<a href="https://i.stack.imgur.com/DgWVA.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DgWVA.png" alt="enter image description here"></a>

I'm using Amazon's CloudFront to serve static files of my web apps. 

Is there no way to tell a cloudfront distribution that it needs to refresh it's file or point out a single file that should be refreshed? 

Amazon recommend that you version your files like logo_1.gif, logo_2.gif and so on as a workaround for this problem but that seems like a pretty stupid solution. Is there absolutely no other way?

Force CloudFront distribution/file update

命令行工具

服务器

我正在使用亚马逊的CloudFront来提供我的web应用程序的静态文件。有没有办法告诉cloudfront发行版它需要刷新它的文件，或者指出应该刷新的单个文件？亚马逊建议你对你的文件进行版本控制，比如logo_1.gif，logo_2.gif等等，作为解决这个问题的变通办法，但这似乎是一个相当愚蠢的解决方案。难道就没...

问强制CloudFront分发/文件更新
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问强制CloudFront分发/文件更新EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问强制CloudFront分发/文件更新
EN