Want to earn more as a dev? Practical tips to improve your coding speed, negotiate a higher salary, and become a top-tier engineer.

    Amazon ECS Express Mode now supports AWS Graviton (ARM64) workloads 0 views Eyal Estrin unread, 6:48 AM (20 minutes ago)    to https://aws.amazon.com/about-aws/whats-new/2026/09/amazon-ecs-express-mode-arm-architecture/ https://docs.aws.amazon.com/AmazonECS/latest/developerguide/express-service-overview.html Eyal Estrin Author | Cloud Architect | AWS • Azure • GCP Insights Social: @eyalestrin Connect: https://linktr.ee/eyalestrin Blog: https://security-24-7.com Reply all Reply to author Forward

    Amazon Route 53 Resolver is now generally available on second-generation AWS Outposts racks 0 views Eyal Estrin unread, 7:47 AM (4 minutes ago)    to https://aws.amazon.com/about-aws/whats-new/2026/09/route-53-resolver-gen2-outposts/ https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/outpost-resolver.html Eyal Estrin Author | Cloud Architect | AWS • Azure • GCP Insights Social: @eyalestrin Connect: https://linktr.ee/eyalestrin Blog: https://security-24-7.com Reply all Reply to author Forward

Amazon Cognito now allows you to configure terms of use and privacy policy documents for https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-managed-login.html pages. This helps customers seamlessly present legal terms during user registration while simplifying implementation. With Managed Login, Cognito customers could previously use its no-code editor to customize the user journey from signup and login to password recovery and multi-factor authentication. Now, customers can additionally use Managed Login to easily set up terms of use and privacy policy documents, saving development teams from building custom solutions. With this capability, you can configure terms of use and privacy policy URLs for each app client in your Cognito user pool. When users register, they see text indicating that by signing up, they agree to your terms of use and privacy policy, and a link to your webpage with the agreement. You can configure different URLs for each https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-managed-login.html#managed-login-localization to match your Managed Login localization settings. For example, if you have configured the privacy policy and terms of use documents for French (fr) and the same is selected in the lang query-parameter on the sign-up page URL, users will see the French URL you configured. This capability is available to Amazon Cognito customers using the https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-sign-in-feature-plans.html in AWS Regions where Cognito is available, including the AWS GovCloud (US) Regions. To learn more, refer to the https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-managed-login.html#managed-login-terms-documents and https://aws.amazon.com/cognito/pricing/ for Cognito Essentials and Plus tier.

Master sensitive data handling with DuckDB in this guide to implementing data privacy techniques such as PII masking (includes practical Python code examples).

AWS SAM now supports WebSocket APIs for Amazon API Gateway 0 views Eyal Estrin unread, 1:40 PM (28 minutes ago)    to https://aws.amazon.com/about-aws/whats-new/2026/05/aws-sam-websocket-apis-api-gateway/ https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-websocket-api-overview.html https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-websocketapi.html Eyal Estrin Author | Cloud Architect | AWS • Azure • GCP Insights Social: @eyalestrin Connect: https://linktr.ee/eyalestrin Blog: https://security-24-7.com Reply all Reply to author Forward

Amazon ECS Service Connect now supports Zone-Aware routing 0 views Eyal Estrin unread,    to https://aws.amazon.com/about-aws/whats-new/2026/07/ecs-service-connect-zone-aware/ https://aws.amazon.com/blogs/containers/announcing-zone-aware-routing-in-amazon-ecs-service-connect/ https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect-zone-aware-routing.html Eyal Estrin Author | Cloud Architect | AWS • Azure • GCP Insights Social: @eyalestrin Connect: https://linktr.ee/eyalestrin Blog: https://security-24-7.com Reply all Reply to author Forward

<p>Starting today, Amazon Elastic Kubernetes Service (EKS) enables default envelope encryption for all Kubernetes API data in EKS clusters running Kubernetes version 1.28 or higher. This provides a managed, default experience that implements defense-in-depth for your Kubernetes applications. Using <a href="https://docs.aws.amazon.com/kms/latest/developerguide/overview.html" target="_blank">AWS Key Management Service (KMS)</a> with <a href="https://kubernetes.io/docs/tasks/administer-cluster/kms-provider/#configuring-the-kms-provider-kms-v2" target="_blank">Kubernetes KMS provider v2</a>, EKS now provides an additional layer of security with an AWS owned, KMS encryption key or the option of bringing your own key.<br> <br> Previously, Amazon EKS provided optional envelope encryption with Kubernetes KMS provider v1. Now this is a default configuration for all objects in the Kubernetes API. By default, <a href="https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-owned-cmk" target="_blank">AWS owns the keys</a> used for envelope encryption. You can alternatively <a href="https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html" target="_blank">create</a> or <a href="https://docs.aws.amazon.com/kms/latest/developerguide/importing-keys-conceptual.html" target="_blank">import externally generated keys</a> to AWS KMS for use in your cluster’s managed Kubernetes control plane. If you have an existing customer managed key (CMK) in KMS that was previously used to envelope encrypt your Kubernetes Secrets, this same key will now be used for envelope encryption of the additional Kubernetes API data types in your cluster.<br> <br> Default envelope encryption in Amazon EKS is automatically enabled for all EKS clusters running Kubernetes version 1.28 or higher, and doesn’t require any action from customers. This feature is available at no additional charge in all commercial AWS Regions and the AWS GovCloud (US) Regions. To learn more, visit the <a href="https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-encryption.html" target="_blank">Amazon EKS documentation</a>.</p>

