#AmazonECS hashtag - Bluesky

@awsrecentnews.bsky.social

3 days ago

Amazon ECS Managed Instances now supports FIPS-certified workloads on Graviton and GPU accelerated instances in AWS GovCloud (US) Regions Starting today, customers can deploy their Graviton-based and GPU-accelerated workloads on Amazon Elastic Container Service (Amazon ECS) Managed Instances in a Federal Information Processing Standard (FIPS) compliant mode in the AWS GovCloud (US) Regions. FIPS is a U.S. and Canadian government standard that specifies the security requirements for cryptographic modules that protect sensitive information. In the AWS GovCloud (US) Regions, Amazon ECS Managed Instances automatically enable FIPS compliance by default. ECS Managed Instances communicate through FIPS-compliant endpoints, use appropriately configured cryptographic modules, and boot the underlying kernel in FIPS mode. Customers with federal compliance requirements can run workloads with FIPS-validated cryptographic modules across a broad range of instance types, including Graviton-based, GPU-accelerated, network-optimized, and burstable performance instances. To learn more about FIPS, refer to FIPS on AWS and AWS Fargate Federal Information Processing Standard (FIPS-140). To get started with ECS Managed Instances, use the AWS Console, Amazon ECS MCP Server, ECS Express Mode, or your favorite infrastructure-as-code tooling to enable it in a new or existing Amazon ECS cluster. You will be charged for the management of compute provisioned, in addition to your regular Amazon EC2 costs. To learn more about ECS Managed Instances, visit the feature page, documentation, and AWS News launch blog.

🆕 Amazon ECS Managed Instances now supports FIPS-certified workloads on Graviton and GPU instances in AWS GovCloud (US). FIPS compliance is enabled by default for federal customers. Learn more on AWS FIPS and ECS Managed Instances pages.

#AWS #AmazonEcs

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 days ago

Amazon ECS Managed Instances now supports FIPS-certified workloads on Graviton and GPU accelerated instances in AWS GovCloud (US) Regions Starting today, customers can deploy their Graviton-based and GPU-accelerated workloads on Amazon Elastic Container Service (Amazon ECS) Managed Instances in a Federal Information Processing Standard (FIPS) compliant mode in the AWS GovCloud (US) Regions. FIPS is a U.S. and Canadian government standard that specifies the security requirements for cryptographic modules that protect sensitive information. In the AWS GovCloud (US) Regions, Amazon ECS Managed Instances automatically enable FIPS compliance by default. ECS Managed Instances communicate through FIPS-compliant endpoints, use appropriately configured cryptographic modules, and boot the underlying kernel in FIPS mode. Customers with federal compliance requirements can run workloads with FIPS-validated cryptographic modules across a broad range of instance types, including Graviton-based, GPU-accelerated, network-optimized, and burstable performance instances. To learn more about FIPS, refer to https://aws.amazon.com/compliance/fips/ and https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-fips-compliance.html. To get started with ECS Managed Instances, use the AWS Console, Amazon ECS MCP Server, ECS Express Mode, or your favorite infrastructure-as-code tooling to enable it in a new or existing Amazon ECS cluster. You will be charged for the management of compute provisioned, in addition to your regular Amazon EC2 costs. To learn more about ECS Managed Instances, visit the https://aws.amazon.com/ecs/managed-instances/, https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ManagedInstances.html, and https://aws.amazon.com/blogs/aws/announcing-amazon-ecs-managed-instances-for-containerized-applications.

Amazon ECS Managed Instances now supports FIPS-certified workloads on Graviton and GPU accelerated instances in AWS GovCloud (US) Regions

Starting today, customers can deploy their Graviton-based and GPU-accelerated workloads on Amazon Elastic Container Service (Amazon ECS) Ma...

#AWS #AmazonEcs

0 0 0 0

stormit

@stormitcloud.bsky.social

3 weeks ago

Hands-on: Creating an ECS Cluster and Task with Auto Scaling | Stormit Amazon ECS Auto Scaling with Route 53 Health Checks (New UI)In this video, you’ll learn how to set up an ECS (Elastic Container Service) cluster and task wit...

Build a production ready Amazon ECS cluster with intelligent auto scaling and Route 53 health checks. Adam walks you through cluster setup, scaling policies, health monitoring, and live testing in the new UI.
Watch here 👇
www.youtube.com/watch?v=UR7n...

#Stormit #AmazonECS #AutoScaling

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

1 month ago

Amazon ECS Managed Instances now integrates with Amazon EC2 Capacity Reservations Amazon Elastic Container Service (Amazon ECS) Managed Instances now integrates with Amazon EC2 Capacity Reservations, enabling you to leverage your reserved capacity for predictable workload availability, while ECS handles all infrastructure management. This integration helps you balance reliable capacity scaling with cost efficiency, helping achieve high availability for mission‑critical workloads. Amazon ECS Managed Instances is a fully managed compute option designed to eliminate infrastructure management overhead, dynamically scale EC2 instances to match your workload requirements, and continuously optimize task placement to reduce infrastructure costs. With today’s launch, you can configure your ECS Managed Instances capacity providers to use capacity reservations by setting the capacityOptionType parameter to reserved, in addition to the existing spot and on-demand options. You can also specify reservation preferences to optimize cost and availability: use reservations-only to launch EC2 instances exclusively in reserved capacity for maximum predictability, reservations-first to prefer reservations while maintaining flexibility to fall back to on-demand capacity when needed, or reservations-excluded to prevent your capacity provider from using reservations altogether. To get started, you can use the AWS Management Console, AWS CLI, AWS CloudFormation, or AWS SDKs to configure your ECS Managed Instances capacity provider by choosing capacityOptionType=reserved and providing a capacity reservation group and reservation strategy. This feature is now available in all AWS Regions. For more details, refer to the documentation.

🆕 Amazon ECS Managed Instances now integrates with EC2 Capacity Reservations for predictable workload availability and cost efficiency, balancing reliable scaling and high availability for mission-critical tasks.

#AWS #AmazonEcs

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

1 month ago

