CTT Big4 News AWS Recently #IBM0011

CTT Big4 News AWS Recently #IBM0011

Hello Friends, welcome to Big4 Recently

AWS, IBM, Google & Azure – the Big4 Cloud Service providers. In this article, we will explore latest AWS Recently.

Amazon MQ Introduces Four New Broker Instances

Amazon MQ now supports four new M5 broker instances that enable you to scale your brokers to meet higher throughput requirements.  

Amazon MQ is a managed message broker service for Apache ActiveMQ that makes it easy to set up and operate message brokers in the cloud. The new M5 instances offer higher CPU power and network capacity that will benefit many use cases, including non-persistent messaging, fast consumers, and batched transactions. The new default production instance, mq.m5.large, is also offered at a price of 2.7% to 5.3% less than the previous default, mq.m4.large. Pricing varies by region. For more information about pricing, see the Amazon MQ pricing page.

The new instances are mq.m5.large, mq.m5.xlarge, mq.m5.2xlarge, and mq.m5.4xlarge. Including previously launched instances, mq.t2.micro and mq.m4.large, Amazon MQ now supports six instances.

M5 instances are available in all regions where Amazon MQ is available: US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), EU (Ireland), EU (Frankfurt), and Asia Pacific (Sydney).

AWS Elastic Beanstalk Console Adds Support for Application Load Balancer Logging

You can now enable access logs for your Application Load Balancer (ALB) to help analyze traffic patterns and troubleshoot issues from within the AWS Elastic Beanstalk console. Access logs capture detailed information about requests sent to your ALB. These logs contain information such as the time the request was received, the client’s IP address, latencies, request paths, and server responses. Access logging is an optional feature that is disabled by default. To enable ALB access logs for your Elastic Beanstalk environment, select the feature to enable access logs and specify the S3 bucket where the logs will be stored from within the configuration-load balancer page in the Elastic Beanstalk console. To learn more, refer to Configuring an Application Load Balancer in Elastic Beanstalk.

Visit the AWS global region table for a full list of AWS Regions where AWS Elastic Beanstalk is available.

Amazon Macie Adds Support for Service-Linked Roles

Today, Amazon Macie is introducing support for using AWS Identity and Access Management (IAM) service-linked roles to setup Amazon Macie with the delegated permissions needed to access resources in other services on your behalf. Service-linked roles also help you meet monitoring and auditing requirements because all actions performed on your behalf by Amazon Macie will appear in your AWS CloudTrail logs.

The Amazon Macie service-linked role called AWSServiceRoleForAmazonMacie is predefined by Macie and includes all the permissions required by Macie to access other AWS services and resources. Unlike a regular IAM role, you cannot delete the service-linked role if it is still in use by Amazon Macie. This protects you from the inadvertent revocation of permissions required by the service leaving your AWS resources in an inconsistent state. For more information, see Using Service-Linked Roles for Amazon Macie.

Amazon Macie is a security service that automatically discovers, classifies, and protects sensitive data in AWS. The service continuously monitors data access activity for anomalies and alerts when private data are made publicly accessible. Amazon Macie is currently available in US East (N. Virginia) and US West (Oregon). Learn more about Amazon Macie.

Amazon EKS is HIPAA Eligible

Amazon Elastic Container Service for Kubernetes (Amazon EKS) is now HIPAA-eligible. If you have an executed Business Associate Addendum (BAA) with AWS, you can use Amazon EKS to manage processing encrypted Protected Health Information (PHI) in Docker containers deployed onto a cluster of Amazon EC2 compute instances.

For more information, please visit our page on HIPAA compliance. If you plan to process, store, or transmit PHI and do not have an executed BAA from AWS, please contact us for more information. See AWS services in scope for information on compliance for all AWS services.

Please visit the AWS region table to see all AWS regions where Amazon EKS is available.

Amazon Transcribe is Now Integrated with AWS CloudTrail and Amazon CloudWatch Events

Amazon Transcribe is an automatic speech recognition (ASR) service that makes it easy for you to add a speech-to-text capability to your applications. Starting today, Amazon Transcribe API calls are recorded with AWS CloudTrail. Also, now you can monitor API call logs in real-time using Amazon CloudWatch Events. With CloudTrail and CloudWatch Events, you can simplify security analysis, resource change tracking, and troubleshooting your transcription applications, as well as better monitor application health and performance.

With AWS CloudTrail, you can log, continuously monitor, and retain account activity related to API calls across your AWS infrastructure. Your Amazon Transcribe API calls are captured so that you can track requests made to Amazon Transcribe, including the origination of the request, such as the source IP address, the date and time the request was made, and the parameters requested.

In addition, Amazon CloudWatch Events delivers a near real-time stream of system events that describe changes in AWS resources. You can create rules for CloudWatch Events, and events that match rules will be routed to targets for processing. With this integration, you can receive a notification when the transcription job is completed instead of having to request an update on the status.

CloudTrail and CloudWatch Events are available at no additional costs besides from the standard charges for Amazon Transcribe and Amazon S3. Both integrations are available in all AWS Regions that support Amazon Transcribe. Refer to the Region Table to see the list. 

Amazon DynamoDB Backup and Restore Regional Expansion

Amazon DynamoDB backup and restore is now available in the EU (Paris) Region. With on-demand backup and restore, you can create full backups of your DynamoDB tables for data archiving and retention, helping you meet your corporate and governmental regulatory requirements. Point-in-time recovery (PITR) provides continuous backups of your DynamoDB table data, protecting you against accidental writes or deletes. When you enable PITR on your DynamoDB table, you can recover that table from backup at any point in time from the moment you enable it to a maximum of the 35 preceding days.

You can enable backup and restore for your DynamoDB table data with a single click in the AWS Management Console, a simple API call, or with the AWS Command Line Interface (CLI). You can back up tables with no impact on performance and availability to your production applications.

DynamoDB backup and restore is now available in 15 AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), EU (Frankfurt), EU (Ireland), EU (London), EU (Paris), and South America (Sao Paulo).

Quick Start update: SAP HANA with high availability on the AWS Cloud

AWS is pleased to release a major update to the SAP HANA Quick Start that supports Multi-AZ, single-node configurations with high availability. 

The Multi-AZ option uses two Availability Zones for the SAP HANA environment on AWS. It provisions two SAP HANA servers (primary and secondary) in separate, private subnets in those zones and configures them for high availability. You can choose to create a new virtual private cloud (VPC) for your deployment, or provision the SAP HANA servers in your existing infrastructure. The deployment takes about 35 minutes.

The Multi-AZ, single-node, high-availability architecture is based on SUSE Linux Enterprise Server (SLES) High Availability Extension (HAE), which is part of the SLES for SAP operating system. The Quick Start supports a performance-optimized setup, where the SAP HANA primary and secondary servers share the same instance size and other characteristics, and use synchronous replication mode.

That’s it friends in this week for AWS Recently, however please visit specific Cloud provider news that you are interested in from below links.

 

Author: Debashree

A Technical writer and passionate about digital life. Always eager to learn and share knowledge.

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.