11/18/2024, 12:00:00 AM ~ 11/19/2024, 12:00:00 AM (UTC)

Recent Announcements

Amazon EC2 X2iezn instances are now available in additional AWS region

Starting today, memory optimized Amazon EC2 X2iezn instances are available in Middle East (UAE). Amazon EC2 X2iezn instances are powered by 2nd generation Intel Xeon Scalable processors with an all core turbo frequency of up to 4.5 GHz, the fastest in the cloud. These instances are a great fit for electronic design automation (EDA) workloads as well as relational databases that benefit from high single-threaded processor performance and a large memory footprint. The combination of high single-threaded compute performance and a 32:1 ratio of memory to vCPU make X2iezn instances an ideal fit for EDA workloads including physical verification, static timing analysis, power sign-off, and full chip gate level simulation, and database workloads that are license bounded. These instances are built on the AWS Nitro System, which is a rich collection of building blocks that offloads many of the traditional virtualization functions to dedicated hardware, delivering high performance, high availability, and highly-secure cloud instances.\n With this additional region, the X2iezn instances are now available in the AWS US West (Oregon), US East (Northern Virginia), Europe (Ireland), Asia Pacific (Tokyo), and Middle East (UAE) regions. X2iezn instances will be available for purchase with Savings Plans, Reserved Instances, Convertible Reserved, On-Demand, and Spot instances, or as Dedicated instances or Dedicated hosts. To get started with X2iezn instances, visit the AWS Management Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, visit the EC2 X2iezn instances Page, visit the AWS forum for EC2 or connect with your usual AWS Support contacts.

AWS IoT SiteWise announces new generative AI-powered industrial assistant

AWS IoT SiteWise is a managed service that simplifies the collection, organization, and monitoring of industrial equipment data at scale. Today, we are excited to announce the general availability of AWS IoT SiteWise Assistant, a generative AI-powered assistant in AWS IoT SiteWise that allows industrial users to gain insights, solve problems, and take actions from their operational data and other data sources intuitively using natural language queries.\n With the AWS IoT SiteWise Assistant, you can easily interact with your operational data by clicking on alarms in the SiteWise Monitor dashboard to get summaries or by asking questions like “What assets have active alarms?” or “How do I fix the wind turbine’s low RPM issue?”. The assistant understands the context of your industrial data in AWS IoT SiteWise from sources like sensors, machines, and related processes, and then contextualizes the data with your centralized knowledge base using Amazon Kendra to provide useful insights, empowering faster decision making to reduce downtime, optimize processes, and improve productivity. AWS IoT SiteWise Assistant introduces new APIs that allow industrial solutions to access these insights on-demand. Developers can integrate capabilities of the Assistant into their industrial applications using updated IoT AppKit widgets like Chatbots, Line Charts, and KPI Gauges. Additionally, a Preview of the new Assistant-aware AWS IoT SiteWise Monitor portal offers a no-code experience for visualizing key data-driven insights. AWS IoT SiteWise Assistant is now available in US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Ireland). Check out the user guide, API reference, and launch blog to learn more.

Amazon EKS simplifies providing IAM permissions to EKS add-ons

Amazon Elastic Kubernetes Service (EKS) now offers a direct integration between EKS add-ons and EKS Pod Identity, streamlining the lifecycle management process for critical cluster operational software that needs to interact with AWS services outside the cluster.\n EKS add-ons that enable integration with underlying AWS resources need IAM permissions to interact with AWS services. EKS Pod Identities simplify how Kubernetes applications obtain AWS IAM permissions. With today’s launch, you can directly manage EKS Pod Identities using EKS add-ons operations through the EKS console, CLI, API, eksctl, and IAC tools like AWS CloudFormation, simplifying usage of Pod Identities for EKS add-ons. This integration expands the selection of Pod Identity compatible EKS add-ons from AWS and AWS Marketplace available for installation through the EKS console during cluster creation. EKS add-ons integration with Pod Identities is generally available in all commercial AWS regions. To get started, see the EKS user guide.