Amazon ECS Managed Instances now integrates with Amazon EC2 Capacity Reservations Amazon Elastic Container Service (Amazon ECS) Managed Instances now integrates with Amazon EC2 Capacity Reservations, enabling you to leverage your reserved capacity for predictable workload availability, while ECS handles all infrastructure management. This integration helps you balance reliable capacity scaling with cost efficiency, helping achieve high availability for mission‑critical workloads. https://aws.amazon.com/ecs/managed-instances/ is a fully managed compute option designed to eliminate infrastructure management overhead, dynamically scale EC2 instances to match your workload requirements, and continuously optimize task placement to reduce infrastructure costs. With today’s launch, you can configure your ECS Managed Instances capacity providers to use capacity reservations by setting the capacityOptionType parameter to reserved, in addition to the existing spot and on-demand options. You can also specify reservation preferences to optimize cost and availability: use reservations-only to launch EC2 instances exclusively in reserved capacity for maximum predictability, reservations-first to prefer reservations while maintaining flexibility to fall back to on-demand capacity when needed, or reservations-excluded to prevent your capacity provider from using reservations altogether. To get started, you can use the AWS Management Console, AWS CLI, AWS CloudFormation, or AWS SDKs to configure your ECS Managed Instances capacity provider by choosing capacityOptionType=reserved and providing a capacity reservation group and reservation strategy. This feature is now available in all AWS Regions. For more details, refer to the https://docs.aws.amazon.com/AmazonECS/latest/developerguide/managed-instances-instance-types.html#managed-instances-instance-billing-and-purchase-options.

Amazon ECS Managed Instances now integrates with Amazon EC2 Capacity Reservations

Amazon Elastic Container Service (Amazon ECS) Managed Instances now integrates with Amazon EC2 Capacity Reservations, enabling you to leverage your reserved capacity for predictable workload avai...

#AWS #AmazonEcs

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

1 month ago

Amazon ECS Managed Instances now available in AWS European Sovereign Cloud Amazon Elastic Container Service (Amazon ECS) Managed Instances is now available in the AWS European Sovereign Cloud. ECS Managed Instances is a fully managed compute option designed to eliminate infrastructure management overhead while giving you access to the full capabilities of Amazon EC2. By offloading infrastructure operations to AWS, you get the application performance you want and the simplicity you need while reducing your total cost of ownership. Managed Instances dynamically scales EC2 instances to match your workload requirements and continuously optimizes task placement to reduce infrastructure costs. It also enhances your security posture through regular security patching initiated every 14 days. You can simply define your task requirements such as the number of vCPUs, memory size, and CPU architecture, and Amazon ECS automatically provisions, configures and operates most optimal EC2 instances within your AWS account using AWS-controlled access. You can also specify desired instance types in Managed Instances Capacity Provider configuration, including GPU-accelerated, network-optimized, and burstable performance, to run your workloads on the instance families you prefer. To get started with ECS Managed Instances, use the AWS Console, Amazon ECS MCP Server, or your favorite infrastructure-as-code tooling to enable it in a new or existing Amazon ECS cluster. You will be charged for the management of compute provisioned, in addition to your regular Amazon EC2 costs. To learn more about ECS Managed Instances, visit the https://aws.eu/ecs/managed-instances/, https://docs.aws.eu/AmazonECS/latest/developerguide/ManagedInstances.html, and https://aws.amazon.com/blogs/aws/announcing-amazon-ecs-managed-instances-for-containerized-applications.

Amazon ECS Managed Instances now available in AWS European Sovereign Cloud

Amazon Elastic Container Service (Amazon ECS) Managed Instances is now available in the AWS European Sovereign Cloud. ECS Managed Instances is a fully managed compute option designed to eliminate infras...

#AWS #AmazonEcs

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

1 month ago

Amazon ECS Managed Instances now available in AWS European Sovereign Cloud Amazon Elastic Container Service (Amazon ECS) Managed Instances is now available in the AWS European Sovereign Cloud. ECS Managed Instances is a fully managed compute option designed to eliminate infrastructure management overhead while giving you access to the full capabilities of Amazon EC2. By offloading infrastructure operations to AWS, you get the application performance you want and the simplicity you need while reducing your total cost of ownership. Managed Instances dynamically scales EC2 instances to match your workload requirements and continuously optimizes task placement to reduce infrastructure costs. It also enhances your security posture through regular security patching initiated every 14 days. You can simply define your task requirements such as the number of vCPUs, memory size, and CPU architecture, and Amazon ECS automatically provisions, configures and operates most optimal EC2 instances within your AWS account using AWS-controlled access. You can also specify desired instance types in Managed Instances Capacity Provider configuration, including GPU-accelerated, network-optimized, and burstable performance, to run your workloads on the instance families you prefer. To get started with ECS Managed Instances, use the AWS Console, Amazon ECS MCP Server, or your favorite infrastructure-as-code tooling to enable it in a new or existing Amazon ECS cluster. You will be charged for the management of compute provisioned, in addition to your regular Amazon EC2 costs. To learn more about ECS Managed Instances, visit the feature page, documentation, and AWS News launch blog.

🆕 Amazon ECS Managed Instances now available in AWS European Sovereign Cloud for simplified, cost-effective container management with automatic scaling, security updates, and customizable instance types.

#AWS #AmazonEcs

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

1 month ago

Amazon ECS adds Network Load Balancer support for Linear and Canary deployments https://aws.amazon.com/ecs/ (Amazon ECS) announces native support for linear and canary deployment strategies for ECS services using Network Load Balancers (NLB). Now, applications that commonly use NLB, such as those requiring TCP/UDP-based connections, low latency, long-lived connections, or static IP addresses, can take advantage of managed, incremental traffic shifting natively from ECS when rolling out updates. With this launch, ECS customers using NLB can shift traffic in a controlled manner during deployments, such as moving traffic in increments or starting with a small percentage to validate changes before completing a rollout. These deployment strategies provide additional confidence during updates by allowing teams to observe application behavior at each traffic-shift step, and integrate with Amazon CloudWatch alarms to automatically stop or roll back deployments if issues are detected. This is especially valuable for workloads running behind an NLB, such as online gaming backends, financial transaction systems, and real-time messaging services. To get started, select your NLB target groups, listener, and preferred deployment strategy in the ECS service configuration using the AWS Management Console, AWS CLI, or Infrastructure-as-Code tools. This can be enabled for both new and existing ECS services in all AWS commercial and AWS GovCloud (US) https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/. For more information, see the documentation for https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-linear.html and https://docs.aws.amazon.com/AmazonECS/latest/developerguide/canary-deployment.html.