Amazon ECS announces faster service auto scaling 0 views Eyal Estrin unread, 9:55 PM (14 minutes ago)    to https://aws.amazon.com/about-aws/whats-new/2026/06/amazon-ecs-faster-autoscaling/ https://aws.amazon.com/blogs/aws/amazon-ecs-introduces-new-high-resolution-metrics-for-faster-service-auto-scaling/ https://docs.aws.amazon.com/AmazonECS/latest/developerguide/target-tracking-faster-auto-scaling.html Eyal Estrin Author | Cloud Architect | AWS • Azure • GCP Insights Social: @eyalestrin Connect: https://linktr.ee/eyalestrin Blog: https://security-24-7.com Reply all Reply to author Forward

https://aws.amazon.com/about-aws/whats-new/2025/10/amazon-ecs-running-firelens-as-nonroot-user/ https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_firelens.html

https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli.html now supports https://runfinch.com/ as an alternative to Docker for local development and testing of serverless applications. This gives developers greater flexibility in choosing their preferred local development environment when working with SAM CLI to build and test their serverless applications. Developers building serverless applications spend significant time in their local development environments. SAM CLI is a command-line tool for local development and testing of serverless applications. It allows you to build, test, debug, and package your serverless applications locally before deploying to AWS Cloud. To provide the local development and testing environment for your applications, SAM CLI uses a tool that can run containers on your local device. Previously, SAM CLI only supported Docker as the tool for running containers locally. Starting today, SAM CLI also supports Finch as a container development tool. Finch is an open-source tool, developed and supported by AWS, for local container development. This means you can now choose between Docker and Finch as your preferred container tool for local development when working with SAM CLI. You can use SAM CLI to invoke Lambda functions locally, test API endpoints, and debug your serverless applications with the same experience you would have in the AWS Cloud. With Finch support, SAM CLI now automatically detects and uses Finch as the container development tool when Docker is not available. You can also set Finch as your preferred container tool for SAM CLI. This new feature supports all core SAM CLI commands including sam build, sam local invoke, sam local start-api, and sam local start-lambda. To learn more about using SAM CLI with Finch, visit the https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/install-finch.html. 

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html now supports seamless communication between services residing in different AWS accounts through integration with https://aws.amazon.com/ram/ (AWS RAM). This enhancement simplifies resource sharing, reduces duplication, and promotes consistent service-to-service communication across environments for organizations with multi-account architectures. Amazon ECS Service Connect leverages AWS Cloud Map namespaces for storing information about ECS services and tasks. To enable seamless cross-account communication between Amazon ECS Service Connect services, you can now share the underlying AWS Cloud Map namespaces using AWS RAM with individual AWS accounts, specific Organizational Units (OUs), or your entire AWS Organization. To get started, create a resource share in AWS RAM, add the namespaces you want to share, and specify the principals (accounts, OUs, or the organization) that should have access. This enables platform engineers to use the same namespace to register Amazon ECS Service Connect services residing in multiple AWS accounts, simplifying service discovery and connectivity. Application developers can then build services that rely on a consistent, shared registry without worrying about availability or synchronization across accounts. Cross-account connectivity support improves operational efficiency and makes it easier to scale Amazon ECS workloads as your organization grows by reducing duplication and streamlining access to common services. This feature is available with both Fargate and EC2 launch modes now in https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ via the AWS Management Console, API, SDK, CLI, and CloudFormation. To learn more, please refer to the Amazon ECS Service Connect https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html.