Amazon Aurora MySQL 3.08 (compatible with MySQL 8.0.39) is generally available

Starting today, Amazon Aurora MySQL-Compatible Edition 3 (with MySQL 8.0 compatibility) will support MySQL 8.0.39. In addition to several security enhancements and bug fixes, MySQL 8.0.39 contains enhancements that improve database availability when handling large number of tables and reduce InnoDB issues related to redo logging, and index handling.\n Aurora MySQL 3.08 also includes multiple availability improvements to reduce database restarts, memory management telemetry improvements with new CloudWatch metrics, major version upgrade optimizations for Aurora MySQL 2 to 3 upgrades, and general improvements around memory management and observability. For more details, refer to the Aurora MySQL 3.08 and MySQL 8.0.39 release notes. To upgrade to Aurora MySQL 3.08, you can initiate a minor version upgrade manually by modifying your DB cluster, or you can enable the “Auto minor version upgrade” option when creating or modifying a DB cluster. This release is available in all AWS regions where Aurora MySQL is available. Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.

AWS Chatbot adds support for chatting about AWS resources with Amazon Q Developer in Microsoft Teams and Slack

We are excited to announce the general availability of Amazon Q Developer in AWS Chatbot, which provides answers to customers’ AWS resource related queries in Microsoft Teams and Slack.\n When issues occur, customers need to quickly find relevant resources to troubleshoot issues. Customer can now ask questions in natural language in chat channels to list resources in AWS accounts, get specific resource details, and ask about related resources using Amazon Q Developer. With Amazon Q Developer in AWS Chatbot, customers find AWS resources by typing “@aws show ec2 instances in running state in us-east-1” or “@aws what is the size of the auto scaling group XX in us-east-2?” Get started with AWS Chatbot by visiting the Chatbot Console and by downloading the AWS Chatbot app from the Microsoft Teams marketplace or Slack App Directory. To get started with chatting with Amazon Q in AWS Chatbot, visit the Asking Amazon Q questions in AWS Chatbot in AWS Chatbot documentation.

Amazon DynamoDB announces general availability of attribute-based access control

Amazon DynamoDB is a serverless, NoSQL, fully managed database with single-digit millisecond performance at any scale. Today, we are announcing the general availability of attribute-based access control (ABAC) support for tables and indexes in all AWS Commercial Regions and the AWS GovCloud (US) Regions. ABAC is an authorization strategy that lets you define access permissions based on tags attached to users, roles, and AWS resources. Using ABAC with DynamoDB helps you simplify permission management with your tables and indexes as your applications and organizations scale.\n ABAC uses tag-based conditions in your AWS Identity and Access Management (IAM) policies or other policies to allow or deny specific actions on your tables or indexes when IAM principals’ tags match the tags for the tables. Using tag-based conditions, you can also set more granular access permissions based on your organizational structures. ABAC automatically applies your tag-based permissions to new employees and changing resource structures, without rewriting policies as organizations grow. There is no additional cost to use ABAC. You can get started with ABAC using the AWS Management Console, AWS API, AWS CLI, AWS SDK, or AWS CloudFormation. Learn more at Using attribute-based access control with DynamoDB.

AWS Controllers for Kubernetes for AWS Private CA now generally available

AWS Controllers for Kubernetes (ACK) service controller for AWS Private Certificate Authority (AWS Private CA) has graduated to generally available status.\n By using ACK service controller for AWS Private CA, customers can now provision and manage AWS Private CA certificate authorities (CAs) and private certificates directly from Kubernetes. You can use private certificates to secure containers with encryption and identify workloads. AWS Private CA enables creation of private CA hierarchies, including root and subordinate CAs, without the investment and maintenance costs of operating an on-premises CA. With AWS Private CA, you can issue certificates automatically and at scale from a highly-available, managed cloud CA that is backed by hardware security modules. To get started using ACK service controller for AWS Private CA visit the documentation. You can learn more about ACK and other service controllers here.