Amazon ECS adds Network Load Balancer support for Linear and Canary deployments

https://aws.amazon.com/ecs/ (Amazon ECS) announces native support for linear and canary deployment strategies for ECS services using Network Load Balancers (NLB). Now, ap...

#AWS #AmazonEcs #AwsFargate #AwsGovcloudUs

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

2 months ago

Amazon ECS now publishes container health status as a CloudWatch metric https://aws.amazon.com/ecs/ (Amazon ECS) now publishes container health status as a new metric in CloudWatch Container Insights with enhanced observability. Customers can now track the operational health of their containers through a dedicated CloudWatch metric and create alarms to respond proactively to unhealthy containers. When customers configure a container health check in the container definition of an ECS task definition, Container Insights now publishes the UnHealthyContainerHealthStatus metric in the ECS/ContainerInsights namespace. The metric reports 0 for HEALTHY and 1 for UNHEALTHY. Container health state information is also available in embedded metric format (EMF) logs, providing additional context while health checks are being evaluated during the UNKNOWN state. The metric is available across cluster, service, task, and container-level dimensions, enabling customers to monitor health at their preferred level of granularity. Customers can create CloudWatch alarms on the metric to receive notifications when containers become unhealthy, allowing teams to take immediate action and maintain application reliability. To get started, enable Container Insights with enhanced observability on your ECS cluster and configure a container health check in your task definition to start collecting the metric in CloudWatch. Container health metric is available in all AWS Regions where Amazon ECS Container Insights is supported. For more information, see the https://docs.aws.amazon.com/AmazonECS/latest/developerguide/healthcheck.html and the https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-enhanced-observability-metrics-ECS.html.

Amazon ECS now publishes container health status as a CloudWatch metric

https://aws.amazon.com/ecs/ (Amazon ECS) now publishes container health status as a new metric in CloudWatch Container Insights with enhanced observability. Cus...

#AWS #AwsGovcloudUs #AmazonCloudwatch #AmazonEcs #AwsFargate

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

2 months ago

Amazon ECS now publishes container health status as a CloudWatch metric Amazon Elastic Container Service (Amazon ECS) now publishes container health status as a new metric in CloudWatch Container Insights with enhanced observability. Customers can now track the operational health of their containers through a dedicated CloudWatch metric and create alarms to respond proactively to unhealthy containers. When customers configure a container health check in the container definition of an ECS task definition, Container Insights now publishes the UnHealthyContainerHealthStatus metric in the ECS/ContainerInsights namespace. The metric reports 0 for HEALTHY and 1 for UNHEALTHY. Container health state information is also available in embedded metric format (EMF) logs, providing additional context while health checks are being evaluated during the UNKNOWN state. The metric is available across cluster, service, task, and container-level dimensions, enabling customers to monitor health at their preferred level of granularity. Customers can create CloudWatch alarms on the metric to receive notifications when containers become unhealthy, allowing teams to take immediate action and maintain application reliability. To get started, enable Container Insights with enhanced observability on your ECS cluster and configure a container health check in your task definition to start collecting the metric in CloudWatch. Container health metric is available in all AWS Regions where Amazon ECS Container Insights is supported. For more information, see the Amazon ECS container health checks documentation and the CloudWatch Container Insights documentation.

🆕 Amazon ECS now offers container health metrics in CloudWatch for better observability, triggering alarms for unhealthy containers. Set up health checks in task definitions to start collecting metrics. Available in all ECS Container In…

#AWS #AwsGovcloudUs #AmazonCloudwatch #AmazonEcs #AwsFargate

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

2 months ago

Amazon ECS Service Connect enhances observability with Envoy access logs in AWS GovCloud (US) Regions https://aws.amazon.com/ecs/ (Amazon ECS) Service Connect now supports Envoy access logs, providing deeper observability into request-level traffic patterns and service interactions. This new capability captures detailed per-request telemetry for end-to-end tracing, debugging, and compliance monitoring. Amazon ECS Service Connect makes it simple to build secure, resilient service-to-service communication across clusters, VPCs, and AWS accounts. It integrates service discovery and service mesh capabilities by automatically injecting AWS-managed Envoy proxies as sidecars that handle traffic routing, load balancing, and inter-service connectivity. Envoy Access logs capture detailed traffic metadata enabling request-level visibility into service communication patterns. This enables you to perform network diagnostics, troubleshoot issues efficiently, and maintain audit trails for compliance requirements. You can now configure access logs within ECS Service Connect by updating the ServiceConnectConfiguration to enable access logging. Query strings are redacted by default to protect sensitive data. Envoy access logs will output to the standard output (STDOUT) stream alongside application logs and flow through the existing ECS log pipeline without requiring additional infrastructure. This configuration supports all existing application protocols (HTTP, HTTP2, GRPC and TCP). 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, visit the https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect-envoy-access-logs.html.

Amazon ECS Service Connect enhances observability with Envoy access logs in AWS GovCloud (US) Regions

https://aws.amazon.com/ecs/ (Amazon ECS) Service Connect now supports Envoy access logs, providing deeper observability into request-level traffic patterns and ...

#AWS #AmazonEcs #AwsGovcloudUs

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

2 months ago

