Home » Posts tagged "cloudfront"

CloudFront 在東京開到第八個點了...

看到 Amazon CloudFront 宣佈在東京開到第八個點了:「Amazon CloudFront launches eighth Edge location in Tokyo, Japan」。

Amazon CloudFront announces the addition of an eighth Edge location in Tokyo, Japan. The addition of another Edge location continues to expand CloudFront's capacity in the region, allowing us to serve increased volumes of web traffic.

這個成長速度有點驚人,一月才加了兩個,現在又要再加一個... 不過大阪還是維持一個。

CloudFront 在台北的第二個 PoP

Twitter 上看到了 Amazon CloudFront 宣佈了台北的第二個 PoP:

這個也是喊好久了,從去年就有消息一直到現在... 這樣台灣多了一個 backup,比較不會導去香港或是日本了。不過新 PoP 的代碼找不到,試著找 tsatpe 以及後面接數字,還是只有找到 tpe50,不知道是不是後來不露出代碼了...

CloudFront 東京加到七個 Edge...

在「Amazon CloudFront announces six new Edge Locations, adding two more in Tokyo, JP, and its first location in Perth, AU」這邊看到 Amazon CloudFront 在東京直接加兩個 Edge,變成七個 Edge 了:

Amazon CloudFront announces six new Edge Locations that are now part of its global network. These six new Edge Locations are located in the following cities:

Perth, Australia; Chennai, India; Rio De Janeiro, Brazil; Los Angeles, California; and two additional Edge Locations in Tokyo, Japan.

再加上大阪還有一個 Edge,日本的量這麼大喔?會跟 Regional Edge 有關嗎...


Hacker News 首頁上看到的文章,講 Jekyll 一路跟 Amazon S3Amazon CloudFront 接上去的步驟:「Jekyll CBCD Pipeline to the Cloud」。

我看了以後覺得好麻煩 @_@

然後回頭看 Hacker News 上的評論:「Jekyll Static Web Hosting – Deployment Pipeline on AWS | Hacker News」,看到這段:

What a nightmare. I'm sure there are use cases for a setup like this, but this is not the system I'd like to maintain. I use Jekyll because of it's simplicity. I edit my site in my favorite text editor and rsync to shared hosting.

好多人都有同感啊 XDDD

另外有人提到 Netlify 這個服務:

After I discovered Netlify, I'm kind of thinking "why bother". It's free, I just push to my repo and they take care of all the building/publishing/hosting/CDNs, and they're very responsive for support and have high availability. I'm a very happy customer (or rather leech, as I don't pay anything).

下面評價看起來還算不錯,而且有 free tier 可以用,也許可以找機會玩看看...

Amazon API Gateway 可以獨立運作了...

Amazon API Gateway 先前一定要跟 Amazon CloudFront 綁在一起 (而且還是很奇怪的 distribution,不是 Price Class 裡面任何一種分類),現在總算可以獨立自己運作了:「Amazon API Gateway Supports Regional API Endpoints」。

A regional API endpoint is a new type of endpoint that is accessed from the same AWS region in which your REST API is deployed. This helps you reduce request latency when API requests originate from the same region as your REST API.

而且這樣一來,如果還是要用 Amazon CloudFront 擋在前面的話,可以自己選擇 Price Class:

Additionally, you can now choose to associate your own Amazon CloudFront distribution with the regional API endpoint.

以前用起來頗莫名其妙的 XDDD

CloudFront 的第 100 個 PoP

昨天還在猜 Amazon CloudFront 的第 100 個 PoP 會在哪裡 (「CloudFront 第 99 個 PoP」),結果今天就開獎了... 是在東京擴充第五個 PoP (加上大阪之後是日本的第六個 PoP):「Amazon CloudFront now has 100 Points of Presence with the launch of its fifth Edge Location in Tokyo, Japan.」。

Our 100th Point of Presence (POP) is also the fifth Edge Location in Tokyo, and our sixth in Japan.

東京擴張的好快... Anyway,這是現狀:

可以看到美國中部的普及率還是偏低,另外缺了非洲... 如果 CloudFront 繼續擴張應該會看到消息。(美國的 PoP 一直有看到在加的消息,比起前幾年是好不少,不過看起來增加的速度還是沒有比其他地區的勤...)

CloudFront 第 99 個 PoP

前陣子在「CloudFront 一直擴點...」看到 98 個了,然後現在宣佈第 99 個... 可以開始猜 CloudFront 的第 100 個 PoP 會是哪邊了 XD:「Amazon CloudFront Announces its 99th Point of Presence with its Second Edge Location in Miami, FL.」。

不過這次是擴增 Miami 的點 (本來就已經有,多增加一個),所以是以 capacity 與 redundancy 為主:

The Amazon CloudFront team is happy to announce its 99th Point of Presence with the addition of a second Edge Location in Miami, Florida.