Buildablock Corp (BABL)

[DD_dempsey]

HUGE New BABL Development- AMAZON CloudFront

It is my opinion, that tonight's update to the BUILDABLOCK.com website servers via Robtex.com is the most significant and EXPLAINS Exactly why we see a 403 Error code - server reconfiguration code on the website tonight. Hold onto your hats folks but the fingerprint for Buildablock has just updated to NOW INCLUDE a GLOBAL content delivery network. THE BABL DEVELOPERS have been working non stop and around the clock entering CODE of 3800 + mail servers connected through name servers to BABL. The nodes have been expanded to include AMAZON CLOUDFRONT !!!!!!!

BABL Robtex fingerprint: https://www.robtex.com/?dns=buildablock.com

TONIGHTS UPDATE TO THE FINGERPRINT directly connects Buildablock.com to Amazon CloudFront is a content delivery network (CDN) offered by Amazon Web Services. Content delivery networks provide a globally-distributed network of proxy servers which cache content, such as web videos or other bulky media, more locally to consumers, thus improving access speed for downloading this content.




What Is Amazon CloudFront?

Amazon CloudFront is a web service that speeds up distribution of your static and dynamic web content, such as .html, .css, .php, and image files, to your users. CloudFront delivers your content through a worldwide network of data centers called edge locations. When a user requests content that you're serving with CloudFront, the user is routed to the edge location that provides the lowest latency (time delay), so that content is delivered with the best possible performance. If the content is already in the edge location with the lowest latency, CloudFront delivers it immediately. If the content is not in that edge location, CloudFront retrieves it from an Amazon S3 bucket or an HTTP server (for example, a web server) that you have identified as the source for the definitive version of your content.

CloudFront speeds up the distribution of your content by routing each user request to the edge location that can best serve your content. Typically, this is the CloudFront edge location that provides the lowest latency. This dramatically reduces the number of networks that your users' requests must pass through, which improves performance. Users get lower latency—the time it takes to load the first byte of the file—and higher data transfer rates. You also get increased reliability and availability because copies of your files (also known as objects) are now held in multiple edge locations around the world.

Please see the image here as evidence of the log in page we saw...



How CloudFront Delivers Content

After some initial setup, CloudFront works invisibly to speed up delivery of your content. This overview includes both the steps you perform before your first user accesses your application or website and how CloudFront serves your content when configuration is complete.

HERE IS A PICTORAL OF WHAT BUILDABLOCK IS USING AMAZON CLOUDFRONT:



Setting up CloudFront involves a few simple steps

How You Configure CloudFront to Deliver Your Content

You configure your origin servers, from which CloudFront gets your files for distribution from CloudFront edge locations all over the world.

An origin server stores the original, definitive version of your objects. If you're serving content over HTTP, your origin server is either an Amazon S3 bucket or an HTTP server, such as a web server. Your HTTP server can run on an Amazon Elastic Compute Cloud (Amazon EC2) instance or on a server that you manage; these servers are also known as custom origins.

If you distribute media files on demand using the Adobe Media Server RTMP protocol, your origin server is always an Amazon S3 bucket.

You upload your files to your origin servers. Your files, also known as objects, typically include web pages, images, and media files, but can be anything that can be served over HTTP or a supported version of Adobe RTMP, the protocol used by Adobe Flash Media Server.

If you're using an Amazon S3 bucket as an origin server, you can make the objects in your bucket publicly readable, so that anyone who knows the CloudFront URLs for your objects can access them. You also have the option of keeping objects private and controlling who accesses them. See Serving Private Content through CloudFront.

You create a CloudFront distribution, which tells CloudFront which origin servers to get your files from when users request the files through your web site or application. At the same time, you specify details such as whether you want CloudFront to log all requests and whether you want the distribution to be enabled as soon as it's created.

CloudFront assigns a domain name to your new distribution and displays it in the CloudFront console or returns it in the response to a programmatic request, for example, an API request.

CloudFront sends your distribution's configuration (but not your content) to all of its edge locations—collections of servers in geographically dispersed data centers where CloudFront caches copies of your objects.


Well folks--- have at it...this is as BIG AS IT GETS with Amazon CloudFront as the CDN!

For more information please go here --->>>
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Introduction.html