Amazon ECS now supports tmpfs mounts on AWS Fargate and ECS Managed Instances https://aws.amazon.com/ecs/ (Amazon ECS) now supports tmpfs mounts for Linux tasks running on AWS Fargate and Amazon ECS Managed Instances, extending beyond the EC2 launch type. With tmpfs, you can now create memory‑backed file systems for your containerized workloads without writing this data to task storage. tmpfs mounts provide a temporary file system that is backed by memory and exposed inside the container at a path you choose. This is ideal for performance‑sensitive workloads that need fast access to scratch files, caches, or temporary working sets, and for security‑sensitive data such as short‑lived secrets or credentials, because the data does not persist after the task stops. tmpfs also lets you keep the container root file system read‑only using the readonlyRootFilesystem setting while still allowing applications to write to specific in‑memory directories. To get started, update your task definition so that the container definitions include a linuxParameters block with one or more tmpfs entries. For each tmpfs mount, specify the containerPath, size, and optional mountOptions. You can register or update task definitions using the Amazon ECS console, AWS CLI, AWS CloudFormation, or AWS CDK. This feature is available in all AWS Regions where Amazon ECS, AWS Fargate, and Amazon ECS Managed Instances are supported. To learn more, see the LinuxParameters and Tmpfs sections in the https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_Tmpfs.html and the https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html.

Amazon ECS now supports tmpfs mounts on AWS Fargate and ECS Managed Instances

https://aws.amazon.com/ecs/ (Amazon ECS) now supports tmpfs mounts for Linux tasks running on AWS Fargate and Amazon ECS Managed Instances, extending beyond the EC2 launch type. With t...

#AWS #AmazonEcs #AwsGovcloudUs

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

2 months ago

Amazon ECS now supports tmpfs mounts on AWS Fargate and ECS Managed Instances Amazon Elastic Container Service (Amazon ECS) now supports tmpfs mounts for Linux tasks running on AWS Fargate and Amazon ECS Managed Instances, extending beyond the EC2 launch type. With tmpfs, you can now create memory‑backed file systems for your containerized workloads without writing this data to task storage. tmpfs mounts provide a temporary file system that is backed by memory and exposed inside the container at a path you choose. This is ideal for performance‑sensitive workloads that need fast access to scratch files, caches, or temporary working sets, and for security‑sensitive data such as short‑lived secrets or credentials, because the data does not persist after the task stops. tmpfs also lets you keep the container root file system read‑only using the readonlyRootFilesystem setting while still allowing applications to write to specific in‑memory directories. To get started, update your task definition so that the container definitions include a linuxParameters block with one or more tmpfs entries. For each tmpfs mount, specify the containerPath, size, and optional mountOptions. You can register or update task definitions using the Amazon ECS console, AWS CLI, AWS CloudFormation, or AWS CDK. This feature is available in all AWS Regions where Amazon ECS, AWS Fargate, and Amazon ECS Managed Instances are supported. To learn more, see the LinuxParameters and Tmpfs sections in the Amazon ECS API Reference and the Amazon ECS Developer Guide.

🆕 Amazon ECS now supports tmpfs mounts on Fargate and ECS Managed Instances for faster scratch files and temp data, keeping container root read-only. Update task defs with linuxParameters for tmpfs. Available globally.

#AWS #AmazonEcs #AwsGovcloudUs

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

Amazon ECS Service Connect enhances observability with Envoy Access Logs https://aws.amazon.com/ecs/ (Amazon ECS) Service Connect now supports Envoy access logs, providing deeper observability into request-level traffic patterns and service interactions. This new capability captures detailed per-request telemetry for end-to-end tracing, debugging, and compliance monitoring. Amazon ECS Service Connect makes it simple to build secure, resilient service-to-service communication across clusters, VPCs, and AWS accounts. It integrates service discovery and service mesh capabilities by automatically injecting AWS-managed Envoy proxies as sidecars that handle traffic routing, load balancing, and inter-service connectivity. Envoy Access logs capture detailed traffic metadata enabling request-level visibility into service communication patterns. This enables you to perform network diagnostics, troubleshoot issues efficiently, and maintain audit trails for compliance requirements. You can now configure access logs within ECS Service Connect by updating the ServiceConnectConfiguration to enable access logging. Query strings are redacted by default to protect sensitive data. Envoy access logs will output to the standard output (STDOUT) stream alongside application logs and flow through the existing ECS log pipeline without requiring additional infrastructure. This configuration supports all existing application protocols (HTTP, HTTP2, GRPC and TCP). This feature is available in AWS GovCloud (US-West) and AWS GovCloud (US-East) regions where Amazon ECS Service Connect is supported. To learn more, visit the https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect-envoy-access-logs.html.

Amazon ECS Service Connect enhances observability with Envoy Access Logs

https://aws.amazon.com/ecs/ (Amazon ECS) Service Connect now supports Envoy access logs, providing deeper observability into request-level traffic patterns and service interactions. This ne...

#AWS #AwsGovcloudUs #AmazonEcs

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

3 months ago

Amazon ECS Service Connect enhances observability with Envoy Access Logs Amazon Elastic Container Service (Amazon ECS) Service Connect now supports Envoy access logs, providing deeper observability into request-level traffic patterns and service interactions. This new capability captures detailed per-request telemetry for end-to-end tracing, debugging, and compliance monitoring. Amazon ECS Service Connect makes it simple to build secure, resilient service-to-service communication across clusters, VPCs, and AWS accounts. It integrates service discovery and service mesh capabilities by automatically injecting AWS-managed Envoy proxies as sidecars that handle traffic routing, load balancing, and inter-service connectivity. Envoy Access logs capture detailed traffic metadata enabling request-level visibility into service communication patterns. This enables you to perform network diagnostics, troubleshoot issues efficiently, and maintain audit trails for compliance requirements. You can now configure access logs within ECS Service Connect by updating the ServiceConnectConfiguration to enable access logging. Query strings are redacted by default to protect sensitive data. Envoy access logs will output to the standard output (STDOUT) stream alongside application logs and flow through the existing ECS log pipeline without requiring additional infrastructure. This configuration supports all existing application protocols (HTTP, HTTP2, GRPC and TCP). This feature is available in AWS GovCloud (US-West) and AWS GovCloud (US-East) regions where Amazon ECS Service Connect is supported. To learn more, visit the Amazon ECS Developer Guide.

🆕 Amazon ECS Service Connect now supports Envoy access logs for enhanced observability, capturing detailed request-level traffic and service interactions for end-to-end tracing and compliance, outputting to STDOUT without extra infrastructure. Available in AWS GovCl…