Announcing business planning feature in AWS Partner Central

AWS Partner Central is launching a business planning feature to help AWS Partners create successful partnerships and accelerate co-sell with AWS.\n Currently, Partners have multiple touchpoints, conversations, and emails with AWS Partner management and sales teams as part of business planning exercises. AWS is making this collaboration easier and more efficient by centralizing the business planning process and standardizing templates in Partner Central. This will provide a central mechanism to help track progress toward business goals with AWS. Partners can create joint business plans with AWS that are tailor-made for their unique business needs. Partners can review and edit inputs, set goals, and track progress in a single experience. Comprehensive reporting provides year-to-date actual performance, current-year attainment, and year-over-year changes for selected business metrics, reducing manual effort for collecting data from various sources. The business planning feature is available to AWS Partners who are actively engaged with AWS Partner management teams to create joint business plans. To get started, reach out to your AWS Partner contact to initiate a business plan. Once a draft plan is shared, log in to AWS Partner Central, navigate to “My company,” and click on “Business plan” to start collaborating.

Easily troubleshoot NodeJS applications with Amazon CloudWatch Application Signals

Today, AWS announces the general availability of NodeJS applications monitoring on Amazon CloudWatch Application Signals, an OpenTelemetry (OTel) compatible application performance monitoring (APM) feature in CloudWatch. Application Signals simplifies the process of automatically tracking application performance against key business or service level objectives (SLOs) for AWS applications. Service operators can access a pre-built, standardized dashboard for AWS application metrics through Application Signals.\n Customers already use Application Signals to monitor their Java, Python and .NET applications deployed on EKS, EC2 and other platforms. With this release, they can now easily onboard and troubleshoot issues in their NodeJS applications with no additional code. NodeJS application developers can quickly triage current operational health, and whether their applications are meeting their longer-term performance goals. Customers can ensure high availability of their NodeJS applications through Application Signals’ easy navigation flow, starting with an alert for a service level indicator (SLI) gone unhealthy and deep diving from there to an error or a spike in the auto generated graphs for application metrics (latency/errors/requests). In a single pane of glass view, they can correlate application metrics with traces, application logs and infrastructure metrics to troubleshoot issues with their application in a few clicks. Application Signals is available in all commercial AWS Regions, except, CA West (Calgary) Region, Asia Pacific (Malaysia), AWS GovCloud (US) Regions and China Regions. For pricing, see Amazon CloudWatch pricing. To learn more, see documentation to enable Amazon CloudWatch Application Signals for Amazon EKS, Amazon EC2, native Kubernetes and custom instrumentation for other platforms.

Amazon Q generative SQL in Amazon Redshift Query Editor now available in additional AWS regions

Amazon Q generative SQL in Amazon Redshift Query Editor is available in AWS South America (Sao Paulo), Europe (London), and Canada (Central) regions. Amazon Q generative SQL is available in Amazon Redshift Query Editor, an out-of-the-box web-based SQL editor for Amazon Redshift, to simplify SQL query authoring and increase your productivity by allowing you to express SQL queries in natural language and receive SQL code recommendations. Furthermore, it allows you to get insights faster without extensive knowledge of your organization’s complex Amazon Redshift database metadata.\n Amazon Q generative SQL uses generative Artificial Intelligence (AI) to analyze user intent, SQL query patterns, and schema metadata to identify common SQL query patterns directly within Amazon Redshift, accelerating the SQL query authoring process for users, and reducing the time required to derive actionable data insights. Amazon Q generative SQL provides a conversational interface where users can submit SQL queries in natural language, within the scope of their current data permissions. For example, when you submit a question such as ‘Find total revenue by region,’ Amazon Q generative SQL will recognize and suggest the appropriate SQL code for this frequent query pattern by joining multiple Amazon Redshift tables, thus saving time and decreasing the likelihood of errors. You can either accept the query or enhance your prior query by asking additional questions. To learn more about pricing, visit the Amazon Q Developer pricing page. See the documentation to get started.

