AWS News Blog

Tag: Amazon CloudFront

IAM Now Available for Amazon CloudFront

You can now use AWS Identity and Access Management (IAM) to regulate access to the Amazon CloudFront APIs.For example, you could easily create three separate IAM groups with names and permissions as follows: Group CloudFrontManagement – Access to all CloudFront APIs. Group Publisher – Access to the CreateDistribution, GetDistribution, UpdateDistribution, and GetDistributionConfig APIs. Group StreamingPublisher […]

Read More

Now Open: AWS Region in Tokyo

I have made many visits to Japan over the last several years to speak at conferences and to meet with developers. I really enjoy the people, the strong sense of community, and the cuisine. Over the years I have learned that there’s really no substitute for sitting down, face to face, with customers and potential […]

Read More

Another New Edge Location for Amazon CloudFront and Amazon Route 53

We’ve just opened up an additional edge location for Amazon CloudFront and Amazon Route 53. Located in picturesque Jacksonville, Florida, this new edge location enjoys long walks on the beach and responding to requests for content (CloudFront) and IP addresses (Route 53) from requesters in the southeast United States. This location brings the total number […]

Read More

Amazon CloudFront – Production Status and an SLA

I’ll be brief. Two quick yet important Amazon CloudFront announcements: First, we’ve removed the beta tag from CloudFront and it is now in full production. During the beta period we listened to our customers and added a number of important features including Invalidation, a default root object, HTTPS access, private content, streamed content, private streamed […]

Read More

Amazon CloudFront Support for Custom Origins

Amazon CloudFront uses an ever-growing network of edge locations to give your users high speed, low latency access to your content, regardless of where they happen to live. Until now, CloudFront could serve up content from Amazon S3. In content-distribution lingo, S3 was the only supported origin server. You would store your web objects (web […]

Read More