#AWS #AwsGovcloudUs #AmazonEcs

0 0 0 0

Robert Mooney

@vermelho18.bsky.social

3 months ago

#AmazonEcs #AwsFargate

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

Amazon ECS now enables you to define weekly event windows for scheduling task retirements on AWS Fargate Amazon ECS now enables you to define weekly event windows for scheduling task retirements on AWS Fargate. This capability provides precise control over when infrastructure updates and task replacements occur, helping prevent disruption to mission-critical workloads during peak business hours. AWS Fargate is a serverless, pay-as-you-go compute engine that lets you focus on building applications without managing servers. As part of the AWS shared responsibility model, Fargate maintains the underlying infrastructure with periodic platform updates. Fargate automatically retires your tasks for these updates and notifies you about upcoming task retirements via email and the AWS Health Dashboard. By default, tasks are retired 7 days after notification, but you can configure the fargateTaskRetirementWaitPeriod account setting to extend the retirement period to 14 days or initiate immediate retirement (0 days). Previously, you could build automation using the task retirement notification and wait period to perform service updates or task replacements on your own cadence. With today's launch, you can now use the Amazon EC2 event windows interface to define weekly event windows for precise control over the timing of Fargate task retirements. For example, you can schedule task retirements for a mission-critical service that requires high uptime during weekdays by configuring retirements to occur only on weekends. To get started, configure the AWS account setting fargateEventWindows to enabled as a one-time set up. Once enabled, configure Amazon EC2 event window(s) by specifying time ranges, and associate the event window(s) with your ECS tasks by selecting Amazon ECS-managed tags as the association target. Use the aws:ecs:clusterArn tag for targeting your tasks in an ECS cluster, aws:ecs:serviceArn tag for ECS services, or aws:ecs:fargateTask with a value of true to apply the window to all Fargate tasks. This feature is now available in all commercial AWS Regions. To learn more, visit our https://docs.aws.amazon.com/AmazonECS/latest/developerguide/prepare-task-retirement.html.

Amazon ECS now enables you to define weekly event windows for scheduling task retirements on AWS Fargate

Amazon ECS now enables you to define weekly event windows for scheduling task retirements on AWS Fargate. This capability provides precise control over when inf...

#AWS #AmazonEcs #AwsFargate

2 1 1 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

Amazon ECS Managed Instances now supports Amazon EC2 Spot Instances https://aws.amazon.com/ecs/managed-instances/ now supports https://aws.amazon.com/ec2/spot/ extending the range of capabilities available with AWS-managed infrastructure. With this launch, you can leverage spare EC2 capacity at up to 90% discount compared to On-Demand prices for fault-tolerant workloads, while AWS handles infrastructure management. ECS Managed Instances is a fully managed compute option designed to eliminate infrastructure management overhead, dynamically scale EC2 instances to match your workload requirements and continuously optimize task placement to reduce infrastructure costs. You can simply define your task requirements such as the number of vCPUs, memory size, and CPU architecture, and Amazon ECS automatically provisions, configures and operates most optimal EC2 instances within your AWS account using AWS-controlled access. You can also specify desired instance types in Managed Instances capacity provider configuration, including GPU-accelerated, network-optimized, and burstable performance, to run your workloads on the instance families you prefer. With today's launch, you can additionally configure a new parameter, capacityOptionType, as spot or on-demand in your capacity provider configuration. Support for EC2 Spot Instances is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ that Amazon ECS Managed Instances is available. You will be charged for the management of compute provisioned, in addition to your spot Amazon EC2 costs. To learn more about ECS Managed Instances, visit the https://aws.amazon.com/ecs/managed-instances/, https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ManagedInstances.html, and https://aws.amazon.com/blogs/aws/announcing-amazon-ecs-managed-instances-for-containerized-applications.

Amazon ECS Managed Instances now supports Amazon EC2 Spot Instances

https://aws.amazon.com/ecs/managed-instances/ now supports https://aws.amazon.com/ec2/spot/ extending the range of capabilities available with AWS-managed infrastructure. With this la...

#AWS #AmazonEc2 #AwsGovcloudUs #AmazonEcs

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

3 months ago

Amazon ECS now enables you to define weekly event windows for scheduling task retirements on AWS Fargate Amazon ECS now enables you to define weekly event windows for scheduling task retirements on AWS Fargate. This capability provides precise control over when infrastructure updates and task replacements occur, helping prevent disruption to mission-critical workloads during peak business hours. AWS Fargate is a serverless, pay-as-you-go compute engine that lets you focus on building applications without managing servers. As part of the AWS shared responsibility model, Fargate maintains the underlying infrastructure with periodic platform updates. Fargate automatically retires your tasks for these updates and notifies you about upcoming task retirements via email and the AWS Health Dashboard. By default, tasks are retired 7 days after notification, but you can configure the fargateTaskRetirementWaitPeriod account setting to extend the retirement period to 14 days or initiate immediate retirement (0 days). Previously, you could build automation using the task retirement notification and wait period to perform service updates or task replacements on your own cadence. With today's launch, you can now use the Amazon EC2 event windows interface to define weekly event windows for precise control over the timing of Fargate task retirements. For example, you can schedule task retirements for a mission-critical service that requires high uptime during weekdays by configuring retirements to occur only on weekends. To get started, configure the AWS account setting fargateEventWindows to enabled as a one-time set up. Once enabled, configure Amazon EC2 event window(s) by specifying time ranges, and associate the event window(s) with your ECS tasks by selecting Amazon ECS-managed tags as the association target. Use the aws:ecs:clusterArn tag for targeting your tasks in an ECS cluster, aws:ecs:serviceArn tag for ECS services, or aws:ecs:fargateTask with a value of true to apply the window to all Fargate tasks. This feature is now available in all commercial AWS Regions. To learn more, visit our documentation.

🆕 Amazon ECS now schedules Fargate task retirements within weekly event windows for precise control, minimizing disruptions during peak hours. Set these windows via the Amazon EC2 interface to align with your operational needs.

#AWS #AmazonEcs #AwsFargate

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

3 months ago