Amazon Route 53 Resolver now supports https://aws.amazon.com/privatelink/. Customers can now access and manage https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html and all the related features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) privately, without going through the public internet. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely over the Amazon network. When Route 53 Resolver and its features are accessed via AWS PrivateLink, all operations, such as creating, deleting, editing, and listing, can be handled via the Amazon private network.  Amazon Route 53 Resolver responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs. Route 53 Resolver also offers features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) that you can opt-into. You can use Resolver and its features with AWS PrivateLink in regions where Route 53 Resolver and all its associated features are available today, including the AWS GovCloud (US) Regions. For more information about the AWS Regions where Resolver and its features are available, see https://docs.aws.amazon.com/general/latest/gr/r53.html. To learn more about Route 53 Resolver and its features, please refer to the service https://docs.aws.amazon.com/Route53/latest/APIReference/API_Operations_Amazon_Route_53_Resolver.html.

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html now supports seamless communication between services residing in different AWS accounts through integration with https://aws.amazon.com/ram/ (AWS RAM). This enhancement simplifies resource sharing, reduces duplication, and promotes consistent service-to-service communication across environments for organizations with multi-account architectures. Amazon ECS Service Connect leverages AWS Cloud Map namespaces for storing information about ECS services and tasks. To enable seamless cross-account communication between Amazon ECS Service Connect services, you can now share the underlying AWS Cloud Map namespaces using AWS RAM with individual AWS accounts, specific Organizational Units (OUs), or your entire AWS Organization. To get started, create a resource share in AWS RAM, add the namespaces you want to share, and specify the principals (accounts, OUs, or the organization) that should have access. This enables platform engineers to use the same namespace to register Amazon ECS Service Connect services residing in multiple AWS accounts, simplifying service discovery and connectivity. Application developers can then build services that rely on a consistent, shared registry without worrying about availability or synchronization across accounts. Cross-account connectivity support improves operational efficiency and makes it easier to scale Amazon ECS workloads as your organization grows by reducing duplication and streamlining access to common services. This feature is available with both Fargate and EC2 launch modes in AWS GovCloud (US-West) and AWS GovCloud (US-East) regions via the AWS Management Console, API, SDK, CLI, and CloudFormation. To learn more, please refer to the Amazon ECS Service Connect https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html.

https://aws.amazon.com/iot-core/ now lets you batch multiple IoT messages into a single https://docs.aws.amazon.com/iot/latest/developerguide/https-rule-action.html, before routing the messages to downstream HTTP endpoints. This enhancement helps you to reduce cost and throughput overhead when ingesting telemetry from your Internet of Things (IoT) workloads. AWS IoT Core is a fully managed service that securely connects millions of IoT devices to the AWS cloud. Using https://docs.aws.amazon.com/iot/latest/developerguide/iot-rules.html, you can filter, process, and decode device data, and route that data to AWS services or third-party endpoints via 20+ https://docs.aws.amazon.com/iot/latest/developerguide/iot-rule-actions.html, such as HTTP rule action - which routes the data to HTTP endpoints. With the new feature, you can now batch messages together before routing that data set to downstream HTTP endpoints. To efficiently process IoT messages using the new batching capability, connect your IoT devices to AWS IoT Core and define a HTTP rule action with your desired batch parameters. AWS IoT Core will then process incoming messages according to these specifications and route the messages to your designated HTTP endpoints. For example, you can now combine IoT messages published from multiple smart home devices in a single batch and route it to a HTTP endpoint in your smart home platform. This new feature is available in all AWS Regions where AWS IoT Core is available, including AWS GovCloud (US) and Amazon China Regions. To learn more, visit our https://docs.aws.amazon.com/iot/latest/developerguide/http_batching.html, https://aws.amazon.com/iot-core/pricing/, and https://docs.aws.amazon.com/iot/latest/apireference/API_CreateTopicRule.html.

Amazon WorkSpaces Applications now supports IPv6 for https://docs.aws.amazon.com/appstream2/latest/developerguide/allowed-domains.html and external endpoints, allowing end users to connect to WorkSpaces Applications over IPv6 from IPv6 compatible devices (except SAML authentication). This helps you meet IPv6 compliance requirements and eliminates the need for expensive networking equipment to handle address translation between IPv4 and IPv6. The Internet's growth is consuming IPv4 addresses quickly. WorkSpaces Applications, by supporting IPv6, assists customers in streamlining their network architecture. This support offers a much larger address space and removes the necessity to manage overlapping address spaces in their VPCs. Customers can now base their applications on IPv6, ensuring their infrastructure is future-ready and compatible with existing IPv4 systems via a fallback mechanism. This feature is available at no additional cost in 16 AWS Regions, including US East (N. Virginia, Ohio), US West (Oregon), Canada (Central), Europe (Paris, Frankfurt, London, Ireland), Asia Pacific (Tokyo, Mumbai, Sydney, Seoul, Singapore), and South America (Sao Paulo) and AWS GovCloud (US-West, US-East). WorkSpaces Applications offers pay-as-you go https://aws.amazon.com/appstream2/pricing/. To get started with WorkSpaces Applications, see https://aws.amazon.com/appstream2/getting-started/. To enable this feature for your users, you must use the latest https://clients.amazonappstream.com/ for Windows, macOS or directly through web access. To learn more about the feature, please refer to the service https://docs.aws.amazon.com/appstream2/latest/developerguide/allowed-domains.html.