Self-service capacity management for AWS Outposts

AWS Outposts now supports self-service capacity management making it easy for you to view and manage compute capacity on your Outposts. Outposts brings native AWS services, infrastructure, and operating models to virtually any data center, co-location space, or on-premises facility by providing the same services, tools, and partner solutions with EC2 on premises. Customers have evolving business requirements and often need to fine-tune their application needs as their business scales. Capacity management enables viewing and modifying the configuration of EC2 capacity installed on Outposts.\n Customers define their configuration when ordering a new Outposts to support a variety of different instances. Customers utilize capacity management to view these instances on their Outposts, their configured sizes, and their placement within the Outposts. Customers can also use capacity management to view, plan, and modify their capacity configuration which they will customize through this new self-service UI and API. These capacity management features are available in all AWS Regions where Outposts is supported. Check out the Outposts rack FAQs page and the Outposts servers FAQs page for the full list of supported Regions. To learn more about these capacity management capabilities for Outposts, read the Outposts user guide. To discuss Outposts capacity needs for your on-premises workloads with an Outposts specialist, submit this form.

AWS End User Messaging announces cost allocation tags for SMS

Today, AWS End User Messaging announces cost allocation tags for SMS resources, allowing you to track spend for each tag associated with a resource. AWS End User Messaging provides developers with a scalable and cost-effective messaging infrastructure without compromising the safety, security, or results of their communications.\n You can now assign a tag to each resource, and summarize the spend of that resource using cost allocation tags in the AWS Billing and Cost management console. To learn more, visit the AWS End User Messaging SMS User Guide.

Amazon Application Recovery Controller zonal shift and zonal autoshift extend support for EC2 Auto Scaling

Amazon Application Recovery Controller (ARC) zonal shift and zonal autoshift have expanded their capabilities and now support EC2 Auto Scaling. ARC zonal shift helps you quickly recover an unhealthy application in an Availability Zone (AZ), and reduce the duration and severity of impact to the application due to events such as power outages and hardware or software failures. ARC zonal autoshift safely and automatically shifts your application’s traffic away from an AZ when AWS identifies a potential failure affecting that AZ.\n EC2 Auto Scaling customers can now shift traffic away from an AZ in the event of a failure. Zonal shift works with EC2 Auto Scaling by stopping dynamic scale-in, so that capacity is not unnecessarily removed and launching new EC2 instances in the healthy AZs only. In addition, you can set health checks to enabled in the impaired AZ or disable health checks in the impaired AZ. When disabled, it will pause unhealthy instance replacement in the AZ that has an active zonal shift. Enable your EC2 Auto Scaling Groups for zonal shift using the EC2 Auto Scaling console or API, and then trigger a zonal shift or enable autoshift via ARC zonal shift console or API. To learn more review the ARC documentation and read this launch blog. There is no additional charge for using zonal shift or zonal autoshift. See the AWS Regional Services List for the most up-to-date availability information.

EC2 Auto Scaling now supports Amazon Application Recovery Controller zonal shift and zonal autoshift

EC2 Auto Scaling now supports Amazon Application Recovery Controller (ARC) zonal shift and zonal autoshift to help you quickly recover an impaired application from failures in an Availability Zone (AZ). Starting today, you can shift the launches of EC2 instances in an Auto Scaling Group (ASG) away from an impaired AZ to quickly recover your unhealthy application in another AZ, reducing the duration and severity of impact due to events such as power outages and hardware, or software failures. This new integration also brings support for ARC zonal autoshift, which automatically starts a zonal shift for enabled ASGs when AWS identifies a potential failure affecting an AZ.\n You can initiate a zonal shift for an ASG from the Amazon EC2 Auto Scaling or Application Recovery Controller console. You can also use the AWS SDK to start a zonal shift and programmatically shift the instances in your ASG away from an AZ, and shift it back once the affected AZ is healthy. There is no additional charge for using zonal shift. Zonal shift is now available in all AWS Regions. To get started, read the launch blog, or refer to the documentation.

