ACUVA

Your Accurate Search for New Technology

Amazon Route 53 Resolver DNS Firewall now supports Domain Redirection

By

Starting today, you can enable Route 53 Resolver DNS Firewall to automatically skip the inspection of domains included in a domain redirection chain, such as Canonical Name (CNAME) and Delegation Name (DNAME), thus avoiding the need to explicitly specify each domain from the chain in your Route 53 DNS Firewall rules when allow-listing domains. Before today, when allow-listing domains, Route 53 DNS Firewall compared every DNS query from your VPC against the domains in the allow-list associated to a DNS Firewall rule. If an incoming query was for a domain present in a redirection chain (e.g. CNAME) that was not included in your allow-list of domains, DNS Firewall would block the DNS resolution for this domain, thereby requiring you to explicitly add each domain in the redirection chain to the allow-list. With this release, you can now configure the DNS Firewall rule to automatically apply to all domains in a redirection chain, such as CNAME or DNAME, without requiring you to add each domain in the chain to the allow-list. Route 53 Resolver DNS Firewall support for domain redirection is available in all Regions where Route 53 is available, including the AWS GovCloud (US) Regions. Visit the AWS Region Table to see all AWS Regions where Amazon Route 53 is available.  You can get started by using the AWS Console or Route 53 API. For more information, visit the Route 53 Resolver product detail page, the feature documentation, or the step-by-step guide in the AWS News Blog. For details on pricing, visit the pricing page.

Amazon Pinpoint now supports multimedia messaging service (MMS)

By

Today, Amazon Pinpoint announces support for outbound multimedia messaging service (MMS) within the United States and Canada. The addition of MMS allows Amazon Pinpoint users to enhance their customer communication experiences with the ability to combine traditional text-only messaging with rich media content such as images, audio, and video files.  To get started, navigate to the phone number page on your Amazon Pinpoint SMS console. This page provides the option to purchase a new phone number with SMS and MMS capability, or to check MMS eligibility on an existing US or Canadian Pinpoint SMS phone number. To submit a new MMS registration request, follow the existing toll-free, 10DLC, and short code registration process. Once your registration is approved, you can begin using the MMS API to send images, video, and audio files. With the new MMS feature, you can track your monthly spend, set Amazon CloudWatch alerts, and collect delivery events using the same AWS tools that are available today. The MMS feature is available in all existing Amazon Pinpoint SMS regions. To learn more and get started, please refer to the following documentation.

Amazon EC2 now protects your AMIs from accidental deregistration

By

Starting today, you can prevent Amazon Machine Images (AMIs) from accidental deregistration by marking them as protected. A protected AMI cannot be deregistered until you explicitly disable deregistration protection. Prior to today, you could recover accidentally deregistered AMIs by onboarding onto Recycle Bin. However, if the AMIs were actively being used to launch instances, unintentional deregistrations could lead to production outages until you recovered those AMIs from Recycle Bin. Now by marking your critical AMIs as protected, you can proactively safeguard your AWS environments against accidental AMI deregistrations. To further safeguard your environments, you can optionally enable a 24-hour cooldown period during which a protected AMI can’t be deregistered even after you disable protection. AMI deregistration protection is now available in all AWS Regions, including the AWS GovCloud (US) Regions and AWS China Regions, and can be enabled through EC2 Console, CLI, and APIs. To learn more, please visit documentation here.

Amazon EC2 simplifies visibility into your active AMIs

By

Starting today, you can check when your Amazon Machine Images (AMIs) were last used to launch EC2 instances by simply describing your AMIs, enabling you to efficiently filter and track your active AMIs. Prior to today, you had to write complex scripts to query which of your AMIs were actively used to launch instances. These scripts became increasingly cumbersome and error-prone as the number of AMIs grew. Now you can easily verify if your AMIs are active – based on when they were used to launch instances – by simply describing those AMIs. You can now easily create advanced filtering scripts through which you can track your active AMIs at-scale and make informed decisions about deprecating, disabling, and deregistering your AMIs. This feature is now available in all AWS Regions, including the AWS GovCloud (US) Regions and AWS China Regions. You can view the last launched time for your AMIs via EC2 Console, CLI, and API. Learn more by visiting the documentation here.

Scroll Up