https://docs.aws.amazon.com/iot/latest/developerguide/device-location.html announces location resolution capabilities for Internet of Things (IoT) devices connected to https://docs.sidewalk.amazon/ network, enabling developers to build asset tracking and geo-fencing applications more efficiently by eliminating the need for GPS hardware in low-power devices. Amazon Sidewalk provides a secure community network through Amazon Sidewalk Gateways (compatible Amazon Echo and Ring devices) to deliver cloud connectivity for IoT devices. https://aws.amazon.com/iot-core/sidewalk/ facilitates connectivity and message transmission between Amazon Sidewalk-connected IoT devices and AWS cloud services. The integration of Amazon Sidewalk with AWS IoT Core, enables you to easily provision, onboard, and monitor your Amazon Sidewalk devices in the AWS cloud. With the new enhancement, you can now use AWS IoT Core’s Device Location feature to resolve the approximate location of your Amazon Sidewalk enabled devices, using input payloads like WiFi access point, Global Navigation Satellite System data, or Bluetooth Low Energy data. AWS IoT Core Device Location uses these inputs to resolve the geo-coordinate data, and delivers the geo-coordinate data to your desired AWS IoT rules or MQTT topics for integration with backend applications. To get started, install Sidewalk SDK v1.19 (or a later version) in your Sidewalk-enabled devices, provision the devices in AWS IoT Core for Amazon Sidewalk, and enable location during the provisioning. This new feature is available in AWS US-East (N. Virginia) Region of AWS cloud where AWS IoT Core for Amazon Sidewalk is available. Please note that Amazon Sidewalk network is available only in the United States of America. For more information, refer https://docs.aws.amazon.com/iot-wireless/latest/developerguide/sidewalk-getting-started.html#sidewalk-gs-workflow, https://docs.sidewalk.amazon/assets/pdf/Amazon_Sidewalk_Location_Library_Developer_Guide-1.0-rev-A.pdf, and https://coverage.sidewalk.amazon/.

AWS announces the release of https://docs.aws.amazon.com/greengrass/v2/developerguide/greengrass-release-2025-11-06.html, introducing new core components for nucleus and nucleus lite. AWS IoT Greengrass is an Internet of Things (IoT) edge runtime and cloud service that helps customers build, deploy, and manage device software at the edge. The latest version 2.16 release includes enhanced debugging capabilities through the system log forwarder component. This component uploads system log files to AWS Cloud Watch, making it easier for developers to troubleshoot IoT edge applications. The AWS IoT Greengrass v2.16 release also features a new nucleus lite version (v2.3) with TPM2.0 specification support, enabling developers to manage edge device security for their resource constrained devices using hardware-based root of trust modules. The implementation helps developers to scale their IoT deployments with confidence while providing secure storage for secrets and streamlined device authentication. AWS IoT Greengrass v2.16 is available in all AWS Regions where AWS IoT Greengrass is offered. To learn more about AWS IoT Greengrass v2.16 and its new features, visit the AWS IoT Greengrass https://docs.aws.amazon.com/greengrass/v2/developerguide/what-is-iot-greengrass.html Follow the Getting Started https://docs.aws.amazon.com/greengrass/v2/developerguide/getting-started.html for a quick introduction to AWS IoT Greengrass.

Eyal Estrin unread, 6:12 AM (1 hour ago)    to https://aws.amazon.com/about-aws/whats-new/2025/12/api-gateway-mcp-proxy-support/ https://docs.aws.amazon.com/apigateway/latest/developerguide/mcp-server.html Eyal Estrin CISSP, CCSP, CISM, CISA, CDPSE, CCSK Blog: https://security-24-7.com | Books: https://amzn.to/42Xai9A | https://amzn.to/3Sggbtv Twitter: @eyalestrin | Bluesky: @eyalestrin.bsky.social

Eyal Estrin unread, 6:57 PM (13 minutes ago)    to https://aws.amazon.com/about-aws/whats-new/2026/06/opensearch-agentic-observability-mcp-app/ https://docs.aws.amazon.com/opensearch-service/latest/developerguide/opensearch-observability-mcp-app.html Eyal Estrin Author | Cloud Architect | AWS • Azure • GCP Insights Social: @eyalestrin Connect: https://linktr.ee/eyalestrin Blog: https://security-24-7.com

Eyal Estrin unread, 12:11 AM (28 minutes ago)    to https://aws.amazon.com/about-aws/whats-new/2025/12/amazon-msk-connect-dual-stack-ipv-and-ipv/ https://docs.aws.amazon.com/msk/latest/developerguide/msk-connect.html Eyal Estrin CISSP, CCSP, CISM, CISA, CDPSE, CCSK Blog: https://security-24-7.com | Books: https://amzn.to/42Xai9A | https://amzn.to/3Sggbtv Twitter: @eyalestrin | Bluesky: @eyalestrin.bsky.social