Announcing Amazon CloudWatch Metrics support in AWS End User Messaging

Today, AWS announces general availability support for 10 new Amazon CloudWatch metrics in AWS End User Messaging for the SMS and MMS channel. AWS End User Messaging provides developers with a scalable and cost-effective messaging infrastructure without compromising the safety, security, or results of their communications.\n You can now use CloudWatch metrics to monitor SMS and MMS message performance. The new metrics allow you to track the number of messages sent and delivered, messages feedback rates such as one-time passcodes conversions, and track messages blocked by SMS protect. Customers can use CloudWatch Metrics Insights to graph and identify trends in real time and monitor those trends directly in the AWS End User Messaging console or in Amazon CloudWatch. To learn more, visit the AWS End User Messaging SMS User Guide.

AWS End User Messaging introduces phone number block/allow rules

Today, AWS End User Messaging expands SMS protect capabilities with phone number rules. With phone number rules, you can explicitly block or allow messages to individual phone numbers overriding your country rule settings.\n You can use the new rules to fine tune your messaging strategy. For instance, you can use “block” rules to stop sending messages to specific numbers where you see abuse, helping you avoid unnecessary SMS costs. The phone number rules can be configured in the AWS End User Messaging console or accessed via APIs, enabling seamless integration with customer data platforms, contact centers, or other systems and databases that you integrate with. To learn more and start using phone number block/allow rules, visit the AWS End User Messaging SMS User Guide.

AWS End User Messaging launches message feedback tracking

Today, AWS End User Messaging now allows you to track feedback for messages sent through the SMS, and MMS channel. AWS End User Messaging provides developers with a scalable and cost-effective messaging infrastructure without compromising the safety, security, or results of their communications.\n For each SMS and MMS you send, you can now track message feedback rates like one-time passcode conversions, promotional offer link clicks, or online shopping cart additions. Message feedback rates allow you to track leading indicators for message performance that is specific to your use-case. To learn more, visit the AWS End User Messaging SMS User Guide.

AWS App Studio is now generally available

AWS App Studio, a generative AI–powered app-building service that uses natural language to build enterprise-grade applications, is now generally available. App Studio helps technical professionals (such as IT project managers, data engineers, enterprise architects, and solution architects) build intelligent, secure, and scalable applications without requiring deep software development skills. App Studio handles deployments, operations, and maintenance, allowing users to focus on solving business challenges and boosting productivity.\n App Studio is the fastest and easiest way to build enterprise-grade applications. Getting started is simple. Users describe the application they need in natural language, and App Studio’s generative AI–powered assistant creates an application with a multipage UI, a data model, and business logic. Builders can easily modify applications using natural language, or with App Studio’s visual canvas. They can also enhance their applications with generative AI using built-in components to generate content, summarize information, and analyze files. Applications can connect to existing data using built-in connectors for AWS (such as Amazon Aurora, Amazon DynamoDB, and Amazon S3) and Salesforce, and also hundreds of third-party services (such as HubSpot, Jira, Twilio, and Zendesk) using an API connector. Users can customize the look and feel of their applications to align with brand guidelines by selecting their logo and company color palette. With App Studio it’s free to build—you only pay for the time employees spend using the published applications, saving up to 80% compared to other comparable offerings.

App Studio is generally available in the following AWS Regions: US West (Oregon) and Europe (Ireland).

To learn more and get started, visit AWS App Studio, review the documentation, and read the announcement.

Amazon Connect offers new personalized and proactive engagement capabilities

Amazon Connect now offers a set of new capabilities to help you proactively address customer needs before they become potential issues, enabling better customer outcomes. You can initiate proactive outbound communications for real-time service updates, promotional offers, product usage tips, and appointment reminders at just the right moments throughout your customer’s experience from the right channel. Use Amazon Connect Customer Profiles to define target segments that are dynamically updated based on real-time customer behaviors including orders from point-of-sale systems, location data from mobile apps, appointments from scheduling systems, or interactions from websites. Use Amazon Connect outbound campaigns to configure outbound communications in just a few clicks and engage customers with timely, personalized communications via their preferred channels, including voice calls, SMS, or email. Visualize campaign performance using dashboards from Amazon Connect Analytics, ensuring clarity and effectiveness in your proactive customer engagement strategies.\n With Amazon Connect Customer Profiles and Amazon Connect outbound campaigns, only pay-as-you-go for customer profiles utilized daily, outbound campaigns processing and for associated channels usage. Both features of Amazon Connect are available in US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Sydney), Canada (Central), and Europe (Frankfurt) and Europe (London). To learn more, visit our webpages for Customer Profiles and for outbound campaigns.

Amazon Q Developer in the AWS Management Console now uses the service you’re viewing as context for your chat

Amazon Q Developer in the AWS Management Console now provides context-aware assistance for your questions about resources in your account. This feature allows you to ask questions directly related to the console page you’re viewing, eliminating the need to specify the service or resource in your query. Q Developer uses the current page as additional context to provide more accurate and relevant responses, streamlining your interaction with AWS services and resources. When the service or resource cannot be inferred, Q Developer now prompts for clarification about the specific resource in question. It presents a list of potentially relevant resources, allowing you to select the appropriate one.\n Customers use AWS Management Console’s curated experiences to investigate and act on their resources. Q Developer chat in the console allows customers to ask questions about AWS services and resources. Now, Q Developer uses the resource you’re currently viewing as context, reducing the need to specify resource identifiers to Q. For example, if you are viewing an EC2 instance and ask Amazon Q, “what is the ami of this instance?” you will not need to specify the instance you are referring to. For ambiguous questions without clear context, Q Developer offers potentially relevant resource options. Q can now count up to 500 resources of a specific type to assist with quantification. Start gaining deeper insight into your resources using the AWS resource inspection capabilities with Amazon Q in the AWS console. Learn more about Amazon Q Developer here.

AWS Command Line Interface adds PKCE-based authorization for single sign-on

The AWS Command Line Interface (AWS CLI) v2 now supports OAuth 2.0 authorization code flows using the Proof Key for Code Exchange (PKCE) standard. This provides a simple and safe way to retrieve credentials for AWS CLI commands.\n The AWS CLI is a unified tool that enables you to control multiple AWS services from the command line and to automate them through scripts. AWS CLI v2 offers integration with AWS IAM Identity Center, the recommended service for managing workforce access to AWS applications and multiple AWS accounts. The authorization code flow with PKCE is the recommended best practice for access to AWS resources from desktops and mobile devices with web browsers. It is now the default behavior when running the aws sso login or aws configure sso commands. To learn more, see Configuring IAM Identity Center authentication with the AWS CLI in the AWS CLI User Guide. Share your questions, comments, and issues with us on GitHub. AWS IAM Identity Center is available at no additional cost in AWS Regions.

Amazon Aurora MySQL now supports R7i instances

Amazon Aurora with MySQL compatibility now supports R7i database instances powered by custom 4th Generation Intel Xeon Scalable processors. R7i instances offer larger instance sizes, up to 48xlarge and features an 8:1 ratio of memory to vCPU, and the latest DDR5 memory. These instances are now available in the following AWS Regions: US East (N. Virginia, Ohio), US West (N. California, Oregon), Asia Pacific (Jakarta, Mumbai, Seoul, Singapore, Sydney, Tokyo), Canada (Central), and Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm).\n You can spin up R7i database instances in the Amazon RDS Management Console or using the AWS CLI. Upgrading a database instance to R7i instance family requires a simple instance type modification. For more details, refer to the Aurora documentation. Amazon Aurora is designed for unparalleled high performance and availability at global scale with MySQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.

AWS Lake Formation is now available in the Asia Pacific (Malaysia) Region

AWS Lake Formation is a service that allows you to set up a secure data lake in days. A data lake is a centralized, curated, and secured repository that stores your data, both in its original form and prepared for analysis. A data lake enables you to break down data silos and combine different types of analytics to gain insights and guide better business decisions.\n Creating a data lake with Lake Formation allows you to define where your data resides and what data access and security policies you want to apply. Your users can then access the centralized AWS Glue Data Catalog which describes available data sets and their appropriate usage. Your users can then leverage these data sets with their choice of analytics and machine learning services, like Amazon EMR for Apache Spark, Amazon Redshift Spectrum, AWS Glue, Amazon QuickSight, and Amazon Athena. For a list of regions where AWS Lake Formation is available, see the AWS Region Table.

AWS End User Messaging announces integration with Amazon EventBridge

Today, AWS End User Messaging announces an integration with Amazon EventBridge. AWS End User Messaging provides developers with a scalable and cost-effective messaging infrastructure without compromising the safety, security, or results of their communications.\n Now your SMS, MMS and voice delivery events which contain information like the status of the message, price, and carrier information will be available in EventBridge. You can then send send your SMS events to other AWS services and the many SaaS applications that EventBridge integrates with. EventBridge also allows you to create rules that filter and route your SMS events to event destinations you specify. To learn more, visit the AWS End User Messaging SMS User Guide.

AWS Batch now supports multiple EC2 Launch Templates per Compute Environment

AWS Batch now supports association of multiple Launch Templates (LTs) with AWS Batch Compute Environment (CE). You no longer need to create separate AWS Batch CEs if you wanted to apply different configurations based on the size and type of your Amazon Elastic Compute Cloud (EC2) instances. With support for multiple LTs per CE, you can dynamically choose a unique Amazon Machine Image (AMI), provision right amount of storage, or apply unique resource tags and more by associating different EC2 launch templates with different EC2 instance types used by a CE, enabling you to define flexible configurations for running your workloads using fewer CEs.\n You can associate multiple LTs while creating a new CE or update an existing CE to use multiple LTs for different instance types. AWS Batch allows you to define up to 10 LTs, overriding the default LT, per CE for different EC2 instance families or instance family and size combinations. For more information, see Launch Templates page in the AWS Batch User Guide. AWS Batch supports developers, scientists, and engineers in running efficient batch processing for ML model training, simulations, and analysis at any scale. Multi-Node Parallel jobs are available in any AWS Region where AWS Batch is available.

Amazon Redshift to enhance security by changing default behavior

Security is the top priority at Amazon Web Services (AWS). To that end, Amazon Redshift is introducing enhanced security defaults which helps you adhere to best practices in data security and reduce the risk of potential misconfigurations.\n Three default security changes will take effect after January 10, 2025. First, public accessibility will be disabled by default for all newly created provisioned clusters and clusters restored from snapshots. By default, connections to clusters will only be permitted from client applications within the same Virtual Private Cloud (VPC). Second, database encryption will be enabled by default for provisioned clusters. When creating a provisioned cluster without specifying a KMS key, the cluster will automatically be encrypted with an AWS-owned key. Third, Amazon Redshift will enforce SSL connections by default for clients connecting to newly created provisioned and restored data warehouses. This default change will also apply to new serverless workgroups. Please review your data warehouse creation configurations, scripts, and tools to make necessary changes to align with new default settings before January 10, 2025, to avoid any potential disruption. You will still have the ability to modify cluster or workgroup settings to change the default behavior.Your existing data warehouses will not be impacted by these security enhancements. However, it is recommended you review and update your configurations to align with the new default security settings in order to further strengthen the security posture. These new default changes will be implemented in all AWS regions where Amazon Redshift is available. For more information, please refer to our documentation.

AWS Lambda now supports SnapStart for Python and .NET functions

Starting today, you can use Lambda SnapStart with your functions that use the Python and .NET managed runtimes, to deliver as low as sub-second startup performance. Lambda SnapStart is an opt-in capability that makes it easier for you to build highly responsive and scalable applications without provisioning resources or implementing complex performance optimizations.\n For latency sensitive applications that support unpredictable bursts of traffic, high startup latencies—known as cold starts—can cause delays in your users’ experience. Lambda SnapStart can improve startup times by initializing the function’s code ahead of time, taking a snapshot of the initialized execution environment, and caching it. When the function is invoked and subsequently scales up, Lambda SnapStart resumes new execution environments from the cached snapshot instead of initializing them from scratch, significantly improving startup latency. Lambda SnapStart is ideal for applications such as synchronous APIs, interactive microservices, data processing, and ML inference. Lambda SnapStart for Python and .NET is generally available in the following AWS Regions: US East (Ohio, N. Virginia), US West (Oregon), Asia Pacific (Singapore, Tokyo, Sydney), and Europe (Frankfurt, Ireland, Stockholm). You can activate SnapStart for new or existing Lambda functions running on Python 3.12 (and newer) and .NET 8 (and newer) using the AWS Lambda API, AWS Management Console, AWS Command Line Interface (AWS CLI), AWS Cloud Formation, AWS Serverless Application Model (AWS SAM), AWS SDK, and AWS Cloud Development Kit (AWS CDK). For more information, see the Lambda documentation, or the launch blog post. To learn more about pricing for SnapStart on Python and .NET, visit AWS Lambda Pricing

Amazon VPC Lattice now supports Amazon Elastic Container Service (Amazon ECS)

Amazon VPC Lattice now provides native integration with Amazon ECS, Amazon’s fully managed container orchestration service that makes it easy for you to deploy, manage, and scale containerized applications. This launch enables VPC Lattice to offer comprehensive support across all major AWS compute services, including Amazon Elastic Compute Cloud (Amazon EC2), Amazon Elastic Kubernetes Service (Amazon EKS), AWS Lambda, Amazon ECS, and AWS Fargate. VPC Lattice is a managed application networking service that simplifies the process of connecting, securing, and monitoring applications across AWS compute services, allowing developers to focus on building applications that matter to their business while reducing time and resources spent on network setup and maintenance.\n With native ECS integration, you can now directly associate your ECS services with VPC Lattice target groups, eliminating the need for an intermediate Application Load Balancer (ALB). This streamlined integration reduces cost, operational overhead, and complexity, while enabling you to leverage the complete feature sets of both ECS and VPC Lattice. Organizations with diverse compute infrastructure, such as a mix of Amazon EC2, Amazon EKS, AWS Lambda, and Amazon ECS workloads, can benefit from this launch by unifying service-to-service connectivity, security, and observability across all compute platforms. This new feature is available in all AWS Regions where Amazon VPC Lattice is available. To get started, see the following resources:

AWS News Blog: Streamline Container Application Networking with native Amazon ECS support in Amazon VPC Lattice

Amazon ECS Developer Guide

Amazon VPC Lattice User Guide

VPC Lattice related blog posts

Amazon Managed Service for Prometheus collector adds support for update and AWS console

Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, adds support for updating the scrape configuration inline and support for configuration via the Amazon Managed Service for Prometheus AWS console. Starting today, you can update collector parameters including scrape configuration as well as the destination Amazon Managed Service for Prometheus workspace. Further, you can view and edit collectors from within the Amazon Managed Service for Prometheus console.\n Customers can now quickly iterate on the scrape configuration of Amazon Managed Service for Prometheus collectors. With this launch, customers can add, remove, and update scrape targets and jobs without downtime. In addition, you can now use the Amazon Managed Service for Prometheus AWS console to list, create, edit, and delete collectors. Amazon Managed Service for Prometheus collector is available in all regions where Amazon Managed Service for Prometheus is available. To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.

AWS Blogs

AWS Japan Blog (Japanese)

AWS News Blog

AWS Architecture Blog

AWS Cloud Operations Blog

AWS Compute Blog

AWS Contact Center

Containers

AWS Database Blog

AWS Developer Tools Blog

AWS for Industries

AWS Machine Learning Blog

AWS Security Blog

Open Source Project

AWS CLI

Bottlerocket OS

Amazon EKS Anywhere