7/29/2024, 12:00:00 AM ~ 7/30/2024, 12:00:00 AM (UTC)
Recent Announcements
Amazon EC2 Fleet and EC2 Auto Scaling groups now supports aliases for Amazon Machine Images (AMIs)
EC2 Fleet and EC2 Auto Scaling group now support using custom identifiers to reference Amazon Machine Images (AMI) in Auto Scaling groups and EC2 Fleet launch requests configured to choose from a diversified list of instance types. You can create these identifiers using AWS Systems Manager Parameter Store and use the parameters to reference your AMI during instance launch. These AMI references to simplify your automation as you no longer need to modify your code every time a new version of an AMI is created.
Amazon Connect Contact Lens now provides downloadable screen recordings
Amazon Connect Contact Lens now provides the ability to download screen recordings from the contact details page in the Amazon Connect UI, for customers that use Contact Lens screen recording. With this launch, managers can evaluate contact quality and agent performance via offline reviews, as well as review downloaded screen recordings with agents for coaching. This launch also provides a new permission to manage who can download screen recordings.\n This feature is available in all AWS regions where Contact Lens screen recording is offered. To learn more about Amazon Connect Contact Lens, see our website. To learn more about this feature, please visit our help documentation.
Amazon MQ now supports ActiveMQ version 5.18
Amazon MQ now supports ActiveMQ minor version 5.18, which introduces several improvements and fixes compared to the previous version of ActiveMQ supported by Amazon MQ. These enhancements include initial support for the JMS 2.0 simplified APIs, such as JMSContext, JMSProducer, and JMSConsumer, as well as the implementation of methods for XA transactions. Starting from ActiveMQ 5.18, Amazon MQ will manage patch version upgrades for your brokers. All brokers on ActiveMQ version 5.18 will be automatically upgraded to the next compatible and secure patch version in your scheduled maintenance window.\n If you are utilizing prior versions of ActiveMQ, such as 5.17, 5.16, or 5.15, we strongly recommend you to upgrade to ActiveMQ 5.18. You can easily perform this upgrade with just a few clicks in the AWS Management Console. To learn more about upgrading, consult the ActiveMQ Version Management section in the Amazon MQ Developer Guide. To learn more about the changes in ActiveMQ 5.18, see the Amazon MQ release notes. This version is available across all AWS Regions where Amazon MQ is available.
AWS Elemental MediaLive now supports SRT caller input
You can now use AWS Elemental MediaLive to receive sources using SRT caller.\n Secure Reliable Transport (SRT), an open source video transport protocol supported by the SRT Alliance, helps deliver video reliably across the internet. SRT has two primary connection modes: caller and listener. With SRT caller input support in MediaLive you can add inputs to a MediaLive channel by calling into an available listener source address and port. For more information on how to use SRT caller input, visit the MediaLive documentation. AWS Elemental MediaLive is a broadcast-grade live video processing service. It lets you create high-quality live video streams for delivery to broadcast televisions and internet-connected multiscreen devices, like connected TVs, tablets, smartphones, and set-top boxes. The MediaLive service functions independently or as part of AWS Media Services, a family of services that form the foundation of cloud-based workflows and offer you the capabilities you need to transport, create, package, monetize, and deliver video. Visit the AWS region table for a full list of AWS Regions where AWS Elemental MediaLive is available.
Amazon Q Business launches support for cross-region AWS IAM Identity Center access
Amazon Q Business is a fully managed, generative-AI powered assistant that enhances workforce productivity by answering questions, providing summaries, generating content, and completing tasks based on customer’s enterprise data. AWS IAM Identity Center helps set up and centrally manage workforce user identity and their access to their AWS accounts and applications. Q Business is integrated with IAM Identity Center so that workforce users can securely and privately access enterprise content using web applications built with Q Business.\n Prior to today, Q Business applications could only connect to, and source user identity information from IAM Identity Center instances located in the same AWS Region as the Q Business application. Starting today, at the time of Q Business application creation, customers can choose to connect to an IAM Identity Center instance located in a region different from the Q Business application to source user identity information. When users access Q Business applications, Q Business makes cross-region API calls to fetch their identity and attributes from the cross-region Identity Center instance to authenticate users, and authorize user access to the content they are allowed to access. Customers can now use Q Business applications to enhance the productivity of a larger set of users than was possible earlier. This feature is available in all AWS Regions where Amazon Q for Business is available, and is supported for organization instances of IAM Identity Center in all regions except opt-in regions. To learn more, visit the documentation. To explore Amazon Q, visit the Amazon Q website.
Introducing AWS End User Messaging
Today, we announce AWS End User Messaging as the new name for Amazon Pinpoint’s SMS, MMS, push, and text to voice messaging capabilities. We are making this change to simplify how you manage end user communications across your applications and other AWS services. AWS End User Messaging provides developers with a scalable and cost-effective messaging infrastructure without compromising the safety, security, or results of their communications. Developers can integrate messaging to support uses cases such as one-time passcodes (OTP) at sign-ups, account updates, appointment reminders, delivery notifications, promotions and more.\n Your existing applications will continue to work as they did previously and you do not need to take any actions. We have updated the new name for SMS, MMS, push, and text to voice messaging in the AWS Management console, AWS Billing console dashboard, documentation, AWS support, and service webpages. There are no changes to APIs, the AWS Command Line Interface (AWS CLI), the AWS Identity and Access Management (IAM) access policies, service events, and endpoints. The marketing features of campaigns, journeys, segmentation, and analytics continue to be available as Amazon Pinpoint. To learn more and get started, see here.
Build your event-driven application using AWS CloudFormation Git sync status changes
AWS CloudFormation Git sync now publishes sync status changes as events to Amazon Eventbridge. With this launch, you can subscribe to new deployment sync events that shows your Git repositories or resource sync status changes. You can also get instant notification and build on top of it to further automate your GitOps workflow. With EventBridge, you can take advantage of a serverless event bus to easily connect and route events between many AWS services and third-party applications. Events are delivered to EventBridge in near real-time, and you can write simple rules to listen for specific events.\n AWS CloudFormation allows you to launch and configure your desired resources and their dependencies together as a stack described in a template. Using AWS CloudFormation Git sync, you can store this template in a remote Git repository and have your stacks synchronized to automate your workflow. Now, using the status changes in Eventbridge, you can build event-driven application based on the notification you received when the sync completed or failed, track the metrics, or automate rollback deployments of broken code. This feature is available in the following 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), Europe (Paris), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Stockholm), and South America (São Paulo). You learn more from our documentation here and our launch blog here.
AWS Blogs
AWS Japan Blog (Japanese)
- AWS Weekly — 2024/7/22
- RIZAP innovates internal knowledge sharing with generative AI and AWS — improving work efficiency and customer satisfaction with AI chatbots
- Weekly Generative AI with AWS — Week 22/7/2024
AWS News Blog
- AWS and Multicloud: Existing capabilities & continued enhancements
- AWS Weekly Roundup: Llama 3.1, Mistral Large 2, AWS Step Functions, AWS Certifications update, and more (July 29, 2024)
AWS Big Data Blog
- Get started with the new Amazon DataZone enhancements for Amazon Redshift
- Monitoring Apache Iceberg metadata layer using AWS Lambda, AWS Glue, and AWS CloudWatch
AWS Compute Blog
AWS DevOps Blog
- Testing your applications with Amazon Q Developer
- Use OpenID Connect with AWS Toolkit for Azure DevOps to perform AWS CodeDeploy deployments
AWS for Industries
- John Hopkins and AWS: A story of Hope
- Enhance Ecommerce Visualization with Avataar’s Creator Platform on AWS
- Personalized patient experience with digital front door
AWS Machine Learning Blog
- Build generative AI–powered Salesforce applications with Amazon Bedrock
- Transition your Amazon Forecast usage to Amazon SageMaker Canvas
- Connect Amazon Q Business to Microsoft SharePoint Online using least privilege access controls
- Improve the productivity of your customer support and project management teams using Amazon Q Business and Atlassian Jira
AWS Messaging & Targeting Blog
Networking & Content Delivery
- Fever: Building a VPN-less secure network for corporate access
- Active Directory Domain Services integration with Amazon Route 53
AWS Security Blog
- AWS revalidates its AAA Pinakes rating for Spanish financial entities
- Accelerate incident response with Amazon Security Lake – Part 2