Amazon ECS Managed Instances now supports Amazon EC2 Spot Instances Amazon ECS Managed Instances now supports Amazon EC2 Spot Instances, extending the range of capabilities available with AWS-managed infrastructure. With this launch, you can leverage spare EC2 capacity at up to 90% discount compared to On-Demand prices for fault-tolerant workloads, while AWS handles infrastructure management. ECS Managed Instances is a fully managed compute option designed to eliminate infrastructure management overhead, dynamically scale EC2 instances to match your workload requirements and continuously optimize task placement to reduce infrastructure costs. You can simply define your task requirements such as the number of vCPUs, memory size, and CPU architecture, and Amazon ECS automatically provisions, configures and operates most optimal EC2 instances within your AWS account using AWS-controlled access. You can also specify desired instance types in Managed Instances capacity provider configuration, including GPU-accelerated, network-optimized, and burstable performance, to run your workloads on the instance families you prefer. With today's launch, you can additionally configure a new parameter, capacityOptionType, as spot or on-demand in your capacity provider configuration. Support for EC2 Spot Instances is available in all AWS Regions that Amazon ECS Managed Instances is available. You will be charged for the management of compute provisioned, in addition to your spot Amazon EC2 costs. To learn more about ECS Managed Instances, visit the feature page, documentation, and AWS News launch blog.

🆕 Amazon ECS Managed Instances now supports EC2 Spot Instances, saving up to 90% for fault-tolerant workloads. AWS manages infrastructure and scaling, letting you choose instance types and set capacity options as spot or on-demand. Available in all ECS re…

#AWS #AmazonEc2 #AwsGovcloudUs #AmazonEcs

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

3 months ago

Amazon ECS now supports custom container stop signals on AWS Fargate https://aws.amazon.com/ecs/ (Amazon ECS) now supports custom container stop signals for Linux tasks running on AWS Fargate, honoring the stop signal configured in Open Container Initiative (OCI) images when tasks are stopped. The enhancement improves graceful shutdown behavior by aligning Fargate task termination with each container’s preferred termination signal. Previously, when an Amazon ECS task running on AWS Fargate was stopped, each Linux container always received SIGTERM followed by SIGKILL after the configured timeout. With the new behavior, the Amazon ECS container agent reads the stop signal from the container image configuration and sends that signal when stopping the task. Containers that rely on signals such as SIGQUIT or SIGINT for graceful shutdown can now run on Fargate with their intended termination semantics. If no STOPSIGNAL is configured, Amazon ECS continues to send SIGTERM by default. Customers can use custom stop signals on Amazon ECS with AWS Fargate by adding a STOPSIGNAL instruction (for example, STOPSIGNAL SIGQUIT) to their OCI‑compliant container images. Support for container‑defined stop signals is available in all AWS Regions. To learn more, refer to the https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-lifecycle-explanation.html.

Amazon ECS now supports custom container stop signals on AWS Fargate

https://aws.amazon.com/ecs/ (Amazon ECS) now supports custom container stop signals for Linux tasks running on AWS Fargate, honoring the stop signal configured in Open Container Initiative (OCI...

#AWS #AwsGovcloudUs #AmazonEcs

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

3 months ago

Amazon ECS now supports custom container stop signals on AWS Fargate Amazon Elastic Container Service (Amazon ECS) now supports custom container stop signals for Linux tasks running on AWS Fargate, honoring the stop signal configured in Open Container Initiative (OCI) images when tasks are stopped. The enhancement improves graceful shutdown behavior by aligning Fargate task termination with each container’s preferred termination signal. Previously, when an Amazon ECS task running on AWS Fargate was stopped, each Linux container always received SIGTERM followed by SIGKILL after the configured timeout. With the new behavior, the Amazon ECS container agent reads the stop signal from the container image configuration and sends that signal when stopping the task. Containers that rely on signals such as SIGQUIT or SIGINT for graceful shutdown can now run on Fargate with their intended termination semantics. If no STOPSIGNAL is configured, Amazon ECS continues to send SIGTERM by default. Customers can use custom stop signals on Amazon ECS with AWS Fargate by adding a STOPSIGNAL instruction (for example, STOPSIGNAL SIGQUIT) to their OCI‑compliant container images. Support for container‑defined stop signals is available in all AWS Regions. To learn more, refer to the ECS Developer Guide.

🆕 Amazon ECS now supports custom container stop signals on AWS Fargate, improving graceful shutdown by aligning Fargate task termination with each container’s preferred termination signal, enhancing shutdown behavior.

#AWS #AwsGovcloudUs #AmazonEcs

0 0 0 0

Elizabeth Fuentes L

@elizabethfue12.bsky.social

4 months ago

Build production-ready applications without infrastructure complexity using Amazon ECS Express Mode | Amazon Web Services Amazon ECS Express Mode simplifies containerized application deployment by automating infrastructure setup through a single command, allowing developers to focus on building applications while following...

📰🚨 Build production-ready applications without infrastructure complexity using Amazon ECS Express Mode

#AmazonECS #Containerization #CloudComputing #DevOps #AWSInnovation

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

Amazon EKS and Amazon ECS announce fully managed MCP servers in preview Today, https://aws.amazon.com/eks/ (EKS) and https://aws.amazon.com/ecs/https://aws.amazon.com/ecs/ (ECS) announced fully managed MCP servers enabling AI powered experiences for development and operations in preview. MCP (Model Context Protocol) provides a standardized interface that enriches AI applications with real-time, contextual knowledge of EKS and ECS clusters, enabling more accurate and tailored guidance throughout the application lifecycle, from development through operations. With this launch, EKS and ECS now offer fully managed MCP servers hosted in the AWS cloud, eliminating the need for local installation and maintenance. The fully managed MCP servers provide enterprise-grade capabilities like automatic updates and patching, centralized security through AWS IAM integration, comprehensive audit logging via AWS CloudTrail, and the proven scalability, reliability, and support of AWS. The fully managed Amazon EKS and ECS MCP servers enable developers to easily configure AI coding assistants like Kiro CLI, Cursor, or Cline for guided development workflows, optimized code generation, and context-aware debugging. Operators gain access to a knowledge base of best practices and troubleshooting guidance derived from extensive operational experience managing clusters at scale. To learn more about the Amazon EKS MCP server preview, visit EKS MCP server https://docs.aws.amazon.com/eks/latest/userguide/eks-mcp-introduction.html and launch https://aws.amazon.com/blogs/containers/introducing-the-fully-managed-amazon-eks-mcp-server-preview/. To learn more about the Amazon ECS MCP server preview, visit ECS MCP server https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-mcp-introduction.html and launch https://aws.amazon.com/blogs/containers/accelerate-container-troubleshooting-with-the-fully-managed-amazon-ecs-mcp-server-preview/.

Amazon EKS and Amazon ECS announce fully managed MCP servers in preview

Today, https://aws.amazon.com/eks/ (EKS) and https://aws.amazon.com/ecs/https://aws.amazon.com/ecs/ (ECS) announced fully managed MCP servers enabling AI powered experiences for development and ...

#AWS #AmazonEcs #AmazonEks

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

4 months ago

Amazon EKS and Amazon ECS announce fully managed MCP servers in preview Today, Amazon Elastic Kubernetes Service (EKS) and Amazon Elastic Container Service (ECS) announced fully managed MCP servers enabling AI powered experiences for development and operations in preview. MCP (Model Context Protocol) provides a standardized interface that enriches AI applications with real-time, contextual knowledge of EKS and ECS clusters, enabling more accurate and tailored guidance throughout the application lifecycle, from development through operations. With this launch, EKS and ECS now offer fully managed MCP servers hosted in the AWS cloud, eliminating the need for local installation and maintenance. The fully managed MCP servers provide enterprise-grade capabilities like automatic updates and patching, centralized security through AWS IAM integration, comprehensive audit logging via AWS CloudTrail, and the proven scalability, reliability, and support of AWS. The fully managed Amazon EKS and ECS MCP servers enable developers to easily configure AI coding assistants like Kiro CLI, Cursor, or Cline for guided development workflows, optimized code generation, and context-aware debugging. Operators gain access to a knowledge base of best practices and troubleshooting guidance derived from extensive operational experience managing clusters at scale. To learn more about the Amazon EKS MCP server preview, visit EKS MCP server documentation and launch blog post. To learn more about the Amazon ECS MCP server preview, visit ECS MCP server documentation and launch blog post.

🆕 Amazon EKS and ECS now offer fully managed MCP servers in preview, enabling AI-powered development and operations with real-time cluster insights, automatic updates, and AWS IAM integration, eliminating local installation and maintenance.

#AWS #AmazonEcs #AmazonEks

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

Amazon ECS Managed Instances now available in AWS GovCloud (US) Regions Amazon Elastic Container Service (Amazon ECS) Managed Instances is now available in the AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. ECS Managed Instances is a fully managed compute option designed to eliminate infrastructure management overhead while giving you access to the full capabilities of Amazon EC2. By offloading infrastructure operations to AWS, you get the application performance you want and the simplicity you need while reducing your total cost of ownership. Managed Instances dynamically scales EC2 instances to match your workload requirements and continuously optimizes task placement to reduce infrastructure costs. It also enhances your security posture through regular security patching initiated every 14 days. You can simply define your task requirements such as the number of vCPUs, memory size, and CPU architecture, and Amazon ECS automatically provisions, configures and operates most optimal EC2 instances within your AWS account using AWS-controlled access. You can also specify desired instance types in Managed Instances Capacity Provider configuration, including GPU-accelerated, network-optimized, and burstable performance, to run your workloads on the instance families you prefer. To get started with ECS Managed Instances, use the AWS Console, Amazon ECS MCP Server, or your favorite infrastructure-as-code tooling to enable it in a new or existing Amazon ECS cluster. You will be charged for the management of compute provisioned, in addition to your regular Amazon EC2 costs. To learn more about ECS Managed Instances, visit the https://aws.amazon.com/ecs/managed-instances/, https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ManagedInstances.html, and https://aws.amazon.com/blogs/aws/announcing-amazon-ecs-managed-instances-for-containerized-applications.

Amazon ECS Managed Instances now available in AWS GovCloud (US) Regions

Amazon Elastic Container Service (Amazon ECS) Managed Instances is now available in the AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. ECS Managed Instances is a fully managed co...

#AWS #AmazonEcs #AwsGovcloudUs

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

Announcing Amazon ECS Express Mode Today, AWS announces Amazon Elastic Container Service (Amazon ECS) Express Mode, a new feature that empowers developers to rapidly launch containerized applications, including web applications and APIs. ECS Express Mode makes it easy to orchestrate and manage the cloud architecture for your application, while maintaining full control over your infrastructure resources. Amazon ECS Express Mode streamlines the deployment and management of containerized applications on AWS, allowing developers to focus on delivering business value through their containerized applications. Every Express Mode service automatically receives an AWS-provided domain name, making your application immediately accessible without additional configuration. Applications using ECS Express Mode incorporate AWS operational best practices, serve either public or private HTTPS requests, and scale in response to traffic patterns. Traffic is distributed through Application Load Balancer (ALB)s, and automatically consolidates up to 25 Express Mode services behind a single ALB when appropriate. ECS Express uses intelligent rule-based routing to maintain isolation between services while efficiently utilizing the ALB resource. All resources provisioned by ECS Express Mode remain fully accessible in your account, ensuring you never sacrifice control or flexibility. As your application requirements evolve, you can directly access and modify any infrastructure resource, leveraging the complete feature set of Amazon ECS and related services without disruption to your running applications. To get started just provide your container image, and ECS Express Mode handles the rest by deploying your application in Amazon ECS and auto-generating a URL. Amazon ECS Express Mode is available now in all AWS Regions at no additional charge. You pay only for the AWS resources created to run your application. To deploy a new ECS Express Mode service, use the Amazon ECS Console, SDK, CLI, CloudFormation, CDK and Terraform. For more information, see the https://aws.amazon.com/blogs/aws/build-production-ready-applications-without-infrastructure-complexity-using-amazon-ecs-express-mode, or the https://docs.aws.amazon.com/AmazonECS/latest/developerguide/express-service-overview.html.

