Amazon Cloudfront simplifies the delivery and security of the web application with a new user -friendly interface | Amazon Web Services

Amazon Cloudfront simplifies the delivery and security of the web application with a new user -friendly interface | Amazon Web Services

Polly expressed

Today, we announce a new simplified experience from OnBooder for Amazon Cloudfront, which developers can use to speed up and secure their web applications in seconds. This new experience, along with improvements to the AWS WAF console, makes it easier for developers than ever to configure content and security services without requireing deep technical knowledge.

The delivery and security settings for web applications are traditionally required to navigate multiple Amazon Web Services (AWS) services and make numerous configuration decisions. With this new cloudfront load experience, developers can now create a fully configured DNS distribution and TLS certificate just a few clicks.

Amazon Cloudfront offers benefits for organizations of all sizes that want to supply content and applications around the world. As a network of CDN) Cloudfront, it significantly improves application performance by serving content from EDGE places closest to your users, latency and improving the user interface. In addition to performance, cloudfront provides built -in security features that protect your applications from distributed attacks to denying the service (DDOS) and other threats on the edge, preventing harmful operations from achieving the infrastructure of origin. The service automatically expands with your operation requirements without required any manual intervention, with ease of manipulation of planned and unsettled traffic spikes. Whether you run a small website or extensive application, Cloudfront integration with other AWS services and new simplified consoles makes it easier to implement these basic applications for your web applications.

Simplified Cloudfront Configuration

A new experience from the cloudfront console leads developers through a simplified workflow that begins with the name of the domain they want for their distribution. When using the Amazon Route 53, the experience is automatically processed into providing TLS certificates and DNS record configurations and includes proven security procedures by default. These united approaches eliminate the need to switch between multiple services such as AWS certificate manager, Route 53 and AWS WAF, and offer developers a rapid time to produce without having to immerse deep configuration options.

For example, a developer can now create a secure cloudfront for its applications before balancing the load by entering the domain name and selecting their load leveling as origin. Automatically, the console recommends optimal CDN configurations and security -based security and application requirements and developers can confidently deploy that the proven AWS procedures.

For developers who want to host the static website at Amazon Simple Storage Service (Amazon S3), Cloudfront provides several important advantages. First, this improves the performance of your site by storing content at EDGE locations closer to your users, reducing latency and improving page loading time. Second, it helps protect your S3 bucket as a safety layer – Cloudfront can be configured as the only way to access your content, and prevent direct access to the S3 bucket. The new experience automatically configures these best security procedures for you.

Increased security integration with AWS WAF

We complement the new experience with Cloudfront and also introduce the improved AWS WAF consoles, which includes intelligent rules packages – curator sets of security rules based on application type and security requirements. These rules packages allow developers to implement undetectivity controls without having to be hearing experts.

When creating cloudfront distribution, developers can now allow AWS WAF protection through an integrated experience that uses these new rules packages. The console provides clear security configurations that developers can use to preview and verify their settings before deployment.

Web applications today face numerous security threats, including SQL Injection Attacks, Cross-Site Scripting (XSS) and another 10 TOP 10 TOP 10. With the new AWS WAF integration, you will automatically provide protection against these common assault vectors. Recommended rules packages provide immense protection against harmful robots, common web exploitation and known bad actors, and at the same time prevent attacks on direct origin that could overcome your infrastructure.

Let’s take a look

If you have ever created Amazon Cloudfront distribution, you will notice that things have changed. The new experience is to follow and understand. For my example, it is a thing to create a distribution for a static website using Amazon S3 as my origin.

A new experience on board for Amazon Cloudfront

IN Step 1I give my distribution name and select from A single site or application Or new Architecture more teen The option I can use to configurate that Missen uses more domains but shares a common configuration. I choose A single site or application and enter the optional domain name. With a new experience I can use Domain check The verification button has my domain as a file of Route 53 zone.

I will also select the origin for distribution, which is which cloudfront load the content that serves and cache. For my Typical originI select Amazon S3. As the previous screshot shows, there are several other options from which you can choose. Each of the options is designed to configure the strictest as possible for the most popular use of boxes. I will also select a bucket of S3, EITH by entering the bucket name or using Browse the S3 Button.

Furthermore, I have several settings related to the use of Amazon S3 as my origin. Tea Grant Cloudfront Access to Origin The possibility is important. This option (selected by default) updates my S3 Bucket policies to allow cloudfront to allow access to my bucket and configure my bucket for Opening of Accession of Origin. In this way, I can use a completely private bucket and know that the assets in my bucket can only be accessed through Cloudfront. This is a critical step to maintain the safety of my bucket and assets.

In the next step I introduce the opportunity to configure AWS WAF. With AWS WAF enabled, my web servers are better protected because they check every Incompan request of potential threats before allowing them to get to my web servers. The AWS WAF permits, and as you can see in the next screen image, there is a calculator that helps estimate additional fees.

A new experience on board for Amazon Cloudfront

Now available

The new AWS WAF insolutions are available today in all AWS regions where these services are offered. You can start using these new features via the AWS management console. There are no additional fees for using this experience – you only pay for WAF Cloud and AWS resources you use based on their respective price models.

If you want to learn more about a new experience on board Cloudfront and WAF AWS enhancements, visit Amazon Cloudfront and AWS WAF documentation. With these simplified experiences, start faster and safer web applications.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *