Lindsey  Koepp

Lindsey Koepp

1602942851

AWS Announces Redis 6 Compatibility to Amazon ElastiCache for Redis

Recently AWS announced Redis 6 compatibility to Amazon ElastiCache for Redis, which brings several new features such as Managed Role-Based Access Control, Client-Side caching and some significant operational improvements.

Earlier this year AWS announced the Global Datastore feature of Amazon ElastiCache for Redis which provides fully-managed, fast, reliable and secure cross-region replication. Moreover, more recent the public cloud vendor improved the ability for customers to monitor their Redis fleet by enabling 18 additional engine and node-level CloudWatch metrics. It also added support for resource-level permission policies - allowing customers to assign AWS Identity and Access Management (IAM) principal permissions to specific ElastiCache resource or resources. And now AWS further enhances the service with Redis 6 compatibility, which brings even more features.

_Source: _https://aws.amazon.com/elasticache

The significant new features that come with the Redis 6 compatibility are:

  • Managed Role-Based Access Control providing users with the ability to create and manage users and user groups that they can use to set up Role-Based Access Control (RBAC) for Redis commands.
  • Client-Side Caching provides server-side enhancements to deliver efficient client-side caching to improve application performance further.
  • Operational Improvements available through several enhancements that improve application availability and reliability, such as improved replication under low memory conditions.

#distributed cache #redis #clustering & caching #cloud #caching #aws #amazon web services #development #architecture & design #devops #news

What is GEEK

Buddha Community

AWS Announces Redis 6 Compatibility to Amazon ElastiCache for Redis
Lindsey  Koepp

Lindsey Koepp

1602942851

AWS Announces Redis 6 Compatibility to Amazon ElastiCache for Redis

Recently AWS announced Redis 6 compatibility to Amazon ElastiCache for Redis, which brings several new features such as Managed Role-Based Access Control, Client-Side caching and some significant operational improvements.

Earlier this year AWS announced the Global Datastore feature of Amazon ElastiCache for Redis which provides fully-managed, fast, reliable and secure cross-region replication. Moreover, more recent the public cloud vendor improved the ability for customers to monitor their Redis fleet by enabling 18 additional engine and node-level CloudWatch metrics. It also added support for resource-level permission policies - allowing customers to assign AWS Identity and Access Management (IAM) principal permissions to specific ElastiCache resource or resources. And now AWS further enhances the service with Redis 6 compatibility, which brings even more features.

_Source: _https://aws.amazon.com/elasticache

The significant new features that come with the Redis 6 compatibility are:

  • Managed Role-Based Access Control providing users with the ability to create and manage users and user groups that they can use to set up Role-Based Access Control (RBAC) for Redis commands.
  • Client-Side Caching provides server-side enhancements to deliver efficient client-side caching to improve application performance further.
  • Operational Improvements available through several enhancements that improve application availability and reliability, such as improved replication under low memory conditions.

#distributed cache #redis #clustering & caching #cloud #caching #aws #amazon web services #development #architecture & design #devops #news

Loma  Baumbach

Loma Baumbach

1596679140

Redis Transactions & Long-Running Lua Scripts

Redis offers two mechanisms for handling transactions – MULTI/EXEC based transactions and Lua scripts evaluation. Redis Lua scripting is the recommended approach and is fairly popular in usage.

Our Redis™ customers who have Lua scripts deployed often report this error – “BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE”. In this post, we will explain the Redis transactional property of scripts, what this error is about, and why we must be extra careful about it on Sentinel-managed systems that can failover.

Redis Lua Scripts Diagram - ScaleGrid Blog

Transactional Nature of Redis Lua Scripts

Redis “transactions” aren’t really transactions as understood conventionally – in case of errors, there is no rollback of writes made by the script.

Atomicity” of Redis scripts is guaranteed in the following manner:

  • Once a script begins executing, all other commands/scripts are blocked until the script completes. So, other clients either see the changes made by the script or they don’t. This is because they can only execute either before the script or after the script.
  • However, Redis doesn’t do rollbacks, so on an error within a script, any changes already made by the script will be retained and future commands/scripts will see those partial changes.
  • Since all other clients are blocked while the script executes, it is critical that the script is well-behaved and finishes in time.

The ‘lua-time-limit’ Value

It is highly recommended that the script complete within a time limit. Redis enforces this in a weak manner with the ‘lua-time-limit’ value. This is the maximum allowed time (in ms) that the script is allowed to run. The default value is 5 seconds. This is a really long time for CPU-bound activity (scripts have limited access and can’t run commands that access the disk).

However, the script is not killed when it executes beyond this time. Redis starts accepting client commands again, but responds to them with a BUSY error.

If you must kill the script at this point, there are two options available:

  • SCRIPT KILL command can be used to stop a script that hasn’t yet done any writes.
  • If the script has already performed writes to the server and must still be killed, use the SHUTDOWN NOSAVE to shutdown the server completely.

It is usually better to just wait for the script to complete its operation. The complete information on methods to kill the script execution and related behavior are available in the documentation.

#cloud #database #developer #high availability #howto #redis #scalegrid #lua-time-limit #redis diagram #redis master #redis scripts #redis sentinel #redis servers #redis transactions #sentinel-managed #server failures

How to Upload to Amazon S3 via AWS CLI and NPM scripts

Static websites are a brilliant way to create performant sites. My website is built using Gatsby and hosted on Amazon S3. I have created a simple script to help you quickly upload your site to S3 by running one simple command in your project terminal.

Prerequisites

Before we start, you must ensure that you have completed the following:

  • Install AWS CLI (Amazon Web Services Command Line Interface) on your machine.
  • Create a bucket in Amazon S3 (this is where we will be uploading our project files to).

This guide assumes that you have some familiarity navigating the AWS Console and each Amazon Web Service.

#aws-s3 #npm #amazon-web-services #amazon #aws #cloud #aws-services

Seamus  Quitzon

Seamus Quitzon

1601341562

AWS Cost Allocation Tags and Cost Reduction

Bob had just arrived in the office for his first day of work as the newly hired chief technical officer when he was called into a conference room by the president, Martha, who immediately introduced him to the head of accounting, Amanda. They exchanged pleasantries, and then Martha got right down to business:

“Bob, we have several teams here developing software applications on Amazon and our bill is very high. We think it’s unnecessarily high, and we’d like you to look into it and bring it under control.”

Martha placed a screenshot of the Amazon Web Services (AWS) billing report on the table and pointed to it.

“This is a problem for us: We don’t know what we’re spending this money on, and we need to see more detail.”

Amanda chimed in, “Bob, look, we have financial dimensions that we use for reporting purposes, and I can provide you with some guidance regarding some information we’d really like to see such that the reports that are ultimately produced mirror these dimensions — if you can do this, it would really help us internally.”

“Bob, we can’t stress how important this is right now. These projects are becoming very expensive for our business,” Martha reiterated.

“How many projects do we have?” Bob inquired.

“We have four projects in total: two in the aviation division and two in the energy division. If it matters, the aviation division has 75 developers and the energy division has 25 developers,” the CEO responded.

Bob understood the problem and responded, “I’ll see what I can do and have some ideas. I might not be able to give you retrospective insight, but going forward, we should be able to get a better idea of what’s going on and start to bring the cost down.”

The meeting ended with Bob heading to find his desk. Cost allocation tags should help us, he thought to himself as he looked for someone who might know where his office is.

#aws #aws cloud #node js #cost optimization #aws cli #well architected framework #aws cost report #cost control #aws cost #aws tags

Hire AWS Developer

Looking to Hire Professional AWS Developers?

The technology inventions have demanded all businesses to use and manage cloud-based computing services and Amazon is dominating the cloud computing services provider in the world.

Hire AWS Developer from HourlyDeveloper.io & Get the best amazon web services development. Take your business to excellence with our best AWS developer that will serve you the benefit of different cloud computing tools.

Consult with experts: https://bit.ly/2CWJgHyAWS Development services

#hire aws developer #aws developers #aws development company #aws development services #aws development #aws