Announcing Amazon ECS Express Mode

Today, AWS announces Amazon Elastic Container Service (Amazon ECS) Express Mode, a new feature that empowers developers to rapidly launch containerized applications, including web applications and APIs. ECS Express Mode makes it easy to orche...

#AWS #AmazonEcs

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

4 months ago

Amazon ECS Managed Instances now available in AWS GovCloud (US) Regions Amazon Elastic Container Service (Amazon ECS) Managed Instances is now available in the AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. ECS Managed Instances is a fully managed compute option designed to eliminate infrastructure management overhead while giving you access to the full capabilities of Amazon EC2. By offloading infrastructure operations to AWS, you get the application performance you want and the simplicity you need while reducing your total cost of ownership. Managed Instances dynamically scales EC2 instances to match your workload requirements and continuously optimizes task placement to reduce infrastructure costs. It also enhances your security posture through regular security patching initiated every 14 days. You can simply define your task requirements such as the number of vCPUs, memory size, and CPU architecture, and Amazon ECS automatically provisions, configures and operates most optimal EC2 instances within your AWS account using AWS-controlled access. You can also specify desired instance types in Managed Instances Capacity Provider configuration, including GPU-accelerated, network-optimized, and burstable performance, to run your workloads on the instance families you prefer. To get started with ECS Managed Instances, use the AWS Console, Amazon ECS MCP Server, or your favorite infrastructure-as-code tooling to enable it in a new or existing Amazon ECS cluster. You will be charged for the management of compute provisioned, in addition to your regular Amazon EC2 costs. To learn more about ECS Managed Instances, visit the feature page, documentation, and AWS News launch blog.

🆕 Amazon ECS Managed Instances now available in AWS GovCloud (US) Regions. Fully managed compute option for EC2, scaling and optimizing tasks, reducing costs, and enhancing security with regular patches. Use AWS Console or infrastructure-as-code tools to enable.

#AWS #AmazonEcs #AwsGovcloudUs

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

4 months ago

Announcing Amazon ECS Express Mode Today, AWS announces Amazon Elastic Container Service (Amazon ECS) Express Mode, a new feature that empowers developers to rapidly launch containerized applications, including web applications and APIs. ECS Express Mode makes it easy to orchestrate and manage the cloud architecture for your application, while maintaining full control over your infrastructure resources. Amazon ECS Express Mode streamlines the deployment and management of containerized applications on AWS, allowing developers to focus on delivering business value through their containerized applications. Every Express Mode service automatically receives an AWS-provided domain name, making your application immediately accessible without additional configuration. Applications using ECS Express Mode incorporate AWS operational best practices, serve either public or private HTTPS requests, and scale in response to traffic patterns. Traffic is distributed through Application Load Balancer (ALB)s, and automatically consolidates up to 25 Express Mode services behind a single ALB when appropriate. ECS Express uses intelligent rule-based routing to maintain isolation between services while efficiently utilizing the ALB resource. All resources provisioned by ECS Express Mode remain fully accessible in your account, ensuring you never sacrifice control or flexibility. As your application requirements evolve, you can directly access and modify any infrastructure resource, leveraging the complete feature set of Amazon ECS and related services without disruption to your running applications. To get started just provide your container image, and ECS Express Mode handles the rest by deploying your application in Amazon ECS and auto-generating a URL. Amazon ECS Express Mode is available now in all AWS Regions at no additional charge. You pay only for the AWS resources created to run your application. To deploy a new ECS Express Mode service, use the Amazon ECS Console, SDK, CLI, CloudFormation, CDK and Terraform. For more information, see the AWS News blog, or the documentation.

🆕 AWS announces Amazon ECS Express Mode, simplifying containerized app deployment with automatic domain, traffic scaling, and resource management, all at no extra charge, available in all regions.

#AWS #AmazonEcs

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

Amazon ECS and Amazon EKS now offer enhanced AI-powered troubleshooting in the Console https://aws.amazon.com/ecs/ (ECS) and https://aws.amazon.com/eks/ (EKS) now offer enhanced AI-powered troubleshooting experiences in the AWS Management Console through Amazon Q Developer. The new AI-powered experiences appear contextually alongside error or status messages in the console, helping customers root cause issues and view mitigation suggestions with a single click. In the ECS Console, customers can use the new “Inspect with Amazon Q” button to troubleshoot issues such as failed tasks, container health check failures, or deployment rollbacks. Simply click the status reason on task details, task definition details, or deployment details page, and click “Inspect with Amazon Q” from the popover to start troubleshooting with context from the issue provided to the agent for you. Once clicked, Amazon Q automatically uses appropriate AI tools to analyze the issue, gather the relevant logs and metrics, help you understand the root cause, and recommend mitigation actions. The Amazon EKS console integrates Amazon Q throughout the observability dashboard, enabling you to inspect and troubleshoot cluster, control plane, and node health issues with contextual AI assistance. Simply click "Inspect with Amazon Q" directly from tables that outline issues, or click on an issue to view details and then select "Inspect with Amazon Q" to begin your investigation. The Q-powered experience provides deeper understanding of cluster-level insights, such as upgrade insights, helping you proactively identify and mitigate potential issues. Amazon Q also streamlines workload troubleshooting by helping you investigate Kubernetes events on pods that indicate issues, accelerating root cause identification and resolution. Amazon Q integration in the Amazon ECS and Amazon EKS consoles is now available in all AWS commercial regions. To learn more, visit the https://docs.aws.amazon.com/AmazonECS/latest/developerguide/troubleshooting-with-Q.html and https://docs.aws.amazon.com/eks/latest/userguide/amazon-q-integration.html.

Amazon ECS and Amazon EKS now offer enhanced AI-powered troubleshooting in the Console

https://aws.amazon.com/ecs/ (ECS) and https://aws.amazon.com/eks/ (EKS) now offer enhanced AI-powered troubleshooting experiences in the AWS Management Console through Amazon Q De...

#AWS #AmazonEks #AmazonEcs

1 0 0 0