{
  "generated_at": "2026-11-13T14:30:24.272Z",
  "site": {
    "name": "EOL Watch",
    "url": "https://eolwatch.dev"
  },
  "count": 536,
  "license": {
    "name": "Not decided yet",
    "url": null,
    "note": "The license for these exports has not been chosen yet, so no reuse terms are stated. Ask the site owner before you redistribute the data. Version dates taken from or cross-checked with endoflife.date remain subject to the license of that project."
  },
  "schema": {
    "slug": "Stable identifier of the item. Never changes once published.",
    "title": "Short headline of the lifecycle change.",
    "summary": "One or two plain sentences describing the change.",
    "cloud": "Cloud the item belongs to: azure, aws, gcp, oci or multi.",
    "service": "Display name of the affected service.",
    "service_slug": "URL-safe identifier of the service.",
    "category": "Kind of thing affected, for example service, runtime, kubernetes or database.",
    "type": "Kind of change: retirement, end_of_support or breaking_change.",
    "announced_date": "Date the vendor announced the change (YYYY-MM-DD), or null when not stated.",
    "effective_date": "Date the change takes effect (YYYY-MM-DD), or null when not announced. For month, quarter and year precision this is the first day of the period.",
    "effective_precision": "How exact effective_date is: day, month, quarter or year.",
    "impact": "What stops working and who is affected.",
    "migration_path": "Steps to take before the effective date. May contain Markdown.",
    "replacement": "Recommended replacement, or null when the vendor names none.",
    "affected_versions": "Versions affected. Array in JSON, joined with \"; \" in CSV.",
    "source_url": "Page the item was verified against: an official vendor page, or the endoflife.date page for the few products where it is the only source of the date.",
    "extra_source_urls": "Additional sources: official pages, or an endoflife.date page. Array in JSON, joined with \"; \" in CSV.",
    "vendor_ref": "Vendor reference for the announcement, or null.",
    "last_checked_at": "Timestamp (ISO 8601, UTC) of the last successful recheck against the source.",
    "created_at": "Timestamp (ISO 8601, UTC) when the item was first published here.",
    "updated_at": "Timestamp (ISO 8601, UTC) of the last change to the item.",
    "url": "Page for this item on the site."
  },
  "items": [
    {
      "slug": "azure-terraform-azapi-2-0-1-breaking-change",
      "title": "Terraform AzAPI provider 2.0.1: breaking changes",
      "summary": "Release date for Terraform AzAPI provider 2.0.1: 21 Oct 2024. Breaking changes listed in the release notes: 9.",
      "cloud": "azure",
      "service": "Terraform AzAPI provider",
      "service_slug": "terraform-azapi",
      "category": "iac_provider",
      "type": "breaking_change",
      "announced_date": "2024-10-21",
      "effective_date": "2024-10-21",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- azapi_resource, azapi_update_resource resources and data sources' output field defaults to the readonly fields when the response_export_values is not specified.\n- azapi_resource_list data source's output field defaults to the response when the response_export_values is not specified.\n- Provider field default_naming_prefix and default_naming_suffix are removed. Please specify the naming prefix and suffix in the resource's name field instead.\n- Provider field enable_hcl_output_for_data_source is removed. The output field in the data source is always in HCL format.\n- The azapi_resource's removing_special_chars field is removed. Please specify the name field and remove the special characters in the name field instead.\n- The ignore_body_changes field is removed. Please use the lifecyle.ignore_changes to ignore some properties when comparing the resource with its current state.\n- The body field now only accepts an HCL object. Please remove the jsonencode function when using the body field.\n- The output field now only exports an HCL object. Please remove the jsondecode function when using the output field.\n- The use_msi field now defaults to false, please set it to true explicitly if you want to authenticate using Managed Service Identity.",
      "migration_path": "1. Give the provider a version constraint in the `required_providers` block. HashiCorp recommends a version constraint for every provider a module depends on.\n2. In a root module, also specify the maximum provider version, to avoid accidental upgrades to incompatible new versions. The `~>` operator is a shorthand that allows the rightmost component of a version to increment. Do not use `~>` or other maximum-version constraints in modules you intend to reuse across many configurations. Specify a minimum version there and let the root module manage the maximum version.\n3. Commit the dependency lock file to version control with the configuration, so that Terraform always installs the same provider versions.\n4. To adopt 2.0.1, change the version in the `required_providers` block and re-run `terraform init`. HashiCorp states that this upgrades the provider version in the lock file. Without a change, Terraform re-selects the version recorded in the lock file, even if a newer version has become available. With the `-upgrade` option, `terraform init` disregards the recorded selection and selects the newest available version matching the version constraint. The [release notes](https://github.com/Azure/terraform-provider-azapi/releases/tag/v2.0.1) list each breaking change.\n5. Review the changes Terraform made to the lock file in version control. If they are changes you made intentionally, send them through the usual code review process.",
      "replacement": null,
      "affected_versions": [
        "2.0.1"
      ],
      "source_url": "https://github.com/Azure/terraform-provider-azapi/releases/tag/v2.0.1",
      "extra_source_urls": [],
      "vendor_ref": "v2.0.1",
      "last_checked_at": "2026-11-12T09:55:26.541Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-terraform-azapi-2-0-1-breaking-change"
    },
    {
      "slug": "aws-terraform-aws-6-0-0-breaking-change",
      "title": "Terraform AWS provider 6.0.0: breaking changes",
      "summary": "Release date for Terraform AWS provider 6.0.0: 18 Jun 2025. Breaking changes listed in the release notes: 92.",
      "cloud": "aws",
      "service": "Terraform AWS provider",
      "service_slug": "terraform-aws",
      "category": "iac_provider",
      "type": "breaking_change",
      "announced_date": "2025-06-18",
      "effective_date": "2025-06-18",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- `aws_ami`: The severity of the diagnostic returned when most_recent is true and owner and image ID filter criteria has been increased to an error. Existing configurations which were previously receiving a warning diagnostic will now fail to apply. To prevent this error, set the owner argument or include a filter block with an image-id or owner-id name/value pair. To continue using unsafe filter values with most_recent set to true, set the new allow_unsafe_filter argument to true. This is not recommended.\n- `aws_ecs_task_definition`: Remove inference_accelerator attribute. Amazon Elastic Inference reached end of life on April, 2024.\n- `aws_ecs_task_execution`: Remove inference_accelerator_overrides attribute. Amazon Elastic Inference reached end of life on April, 2024.\n- `aws_elbv2_listener_rule`: The action.authenticate_cognito, action.authenticate_oidc, action.fixed_response, action.forward, action.forward.stickiness, action.redirect, condition.host_header, condition.http_header, condition.http_request_method, condition.path_pattern, condition.query_string, and condition.source_ip attributes are now list nested blocks instead of single nested blocks\n- `aws_identitystore_user`: filter has been removed\n- `aws_launch_template`: Remove elastic_inference_accelerator attribute. Amazon Elastic Inference reached end of life on April, 2024.\n- `aws_launch_template`: elastic_gpu_specifications has been removed\n- `aws_opensearch_domain`: kibana_endpoint has been removed\n- `aws_opensearchserverless_security_config`: saml_options is now a list nested block instead of a single nested block\n- `aws_service_discovery_service`: Remove tags_all attribute\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_application resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_custom_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_ecs_cluster_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_ganglia_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_haproxy_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_instance resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_java_app_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_memcached_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_mysql_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_nodejs_app_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_permission resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_php_app_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_rails_app_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_rds_db_instance resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_stack resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_static_web_layer resource has been removed\n- provider: As the AWS OpsWorks Stacks service has reached End Of Life, the aws_opsworks_user_profile resource has been removed\n- provider: As the AWS SDK for Go v2 does not support Amazon SimpleDB the aws_simpledb_domain resource has been removed. Add a constraint to v5 of the Terraform AWS Provider for continued use of this resource\n- provider: As the AWS SDK for Go v2 does not support Amazon Worklink, the aws_worklink_fleet resource has been removed\n- provider: As the AWS SDK for Go v2 does not support Amazon Worklink, the aws_worklink_website_certificate_authority_association resource has been removed\n- provider: The aws_redshift_service_account resource has been removed. AWS recommends that a service principal name should be used instead of an AWS account ID in any relevant IAM policy\n- provider: The endpoints.iotanalytics and endpoints.iotevents configuration arguments have been removed\n- provider: The endpoints.opsworks configuration argument has been removed\n- provider: The endpoints.simpledb and endpoints.sdb configuration arguments have been removed\n- provider: The endpoints.worklink configuration argument has been removed\n- `aws_accessanalyzer_archive_rule`: filter.exists now only accepts one of \"\" (empty string), true, or false\n- `aws_alb_target_group`: preserve_client_ip now only accepts one of \"\" (empty string), true, or false\n- `aws_api_gateway_account`: The reset_on_delete argument has been removed\n- `aws_api_gateway_deployment`: Remove canary_settings, execution_arn, invoke_url, stage_description, and stage_name arguments. Instead, use the aws_api_gateway_stage resource to manage stages.\n- `aws_batch_compute_environment`: Rename compute_environment_name to name resource/aws_batch_compute_environment: Rename compute_environment_name_prefix to name_prefix\n- `aws_batch_compute_environment_data_source`: Rename compute_environment_name to name\n- `aws_batch_job_queue`: Remove deprecated parameter compute_environments in place of compute_environment_order\n- `aws_bedrock_model_invocation_logging_configuration`: logging_config, logging_config.cloudwatch_config, logging_config.cloudwatch_config.large_data_delivery_s3_config, and logging_config.s3_config are now list nested blocks instead of single nested blocks\n- `aws_cloudfront_key_value_store`: Attribute id is now set to remote object's Id instead of name\n- `aws_cloudfront_response_headers_policy`: The etag argument is now computed only\n- `aws_cloudtrail_event_data_store`: suspend now only accepts one of \"\" (empty string), true, or false\n- `aws_cognito_user_in_group`: The id attribute is now a comma-delimited string concatenating the user_pool_id, group_name, and username arguments\n- `aws_cur_report_definition`: The s3_prefix argument is now required\n- `aws_db_instance`: character_set_name now cannot be set with replicate_source_db, restore_to_point_in_time, s3_import, or snapshot_identifier.\n- `aws_dms_endpoint`: Remove s3_settings attribute. Use aws_dms_s3_endpoint instead\n- `aws_dx_gateway_association`: vpn_gateway_id has been removed\n- `aws_ec2_spot_instance_fleet`: terminate_instances_on_delete now only accepts one of \"\" (empty string), true, or false\n- `aws_ec2_spot_instance_request`: Remove block_duration_minutes attribute\n- `aws_ecs_task_definition`: Remove inference_accelerator attribute. Amazon Elastic Inference reached end of life on April, 2024.\n- `aws_eip`: vpc has been removed. Use domain instead.\n- `aws_eks_addon`: resolve_conflicts has been removed. Use resolve_conflicts_on_create and resolve_conflicts_on_update instead.\n- `aws_elasticache_cluster`: auto_minor_version_upgrade now only accepts one of \"\" (empty string), true, or false\n- `aws_elasticache_replication_group`: at_rest_encryption_enabled and auto_minor_version_upgrade now only accept one of \"\" (empty string), true, or false\n- `aws_elasticache_replication_group`: auth_token_update_strategy no longer has a default value. If auth_token is set, auth_token_update_strategy must also be explicitly configured.\n- `aws_evidently_feature`: variations.value.bool_value now only accepts one of \"\" (empty string), true, or false\n- `aws_flow_log`: log_group_name has been removed. Use log_destination instead.\n- `aws_globalaccelerator_accelerator`: The id attribute is now computed only\n- `aws_guardduty_detector`: Deprecates datasources. Use aws_guardduty_detector_feature resources instead.\n- `aws_guardduty_organization_configuration`: The auto_enable attribute has been removed\n- `aws_identitystore_group`: filter has been removed\n- `aws_imagebuilder_container_recipe`: instance_configuration.block_device_mapping.ebs.delete_on_termination and instance_configuration.block_device_mapping.ebs.encrypted now only accept one of \"\" (empty string), true, or false\n- `aws_imagebuilder_image_recipe`: block_device_mapping.ebs.delete_on_termination and block_device_mapping.ebs.encrypted now only accept one of \"\" (empty string), true, or false\n- `aws_instance`: Remove cpu_core_count and cpu_threads_per_core. Instead, use cpu_options.\n- `aws_instance`: user_data now displays cleartext instead of a hash. Base64 encoded content should use user_data_base64 instead.\n- `aws_launch_template`: block_device_mappings.ebs.delete_on_termination, block_device_mappings.ebs.encrypted, ebs_optimized, network_interfaces.associate_carrier_ip_address, network_interfaces.associate_public_ip_address, network_interfaces.delete_on_termination, and network_interfaces.primary_ipv6 now only accept one of \"\" (empty string), true, or false\n- `aws_launch_template`: Remove elastic_inference_accelerator attribute. Amazon Elastic Inference reached end of life on April, 2024.\n- `aws_launch_template`: elastic_gpu_specifications has been removed\n- `aws_lb_listener`: mutual_authentication attributes advertise_trust_store_ca_names, ignore_client_certificate_expiry, and trust_store_arn are only valid if mode is verify\n- `aws_lb_target_group`: preserve_client_ip now only accepts one of \"\" (empty string), true, or false\n- `aws_mq_broker`: logs.audit now only accepts one of \"\" (empty string), true, or false\n- `aws_networkmanager_core_network`: The base_policy_region argument has been removed. Use base_policy_regions instead.\n- `aws_opensearch_domain`: kibana_endpoint has been removed\n- `aws_opensearchserverless_security_config`: saml_options is now a list nested block instead of a single nested block\n- `aws_paymentcryptography_key`: key_attributes and key_attributes.key_modes_of_use are now list nested blocks instead of single nested blocks.\n- `aws_quicksight_data_set`: tags_all has been removed\n- `aws_redshift_cluster`: Attributes cluster_public_key, cluster_revision_number, and endpoint are now read only and should not be set\n- `aws_redshift_cluster`: The logging attribute has been removed\n- `aws_redshift_cluster`: The publicly_accessible attribute now defaults to false\n- `aws_redshift_cluster`: The snapshot_copy attribute has been removed\n- `aws_rekognition_stream_processor`: regions_of_interest.bounding_box is now a list nested block instead of a single nested block\n- `aws_resiliencehub_resiliency_policy`: policy, policy.az, policy.hardware, policy.software, and policy.region are now list nested blocks instead of single nested blocks\n- `aws_sagemaker_app_image_config`: Exactly one code_editor_app_image_config, jupyter_lab_image_config, or kernel_gateway_image_config block must be configured\n- `aws_sagemaker_image_version`: id is now a comma-delimited string concatenating image_name and version\n- `aws_sagemaker_notebook_instance`: Remove accelerator_types from your configuration, it no longer exists. Instead, use instance_type to use Inferentia.\n- `aws_ssm_association`: Remove instance_id argument\n- `aws_verifiedpermissions_schema`: definition is now a list nested block instead of a single nested block\n- `aws_wafv2_web_acl`: rule.statement.managed_rule_group_statement.managed_rule_group_configs.aws_managed_rules_bot_control_rule_set.enable_machine_learning now defaults to false",
      "migration_path": "1. Give the provider a version constraint in the `required_providers` block. HashiCorp recommends a version constraint for every provider a module depends on.\n2. In a root module, also specify the maximum provider version, to avoid accidental upgrades to incompatible new versions. The `~>` operator is a shorthand that allows the rightmost component of a version to increment. Do not use `~>` or other maximum-version constraints in modules you intend to reuse across many configurations. Specify a minimum version there and let the root module manage the maximum version.\n3. Commit the dependency lock file to version control with the configuration, so that Terraform always installs the same provider versions.\n4. To adopt 6.0.0, change the version in the `required_providers` block and re-run `terraform init`. HashiCorp states that this upgrades the provider version in the lock file. Without a change, Terraform re-selects the version recorded in the lock file, even if a newer version has become available. With the `-upgrade` option, `terraform init` disregards the recorded selection and selects the newest available version matching the version constraint. The [release notes](https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.0.0) list each breaking change.\n5. Review the changes Terraform made to the lock file in version control. If they are changes you made intentionally, send them through the usual code review process.",
      "replacement": null,
      "affected_versions": [
        "6.0.0"
      ],
      "source_url": "https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.0.0",
      "extra_source_urls": [
        "https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-6-upgrade"
      ],
      "vendor_ref": "v6.0.0",
      "last_checked_at": "2026-11-12T09:55:27.655Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-terraform-aws-6-0-0-breaking-change"
    },
    {
      "slug": "azure-terraform-azurerm-5-0-0-breaking-change",
      "title": "Terraform AzureRM provider 5.0.0: breaking changes",
      "summary": "Release date for Terraform AzureRM provider 5.0.0: 27 Jul 2026. Breaking changes listed in the release notes: 1.",
      "cloud": "azure",
      "service": "Terraform AzureRM provider",
      "service_slug": "terraform-azurerm",
      "category": "iac_provider",
      "type": "breaking_change",
      "announced_date": "2026-07-27",
      "effective_date": "2026-07-27",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Major Version: Version 5.0 of the Azure Provider is a major version - some behaviours have changed and some deprecated fields/resources have been removed - please refer to the 5.0 upgrade guide for more information.",
      "migration_path": "1. Give the provider a version constraint in the `required_providers` block. HashiCorp recommends a version constraint for every provider a module depends on.\n2. In a root module, also specify the maximum provider version, to avoid accidental upgrades to incompatible new versions. The `~>` operator is a shorthand that allows the rightmost component of a version to increment. Do not use `~>` or other maximum-version constraints in modules you intend to reuse across many configurations. Specify a minimum version there and let the root module manage the maximum version.\n3. Commit the dependency lock file to version control with the configuration, so that Terraform always installs the same provider versions.\n4. To adopt 5.0.0, change the version in the `required_providers` block and re-run `terraform init`. HashiCorp states that this upgrades the provider version in the lock file. Without a change, Terraform re-selects the version recorded in the lock file, even if a newer version has become available. With the `-upgrade` option, `terraform init` disregards the recorded selection and selects the newest available version matching the version constraint. The [release notes](https://github.com/hashicorp/terraform-provider-azurerm/releases/tag/v5.0.0) list each breaking change.\n5. Review the changes Terraform made to the lock file in version control. If they are changes you made intentionally, send them through the usual code review process.",
      "replacement": null,
      "affected_versions": [
        "5.0.0"
      ],
      "source_url": "https://github.com/hashicorp/terraform-provider-azurerm/releases/tag/v5.0.0",
      "extra_source_urls": [
        "https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/5.0-upgrade-guide"
      ],
      "vendor_ref": "v5.0.0",
      "last_checked_at": "2026-11-12T09:55:24.324Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-terraform-azurerm-5-0-0-breaking-change"
    },
    {
      "slug": "azure-defender-for-cloud-azure-china-21vianet-retirement",
      "title": "Microsoft Defender for Cloud: retirement in Azure operated by 21Vianet",
      "summary": "Retirement date for Microsoft Defender for Cloud in Microsoft Azure operated by 21Vianet (Azure in China): 18 Aug 2026. Microsoft announced the removal of all related features and services in that environment.",
      "cloud": "azure",
      "service": "Microsoft Defender for Cloud",
      "service_slug": "defender-for-cloud",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-08-20",
      "effective_date": "2026-08-18",
      "effective_precision": "day",
      "impact": "Microsoft announced the retirement and removal of all features and services related to Microsoft Defender for Cloud within Microsoft Azure operated by 21Vianet, with the date 18 Aug 2026. After the retirement date, customers cannot access the Microsoft Defender for Cloud portal or any associated Microsoft Defender for Cloud services or features in that environment. The retirement applies to Microsoft Defender for Cloud within Microsoft Azure operated by 21Vianet, also known as Azure in China.",
      "migration_path": "Microsoft advises customers to work with their account representatives for Microsoft Azure operated by 21Vianet to assess the impact of the retirement on their operations in that environment. Further details are on [this documentation page](https://aka.ms/MDC21Vdeprecationdocs).",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=498749",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/china/overview-operations",
        "https://aka.ms/MDC21Vdeprecationdocs"
      ],
      "vendor_ref": "498749",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-defender-for-cloud-azure-china-21vianet-retirement"
    },
    {
      "slug": "azure-sentinel-21vianet-china-retirement",
      "title": "Microsoft Sentinel: retirement in Azure operated by 21Vianet",
      "summary": "Retirement date for Microsoft Sentinel in Microsoft Azure operated by 21Vianet (Azure in China): 18 Aug 2026. After that date the Microsoft Sentinel portal and any associated Sentinel services or features are no longer accessible in that environment.",
      "cloud": "azure",
      "service": "Microsoft Sentinel",
      "service_slug": "sentinel",
      "category": "service",
      "type": "retirement",
      "announced_date": "2025-08-20",
      "effective_date": "2026-08-18",
      "effective_precision": "day",
      "impact": "Microsoft announced a plan to retire and remove all features and services related to Microsoft Sentinel within Microsoft Azure operated by 21Vianet, also known as Azure in China. After the retirement date, customers can no longer access the Microsoft Sentinel portal or any associated Microsoft Sentinel services or features in that environment.",
      "migration_path": "Work with your account representative for Microsoft Azure operated by 21Vianet to assess the impact of this retirement on your operations in that environment.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=498754",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/china/overview-operations"
      ],
      "vendor_ref": "498754",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sentinel-21vianet-china-retirement"
    },
    {
      "slug": "gcp-cloud-run-go-1-23-retirement",
      "title": "Cloud Run: Go 1.23 decommission",
      "summary": "Decommission date for Go 1.23 on Cloud Run: 21 Aug 2026. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2026-08-21",
      "effective_precision": "day",
      "impact": "The decommission date of Go 1.23 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-go-1-23-retirement"
    },
    {
      "slug": "azure-ai-personalizer-retirement",
      "title": "Azure AI Personalizer retirement",
      "summary": "Retirement date for AI Services Personalizer: 25 Aug 2026. Existing resources can be used until that date. After it, the service is not supported and can no longer be used with applications.",
      "cloud": "azure",
      "service": "Azure AI Personalizer",
      "service_slug": "ai-personalizer",
      "category": "service",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-08-25",
      "effective_precision": "day",
      "impact": "AI Services Personalizer is retired on the retirement date. Existing AI Services Personalizer resources can be used until the retirement date. After the retirement date, AI Services Personalizer is not supported and can no longer be used with applications.",
      "migration_path": "Microsoft has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=ai-services-personalizer-will-be-retired-on-1-october-2026",
      "extra_source_urls": [],
      "vendor_ref": "ai-services-personalizer-will-be-retired-on-1-october-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-personalizer-retirement"
    },
    {
      "slug": "multi-terraform-1-14-end-of-support",
      "title": "Terraform CLI: Terraform 1.14 end of support",
      "summary": "End of support date for Terraform 1.14: 26 Aug 2026. Under the HashiCorp policy as summarized by endoflife.date, fixes are provided for up to two releases from the most current major release, where a major release is a change in the first or second digit of X.Y.Z.",
      "cloud": "multi",
      "service": "Terraform",
      "service_slug": "terraform",
      "category": "iac_language",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-08-26",
      "effective_precision": "day",
      "impact": "endoflife.date summarizes the HashiCorp support period policy as follows. Generally Available (GA) releases of active products are supported for up to two (2) years. Eligible code fixes and hot fixes are provided through a new minor release (Z) on top of the latest major release branch, for up to two (2) releases from the most current major release. A major release is identified by a change in the first (X) or second (Y) digit of version X.Y.Z.",
      "migration_path": "1. Move to a Terraform release that is still supported.\n2. The [Terraform upgrade guides](https://developer.hashicorp.com/terraform/language/upgrade-guides) page shows the guide for the latest version. Use the version selector to view the upgrade guides for older Terraform versions.",
      "replacement": null,
      "affected_versions": [
        "1.14"
      ],
      "source_url": "https://endoflife.date/terraform",
      "extra_source_urls": [
        "https://support.hashicorp.com/hc/en-us/articles/360021185113-Support-Period-and-End-of-Life-EOL-Policy"
      ],
      "vendor_ref": "terraform@1.14",
      "last_checked_at": "2026-11-12T09:55:38.105Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-terraform-1-14-end-of-support"
    },
    {
      "slug": "aws-rds-mariadb-10-5-end-of-support",
      "title": "Amazon RDS for MariaDB: MariaDB 10.5 end of standard support",
      "summary": "RDS end of standard support date for MariaDB 10.5 on Amazon RDS for MariaDB: 31 Aug 2026. AWS lists this date so that testing and upgrade cycles can be planned around it.",
      "cloud": "aws",
      "service": "Amazon RDS for MariaDB",
      "service_slug": "rds-mariadb",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-08-31",
      "effective_precision": "day",
      "impact": "31 Aug 2026 is the RDS end of standard support date that AWS lists for MariaDB 10.5. The AWS page does not state what happens to DB instances still on MariaDB 10.5 after that date.\n\n- RDS for MariaDB major versions remain available at least until community end of life for the corresponding community version.\n- A date with only a month and a year is approximate and is replaced by an exact date once known.\n- If AWS extends support for a version beyond the stated date, it plans to update its version table with the later date.\n- Deprecation policy: see the [Amazon RDS FAQs](https://aws.amazon.com/rds/faqs/).",
      "migration_path": "1. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command.\n2. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n3. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MariaDB](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MariaDB.Major.html). Major version upgrades are performed manually.\n4. Plan for downtime: database engine upgrades require downtime, and its duration varies with the size of the DB instance.\n5. Downtime for the upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. The engine cannot be reverted after the upgrade completes. To return to the previous version, restore the first DB snapshot taken during the upgrade to a new DB instance. Amazon RDS only takes these snapshots if the backup retention period of the DB instance is greater than 0.",
      "replacement": null,
      "affected_versions": [
        "10.5"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MariaDB.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mariadb"
      ],
      "vendor_ref": "amazon-rds-mariadb@10.5",
      "last_checked_at": "2026-11-12T09:55:39.673Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mariadb-10-5-end-of-support"
    },
    {
      "slug": "azure-ai-document-intelligence-v2-0-api-retirement",
      "title": "Azure AI Document Intelligence: v2.0 API retirement",
      "summary": "Retirement date for the Azure AI Document Intelligence v2.0 API: 31 Aug 2026. Microsoft asks customers to transition to the v3.1 API by that date.",
      "cloud": "azure",
      "service": "Azure AI Document Intelligence",
      "service_slug": "ai-document-intelligence",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-09-15",
      "effective_date": "2026-08-31",
      "effective_precision": "day",
      "impact": "The Azure AI Document Intelligence v2.0 API is retired on 31 Aug 2026. Customers using v2.0 are asked to transition to the v3.1 API by that date. Azure Form Recognizer is the former name of Azure AI Document Intelligence.",
      "migration_path": "Follow the [detailed steps](https://aka.ms/doc-intelligence/migration) to transition to Azure AI Document Intelligence v3.1. Pricing information is in the [pricing documentation](https://aka.ms/doc-intelligence/pricing).",
      "replacement": "Azure AI Document Intelligence v3.1 API",
      "affected_versions": [
        "2.0"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=retirement-azure-ai-document-intelligence-v20-api-will-be-retired-on-31-august-2026",
      "extra_source_urls": [
        "https://techcommunity.microsoft.com/t5/azure-ai-services-blog/azure-form-recognizer-is-now-azure-ai-document-intelligence-with/ba-p/3875765",
        "https://aka.ms/doc-intelligence/migration",
        "https://aka.ms/doc-intelligence/pricing",
        "https://azure.microsoft.com/updates?id=migrate-to-azure-ai-document-intelligence-v31-ga-version"
      ],
      "vendor_ref": "retirement-azure-ai-document-intelligence-v20-api-will-be-retired-on-31-august-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-document-intelligence-v2-0-api-retirement"
    },
    {
      "slug": "azure-vpn-gateway-vpn-client-for-linux-preview-retirement",
      "title": "Azure VPN Gateway: Azure VPN Client for Linux (Preview) retirement",
      "summary": "Retirement date for the Azure VPN Client for Linux (Preview): 31 Aug 2026. After that date, Point-to-Site (P2S) VPN connections that use this client may fail.",
      "cloud": "azure",
      "service": "Azure VPN Gateway",
      "service_slug": "vpn-gateway",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2026-06-10",
      "effective_date": "2026-08-31",
      "effective_precision": "day",
      "impact": "The Azure VPN Client for Linux (Preview) stayed in public preview and has no path to general availability. After the retirement date, connections using the client may fail, which can result in loss of access to Azure resources through Point-to-Site (P2S) VPN connections. From September 1, 2026, the Linux preview client is not supported for Azure VPN Gateway P2S connections.",
      "migration_path": "1. Transition your Azure VPN Gateway Point-to-Site (P2S) configuration to support alternative Linux VPN clients.\n2. Distribute those clients to users before September 1, 2026.\n3. For supported Point-to-Site VPN options and configuration steps, [see the Azure VPN Gateway documentation](https://aka.ms/AzVPNClientLinuxRetire).\n4. Update the VPN gateway configuration and end-user clients through your standard change management process.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=565393",
      "extra_source_urls": [
        "https://aka.ms/AzVPNClientLinuxRetire"
      ],
      "vendor_ref": "565393",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-vpn-gateway-vpn-client-for-linux-preview-retirement"
    },
    {
      "slug": "gcp-compute-engine-debian-11-image-end-of-support",
      "title": "Compute Engine: Debian 11 image end of support",
      "summary": "EOS and image deprecation date for the Debian 11 public image on Compute Engine: 31 Aug 2026. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-08-31",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Debian 11 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Debian 11"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "debian-11",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-debian-11-image-end-of-support"
    },
    {
      "slug": "aws-msk-apache-kafka-3-7-end-of-support",
      "title": "Amazon MSK: Apache Kafka 3.7 end of support",
      "summary": "End of support date for Apache Kafka 3.7 on Amazon MSK: 1 Sep 2026. After that date, a cluster still using the version is auto-upgraded to the recommended Kafka version.",
      "cloud": "aws",
      "service": "Amazon MSK",
      "service_slug": "msk",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-09-01",
      "effective_precision": "day",
      "impact": "Amazon MSK supports a Kafka version until its end of support date. After that date:\n\n- A cluster still using the version is auto-upgraded to the recommended Kafka version.\n- The automatic upgrade can happen at any time after the end of support date.\n- No notification is sent before the upgrade.\n\nFor Kafka versions with a published end of support date, AWS states its intent to phase out support for newly created clusters. The page gives no date for this.",
      "migration_path": "1. Upgrade the MSK cluster to the recommended Kafka version or a higher version before the end of support date. The recommended version is marked in [Supported Apache Kafka versions](https://docs.aws.amazon.com/msk/latest/developerguide/supported-kafka-versions.html).\n2. Before upgrading, verify that the version of your client-side software supports the features in the new Kafka version. Server-side upgrades do not automatically update client applications.\n3. Follow [Upgrade the Apache Kafka version](https://docs.aws.amazon.com/msk/latest/developerguide/version-upgrades.html) to upgrade with the console, the AWS CLI or the API. The CLI command `aws kafka get-compatible-kafka-versions` lists the versions the cluster can upgrade to.\n4. Version downgrades are not supported.\n5. See [Best practices for version upgrades](https://docs.aws.amazon.com/msk/latest/developerguide/version-upgrades-best-practices.html).",
      "replacement": null,
      "affected_versions": [
        "3.7"
      ],
      "source_url": "https://docs.aws.amazon.com/msk/latest/developerguide/supported-kafka-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-msk"
      ],
      "vendor_ref": "amazon-msk@3.7",
      "last_checked_at": "2026-11-12T09:55:42.420Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-msk-apache-kafka-3-7-end-of-support"
    },
    {
      "slug": "azure-blob-storage-blobfuse-v1-end-of-support",
      "title": "Azure Blob Storage: BlobFuse v1 end of support",
      "summary": "End of support date for BlobFuse v1: Sep 2026. Microsoft recommends upgrading to BlobFuse v2.",
      "cloud": "azure",
      "service": "Azure Blob Storage",
      "service_slug": "blob-storage",
      "category": "api_sdk",
      "type": "end_of_support",
      "announced_date": "2025-09-26",
      "effective_date": "2026-09-01",
      "effective_precision": "month",
      "impact": "Support for BlobFuse v1 is discontinued effective Sep 2026. All future enhancements related to Azure Blob Storage file system access are focused exclusively on BlobFuse v2.",
      "migration_path": "Migrate to [BlobFuse v2](https://aka.ms/blobfuse) using Microsoft's [migration instructions](https://github.com/Azure/azure-storage-fuse/blob/main/MIGRATION.md).",
      "replacement": "BlobFuse v2",
      "affected_versions": [
        "1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=498563",
      "extra_source_urls": [
        "https://aka.ms/blobfuse",
        "https://github.com/Azure/azure-storage-fuse/blob/main/MIGRATION.md"
      ],
      "vendor_ref": "498563",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-blob-storage-blobfuse-v1-end-of-support"
    },
    {
      "slug": "azure-container-registry-2017-03-01-ga-api-retirement",
      "title": "Azure Container Registry: 2017-03-01-GA API retirement",
      "summary": "Retirement of the 2017-03-01-GA API of Azure Container Registry: Sep 2026. After that date, this API version no longer works.",
      "cloud": "azure",
      "service": "Azure Container Registry",
      "service_slug": "container-registry",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-01",
      "effective_precision": "month",
      "impact": "After the retirement date, the 2017-03-01-GA API no longer works. Microsoft asks users of this API to move to a newer version of the ACR API to avoid errors from using a deprecated API. The API may also be consumed through one or more SDKs.",
      "migration_path": "1. Move to a newer version of the ACR API. See the [list of supported versions](https://learn.microsoft.com/azure/templates/microsoft.containerregistry/allversions).\n2. If you consume this API through an SDK, update to a newer version of the SDK. See the [list of SDKs and their latest versions](https://azure.github.io/azure-sdk/releases/latest/index.html?search=containerregistry).",
      "replacement": null,
      "affected_versions": [
        "2017-03-01-GA"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=we-re-ending-support-for-the-20170301ga-api",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/templates/microsoft.containerregistry/allversions"
      ],
      "vendor_ref": "we-re-ending-support-for-the-20170301ga-api",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-container-registry-2017-03-01-ga-api-retirement"
    },
    {
      "slug": "azure-virtual-machines-cc-v5-nested-confidential-vm-series-retirement",
      "title": "Azure Virtual Machines: cc_v5 nested confidential VM series retirement",
      "summary": "Retirement date for the cc_v5 confidential VM series on Azure Virtual Machines: 1 Sep 2026. From that date the series is not available for use or purchase.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-08-05",
      "effective_date": "2026-09-01",
      "effective_precision": "day",
      "impact": "From the retirement date, the cc_v5 confidential VM series is not available for use or purchase. The retired VM sizes are DCas_cc_v5, DCads_cc_v5, ECas_cc_v5 and ECads_cc_v5. Any affected VM that was not resized before the retirement date is deallocated.",
      "migration_path": "Resize affected DCas_cc_v5, DCads_cc_v5, ECas_cc_v5 and ECads_cc_v5 VMs before 1 Sep 2026. Any affected VM not resized before that date is deallocated.",
      "replacement": null,
      "affected_versions": [
        "DCas_cc_v5",
        "DCads_cc_v5",
        "ECas_cc_v5",
        "ECads_cc_v5"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=568661",
      "extra_source_urls": [],
      "vendor_ref": "568661",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-cc-v5-nested-confidential-vm-series-retirement"
    },
    {
      "slug": "gcp-compute-engine-cos-117-lts-image-end-of-support",
      "title": "Compute Engine: COS 117 LTS image end of support",
      "summary": "EOS and image deprecation date for the COS 117 LTS public image on Compute Engine: Sep 2026. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-09-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of COS 117 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "COS 117 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "cos-117-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-cos-117-lts-image-end-of-support"
    },
    {
      "slug": "oci-terraform-oci-9-0-0-breaking-change",
      "title": "Terraform OCI provider 9.0.0: breaking changes",
      "summary": "Release date for Terraform OCI provider 9.0.0: 2 Sep 2026. Removals or breaking changes listed in the release notes: 1.",
      "cloud": "oci",
      "service": "Terraform OCI provider",
      "service_slug": "terraform-oci",
      "category": "iac_provider",
      "type": "breaking_change",
      "announced_date": "2026-09-02",
      "effective_date": "2026-09-02",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Removed Terraform Support for distributed_database",
      "migration_path": "1. Give the provider a version constraint in the `required_providers` block. HashiCorp recommends a version constraint for every provider a module depends on.\n2. In a root module, also specify the maximum provider version, to avoid accidental upgrades to incompatible new versions. The `~>` operator is a shorthand that allows the rightmost component of a version to increment. Do not use `~>` or other maximum-version constraints in modules you intend to reuse across many configurations. Specify a minimum version there and let the root module manage the maximum version.\n3. Commit the dependency lock file to version control with the configuration, so that Terraform always installs the same provider versions.\n4. To adopt 9.0.0, change the version in the `required_providers` block and re-run `terraform init`. HashiCorp states that this upgrades the provider version in the lock file. Without a change, Terraform re-selects the version recorded in the lock file, even if a newer version has become available. With the `-upgrade` option, `terraform init` disregards the recorded selection and selects the newest available version matching the version constraint. The [release notes](https://github.com/oracle/terraform-provider-oci/releases/tag/v9.0.0) list each removal or breaking change.\n5. Review the changes Terraform made to the lock file in version control. If they are changes you made intentionally, send them through the usual code review process.",
      "replacement": null,
      "affected_versions": [
        "9.0.0"
      ],
      "source_url": "https://github.com/oracle/terraform-provider-oci/releases/tag/v9.0.0",
      "extra_source_urls": [],
      "vendor_ref": "v9.0.0",
      "last_checked_at": "2026-11-12T09:55:31.026Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/oci-terraform-oci-9-0-0-breaking-change"
    },
    {
      "slug": "azure-computer-vision-v1-0-v2-0-v2-1-v3-0-v3-1-apis-retirement",
      "title": "Azure Computer Vision: v1.0, v2.0, v2.1, v3.0 and v3.1 APIs retirement",
      "summary": "Retirement date for the Computer Vision v1.0, v2.0, v2.1, v3.0 and v3.1 APIs: 13 Sep 2026. After that date, API calls to these versions are no longer possible.",
      "cloud": "azure",
      "service": "Azure Computer Vision",
      "service_slug": "computer-vision",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-13",
      "effective_precision": "day",
      "impact": "After 13 Sep 2026, API calls to the Computer Vision v1.0, v2.0, v2.1, v3.0 and v3.1 APIs are no longer possible. Azure Computer Vision workloads that still call these API versions are affected.",
      "migration_path": "Migrate workloads to the Computer Vision v3.2 API before 13 Sep 2026, using Microsoft's migration [documentation](https://aka.ms/cv32migration).",
      "replacement": "Computer Vision v3.2 API",
      "affected_versions": [
        "1.0",
        "2.0",
        "2.1",
        "3.0",
        "3.1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=computer-vision-api-retirements-13-9-2026",
      "extra_source_urls": [
        "https://aka.ms/cv32migration"
      ],
      "vendor_ref": "computer-vision-api-retirements-13-9-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-computer-vision-v1-0-v2-0-v2-1-v3-0-v3-1-apis-retirement"
    },
    {
      "slug": "azure-functions-runtime-1-x-end-of-support",
      "title": "Azure Functions: runtime version 1.x end of support",
      "summary": "End of support date for version 1.x of the Azure Functions runtime: 14 Sep 2026. The version can still be used after that date but no longer receives support or software and security updates.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "feature",
      "type": "end_of_support",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-14",
      "effective_precision": "day",
      "impact": "Support for version 1.x of the Azure Functions runtime ends on 14 Sep 2026. Version 1.x can still be used beyond that date, but it is no longer supported and no longer receives software or security updates.",
      "migration_path": "To stay on a supported version, [migrate to version 4.x of the Azure Functions runtime](https://aka.ms/v1-af-dotnet-migration) by the end of support date.",
      "replacement": "Azure Functions runtime version 4.x",
      "affected_versions": [
        "1.x"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=support-for-the-1x-version-of-azure-functions-ends-14-september-2026",
      "extra_source_urls": [
        "https://aka.ms/v1-af-dotnet-migration",
        "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions"
      ],
      "vendor_ref": "support-for-the-1x-version-of-azure-functions-ends-14-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-runtime-1-x-end-of-support"
    },
    {
      "slug": "azure-monitor-aks-engine-monitoring-retirement",
      "title": "Azure Monitor: AKS-Engine monitoring retirement",
      "summary": "Retirement date for AKS-Engine and for Azure Monitor support of applications hosted on it: 14 Sep 2026. Azure Monitor users lose the UX support, portal experience and monitoring agent for those applications.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2023-09-22",
      "effective_date": "2026-09-14",
      "effective_precision": "day",
      "impact": "AKS-Engine is retired on 14 Sep 2026. With this retirement, Azure Monitor users no longer have access to the UX support, portal experience, or monitoring agent for any applications hosted on AKS-Engine.",
      "migration_path": "[Enable Azure Monitor](https://learn.microsoft.com/azure/azure-monitor/containers/container-insights-enable-aks?tabs=azure-cli) when you migrate to AKS, before the retirement date.",
      "replacement": "AKS with Azure Monitor enabled",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-monitor-for-aksengine-will-not-be-supported-on-14-september-2026",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-monitor/containers/container-insights-enable-aks?tabs=azure-cli",
        "https://github.com/Azure/aks-engine/blob/master/SUPPORT.md"
      ],
      "vendor_ref": "azure-monitor-for-aksengine-will-not-be-supported-on-14-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-aks-engine-monitoring-retirement"
    },
    {
      "slug": "azure-monitor-data-collector-api-retirement",
      "title": "Azure Monitor: Data Collector API retirement",
      "summary": "Retirement date for the Data Collector API used to ingest custom logs into Azure Monitor logs: 14 Sep 2026. Microsoft names the Data Collection Rules based Log Ingestion API as the replacement.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-09-22",
      "effective_date": "2026-09-14",
      "effective_precision": "day",
      "impact": "Clients that send custom logs to Azure Monitor logs through the Data Collector API are affected. Data Collector API endpoints become unavailable after the retirement date. The source warns of ingestion errors and data loss for clients that have not transitioned.",
      "migration_path": "Transition to the DCR-based Log Ingestion API before the retirement date, using the Microsoft guide: [transition to the DCR-based Log Ingestion API](https://aka.ms/datacollectorapimigrate).",
      "replacement": "DCR-based Log Ingestion API",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-monitor-data-collection-api-retirement",
      "extra_source_urls": [
        "https://aka.ms/datacollectorapimigrate"
      ],
      "vendor_ref": "azure-monitor-data-collection-api-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-data-collector-api-retirement"
    },
    {
      "slug": "azure-sentinel-sap-containerized-data-connector-agent-retirement",
      "title": "Microsoft Sentinel: containerized SAP data connector agent retirement",
      "summary": "Retirement date for the containerized data connector agent for the Microsoft Sentinel solution for SAP applications: 14 Sep 2026. After that date the agent is permanently disabled and stops sending SAP logs to Microsoft Sentinel.",
      "cloud": "azure",
      "service": "Microsoft Sentinel",
      "service_slug": "sentinel",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2026-08-12",
      "effective_date": "2026-09-14",
      "effective_precision": "day",
      "impact": "The containerized data connector agent is retired on 14 Sep 2026. SAP log collection through it stops on that date, and after that date the agent is permanently disabled and stops sending SAP logs to Microsoft Sentinel. Analytics rules, workbooks, hunting queries and playbooks that rely on this data stop returning results for the affected SAP systems, and customers already using the agentless connector are not affected. Creation of new containerized agents was already disabled when the retirement was announced, and pricing and billing meters do not change.",
      "migration_path": "1. Migrate to the SAP agentless data connector before 14 Sep 2026. Start by deploying it alongside your existing containerized agent. [Learn more](https://learn.microsoft.com/azure/sentinel/sap/sap-agent-migrate).\n2. Validate log ingestion through the agentless connector.\n3. Decommission the containerized agent.",
      "replacement": "SAP agentless data connector",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=568457",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/sentinel/sap/sap-agent-migrate"
      ],
      "vendor_ref": "568457",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sentinel-sap-containerized-data-connector-agent-retirement"
    },
    {
      "slug": "azure-maps-gen1-price-tier-retirement",
      "title": "Azure Maps: Gen1 price tier (Standard S0 and S1) retirement",
      "summary": "Retirement date for the Azure Maps Gen1 price tier (Standard S0 and Standard S1): 15 Sep 2026. On that date, accounts still on Gen1 are automatically upgraded to the Gen2 price tier.",
      "cloud": "azure",
      "service": "Azure Maps",
      "service_slug": "maps",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2023-09-15",
      "effective_date": "2026-09-15",
      "effective_precision": "day",
      "impact": "Azure Maps accounts that use the Gen1 price tier (Standard S0 or Standard S1) are affected. On the retirement date, these accounts are automatically upgraded to the Gen2 price tier. Gen1 has not been offered for new accounts, or as a switch target from Gen2, in the Azure portal since 14 September 2023 and in Azure Resource Manager templates since 12 October 2023.",
      "migration_path": "1. Update Azure Resource Manager templates that create Azure Maps accounts so they use the Gen2 price tier, following the Microsoft [instructions](https://aka.ms/AzureMapsGen1PriceTierRetirement). The source set 12 October 2023 as the date for this change to avoid deployment disruptions.\n2. Switch existing Azure Maps accounts from the Gen1 price tier to the Gen2 price tier, as described in the same [instructions](https://aka.ms/AzureMapsGen1PriceTierRetirement).\n3. Review Gen2 pricing on the [Azure Maps Pricing](https://azure.microsoft.com/pricing/details/azure-maps/) page.",
      "replacement": "Azure Maps Gen2 price tier",
      "affected_versions": [
        "Gen1",
        "Standard S0",
        "Standard S1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=azure-maps-gen1-price-tier-retirement",
      "extra_source_urls": [
        "https://aka.ms/AzureMapsGen1PriceTierRetirement",
        "https://azure.microsoft.com/pricing/details/azure-maps/"
      ],
      "vendor_ref": "azure-maps-gen1-price-tier-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-maps-gen1-price-tier-retirement"
    },
    {
      "slug": "azure-monitor-activity-logs-legacy-solution-retirement",
      "title": "Azure Monitor: Activity Logs legacy solution retirement",
      "summary": "The Azure Activity Logs legacy solution is retired and replaced by Diagnostic settings. The source gives 15 March 2026 as the date the legacy flow stops working and all customers are auto migrated, and a manual move period through 15 Sep 2026.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2023-10-06",
      "effective_date": "2026-09-15",
      "effective_precision": "day",
      "impact": "The Azure Activity logs solution, which forwarded Activity Logs to Azure Log Analytics, EventHub and storage, is retired and automatically converted to Diagnostic settings. The source gives 15 March 2026 as the deprecation date, when all customers are auto migrated and the legacy flow stops working, and a manual move period through 15 Sep 2026. Automation that enables or disables the connector using the Legacy API is not supported and has to be recreated using the new API.",
      "migration_path": "1. Move manually to Diagnostic settings as explained in the [legacy collection methods documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log?tabs=powershell#legacy-collection-methods).\n2. If automation enables or disables the connector using the Legacy API, recreate it using the new API.",
      "replacement": "Diagnostic settings",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-activity-logs-legacy-solution-is-replaced-by-diagnostic-settings",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/activity-log?tabs=powershell#legacy-collection-methods"
      ],
      "vendor_ref": "azure-activity-logs-legacy-solution-is-replaced-by-diagnostic-settings",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-activity-logs-legacy-solution-retirement"
    },
    {
      "slug": "gcp-compute-engine-nvidia-p100-retirement",
      "title": "Compute Engine: NVIDIA P100 GPU shutdown",
      "summary": "Shutdown date for NVIDIA P100 GPUs on Google Cloud: 15 Sep 2026. After that date, resources that run NVIDIA P100 GPUs cannot be created or accessed.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-09-15",
      "effective_date": "2026-09-15",
      "effective_precision": "day",
      "impact": "After 15 Sep 2026, you cannot create or access any Google Cloud resources that run NVIDIA P100 GPUs. Besides Compute Engine VM instances, the affected resources include Google Kubernetes Engine nodes, Cloud Workstations workstations and Dataflow pipeline jobs. Until 15 Sep 2026, resources that run NVIDIA P100 GPUs are not affected. Google Cloud does not support products or features that have reached end of support (EOS).",
      "migration_path": "1. Choose a new GPU model. Google recommends the G2 or G4 machine series.\n2. Check that the selected GPU model is available in your locations. For services other than Gemini Enterprise Agent Platform, Colab Enterprise and Cloud Workstations, see [GPU regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones). For those services, see [Gemini Enterprise Agent Platform accelerator locations](https://docs.cloud.google.com/gemini-enterprise-agent-platform/machine-learning/general/locations#accelerators) and [Cloud Workstations GPU availability by region and zone](https://docs.cloud.google.com/workstations/docs/available-gpus#gpu_availability_by_region_and_zone).\n3. For Compute Engine, move to a new VM if the new GPU model runs on an accelerator-optimized machine type or is not supported in the zone of the existing VM. If the existing VM uses Local SSD disks with data you want to keep, move the contents to a Persistent Disk volume first. See [Create a G2 instance](https://docs.cloud.google.com/compute/docs/gpus/create-gpu-vm-g-series).\n4. Move Persistent Disk volumes to the new VM, reassign static IP addresses, install GPU drivers and your applications, then delete the old VM.\n5. If the new GPU model is supported in the same zone and runs on N1 general-purpose machine types, you can modify the existing VM instead: verify quota for the new GPU type, verify that your critical applications are stopped, stop the VM, change the GPU model, and start the VM.\n6. For other Google Cloud services, update your configurations to reference a supported GPU model, then restart or recreate your resources.",
      "replacement": "G2 (NVIDIA L4) or G4 (NVIDIA RTX PRO 6000) machine series",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/compute/docs/deprecations",
      "extra_source_urls": [
        "https://docs.cloud.google.com/compute/docs/eol/p100-eos"
      ],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-nvidia-p100-retirement"
    },
    {
      "slug": "azure-avm-web-site-0-23-0-breaking-change",
      "title": "avm-res-web-site 0.23.0: breaking changes",
      "summary": "Release date of version 0.23.0 of the Azure Verified Module avm-res-web-site: 15 Sep 2026. Breaking changes listed in the release notes: 6.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-09-15",
      "effective_date": "2026-09-15",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Logic App Node.js default: Logic Apps that do not set WEBSITE_NODE_DEFAULT_VERSION move from Node.js ~18 to ~22. Validate workflows before applying, or set logic_app_node_version = \"~18\" to retain the old runtime. (#344)\n- Logic App worker runtime: The module now sends Microsoft's documented FUNCTIONS_WORKER_RUNTIME = \"dotnet\" instead of \"node\". Microsoft says this should not affect workflow execution. To retain the old value, set app_settings = { FUNCTIONS_WORKER_RUNTIME = \"node\" } using that casing. (#379)\n- Removed outputs: Unused whole-resource outputs were removed from the certificate and configuration submodules. The root deployment_slot_locks, resource_lock, and resource_private_endpoints outputs were removed, and deployment_slots now exposes only each slot's name and resource_id. The root resource and private_endpoints compatibility outputs remain. Replace references with the available discrete outputs. (#369)\n- Output sensitivity: custom_domain_verification_id is now sensitive. Mark downstream outputs as sensitive, or use nonsensitive() when publishing it to the public asuid.<hostname> DNS TXT record. Resource and managed-identity IDs are no longer marked sensitive; existing downstream sensitive = true declarations remain valid. (#371)\n- Explicit null collection inputs: always_ready, backup, connection_strings, site_config, slots_storage_shares_to_mount_sensitive_values, sticky_settings, and storage_shares_to_mount now treat explicit null as absent and use their declared defaults. Remove explicit null assignments when upgrading. retry = null remains supported and continues to disable retries. (#374)\n- Flex Consumption app settings: New FC1 deployments no longer receive module-supplied FUNCTIONS_EXTENSION_VERSION or WEBSITE_CONTENTSHARE. Existing apps may retain previously written values because the underlying update resource merges settings; FC1 ignores them. Explicit caller-supplied app settings still pass through. (#380)",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-web-site/releases/tag/v0.23.0) for 0.23.0: 6. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-web-site from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-web-site). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.23.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.23.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.23.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-web-site/releases/tag/v0.23.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-web-site"
      ],
      "vendor_ref": "v0.23.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-web-site-0-23-0-breaking-change"
    },
    {
      "slug": "azure-maps-render-v1-apis-retirement",
      "title": "Azure Maps: Render V1 APIs retirement",
      "summary": "Retirement date for the Azure Maps Render V1 APIs: 17 Sep 2026. Microsoft directs users to the Azure Maps Render V2 APIs.",
      "cloud": "azure",
      "service": "Azure Maps",
      "service_slug": "maps",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-09-22",
      "effective_date": "2026-09-17",
      "effective_precision": "day",
      "impact": "Workloads that call the Azure Maps Render V1 APIs are affected. The source states that on the retirement date these workloads are deleted and associated application data is lost. The source states that the Render V1 APIs can be used without disruption up to the retirement date.",
      "migration_path": "Upgrade to the Azure Maps Render V2 APIs by the retirement date, using the Microsoft [upgrade documentation](https://aka.ms/AzureMapsRenderV1Retirement).",
      "replacement": "Azure Maps Render V2 APIs",
      "affected_versions": [
        "V1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=azure-maps-render-v1-apis-will-be-retired-on-17-september-2026",
      "extra_source_urls": [
        "https://aka.ms/AzureMapsRenderV1Retirement"
      ],
      "vendor_ref": "azure-maps-render-v1-apis-will-be-retired-on-17-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-maps-render-v1-apis-retirement"
    },
    {
      "slug": "azure-maps-web-sdk-map-control-v1-retirement",
      "title": "Azure Maps: Web SDK Map Control version 1.xx retirement",
      "summary": "Retirement date for Azure Maps Web SDK Map Control version 1.xx: 19 Sep 2026. Microsoft directs users to Web SDK Map Control version 3.xx.",
      "cloud": "azure",
      "service": "Azure Maps",
      "service_slug": "maps",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-19",
      "effective_precision": "day",
      "impact": "Applications that use Azure Maps Web SDK Map Control version 1.xx are affected. Microsoft states that on the retirement date workloads running Web SDK Map Control version 1.xx are deleted and the associated application data is lost.",
      "migration_path": "Follow Microsoft's [instructions](https://aka.ms/AzureMapsWebSDKMigrationGuide) to migrate to Azure Maps Web SDK Map Controls version 3.xx. The [Map Control release notes](https://learn.microsoft.com/azure/azure-maps/release-notes-map-control#v2-latest) describe version 3.xx.",
      "replacement": "Azure Maps Web SDK Map Control version 3.xx",
      "affected_versions": [
        "1.xx"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=azure-maps-web-sdk-map-controls-version-1xx-will-be-retired-on-19-september-2026",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-maps/release-notes-map-control#v2-latest",
        "https://aka.ms/AzureMapsWebSDKMigrationGuide"
      ],
      "vendor_ref": "azure-maps-web-sdk-map-controls-version-1xx-will-be-retired-on-19-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-maps-web-sdk-map-control-v1-retirement"
    },
    {
      "slug": "azure-health-data-services-smart-on-fhir-proxy-retirement",
      "title": "Azure Health Data Services: SMART on FHIR proxy retirement",
      "summary": "Retirement date for the SMART on FHIR proxy feature in the FHIR service of Azure Health Data Services: 21 Sep 2026. Microsoft names SMART on FHIR (Enhanced) as the replacement.",
      "cloud": "azure",
      "service": "Azure Health Data Services",
      "service_slug": "health-data-services",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-21",
      "effective_precision": "day",
      "impact": "After the retirement date, applications relying on SMART on FHIR proxy report errors in accessing the FHIR service. The proxy is integrated as part of the FHIR service, while the replacement, SMART on FHIR (Enhanced), requires integrating an open-source sample with the FHIR service. It also requires Azure products such as Azure API Management (APIM). Microsoft support covers the FHIR service, and support for the open-source sample is reported and monitored via [GitHub](https://github.com/Azure-Samples/azure-health-data-and-ai-samples/issues).",
      "migration_path": "1. Follow the instructions on [SMART on FHIR - Azure Health Data Services](https://aka.ms/SMARTAzuredocumentation) to migrate to the replacement option by the retirement date.\n2. Integrate the open-source sample with the FHIR service. The Microsoft documentation says to use the [Azure Health Data and AI Samples open source repo](https://github.com/Azure-Samples/azure-health-data-and-ai-samples) to set up the SMART on FHIR experience.",
      "replacement": "SMART on FHIR (Enhanced)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=smart-on-fhir-proxy-feature-in-azure-health-data-services-will-be-retired-on-21st-september-2026-transition-to-smart-on-fhir",
      "extra_source_urls": [
        "https://aka.ms/SMARTAzuredocumentation",
        "https://github.com/Azure-Samples/azure-health-data-and-ai-samples",
        "https://github.com/Azure-Samples/azure-health-data-and-ai-samples/issues"
      ],
      "vendor_ref": "smart-on-fhir-proxy-feature-in-azure-health-data-services-will-be-retired-on-21st-september-2026-transition-to-smart-on-fhir",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-health-data-services-smart-on-fhir-proxy-retirement"
    },
    {
      "slug": "azure-api-for-fhir-retirement",
      "title": "Azure API for FHIR retirement",
      "summary": "Retirement date for Azure API for FHIR: 30 Sep 2026. Microsoft directs customers to migrate to the Azure Health Data Services FHIR service before that date.",
      "cloud": "azure",
      "service": "Azure API for FHIR",
      "service_slug": "api-for-fhir",
      "category": "service",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Azure API for FHIR is retired on the retirement date. Customers running Azure API for FHIR need to migrate to the Azure Health Data Services FHIR service before that date to avoid service disruptions. New Azure API for FHIR deployments are blocked from 1 April 2025.",
      "migration_path": "Follow the [migration strategies](https://aka.ms/RetirementAPIFHIR) to migrate to the Azure Health Data Services [FHIR service](https://learn.microsoft.com/azure/healthcare-apis/fhir/overview) before 30 Sep 2026.",
      "replacement": "Azure Health Data Services FHIR service",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-api-for-fhir-retirement",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/healthcare-apis/healthcare-apis-overview",
        "https://learn.microsoft.com/azure/healthcare-apis/fhir/overview",
        "https://aka.ms/RetirementAPIFHIR"
      ],
      "vendor_ref": "azure-api-for-fhir-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-api-for-fhir-retirement"
    },
    {
      "slug": "azure-automation-python-2-7-3-8-powershell-7-1-7-2-end-of-support",
      "title": "Azure Automation: Python 2.7, 3.8 and PowerShell 7.1, 7.2 end of support",
      "summary": "Last day of support for the Python 2.7, Python 3.8, PowerShell 7.1 and PowerShell 7.2 runtime versions in Azure Automation: 30 Sep 2026. Runbooks on these versions may keep running but get no security updates, bug fixes or official support.",
      "cloud": "azure",
      "service": "Azure Automation",
      "service_slug": "automation",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-07-10",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "After the end of support date, Azure Automation no longer supports the runtime versions Python 2.7, Python 3.8, PowerShell 7.1 and PowerShell 7.2. Runbooks using these versions may continue to run but do not receive security updates, bug fixes or official support. Upgrading is required to maintain support eligibility and continued access to security updates and platform features.",
      "migration_path": "1. Upgrade the affected runbooks to supported runtime versions of Python and PowerShell.\n2. Use the support lifecycle resources Microsoft lists for guidance: [PowerShell Support Lifecycle](https://learn.microsoft.com/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.6) and [Python Version Support Status](https://devguide.python.org/versions/).\n3. See Microsoft's [Azure Automation runtime retirement policy](https://learn.microsoft.com/azure/automation/automation-runtime-retirement-policy) for details.",
      "replacement": null,
      "affected_versions": [
        "Python 2.7",
        "Python 3.8",
        "PowerShell 7.1",
        "PowerShell 7.2"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=567556",
      "extra_source_urls": [
        "https://learn.microsoft.com/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.6",
        "https://learn.microsoft.com/azure/automation/automation-runtime-retirement-policy"
      ],
      "vendor_ref": "567556",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-automation-python-2-7-3-8-powershell-7-1-7-2-end-of-support"
    },
    {
      "slug": "azure-batch-nvv3-nvv4-series-vm-retirement",
      "title": "Azure Batch: NVv3 and NVv4-series VM retirement",
      "summary": "Retirement date for NVv3-series and NVv4-series virtual machines in Azure Batch pools: 30 Sep 2026. After that date, new pools with these VM families cannot be created, and existing pools cannot scale out and are subject to forced resize to zero nodes.",
      "cloud": "azure",
      "service": "Azure Batch",
      "service_slug": "batch",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-03-16",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Azure Batch follows the Azure retirement dates for NVv3-series and NVv4-series VM support in Batch pools. After the retirement date, new Batch pools that specify the NVv3 or NVv4-series VM family cannot be created. Existing pools with NVv3 or NVv4-series VMs can no longer scale out and are subject to forced resize to zero nodes. The affected sizes are Standard_NV12s_v3, Standard_NV12hs_v3, Standard_NV24s_v3, Standard_NV24ms_v3, Standard_NV32ms_v3 and Standard_NV48s_v3 (NVv3), and Standard_NV4as_v4, Standard_NV4ahs_v4, Standard_NV8as_v4, Standard_NV8ahs_v4, Standard_NV16as_v4, Standard_NV16ahs_v4, Standard_NV32as_v4 and Standard_NV32ahs_v4 (NVv4).",
      "migration_path": "1. Microsoft's notice says to migrate Batch pools to \"a newer VM series in the same NC product line\", or to a different [Batch-supported VM size](https://go.microsoft.com/fwlink/?linkid=2285739) suitable for the workload.\n2. For the underlying VM retirements, see [NVv3 series retirement](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nvv3-series-retirement) and [NVv4 series retirement](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nvv4-retirement).",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=516070",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nvv3-series-retirement",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nvv4-retirement"
      ],
      "vendor_ref": "516070",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-batch-nvv3-nvv4-series-vm-retirement"
    },
    {
      "slug": "azure-mysql-5-7-end-of-support",
      "title": "Azure Database for MySQL: MySQL 5.7 end of standard support",
      "summary": "Azure Standard Support End Date for MySQL 5.7 on Azure Database for MySQL: 30 Sep 2026. After that date, servers still running the version are automatically enrolled in Extended Support and charged for it.",
      "cloud": "azure",
      "service": "Azure Database for MySQL",
      "service_slug": "mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "After the Standard Support end date, servers running MySQL 5.7 are automatically enrolled in Extended Support and automatically charged for it.\n\n- Extended Support provides critical security updates for up to three years after the end of Standard Support.\n- New features and minor version upgrades might not be guaranteed.\n- The charge is billed per vCore per hour, so read replicas and HA-enabled servers are billed for the additional vCores they consume.\n- Servers in stopped state are not charged for Extended Support.",
      "migration_path": "1. Choose a target MySQL version that is still within Standard Support. Upgrading to it avoids Extended Support charges.\n2. Upgrade read replicas that use an older MySQL version before upgrading the primary server.\n3. Check schema compatibility with the target version using the Validate feature in the Azure portal. Validation locks tables, and the page directs large-scale production environments to Oracle's client-side upgrade checker tool. Verify deprecated sql_mode values and remove or deselect them in the Server Parameters pane before upgrading, to avoid deployment failure.\n4. Ensure there are no active or pending XA transactions on the database. Ongoing XA transactions can cause the upgrade to fail.\n5. Trigger an on-demand backup before the major version upgrade of a production server, and perform the upgrade first on a restored server copy rather than on production directly.\n6. In the Azure portal, open the server, and on the Overview page select Upgrade. The major version upgrade is irreversible. Burstable SKU servers use a separate workflow that first upgrades the compute tier to a General-Purpose SKU. See [Major version upgrade in Azure Database for MySQL](https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-upgrade).",
      "replacement": null,
      "affected_versions": [
        "5.7"
      ],
      "source_url": "https://learn.microsoft.com/azure/mysql/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-mysql"
      ],
      "vendor_ref": "azure-database-for-mysql@5.7",
      "last_checked_at": "2026-11-12T09:55:37.239Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-mysql-5-7-end-of-support"
    },
    {
      "slug": "azure-functions-runtime-v3-linux-consumption-retirement",
      "title": "Azure Functions: runtime v3 on Linux Consumption retirement",
      "summary": "After 30 Sep 2026, function apps using Azure Functions runtime v3 on the Linux Consumption plan no longer start or process executions.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-04-17",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Azure Functions runtime v3 was retired on December 13, 2022, and Azure enforces that retirement for Linux Consumption function apps still on runtime v3. After 30 Sep 2026, function apps using runtime v3 on Linux Consumption no longer start or process executions. Existing deployments in this configuration stop functioning.",
      "migration_path": "1. Migrate affected apps to Azure Functions runtime v4 before the enforcement date. See [Migrate apps from Azure Functions version 3.x to version 4.x](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-version-3-version-4).\n2. The Linux Consumption plan has its own retirement date in September 2028, so Microsoft encourages migrating to Azure Functions Flex Consumption, which supports runtime v4. See [Migrate Azure Functions Linux Consumption plan apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex).",
      "replacement": "Azure Functions runtime v4",
      "affected_versions": [
        "3.x"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=559311",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/migrate-version-3-version-4",
        "https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex"
      ],
      "vendor_ref": "559311",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-runtime-v3-linux-consumption-retirement"
    },
    {
      "slug": "azure-aks-network-policy-manager-windows-end-of-support",
      "title": "Azure Kubernetes Service: Network Policy Manager on Windows nodes end of support",
      "summary": "End of support date for Azure Network Policy Manager (NPM) on Windows nodes in AKS: 30 Sep 2026. Microsoft points to alternatives such as Network Security Groups on the node level or Project Calico.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "feature",
      "type": "end_of_support",
      "announced_date": "2025-10-07",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Microsoft ends support for Azure Network Policy Manager (NPM) on Windows nodes in AKS on the end of support date. The existing Azure Network Policy Manager experience for Windows nodes is no longer supported from that date. Microsoft points to alternative options for a setup to continue to receive support, security updates and deployment compatibility.",
      "migration_path": "1. Run the Azure Resource Graph query linked in the source to view impacted resources.\n2. Explore alternative options before the end of support date, such as [Network Security Groups (NSGs) on the node level](https://learn.microsoft.com/en-us/azure/aks/concepts-network#network-security-groups) or open-source tools like [Project Calico](https://www.tigera.io/tigera-products/calico/).",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=500273",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/aks/concepts-network#network-security-groups",
        "https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request"
      ],
      "vendor_ref": "500273",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-network-policy-manager-windows-end-of-support"
    },
    {
      "slug": "azure-machine-learning-data-labeling-retirement",
      "title": "Azure Machine Learning: data labeling retirement",
      "summary": "Retirement date for data labeling in Azure Machine Learning: 30 Sep 2026. On that date, workloads running data labeling are deleted and the associated application data is lost.",
      "cloud": "azure",
      "service": "Azure Machine Learning",
      "service_slug": "machine-learning",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-10-01",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Data labeling in Azure Machine Learning is retired on 30 Sep 2026. On the retirement date, workloads running data labeling are deleted and the associated application data is lost.",
      "migration_path": "1. Migrate existing data labeling workloads to third-party data labeling providers before the retirement date.\n2. Once labeled data is generated, copy it into an Azure Machine Learning storage account for further pre-processing or model training as required.",
      "replacement": "Third-party data labeling providers",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=501692",
      "extra_source_urls": [],
      "vendor_ref": "501692",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-machine-learning-data-labeling-retirement"
    },
    {
      "slug": "azure-machine-learning-external-data-import-and-data-connections-retirement",
      "title": "Azure Machine Learning: external data import and data connections retirement",
      "summary": "Import data from external sources (Preview) and external Data Connections (Preview) in Azure Machine Learning are not available after 30 Sep 2026. Existing connections are not available, and imported assets stay available but scheduled refreshes stop working.",
      "cloud": "azure",
      "service": "Azure Machine Learning",
      "service_slug": "machine-learning",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-03-31",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "After 30 Sep 2026, Import data from external sources (Preview), S3, Snowflake, Azure SQL Db and external Data Connections (Preview) in Azure Machine Learning are no longer available. Existing external data connections are not available. New data imports and new external data connections cannot be created. Pre-existing imported assets continue to be available, but any scheduled refresh no longer works.",
      "migration_path": "Microsoft recommends migrating external data imports to Microsoft Fabric and using AzureML datastores to make the data available in AzureML.",
      "replacement": "Microsoft Fabric with Azure Machine Learning datastores",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=557406",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request"
      ],
      "vendor_ref": "557406",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-machine-learning-external-data-import-and-data-connections-retirement"
    },
    {
      "slug": "azure-maps-web-sdk-map-control-2-0-x-and-service-module-retirement",
      "title": "Azure Maps: Web SDK Map Control 2.0.x and Service Module retirement",
      "summary": "Retirement date for Azure Maps Web SDK Map Control version 2.0.x and the Azure Maps Service Module: 30 Sep 2026. Microsoft names Web SDK Map Control version 3 and the Azure Maps JavaScript REST SDK as the replacements.",
      "cloud": "azure",
      "service": "Azure Maps",
      "service_slug": "maps",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2024-03-29",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Applications that use Azure Maps Web SDK Map Control version 2.0.x or the Azure Maps Service Module are affected. The source states that on the retirement date workloads running either one are deleted and any associated application data is lost. The source states that both can be used without disruption up to the retirement date.",
      "migration_path": "1. If you use Web SDK Map Control version 2.0.x, follow the Microsoft [instructions to migrate](https://aka.ms/azuremapswebsdkmigrationguide) to the Azure Maps Web SDK version 3.0 by the retirement date. Version 3 is described in the [release notes](https://learn.microsoft.com/azure/azure-maps/release-notes-map-control#v3-latest).\n2. If you use the Azure Maps Service Module, follow the [developer guide to migrate](https://aka.ms/azuremapsservicemodulemigrationguide) to the Azure Maps JavaScript REST SDK by the retirement date. Usage is covered in the [JavaScript REST SDK guide](https://learn.microsoft.com/azure/azure-maps/how-to-dev-guide-js-sdk).",
      "replacement": "Azure Maps Web SDK Map Control version 3 and Azure Maps JavaScript REST SDK",
      "affected_versions": [
        "2.0.x"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=azure-maps-web-sdk-map-control-version-20x-and-azure-maps-service-module-will-be-retired-on-30-september-2026",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-maps/release-notes-map-control#v3-latest",
        "https://learn.microsoft.com/azure/azure-maps/how-to-dev-guide-js-sdk",
        "https://aka.ms/azuremapswebsdkmigrationguide",
        "https://aka.ms/azuremapsservicemodulemigrationguide"
      ],
      "vendor_ref": "azure-maps-web-sdk-map-control-version-20x-and-azure-maps-service-module-will-be-retired-on-30-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-maps-web-sdk-map-control-2-0-x-and-service-module-retirement"
    },
    {
      "slug": "azure-monitor-scom-managed-instance-retirement",
      "title": "Azure Monitor SCOM Managed Instance retirement",
      "summary": "Retirement date for Azure Monitor SCOM Managed Instance: 30 Sep 2026. After that date, customers can no longer access the service.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-10-03",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Customers that run Azure Monitor SCOM Managed Instance (SCOM MI) are affected. After the retirement date, customers are no longer able to access the service. Both transition paths in the source require deleting the existing SCOM MI instance.",
      "migration_path": "1. To monitor on-premises workloads, transition to [Operations Manager](https://learn.microsoft.com/system-center/scom/manage-operations-guide-overview?view=sc-om-2025) on-premises: delete the existing SCOM MI instance and re-deploy SCOM on-premises (hosted in on-premises datacenters or in Azure) using [these steps](https://learn.microsoft.com/system-center/scom/get-started?view=sc-om-2025).\n2. To monitor Azure-hosted or Azure Arc-enabled workloads, transition to [Azure Monitor](https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/overview) and delete the existing SCOM MI instance.\n3. For the Azure Monitor path, obtain a list of the rules and monitors in the SCOM MI Management Packs in use.\n4. Determine the equivalent of those rules and monitors in Azure Monitor [Data Collection Rules](https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/data-collection-rule-overview) (DCR): create a DCR for each SCOM MP monitor in use and integrate it with Azure Monitor VM Insights Alerts.\n5. See the Microsoft [retirement documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/scom-manage-instance/overview) for more details.",
      "replacement": "Operations Manager on-premises or Azure Monitor",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=501673",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-monitor/scom-manage-instance/overview",
        "https://learn.microsoft.com/system-center/scom/manage-operations-guide-overview?view=sc-om-2025",
        "https://learn.microsoft.com/system-center/scom/get-started?view=sc-om-2025",
        "https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/overview",
        "https://learn.microsoft.com/en-us/azure/azure-monitor/data-collection/data-collection-rule-overview"
      ],
      "vendor_ref": "501673",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-scom-managed-instance-retirement"
    },
    {
      "slug": "azure-monitor-container-insights-legacy-authentication-retirement",
      "title": "Azure Monitor: Container Insights legacy authentication retirement",
      "summary": "Retirement date for legacy authentication in Azure Monitor Container Insights: 30 Sep 2026. Clusters that use it must move to Managed Identity authentication.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-10-07",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Legacy authentication in Container Insights is retired on 30 Sep 2026. Clusters that still use legacy authentication are affected and must be migrated to Managed Identity authentication. Syslog collection and High Scale mode are available only with Managed Identity.",
      "migration_path": "1. Migrate each cluster to Managed Identity authentication before 30 Sep 2026.\n2. Use the single-click migration in the Azure portal, or the command line options and bulk migration script in the Azure Monitor documentation.\n3. Follow the [migration guidance](https://aka.ms/CILegacyAuthMigration).",
      "replacement": "Managed Identity authentication",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=500853",
      "extra_source_urls": [
        "https://aka.ms/CILegacyAuthMigration"
      ],
      "vendor_ref": "500853",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-container-insights-legacy-authentication-retirement"
    },
    {
      "slug": "azure-monitor-containerlog-table-retirement",
      "title": "Azure Monitor: Container insights ContainerLog table retirement",
      "summary": "Retirement date for the ContainerLog table in Azure Monitor container insights: 30 Sep 2026. Workloads that use it need to transition to the ContainerLogV2 table.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "The ContainerLog table in Azure Monitor container insights is retired on 30 Sep 2026. Alerts and dashboards that rely on ContainerLog need to be transitioned to ContainerLogV2 to keep working as expected. ContainerLogV2 offers all the functionality of ContainerLog, plus compatibility with the basic logs pricing tier, additional pod and container metadata, and support for multiline log entries.",
      "migration_path": "[Transition](https://aka.ms/containerlogmigration) to the ContainerLogV2 table by 30 Sep 2026 so that alerts and dashboards continue to work as expected.",
      "replacement": "ContainerLogV2 table",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=transition-to-the-containerlogv2-table-by-30-september-2026",
      "extra_source_urls": [
        "https://aka.ms/containerlogmigration"
      ],
      "vendor_ref": "transition-to-the-containerlogv2-table-by-30-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-containerlog-table-retirement"
    },
    {
      "slug": "azure-monitor-getalertsummary-api-retirement",
      "title": "Azure Monitor: GetAlertSummary API retirement",
      "summary": "Retirement date for the GetAlertSummary API in Azure Monitor: 30 Sep 2026. Callers need to move to an ARG query to get the alert summary.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "After the retirement date, the GetAlertSummary API in Azure Monitor is retired. Systems that call the GetAlertSummary API are affected and face a breaking change unless they move to an ARG query. Microsoft states that the ARG query provides all of the functionality of the GetAlertSummary API plus new ones, including the ability to add new fields to the query that returns the alert summary and to be more flexible in that query.",
      "migration_path": "1. Follow the Microsoft [migration path](https://aka.ms/MigrationPlanGetAlertSummary) to start using an ARG query before the retirement date.\n2. For questions, use [Microsoft Q&A](https://aka.ms/RetiermentQandA). With a support plan, create a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) under the service type Alerts and Action Groups.",
      "replacement": "ARG query",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=action-required-migrate-to-using-arg-query-for-get-alert-summary-in-azure-monitor",
      "extra_source_urls": [
        "https://aka.ms/MigrationPlanGetAlertSummary"
      ],
      "vendor_ref": "action-required-migrate-to-using-arg-query-for-get-alert-summary-in-azure-monitor",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-getalertsummary-api-retirement"
    },
    {
      "slug": "azure-event-hubs-older-control-plane-api-versions-retirement",
      "title": "Azure Service Bus, Event Hubs and Relay: older control plane APIs retirement",
      "summary": "Retirement date for Azure Resource Manager control plane API versions 2014-09-01, 2015-08-01 and 2016-07-01 for Azure Service Bus, Event Hubs and Relay: 30 Sep 2026. The replacement is control plane API version 2021-11-01.",
      "cloud": "azure",
      "service": "Azure Event Hubs",
      "service_slug": "event-hubs",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-10-06",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Azure Resource Manager control plane APIs 2014-09-01, 2015-08-01 and 2016-07-01 are retired on 30 Sep 2026. This affects customers who use these older control plane APIs to interact with Azure Service Bus, Azure Event Hubs or Azure Relay resources. Microsoft states that migrating to the latest control plane API version by that date avoids potential service outages in these services.",
      "migration_path": "[Migrate](https://aka.ms/MessagingAPIDeprecations) to Resource Manager control plane API 2021-11-01 by 30 Sep 2026.",
      "replacement": "Azure Resource Manager control plane API version 2021-11-01",
      "affected_versions": [
        "2014-09-01",
        "2015-08-01",
        "2016-07-01"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=migrate-to-azure-resource-manager-control-plane-api-version-20211101-by-30-september-2026",
      "extra_source_urls": [
        "https://aka.ms/MessagingAPIDeprecations"
      ],
      "vendor_ref": "migrate-to-azure-resource-manager-control-plane-api-version-20211101-by-30-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-event-hubs-older-control-plane-api-versions-retirement"
    },
    {
      "slug": "azure-service-bus-older-sdk-libraries-end-of-support",
      "title": "Azure Service Bus: older SDK libraries end of support and SBMP retirement",
      "summary": "End of support date for the Azure Service Bus SDK libraries WindowsAzure.ServiceBus, Microsoft.Azure.ServiceBus and com.microsoft.azure.servicebus: 30 Sep 2026. The SBMP protocol can no longer be used after that date. WindowsAzure.ServiceBus stays supported with Azure WCF Relay.",
      "cloud": "azure",
      "service": "Azure Service Bus",
      "service_slug": "service-bus",
      "category": "api_sdk",
      "type": "end_of_support",
      "announced_date": "2023-10-06",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "The Azure Service Bus SDK libraries WindowsAzure.ServiceBus, Microsoft.Azure.ServiceBus and com.microsoft.azure.servicebus are retired on the retirement date. Microsoft.Azure.ServiceBus and com.microsoft.azure.servicebus can still be used after that date but no longer receive support or updates. For WindowsAzure.ServiceBus, support for the SBMP protocol also ends and the protocol can no longer be used after the date, while the library keeps working with the AMQP protocol without support or updates. Applications that still use WindowsAzure.ServiceBus with Azure Event Hubs also need to migrate, while support for this library with Azure WCF Relay continues until further notice.",
      "migration_path": "1. .NET applications on WindowsAzure.ServiceBus or Microsoft.Azure.ServiceBus: move to [Azure.Messaging.ServiceBus](https://www.nuget.org/packages/Azure.Messaging.ServiceBus).\n2. Java applications on com.microsoft.azure.servicebus: move to [azure-messaging-servicebus](https://central.sonatype.com/artifact/com.azure/azure-messaging-servicebus).\n3. Applications that use WindowsAzure.ServiceBus with Event Hubs: move to [Azure.Messaging.EventHubs](https://www.nuget.org/packages/Azure.Messaging.EventHubs/).\n4. Follow the migration guide for your library: [WindowsAzure.ServiceBus](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/MigrationGuide_WindowsAzureServiceBus.md), [Microsoft.Azure.ServiceBus](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/MigrationGuide.md) or [com.microsoft.azure.servicebus](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/servicebus/azure-messaging-servicebus/migration-guide.md).\n5. If you keep using Microsoft.Azure.ServiceBus or com.microsoft.azure.servicebus, the source code is on GitHub and you can apply your own fixes.",
      "replacement": "Azure.Messaging.ServiceBus (.NET), azure-messaging-servicebus (Java), Azure.Messaging.EventHubs (.NET)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=retirement-notice-update-your-azure-service-bus-sdk-libraries-by-30-september-2026",
      "extra_source_urls": [
        "https://azure.microsoft.com/blog/previewing-azure-sdks-following-new-azure-sdk-api-standards/",
        "https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/MigrationGuide_WindowsAzureServiceBus.md",
        "https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/servicebus/Azure.Messaging.ServiceBus/MigrationGuide.md",
        "https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/servicebus/azure-messaging-servicebus/migration-guide.md",
        "https://github.com/Azure/azure-service-bus"
      ],
      "vendor_ref": "retirement-notice-update-your-azure-service-bus-sdk-libraries-by-30-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-service-bus-older-sdk-libraries-end-of-support"
    },
    {
      "slug": "azure-vpn-gateway-vpngw1-5-non-az-skus-retirement",
      "title": "Azure VPN Gateway: VpnGw1-5 non-AZ SKUs retirement",
      "summary": "Retirement date for the VpnGw1-5 non-AZ SKUs of Azure VPN Gateway: 30 Sep 2026. Microsoft migrates gateways on these SKUs to the VpnGw1-5 AZ SKUs automatically.",
      "cloud": "azure",
      "service": "Azure VPN Gateway",
      "service_slug": "vpn-gateway",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-09-26",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "On 30 Sep 2026, the VpnGw1-5 (Non-AZ SKUs) are retired. Gateways on VpnGw1-5 Non-Availability Zones SKUs are affected. Creating new gateways on these SKUs has not been possible since Jan 1, 2025. Microsoft states that all gateways are automatically migrated to AZ SKUs before the retirement date.",
      "migration_path": "Microsoft migrates all gateways on VpnGw1-5 (Non-AZ SKUs) to VpnGw1-5 (AZ SKUs), in a window the source gives as April 2025 to October 2026. Microsoft states that reduced pricing for AZ SKUs took effect on Jan 1, 2025. Refer to the [pricing page](https://azure.microsoft.com/pricing/details/vpn-gateway/) to select the appropriate SKU for your organization.",
      "replacement": "VpnGw1-5 AZ SKUs",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026",
      "extra_source_urls": [
        "https://azure.microsoft.com/pricing/details/vpn-gateway/"
      ],
      "vendor_ref": "vpngw1-5-non-az-skus-will-be-retired-on-30-september-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-vpn-gateway-vpngw1-5-non-az-skus-retirement"
    },
    {
      "slug": "azure-virtual-desktop-classic-retirement",
      "title": "Azure Virtual Desktop (classic) retirement",
      "summary": "Retirement date for Azure Virtual Desktop (classic): 30 Sep 2026. Azure Virtual Desktop fully replaces it.",
      "cloud": "azure",
      "service": "Azure Virtual Desktop",
      "service_slug": "virtual-desktop",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "Existing Azure Virtual Desktop (classic) resources can be managed, migrated, and supported through 30 Sep 2026. New Azure Virtual Desktop (classic) tenants cannot be created from 30 September 2023. Customers with more than 500 application groups, or who manage multi-tenant (B2B) environments, can request an exception to the block on new tenant creation through a support request.",
      "migration_path": "Migrate to Azure Virtual Desktop using one of the two documents Microsoft links:\n\n1. [Migrate manually from Azure Virtual Desktop (classic)](https://aka.ms/avd-classic-migration).\n2. [Migrate automatically from Azure Virtual Desktop (classic)](https://aka.ms/avd-classic-migration/automatic).",
      "replacement": "Azure Virtual Desktop",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-virtual-desktop-classic-will-be-retired-on-30-september-2026-please-transition-to-azure-virtual-desktop",
      "extra_source_urls": [
        "https://aka.ms/avd-classic-migration",
        "https://aka.ms/avd-classic-migration/automatic"
      ],
      "vendor_ref": "azure-virtual-desktop-classic-will-be-retired-on-30-september-2026-please-transition-to-azure-virtual-desktop",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-desktop-classic-retirement"
    },
    {
      "slug": "azure-virtual-machines-nvv3-series-retirement",
      "title": "Azure Virtual Machines: NVv3-series retirement",
      "summary": "Retirement date for the NVv3-series Azure VMs: 30 Sep 2026. Remaining NVv3-series VMs are set to a deallocated state and stop working. The Azure UAE North region has an extension date of January 31, 2027.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-09-30",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "The retirement covers the Standard_NV12s_v3, Standard_NV12hs_v3, Standard_NV24s_v3, Standard_NV24ms_v3, Standard_NV32ms_v3, and Standard_NV48s_v3 virtual machines. Outside the Azure UAE North exception, remaining NVv3-series VMs are set to a deallocated state, stop working, no longer incur billing charges, and are no longer under SLA or covered by included support. Exception: for NVv3-series VMs already in use in the Azure UAE North region, the extension date is January 31, 2027, and customers in that region must migrate off the NVv3-series VMs by that date. 1-year and 3-year Reserved Instance purchases for the NVv3-series ended on November 2, 2025.",
      "migration_path": "Customers in the Azure UAE North region must migrate off the NVv3-series VMs by January 31, 2027. The Microsoft update lists no migration steps in its own text and links the NVv3-series retirement page: [Learn more](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nvv3-series-retirement).",
      "replacement": null,
      "affected_versions": [
        "NVv3"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=573414",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/nvv3-series-retirement",
        "https://azure.microsoft.com/updates?id=500573"
      ],
      "vendor_ref": "573414",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-nvv3-series-retirement"
    },
    {
      "slug": "azure-virtual-machines-nvv4-series-retirement",
      "title": "Azure Virtual Machines: NVv4-series retirement",
      "summary": "Retirement date for the NVv4-series Azure VMs: 30 Sep 2026. Remaining NVv4-series VMs are set to a deallocated state, stop working, and are no longer under SLA or covered by included support.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-09-30",
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "The retirement covers the Standard_NV4as_v4, Standard_NV4ahs_v4, Standard_NV8as_v4, Standard_NV8ahs_v4, Standard_NV16as_v4, Standard_NV16ahs_v4, Standard_NV32as_v4, and Standard_NV32ahs_v4 virtual machines. Remaining NVv4-series VMs are set to a deallocated state, stop working, no longer incur billing charges, and are no longer under SLA or covered by included support. 1-year and 3-year Reserved Instance purchases for the NVv4-series ended on November 2, 2025. All Compute Pre-Purchase sales for the NVv4-series ended on June 2, 2026.",
      "migration_path": "The Microsoft update lists no migration steps in its own text. It links the NVv4-series retirement page: [Learn more](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/lifecycle/retirement/nvv4-retirement).",
      "replacement": null,
      "affected_versions": [
        "NVv4"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=573415",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/lifecycle/retirement/nvv4-retirement",
        "https://azure.microsoft.com/updates?id=500578"
      ],
      "vendor_ref": "573415",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-nvv4-series-retirement"
    },
    {
      "slug": "gcp-cloud-run-ruby-3-2-retirement",
      "title": "Cloud Run: Ruby 3.2 decommission",
      "summary": "Decommission date for Ruby 3.2 on Cloud Run: 30 Sep 2026. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2026-09-30",
      "effective_precision": "day",
      "impact": "The decommission date of Ruby 3.2 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-ruby-3-2-retirement"
    },
    {
      "slug": "azure-aks-enabled-by-azure-arc-windows-server-2022-retirement",
      "title": "AKS enabled by Azure Arc: Windows Server 2022 retirement",
      "summary": "Retirement date for Windows Server 2022 on Azure Kubernetes Service enabled by Azure Arc: Oct 2026.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service enabled by Azure Arc",
      "service_slug": "aks-enabled-by-azure-arc",
      "category": "os_image",
      "type": "retirement",
      "announced_date": "2025-11-14",
      "effective_date": "2026-10-01",
      "effective_precision": "month",
      "impact": "Microsoft announced the retirement of Windows Server 2022 on Azure Kubernetes Service enabled by Azure Arc. The announcement gives no further detail on which resources or configurations are affected.",
      "migration_path": "Microsoft has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [
        "2022"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=499906",
      "extra_source_urls": [],
      "vendor_ref": "499906",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-enabled-by-azure-arc-windows-server-2022-retirement"
    },
    {
      "slug": "azure-ai-services-anomaly-detector-retirement",
      "title": "Azure AI Services Anomaly Detector retirement",
      "summary": "Retirement date for AI Services Anomaly Detector: 1 Oct 2026. After that date, the service can no longer be used with applications.",
      "cloud": "azure",
      "service": "Azure AI Services Anomaly Detector",
      "service_slug": "ai-services-anomaly-detector",
      "category": "service",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-10-01",
      "effective_precision": "day",
      "impact": "After 1 Oct 2026, AI Services Anomaly Detector can no longer be used with applications. Existing AI Services Anomaly Detector resources remain usable until the retirement date. Customers using AI Services Anomaly Detector are affected.",
      "migration_path": "Microsoft has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=ai-services-anomaly-detector-will-be-retired-on-1-october-2026",
      "extra_source_urls": [
        "https://aka.ms/AnomalyDetectorQnA"
      ],
      "vendor_ref": "ai-services-anomaly-detector-will-be-retired-on-1-october-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-services-anomaly-detector-retirement"
    },
    {
      "slug": "azure-ai-translator-s2-s4-pricing-instances-retirement",
      "title": "Azure AI Translator: S2-S4 pricing instances retirement",
      "summary": "Deadline to migrate Azure AI Translator Volume Discount S2-S4 pricing instances to Commitment Tiers: 1 Oct 2026. Microsoft consolidated the paid pricing instances into Commitment Tiers.",
      "cloud": "azure",
      "service": "Azure AI Translator",
      "service_slug": "ai-translator",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2023-09-29",
      "effective_date": "2026-10-01",
      "effective_precision": "day",
      "impact": "Azure AI Translator resources on the Volume Discount S2-S4 pricing instances are affected. Microsoft consolidated the paid pricing instances into Commitment Tiers, and the deadline to migrate is 1 Oct 2026. Creating new S2-S4 instances, or switching from S1 to S2-S4, is not allowed after 14 September 2026.",
      "migration_path": "Move the resource to the Commitment Tier pricing instance before the retirement date. Microsoft links a [guide on how to migrate](https://aka.ms/CSCommit) from S2-S4, and describes [Commitment Tiers](https://learn.microsoft.com/azure/ai-services/commitment-tier) in its documentation.",
      "replacement": "Commitment Tiers",
      "affected_versions": [
        "S2-S4"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=azure-ai-translator-s2s4-billing-instances-will-be-retired-on-1-october-2026-transition-to-commitment-tiers-for-discounted-pr",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/ai-services/commitment-tier",
        "https://aka.ms/CSCommit"
      ],
      "vendor_ref": "azure-ai-translator-s2s4-billing-instances-will-be-retired-on-1-october-2026-transition-to-commitment-tiers-for-discounted-pr",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-translator-s2-s4-pricing-instances-retirement"
    },
    {
      "slug": "azure-app-service-python-3-10-end-of-support",
      "title": "Azure App Service: Python 3.10 end of support",
      "summary": "End of extended support for Python 3.10 on Azure App Service: 1 Oct 2026. Apps keep running after that date but stop receiving security updates and customer service for Python 3.10.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2025-11-14",
      "effective_date": "2026-10-01",
      "effective_precision": "day",
      "impact": "On 1 Oct 2026, extended support for Python 3.10 on Azure App Service ends. Apps hosted on App Service that use Python 3.10 continue to run. After that date, security updates are no longer available and Microsoft no longer provides customer service for Python 3.10.",
      "migration_path": "[Follow the steps to upgrade your app](https://aka.ms/pythonsupport) to Python 3.11 before the end of support date. Microsoft describes its policy in [App Service language support](https://learn.microsoft.com/azure/app-service/language-support-policy).",
      "replacement": "Python 3.11",
      "affected_versions": [
        "3.10"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=509686",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/app-service/language-support-policy",
        "https://aka.ms/pythonsupport",
        "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy"
      ],
      "vendor_ref": "509686",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-python-3-10-end-of-support"
    },
    {
      "slug": "azure-databricks-standard-tier-retirement",
      "title": "Azure Databricks: Standard tier retirement",
      "summary": "Retirement of the Azure Databricks Standard tier: Oct 2026. From that point, all Standard tier workspaces are automatically upgraded to the Premium tier.",
      "cloud": "azure",
      "service": "Azure Databricks",
      "service_slug": "databricks",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-09-16",
      "effective_date": "2026-10-01",
      "effective_precision": "month",
      "impact": "From Oct 2026, all Azure Databricks Standard tier workspaces are automatically upgraded to the Premium tier. Azure subscriptions no longer support the creation of Standard tier workspaces after April 1st, 2026.",
      "migration_path": "Microsoft has not published migration steps. See the source for details.",
      "replacement": "Azure Databricks Premium tier",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=502623",
      "extra_source_urls": [
        "https://azure.microsoft.com/en-us/pricing/details/databricks/"
      ],
      "vendor_ref": "502623",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-databricks-standard-tier-retirement"
    },
    {
      "slug": "azure-functions-python-3-10-end-of-support",
      "title": "Azure Functions: Python 3.10 end of support",
      "summary": "End of support date for Python 3.10 on Azure Functions: 1 Oct 2026. Apps keep running after that date but stop receiving security updates, performance optimizations and customer service.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-01-28",
      "effective_date": "2026-10-01",
      "effective_precision": "day",
      "impact": "Support for Python 3.10 in Azure Functions ends on 1 Oct 2026, in alignment with the end of community support. Apps hosted on Functions continue to run, but security updates and performance optimizations are no longer available. Microsoft no longer provides customer service for Python 3.10.",
      "migration_path": "By the end of support date, upgrade function apps to Python 3.13 following the steps in [Update the stack configuration](https://learn.microsoft.com/azure/azure-functions/update-language-versions?tabs=azure-portal%2Clinux&pivots=programming-language-python#update-the-stack-configuration). The support policy is described in [Azure Functions stack version support](https://learn.microsoft.com/azure/azure-functions/language-support-policy).",
      "replacement": "Python 3.13",
      "affected_versions": [
        "3.10"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=545771",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-functions/language-support-policy",
        "https://learn.microsoft.com/azure/azure-functions/update-language-versions?tabs=azure-portal%2Clinux&pivots=programming-language-python#update-the-stack-configuration"
      ],
      "vendor_ref": "545771",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-python-3-10-end-of-support"
    },
    {
      "slug": "azure-sql-database-fsv2-series-hardware-retirement",
      "title": "Azure SQL Database: FSV2-series hardware retirement",
      "summary": "Retirement date for the FSV2-series hardware option in Azure SQL Database: 1 Oct 2026. After that date, databases still on FSV2-series hardware are no longer supported and are migrated to the General-purpose tier.",
      "cloud": "azure",
      "service": "Azure SQL Database",
      "service_slug": "sql-database",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-03-28",
      "effective_date": "2026-10-01",
      "effective_precision": "day",
      "impact": "After the retirement date, Azure SQL databases running on FSV2-series hardware are no longer supported. Remaining databases on FSV2-series hardware are migrated to the General-purpose tier with similar configurations. Since October 1, 2025, customers who had not already deployed Azure SQL Database on FSV2-series cannot create new databases on it, while existing FSV2-series customers could continue to use their databases until the retirement date. Microsoft gives limited regional availability of this hardware as the reason.",
      "migration_path": "1. Move databases off FSV2-series hardware to another option within Azure SQL Database before the retirement date.\n2. Microsoft recommends the Hyperscale premium-series or General-purpose standard-series (Gen5) service tier to maintain comparable performance levels.\n3. For more information on SQL Database service tiers, see the [Azure documentation](https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tiers-sql-database-vcore?view=azuresql#service-tiers). For the retirement itself, see the [FAQ for FSV2 offer retirement](https://aka.ms/FSV2-FAQ).",
      "replacement": "Hyperscale premium-series or General-purpose standard-series (Gen5)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=485030",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tiers-sql-database-vcore?view=azuresql#service-tiers",
        "https://aka.ms/FSV2-FAQ"
      ],
      "vendor_ref": "485030",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sql-database-fsv2-series-hardware-retirement"
    },
    {
      "slug": "aws-terraform-aws-6-68-0-breaking-change",
      "title": "Terraform AWS provider 6.68.0: breaking changes",
      "summary": "Release date for Terraform AWS provider 6.68.0: 7 Oct 2026. Breaking changes listed in the release notes: 2.",
      "cloud": "aws",
      "service": "Terraform AWS provider",
      "service_slug": "terraform-aws",
      "category": "iac_provider",
      "type": "breaking_change",
      "announced_date": "2026-10-07",
      "effective_date": "2026-10-07",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- `aws_docdb_cluster`: availability_zones now validates that at most 3 items are provided at plan time. This is acceptable in a minor version because AWS would always reject requests with more than 3 availability zones at apply time.\n- `aws_rds_cluster`: availability_zones now validates that at most 3 items are provided at plan time. This is acceptable in a minor version because AWS would always reject requests with more than 3 availability zones at apply time.",
      "migration_path": "1. Give the provider a version constraint in the `required_providers` block. HashiCorp recommends a version constraint for every provider a module depends on.\n2. In a root module, also specify the maximum provider version, to avoid accidental upgrades to incompatible new versions. The `~>` operator is a shorthand that allows the rightmost component of a version to increment. Do not use `~>` or other maximum-version constraints in modules you intend to reuse across many configurations. Specify a minimum version there and let the root module manage the maximum version.\n3. Commit the dependency lock file to version control with the configuration, so that Terraform always installs the same provider versions.\n4. To adopt 6.68.0, change the version in the `required_providers` block and re-run `terraform init`. HashiCorp states that this upgrades the provider version in the lock file. Without a change, Terraform re-selects the version recorded in the lock file, even if a newer version has become available. With the `-upgrade` option, `terraform init` disregards the recorded selection and selects the newest available version matching the version constraint. The [release notes](https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.68.0) list each breaking change.\n5. Review the changes Terraform made to the lock file in version control. If they are changes you made intentionally, send them through the usual code review process.",
      "replacement": null,
      "affected_versions": [
        "6.68.0"
      ],
      "source_url": "https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.68.0",
      "extra_source_urls": [],
      "vendor_ref": "v6.68.0",
      "last_checked_at": "2026-11-12T09:55:27.655Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-terraform-aws-6-68-0-breaking-change"
    },
    {
      "slug": "azure-avm-network-networksecuritygroup-0-6-0-breaking-change",
      "title": "avm-res-network-networksecuritygroup 0.6.0: breaking changes",
      "summary": "Release date of version 0.6.0 of the Azure Verified Module avm-res-network-networksecuritygroup: 7 Oct 2026. Breaking changes listed in the release notes: 6.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-10-07",
      "effective_date": "2026-10-07",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- This release moves the module from the AzureRM provider to AzAPI. Existing deployments are adopted in place through moved blocks, and nothing is destroyed or recreated. Read the upgrade steps below before you upgrade.\n- Requires Terraform 1.11 or later (was 1.9).\n- Replaces the resource_group_name input with parent_id, the resource ID of the resource group.\n- Manages every resource with AzAPI. The module no longer requires the AzureRM provider, and it now requires the hashicorp/time provider (~> 0.13).\n- The security_rules output no longer includes timeouts.\n- Role names are looked up in the resource group, so a custom role that can only be assigned on the network security group itself must be given by ID.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-network-networksecuritygroup/releases/tag/v0.6.0) for 0.6.0: 6. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-network-networksecuritygroup from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-network-networksecuritygroup). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.6.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.6.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.6.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-network-networksecuritygroup/releases/tag/v0.6.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-network-networksecuritygroup"
      ],
      "vendor_ref": "v0.6.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-network-networksecuritygroup-0-6-0-breaking-change"
    },
    {
      "slug": "azure-avm-web-site-0-24-0-breaking-change",
      "title": "avm-res-web-site 0.24.0: breaking changes",
      "summary": "Release date of version 0.24.0 of the Azure Verified Module avm-res-web-site: 12 Oct 2026. Breaking changes listed in the release notes: 1.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-10-12",
      "effective_date": "2026-10-12",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Breaking, only if you call modules/site_config_helpers directly: it now requires is_function_app (bool). Pass true for Function Apps and false otherwise. Callers of the root module are unaffected.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-web-site/releases/tag/v0.24.0) for 0.24.0: 1. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-web-site from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-web-site). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.24.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.24.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.24.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-web-site/releases/tag/v0.24.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-web-site"
      ],
      "vendor_ref": "v0.24.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-web-site-0-24-0-breaking-change"
    },
    {
      "slug": "azure-storage-accounts-gpv1-and-legacy-blob-accounts-retirement",
      "title": "Azure Storage Accounts: GPv1 and legacy blob storage account retirement",
      "summary": "General purpose v1 (GPv1) storage accounts, legacy blob storage accounts and Files accounts hosted on GPv1 are retired on 13 Oct 2026. After that date, remaining GPv1 accounts are migrated to GPv2 automatically.",
      "cloud": "azure",
      "service": "Azure Storage Accounts",
      "service_slug": "storage-accounts",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-06-11",
      "effective_date": "2026-10-13",
      "effective_precision": "day",
      "impact": "All General purpose v1 (GPv1) storage accounts are retired, in all redundancy options, together with legacy blob storage accounts and Files storage accounts hosted on GPv1. Creation of new accounts is blocked from September 1st, 2026. After the retirement date, all existing GPv1 accounts are automatically migrated to a GPv2 account, which may result in higher billing costs. Microsoft treats a decision not to migrate an existing GPv1 account as consent to migrate the account on the customer's behalf.",
      "migration_path": "1. Choose a target account type for each affected account: General Purpose v2 (GPv2), or a specialized alternative such as BlockBlobStorage or FileStorage, depending on workload requirements.\n2. Upgrade the account with the [storage account upgrade guide](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-upgrade).\n3. For GPv1 accounts, read the [GPv1 storage account retirement overview](https://learn.microsoft.com/en-us/azure/storage/common/general-purpose-version-1-account-migration-overview).\n4. For legacy blob storage accounts, read the [Legacy Blob Storage account retirement overview](https://learn.microsoft.com/en-us/azure/storage/common/legacy-blob-storage-account-migration-overview).",
      "replacement": "General Purpose v2 (GPv2) storage accounts",
      "affected_versions": [
        "GPv1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=564441",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/storage/common/storage-account-upgrade",
        "https://learn.microsoft.com/en-us/azure/storage/common/general-purpose-version-1-account-migration-overview",
        "https://learn.microsoft.com/en-us/azure/storage/common/legacy-blob-storage-account-migration-overview",
        "https://azure.microsoft.com/updates?id=496964"
      ],
      "vendor_ref": "564441",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-storage-accounts-gpv1-and-legacy-blob-accounts-retirement"
    },
    {
      "slug": "azure-sentinel-sap-connector-container-images-retirement",
      "title": "Microsoft Sentinel: containerized SAP data connector images removal",
      "summary": "Removal date for the container images of the containerized SAP data connector: 14 Oct 2026. The connector itself retired on September 14, 2026 and is unsupported and unmaintained.",
      "cloud": "azure",
      "service": "Microsoft Sentinel",
      "service_slug": "sentinel",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2026-09-16",
      "effective_date": "2026-10-14",
      "effective_precision": "day",
      "impact": "From 14 Oct 2026, the container images are removed, which prevents new pulls, installation, redeployment, scaling, replacement, and disaster recovery. The containerized SAP data connector retired on September 14, 2026 and is unsupported and unmaintained. Existing TLS-compliant agents may continue sending logs through the retired HTTP Data Collector API.",
      "migration_path": "Migrate to the supported SAP agentless connector. [Learn more](https://learn.microsoft.com/azure/sentinel/sap/sap-agent-migrate).",
      "replacement": "SAP agentless connector",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=571342",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/sentinel/sap/sap-agent-migrate"
      ],
      "vendor_ref": "571342",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sentinel-sap-connector-container-images-retirement"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-gemini-2-5-flash-retirement",
      "title": "Gemini Enterprise Agent Platform: gemini-2.5-flash retirement",
      "summary": "Retirement date for gemini-2.5-flash on Gemini Enterprise Agent Platform: 20 Oct 2026. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2026-10-20",
      "effective_precision": "day",
      "impact": "Google lists gemini-2.5-flash with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": "gemini-3.8-flash or gemini-3.5-flash-lite",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-gemini-2-5-flash-retirement"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-gemini-2-5-flash-lite-retirement",
      "title": "Gemini Enterprise Agent Platform: gemini-2.5-flash-lite retirement",
      "summary": "Retirement date for gemini-2.5-flash-lite on Gemini Enterprise Agent Platform: 20 Oct 2026. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2026-10-20",
      "effective_precision": "day",
      "impact": "Google lists gemini-2.5-flash-lite with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": "gemini-3.8-flash or gemini-3.5-flash-lite or Gemma 4",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-gemini-2-5-flash-lite-retirement"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-gemini-2-5-pro-retirement",
      "title": "Gemini Enterprise Agent Platform: gemini-2.5-pro retirement",
      "summary": "Retirement date for gemini-2.5-pro on Gemini Enterprise Agent Platform: 20 Oct 2026. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2026-10-20",
      "effective_precision": "day",
      "impact": "Google lists gemini-2.5-pro with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": "gemini-3.8-flash or gemini-3.5-flash",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-gemini-2-5-pro-retirement"
    },
    {
      "slug": "aws-terraform-aws-6-70-0-breaking-change",
      "title": "Terraform AWS provider 6.70.0: breaking changes",
      "summary": "Release date for Terraform AWS provider 6.70.0: 21 Oct 2026. Breaking changes listed in the release notes: 1.",
      "cloud": "aws",
      "service": "Terraform AWS provider",
      "service_slug": "terraform-aws",
      "category": "iac_provider",
      "type": "breaking_change",
      "announced_date": "2026-10-21",
      "effective_date": "2026-10-21",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- `aws_route53domains_delegation_signer_record`: Change the format of the import ID from domain_name,dnssec_key_id to domain_name,flags,algorithm,public_key. This is acceptable in a minor version because AWS no longer return DNSKEY flags and delegation signer records can no longer reliably be found by domain name and key ID",
      "migration_path": "1. Give the provider a version constraint in the `required_providers` block. HashiCorp recommends a version constraint for every provider a module depends on.\n2. In a root module, also specify the maximum provider version, to avoid accidental upgrades to incompatible new versions. The `~>` operator is a shorthand that allows the rightmost component of a version to increment. Do not use `~>` or other maximum-version constraints in modules you intend to reuse across many configurations. Specify a minimum version there and let the root module manage the maximum version.\n3. Commit the dependency lock file to version control with the configuration, so that Terraform always installs the same provider versions.\n4. To adopt 6.70.0, change the version in the `required_providers` block and re-run `terraform init`. HashiCorp states that this upgrades the provider version in the lock file. Without a change, Terraform re-selects the version recorded in the lock file, even if a newer version has become available. With the `-upgrade` option, `terraform init` disregards the recorded selection and selects the newest available version matching the version constraint. The [release notes](https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.70.0) list each breaking change.\n5. Review the changes Terraform made to the lock file in version control. If they are changes you made intentionally, send them through the usual code review process.",
      "replacement": null,
      "affected_versions": [
        "6.70.0"
      ],
      "source_url": "https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.70.0",
      "extra_source_urls": [],
      "vendor_ref": "v6.70.0",
      "last_checked_at": "2026-11-12T09:55:27.655Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-terraform-aws-6-70-0-breaking-change"
    },
    {
      "slug": "multi-terraform-1-15-end-of-support",
      "title": "Terraform CLI: Terraform 1.15 end of support",
      "summary": "End of support date for Terraform 1.15: 21 Oct 2026. Under the HashiCorp policy as summarized by endoflife.date, fixes are provided for up to two releases from the most current major release, where a major release is a change in the first or second digit of X.Y.Z.",
      "cloud": "multi",
      "service": "Terraform",
      "service_slug": "terraform",
      "category": "iac_language",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-21",
      "effective_precision": "day",
      "impact": "endoflife.date summarizes the HashiCorp support period policy as follows. Generally Available (GA) releases of active products are supported for up to two (2) years. Eligible code fixes and hot fixes are provided through a new minor release (Z) on top of the latest major release branch, for up to two (2) releases from the most current major release. A major release is identified by a change in the first (X) or second (Y) digit of version X.Y.Z.",
      "migration_path": "1. Move to a Terraform release that is still supported.\n2. The [Terraform upgrade guides](https://developer.hashicorp.com/terraform/language/upgrade-guides) page shows the guide for the latest version. Use the version selector to view the upgrade guides for older Terraform versions.",
      "replacement": null,
      "affected_versions": [
        "1.15"
      ],
      "source_url": "https://endoflife.date/terraform",
      "extra_source_urls": [
        "https://support.hashicorp.com/hc/en-us/articles/360021185113-Support-Period-and-End-of-Life-EOL-Policy"
      ],
      "vendor_ref": "terraform@1.15",
      "last_checked_at": "2026-11-12T09:55:38.105Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-terraform-1-15-end-of-support"
    },
    {
      "slug": "gcp-gke-kubernetes-1-31-extended-support-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.31 end of extended support",
      "summary": "End of extended support date for GKE Kubernetes 1.31: 22 Oct 2026. From that date the minor version receives no security patches, and GKE upgrades Extended channel clusters still running it to the next minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-22",
      "effective_precision": "day",
      "impact": "At the end of extended support, GKE does not provide any patches for security fixes, and the minor version is considered unsupported. GKE upgrades clusters still running it to the next minor version.\n\n- The upgrade happens regardless of the cluster's use of deprecated features or APIs.\n- Maintenance exclusions cannot be configured past this date, except as a temporary, emergency measure with the \"No upgrades\" scope.\n- That exclusion can delay the upgrade for up to 90 days after the end of support date. Google does not recommend it.\n- Dates in the GKE release schedule are updated monthly and subject to change.",
      "migration_path": "1. Google does not recommend enrolling a cluster in the Extended channel without plans to move to the next minor version, because GKE eventually upgrades the cluster to newer minor versions.\n2. Around 2 months before the end of extended support, GKE begins upgrading clusters in the Extended channel to the next minor version, unless the cluster is using deprecated features or APIs.\n3. Maintenance exclusions can prevent minor version upgrades until the end of extended support. A temporary, emergency exclusion with the \"No upgrades\" scope can delay the upgrade for up to 90 days after the end of support date. After that exclusion expires, GKE upgrades the cluster.\n4. At the end of extended support, GKE upgrades all clusters still running the minor version, regardless of blocking issues. See [GKE minor version lifecycle](https://docs.cloud.google.com/kubernetes-engine/versioning#lifecycle).",
      "replacement": null,
      "affected_versions": [
        "1.31"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [],
      "vendor_ref": "gke@1.31",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-31-extended-support-end-of-support"
    },
    {
      "slug": "azure-avm-network-privateendpoint-0-3-0-breaking-change",
      "title": "avm-res-network-privateendpoint 0.3.0: breaking changes",
      "summary": "Release date of version 0.3.0 of the Azure Verified Module avm-res-network-privateendpoint: 22 Oct 2026. Breaking changes listed in the release notes: 5.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-10-22",
      "effective_date": "2026-10-22",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Provider and Terraform requirements: Terraform >= 1.16, < 2.0 and Azure/azapi ~> 2.12 are now required.\n- Parent scope: Replace resource_group_name with parent_id, containing the resource group's full Azure resource ID.\n- Outputs: The whole-resource resource output has been removed. Use name, resource_id, network_interface_ids, private_ip_addresses, and application_security_group_association_ids instead.\n- Role assignments: Remove role_assignment_name_use_random_uuid from module inputs. Existing assignment GUIDs are preserved through the supported migration path.\n- DNS zone group ownership: Private DNS zone groups now have an independently managed child-module state address and require the managed migration flag when upgrading an existing configured group.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-network-privateendpoint/releases/tag/v0.3.0) for 0.3.0: 5. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-network-privateendpoint from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-network-privateendpoint). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.3.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.3.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.3.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-network-privateendpoint/releases/tag/v0.3.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-network-privateendpoint"
      ],
      "vendor_ref": "v0.3.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-network-privateendpoint-0-3-0-breaking-change"
    },
    {
      "slug": "azure-avm-managedidentity-userassignedidentity-0-6-0-breaking-change",
      "title": "avm-res-managedidentity-userassignedidentity 0.6.0: breaking changes",
      "summary": "Release date of version 0.6.0 of the Azure Verified Module avm-res-managedidentity-userassignedidentity: 27 Oct 2026. Breaking changes listed in the release notes: 4.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-10-27",
      "effective_date": "2026-10-27",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Rename role_assignments to outbound_role_assignments in every module call; the old argument is no longer accepted. Preserve the existing map keys and values. These remain outbound grants to the created identity at each supplied scope, not grants to other principals on the identity. The resource block remains azurerm_role_assignment.this, so the input rename alone does not require state moves.\n- Outbound role assignment description is now applied instead of ignored. AzureRM treats description changes as replacement, so existing non-null descriptions can replace assignments on upgrade. Inspect the plan for resulting access changes. Other role attributes and their existing null defaults remain unchanged.\n- enable_telemetry remains true by default. Enabled telemetry creates an empty Incremental Microsoft.Resources/deployments resource at the AzAPI provider subscription, using the existing required real region. Subscription deployment-management permissions are required; resource-group-only permissions may be insufficient. Owner is not specifically required. Configure the intended AzAPI subscription or set enable_telemetry=false. Deployment-history records and plan-timestamp updates are new behavior.\n- ModTM and telemetry-only root random requirements are removed. removed blocks with destroy=false request forgetting the old telemetry resources without destruction. Workload addresses are preserved; historical-state migration has not been exercised. Back up state and inspect the upgrade plan, especially outbound assignment descriptions, before applying.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-managedidentity-userassignedidentity/releases/tag/v0.6.0) for 0.6.0: 4. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-managedidentity-userassignedidentity from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-managedidentity-userassignedidentity). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.6.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.6.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.6.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-managedidentity-userassignedidentity/releases/tag/v0.6.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-managedidentity-userassignedidentity"
      ],
      "vendor_ref": "v0.6.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-managedidentity-userassignedidentity-0-6-0-breaking-change"
    },
    {
      "slug": "azure-avm-network-routetable-0-6-0-breaking-change",
      "title": "avm-res-network-routetable 0.6.0: breaking changes",
      "summary": "Release date of version 0.6.0 of the Azure Verified Module avm-res-network-routetable: 27 Oct 2026. Breaking changes listed in the release notes: 5.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-10-27",
      "effective_date": "2026-10-27",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Direct users of modules/route must now supply a non-null real Azure location even when enable_telemetry=false. Root callers already supply location; the root forwards it and enable_telemetry to each route child. No new required root input is added.\n- Default-enabled telemetry now creates empty Incremental subscription deployments for the root and every instantiated non-legacy route child. Subscription deployment-management permissions are required; resource-group-only routing permissions may be insufficient. Owner is not specifically required. Configure the intended AzAPI subscription or explicitly disable telemetry. Expect additional deployment-history records per child and plan-timestamp updates. Existing routes_legacy_mode selection is unchanged.\n- AzAPI now requires~>2.12 instead of~>2.4 in root and direct route child. Terraform>=1.9,<2.0 and AzureRM~>4.0 remain unchanged. Refresh provider locks as appropriate.\n- ModTM and telemetry-only root Random requirements are removed. Non-destructive removed blocks request forgetting old root telemetry resources. Workload addresses and map keys are preserved, but an actual historical-state upgrade has not been exercised; back up state and inspect the plan.\n- Route-table/route request bodies, route outputs, subnet associations, locks and role assignments retain their existing contract. Examples use exact certified Naming0.2.0 and legacy Regions0.8.2.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-network-routetable/releases/tag/v0.6.0) for 0.6.0: 5. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-network-routetable from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-network-routetable). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.6.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.6.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.6.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-network-routetable/releases/tag/v0.6.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-network-routetable"
      ],
      "vendor_ref": "v0.6.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-network-routetable-0-6-0-breaking-change"
    },
    {
      "slug": "azure-avm-containerregistry-registry-0-9-0-breaking-change",
      "title": "avm-res-containerregistry-registry 0.9.0: breaking changes",
      "summary": "Release date of version 0.9.0 of the Azure Verified Module avm-res-containerregistry-registry: 29 Oct 2026. Breaking changes listed in the release notes: 5.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-10-29",
      "effective_date": "2026-10-29",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Direct users of modules/cache-rule, modules/credential-set and modules/scope-map must now supply a non-null location, including when enable_telemetry=false. Root calls already forward the existing root location.\n- Direct modules/scope-map users now require Terraform >= 1.5.0, < 2.0.0 instead of >= 1.3.0, because telemetry uses plantimestamp() and terraform_data. The root, cache-rule and credential-set minima remain >= 1.8.\n- Root AzAPI changes from ~> 2.4 to ~> 2.12; cache-rule and credential-set change from >= 2.0, < 3.0 to ~> 2.12; scope-map newly requires AzAPI ~> 2.12. Refresh incompatible lockfiles. Root AzureRM remains >= 4.81.0, < 5.0.0.\n- Root and all three children enable subscription-scope deployment telemetry by default. Configure the intended AzAPI subscription and grant appropriate subscription-deployment lifecycle permissions, or disable telemetry. Root enable_telemetry is forwarded to its children; direct child callers must configure their own flag. Deployments contain no workload resources, but add deployment-history and plan-timestamp updates.\n- Root ModTM and telemetry-only Random requirements are removed. removed blocks request forgetting the old telemetry resources without destruction; actual historical-state migration was not exercised. Back up state and inspect the upgrade plan. Naming examples still legitimately consume Random through the ModTM-free Naming module.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-containerregistry-registry/releases/tag/v0.9.0) for 0.9.0: 5. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-containerregistry-registry from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-containerregistry-registry). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.9.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.9.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.9.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-containerregistry-registry/releases/tag/v0.9.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-containerregistry-registry"
      ],
      "vendor_ref": "v0.9.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-containerregistry-registry-0-9-0-breaking-change"
    },
    {
      "slug": "gcp-cloud-run-node-20-retirement",
      "title": "Cloud Run: Node.js 20 decommission",
      "summary": "Decommission date for Node.js 20 on Cloud Run: 30 Oct 2026. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2026-10-30",
      "effective_precision": "day",
      "impact": "The decommission date of Node.js 20 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-node-20-retirement"
    },
    {
      "slug": "aws-lambda-python3-10-end-of-support",
      "title": "AWS Lambda: Python 3.10 (python3.10) deprecation",
      "summary": "Deprecation date for Python 3.10 (python3.10) on AWS Lambda: 31 Oct 2026. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "After deprecation (31 Oct 2026), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 29 Jul 2027, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2027, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2027), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "python3.10"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "python3.10",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-python3-10-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-14-18-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14.18 end of standard support",
      "summary": "End of standard support date for PostgreSQL 14.18 on Amazon RDS for PostgreSQL: 31 Oct 2026. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 31 Oct 2026 as the RDS end of standard support date of minor version 14.18. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "14.18"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@14.18",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-18-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-14-19-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14.19 end of standard support",
      "summary": "End of standard support date for PostgreSQL 14.19 on Amazon RDS for PostgreSQL: 31 Oct 2026. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 31 Oct 2026 as the RDS end of standard support date of minor version 14.19. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "14.19"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@14.19",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-19-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-15-13-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15.13 end of standard support",
      "summary": "End of standard support date for PostgreSQL 15.13 on Amazon RDS for PostgreSQL: 31 Oct 2026. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 31 Oct 2026 as the RDS end of standard support date of minor version 15.13. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "15.13"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@15.13",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-13-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-15-14-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15.14 end of standard support",
      "summary": "End of standard support date for PostgreSQL 15.14 on Amazon RDS for PostgreSQL: 31 Oct 2026. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 31 Oct 2026 as the RDS end of standard support date of minor version 15.14. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "15.14"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@15.14",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-14-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-10-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16.10 end of standard support",
      "summary": "End of standard support date for PostgreSQL 16.10 on Amazon RDS for PostgreSQL: 31 Oct 2026. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 31 Oct 2026 as the RDS end of standard support date of minor version 16.10. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "16.10"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@16.10",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-10-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-9-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16.9 end of standard support",
      "summary": "End of standard support date for PostgreSQL 16.9 on Amazon RDS for PostgreSQL: 31 Oct 2026. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 31 Oct 2026 as the RDS end of standard support date of minor version 16.9. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "16.9"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@16.9",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-9-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-5-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17.5 end of standard support",
      "summary": "End of standard support date for PostgreSQL 17.5 on Amazon RDS for PostgreSQL: 31 Oct 2026. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 31 Oct 2026 as the RDS end of standard support date of minor version 17.5. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "17.5"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@17.5",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-5-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-6-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17.6 end of standard support",
      "summary": "End of standard support date for PostgreSQL 17.6 on Amazon RDS for PostgreSQL: 31 Oct 2026. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 31 Oct 2026 as the RDS end of standard support date of minor version 17.6. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "17.6"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@17.6",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-6-end-of-support"
    },
    {
      "slug": "azure-resource-manager-custom-resource-providers-retirement",
      "title": "Azure Resource Manager: Custom Resource Providers retirement",
      "summary": "The Custom Resource Provider (CuRP) feature of Azure Resource Manager is retired by 31 Oct 2026. Creates, updates, patches and actions are blocked from July 31, 2026.",
      "cloud": "azure",
      "service": "Azure Resource Manager",
      "service_slug": "resource-manager",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-12-29",
      "effective_date": "2026-10-31",
      "effective_precision": "day",
      "impact": "Azure Resource Manager retires the Custom Resource Provider (CuRP) feature by 31 Oct 2026. From July 31, 2026, creates, updates, patches, and actions to custom resources and resource providers are blocked. From that point, custom resources and resource providers can only be read and deleted. Microsoft scheduled a scream test on October 27, 2025 as part of the deprecation.",
      "migration_path": "1. If the scenario only involves triggering an endpoint without the need for persistent resource management, consider [Deployment Scripts](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-script-template).\n2. If the same scenario uses Bicep, consider [Bicep Extensions](https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-extension).\n3. If the scenario involves triggering several different endpoints or services, consider [Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/functions-overview).\n4. For questions, ask your Microsoft account manager to email curpdeprecation@microsoft.com with your name, company name, email contact, and subscription ID.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=513892",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-script-template",
        "https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-extension",
        "https://learn.microsoft.com/en-us/azure/azure-functions/functions-overview"
      ],
      "vendor_ref": "513892",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-resource-manager-custom-resource-providers-retirement"
    },
    {
      "slug": "azure-aks-kubernetes-1-31-lts-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.31 LTS end of life",
      "summary": "LTS end of life date for Kubernetes 1.31 on Azure Kubernetes Service: Nov 2026. For clusters with long-term support enabled, support for the version continues only until that date. After it, those clusters must move to the next supported LTS version.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-11-01",
      "effective_precision": "month",
      "impact": "After the LTS end of life date, long-term support for Kubernetes 1.31 ends. LTS-enabled clusters must then be upgraded to the next supported LTS version.\n\n- If a cluster is not upgraded, AKS upgrades it to the next supported LTS version through a platform-initiated upgrade. The cluster is not dropped to a community-supported version.\n- The LTS page places this after the 60-day grace period that follows the LTS end of life date. For the initial rollout, the grace period is the window through May 31, 2027, and no platform-initiated upgrade starts before June 1, 2027. After the initial rollout, every end-of-support event has a 60-day grace period before platform-initiated upgrades begin.\n- Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget.\n- The platform-initiated upgrade month in the AKS LTS release calendar is a planning estimate, not an exact upgrade date.",
      "migration_path": "1. List the versions AKS offers as upgrade targets with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. Test the workloads against deprecated APIs and other breaking changes between the current and target versions.\n3. Upgrade to an offered higher LTS version with `az aks upgrade --resource-group <resource-group-name> --name <cluster-name> --kubernetes-version <lts-kubernetes-version>`. An LTS cluster can skip minor versions when the upgrade satisfies version-skew requirements and validation checks. See [Long-term support for AKS versions](https://learn.microsoft.com/en-us/azure/aks/long-term-support).\n4. If the cluster is already past its LTS end of life date, skipping minor versions is conditional: the target must be listed by AKS and satisfy validation checks. AKS allows this upgrade but treats it as an unsupported recovery path.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To leave LTS instead, move the cluster to the Free or Standard tier and select the KubernetesOfficial support plan. This is possible while the cluster's Kubernetes version is still in community support. After that version exits community support, first upgrade the cluster to a community-supported version.",
      "replacement": "Next supported AKS LTS version",
      "affected_versions": [
        "1.31"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.31",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-31-lts-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-34-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.34 end of life",
      "summary": "End of life date for Kubernetes 1.34 on Azure Kubernetes Service: Nov 2026. After that date, community support for the version ends and clusters not enrolled in long-term support enter platform support, which covers AKS and Azure platform issues only.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-11-01",
      "effective_precision": "month",
      "impact": "After the end of life date, community support for Kubernetes 1.34 ends. Clusters not enrolled in long-term support enter platform support.\n\n- Platform support covers AKS and Azure platform issues only, not Kubernetes functionality and components. New clusters cannot be created during the platform support period.\n- There is a 60-day platform support grace period after the published end of life date to upgrade to a supported minor version. For the initial rollout, the grace period is the window through May 31, 2027.\n- After the grace period, the cluster is eligible for a platform-initiated upgrade to the lowest supported community minor version. No such upgrade starts before June 1, 2027. Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget. Its month in the release calendar is a planning estimate, not an exact date.\n- Regional version removal can happen at a different time from the published date.",
      "migration_path": "1. List the versions AKS offers for the cluster with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. While the cluster is a supported non-LTS cluster, upgrade one minor version at a time. Minor versions cannot be skipped.\n3. Upgrade the control plane and all node pools with `az aks upgrade`, as described in [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n4. If the cluster is already on an unsupported version, use the oldest supported GA target that AKS offers and perform a full-cluster upgrade. Control-plane-only upgrades are not supported for this path. The version-skipping table in [Supported Kubernetes versions in Azure Kubernetes Service (AKS)](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions) labels this an unsupported recovery path: AKS allows the upgrade to proceed, but it is not supported and might carry risks. The platform support table on the same page lists upgrades from an N-3 version to a supported version as supported.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To get extended support for the version instead, enable [long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support). This requires moving the cluster to the Premium tier and explicitly selecting the LTS support plan. Microsoft-managed Calico is not supported in LTS. Once community support for the version has ended, LTS cannot be disabled for that version.",
      "replacement": null,
      "affected_versions": [
        "1.34"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.34",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-34-end-of-support"
    },
    {
      "slug": "azure-aks-managed-nginx-ingress-application-routing-retirement",
      "title": "Azure Kubernetes Service: managed NGINX ingress (Application Routing) retirement",
      "summary": "End of support date for the NGINX ingress controller within the AKS Application Routing add-on: Nov 2026. Critical security patches from Microsoft end on that date.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-02-27",
      "effective_date": "2026-11-01",
      "effective_precision": "month",
      "impact": "Critical security patches from Microsoft for the NGINX ingress controller in the Application Routing add-on end on Nov 2026. After that date, the NGINX ingress controller is no longer supported within the Application Routing add-on. Microsoft states that the upstream Ingress-NGINX project receives no updates after March 2026.",
      "migration_path": "The Microsoft update lists no migration steps. It names supported alternatives: Gateway API with Application Routing (in development), Application Gateway for Containers, and Istio Service Mesh. See [Learn more.](https://learn.microsoft.com/en-us/azure/aks/app-routing)",
      "replacement": "Gateway API with Application Routing (in development), Application Gateway for Containers, or Istio Service Mesh",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=555839",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/aks/app-routing"
      ],
      "vendor_ref": "555839",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-managed-nginx-ingress-application-routing-retirement"
    },
    {
      "slug": "azure-avm-network-virtualnetwork-0-23-0-breaking-change",
      "title": "avm-res-network-virtualnetwork 0.23.0: breaking changes",
      "summary": "Release date of version 0.23.0 of the Azure Verified Module avm-res-network-virtualnetwork: 4 Nov 2026. Breaking changes listed in the release notes: 2.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-11-04",
      "effective_date": "2026-11-04",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Standalone modules/subnet and modules/peering now enable telemetry by default and require a non-null location when telemetry is enabled. Existing direct callers must supply location or explicitly set enable_telemetry = false. The root module passes its existing location to these children.\n- Enabled telemetry now creates Azure subscription-scope deployments through AzAPI, including for the root module and enabled children. Identities must have the necessary subscription-scope deployment permissions; alternatively disable telemetry. Terraform state forgets legacy ModTM telemetry and telemetry UUID objects without destroying them and tracks the new telemetry deployment resources.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/releases/tag/v0.23.0) for 0.23.0: 2. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-network-virtualnetwork from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-network-virtualnetwork). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.23.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.23.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.23.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/releases/tag/v0.23.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-network-virtualnetwork"
      ],
      "vendor_ref": "v0.23.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-network-virtualnetwork-0-23-0-breaking-change"
    },
    {
      "slug": "azure-avm-storage-storageaccount-0-11-0-breaking-change",
      "title": "avm-res-storage-storageaccount 0.11.0: breaking changes",
      "summary": "Release date of version 0.11.0 of the Azure Verified Module avm-res-storage-storageaccount: 4 Nov 2026. Breaking changes listed in the release notes: 5.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-11-04",
      "effective_date": "2026-11-04",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- The tracing_tags_header input was removed from the blob_service, container, data_lake_filesystem, diagnostic_setting, file_service, local_user, management_policy, private_endpoint, queue, queue_service, role_assignments, share, table, and table_service child modules. The static_website child retains this input.\n- Direct callers must now supply location to container, diagnostic_setting, local_user, queue, role_assignments, share, and table. Direct callers of blob_service, data_lake_filesystem, file_service, management_policy, queue_service, static_website, and table_service must supply location when telemetry is enabled (the default).\n- The minimum Azure AzAPI provider version increases to 2.12 for the root and all child modules.\n- Enabled telemetry now creates subscription-scope ARM deployments. The caller needs subscription-scope deployment read, write, and delete permissions. The root and instrumented children honor enable_telemetry = false; root input and output contracts are unchanged.\n- The root and its updated Interfaces dependencies retire legacy ModTM and random telemetry state with destroy = false. Upgrading existing state may still require the legacy providers during initialization. Review the plan before applying.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-storage-storageaccount/releases/tag/v0.11.0) for 0.11.0: 5. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-storage-storageaccount from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-storage-storageaccount). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.11.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.11.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.11.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-storage-storageaccount/releases/tag/v0.11.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-storage-storageaccount"
      ],
      "vendor_ref": "v0.11.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-storage-storageaccount-0-11-0-breaking-change"
    },
    {
      "slug": "azure-avm-network-privatednszone-0-6-0-breaking-change",
      "title": "avm-res-network-privatednszone 0.6.0: breaking changes",
      "summary": "Release date of version 0.6.0 of the Azure Verified Module avm-res-network-privatednszone: 5 Nov 2026. Breaking changes listed in the release notes: 4.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-11-05",
      "effective_date": "2026-11-05",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Root and directly consumed child modules require location when telemetry is enabled (the default). Set a valid Azure region, or explicitly disable telemetry.\n- The minimum Azure AzAPI provider version is now 2.12 for the root and child modules.\n- Enabled telemetry now creates subscription-scope ARM deployments and requires permissions to manage those deployments. Previous telemetry state entries are retired without destruction, and new telemetry resources enter state.\n- The root name output now uses the configured resource name instead of the name returned in the API response.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-network-privatednszone/releases/tag/v0.6.0) for 0.6.0: 4. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-network-privatednszone from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-network-privatednszone). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.6.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.6.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.6.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-network-privatednszone/releases/tag/v0.6.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-network-privatednszone"
      ],
      "vendor_ref": "v0.6.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-network-privatednszone-0-6-0-breaking-change"
    },
    {
      "slug": "azure-avm-resources-resourcegroup-0-5-0-breaking-change",
      "title": "avm-res-resources-resourcegroup 0.5.0: breaking changes",
      "summary": "Release date of version 0.5.0 of the Azure Verified Module avm-res-resources-resourcegroup: 6 Nov 2026. Breaking changes listed in the release notes: 8.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-11-06",
      "effective_date": "2026-11-06",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Back up state and inspect the complete plan before applying. These changes are not a guarantee of a safe or replacement-free upgrade.\n- Resource-group state now uses a counted AzAPI address. The move chain is azurerm_resource_group.this → azapi_resource.this → azapi_resource.this[0]; the last step also covers v0.4.0's unkeyed AzAPI address. Cross-provider conversion requires supported provider versions and usable Azure resource IDs. If conversion cannot be performed, explicit migration or import may be required.\n- The new ignore_tag_changes input defaults to false. Do not toggle it on an existing group without a reviewed migration: switching resource definitions can plan a delete and create of the resource group, with potential loss of its contents.\n- Lock configuration now includes notes = null; v0.4.0 omitted notes and older AzureRM-based versions supplied notes. Azure's handling of the explicit null has not been verified. Review existing notes and the plan.\n- For AzureRM-era role assignments, explicitly set role_assignments[*].name to the existing assignment GUID before migration and inspect the plan; otherwise a new UUID can result in a different assignment name.\n- The full resource output changes shape: a resource attribute is added (null in the default synthetic fixture). With ignore_tag_changes = true, reported tags are null. Consumers relying on the exact output object should review their use.\n- AzAPI changes from ~> 2.4 to ~> 2.12; Terraform remains >= 1.9, < 2.0. Interfaces changes from 0.6.0 to 0.10.0. Active ModTM telemetry is replaced by subscription-scope AzAPI deployments. When telemetry is enabled, deployment read, write and delete permissions are required at subscription scope. Old telemetry state may need its old providers for a final initialization; removed telemetry resources are forgotten without destruction. Telemetry can be disabled with enable_telemetry = false.\n- Offline synthetic-state/mock-provider plans covered the v0.4.0 and older AzureRM address chains; they do not prove live Azure behavior or all provider/Terraform version combinations. No live upgrade was performed.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-resources-resourcegroup/releases/tag/v0.5.0) for 0.5.0: 8. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-resources-resourcegroup from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-resources-resourcegroup). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.5.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.5.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.5.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-resources-resourcegroup/releases/tag/v0.5.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-resources-resourcegroup"
      ],
      "vendor_ref": "v0.5.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-resources-resourcegroup-0-5-0-breaking-change"
    },
    {
      "slug": "azure-avm-network-loadbalancer-0-6-0-breaking-change",
      "title": "avm-res-network-loadbalancer 0.6.0: breaking changes",
      "summary": "Release date of version 0.6.0 of the Azure Verified Module avm-res-network-loadbalancer: 9 Nov 2026. Breaking changes listed in the release notes: 9.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-11-09",
      "effective_date": "2026-11-09",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- Read the v0.5.0 upgrade guide before upgrading. This is not a drop-in provider replacement.\n- Requirements: Terraform >= 1.16, < 2.0 and effective AzAPI provider minimum 2.13.\n- Parent scope: replace resource_group_name with the existing resource group's parent_id.\n- Public IP ownership: bundled public IP creation and extension management are removed. Manage and adopt existing public IPs and their extensions in the consumer configuration, then supply their resource IDs.\n- Native NIC associations: backend_address_pool_network_interfaces is removed. Manage complete native membership lists exclusively through the NIC/compute owner, using the module's keyed backend pool IDs.\n- Backend pool defaults: omitted or null backend_address_type now means \"NIC\". Explicit IP pools must select \"IP\"; Global regional-frontend pools must select \"Frontend\". These modes do not automatically convert existing pools.\n- Diagnostic settings: replace legacy category arrays with canonical logs and metrics objects.\n- Outputs: replace removed whole-resource objects with discrete IDs, keyed child-ID maps and name. Legacy AzureRM object shapes are not preserved.\n- Authoritative collections: configure all intended children and explicit members; omitted entries can be removed.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-network-loadbalancer/releases/tag/v0.6.0) for 0.6.0: 9. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-network-loadbalancer from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-network-loadbalancer). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.6.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.6.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.6.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-network-loadbalancer/releases/tag/v0.6.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-network-loadbalancer"
      ],
      "vendor_ref": "v0.6.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-network-loadbalancer-0-6-0-breaking-change"
    },
    {
      "slug": "aws-lambda-dotnet8-end-of-support",
      "title": "AWS Lambda: .NET 8 (dotnet8) deprecation",
      "summary": "Deprecation date for .NET 8 (dotnet8) on AWS Lambda: 10 Nov 2026. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-11-10",
      "effective_precision": "day",
      "impact": "After deprecation (10 Nov 2026), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 29 Jul 2027, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2027, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2027), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "dotnet8"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "dotnet8",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-dotnet8-end-of-support"
    },
    {
      "slug": "azure-app-service-dotnet-8-end-of-support",
      "title": "Azure App Service: .NET 8 (LTS) end of support",
      "summary": "End of support date for .NET 8 (LTS) on Azure App Service: 10 Nov 2026. Apps keep running after that date but stop receiving security updates and customer service for .NET 8.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-04-24",
      "effective_date": "2026-11-10",
      "effective_precision": "day",
      "impact": "Apps hosted on App Service that use .NET 8 (LTS) continue to run after the end of support date. Security updates are no longer available for .NET 8 (LTS). Microsoft no longer provides customer service for .NET 8 (LTS).",
      "migration_path": "Upgrade the app to .NET 10 (LTS) before the end of support date: [follow the steps to upgrade your app](https://aka.ms/dotnetversion). See also: [Learn more](https://learn.microsoft.com/azure/app-service/language-support-policy).",
      "replacement": ".NET 10 (LTS)",
      "affected_versions": [
        "8"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=558033",
      "extra_source_urls": [
        "https://aka.ms/dotnetversion",
        "https://learn.microsoft.com/azure/app-service/language-support-policy",
        "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy"
      ],
      "vendor_ref": "558033",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-dotnet-8-end-of-support"
    },
    {
      "slug": "azure-app-service-dotnet-9-end-of-support",
      "title": "Azure App Service: .NET 9 (STS) end of support",
      "summary": "End of support date for .NET 9 (STS) on Azure App Service: 10 Nov 2026. Apps keep running after that date but stop receiving security updates and customer service for .NET 9.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2025-06-05",
      "effective_date": "2026-11-10",
      "effective_precision": "day",
      "impact": "Apps hosted on App Service that use .NET 9 (STS) continue to run after the end of support date. Security updates are no longer available for .NET 9 (STS). Microsoft no longer provides customer service for .NET 9 (STS).",
      "migration_path": "Upgrade the app to .NET 10 (LTS) before the end of support date by following the steps Microsoft links: [follow the steps to upgrade your app to .NET 10 (LTS)](https://aka.ms/dotnetversion). The support policy is described in [App Service language support](https://learn.microsoft.com/azure/app-service/language-support-policy).",
      "replacement": ".NET 10 (LTS)",
      "affected_versions": [
        "9"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=485077",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/app-service/language-support-policy",
        "https://aka.ms/dotnetversion",
        "https://aka.ms/nodeversion",
        "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy"
      ],
      "vendor_ref": "485077",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-dotnet-9-end-of-support"
    },
    {
      "slug": "azure-functions-dotnet-8-and-9-end-of-support",
      "title": "Azure Functions: .NET 8 and .NET 9 end of support",
      "summary": "End of support date for .NET 8 and .NET 9 on Azure Functions: 10 Nov 2026. Function apps keep operating after that date but stop receiving security updates and support.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-09-23",
      "effective_date": "2026-11-10",
      "effective_precision": "day",
      "impact": "After the end of support date, function apps on .NET 8 and .NET 9 continue to operate, but security updates are no longer provided and support for these versions on Azure Functions ends. Microsoft states that running function apps on an unsupported runtime or language version might lead to security and performance issues. Apps that use the in-process model must move to the isolated worker model before they can upgrade. Apps on a Linux Consumption plan must first upgrade to the Flex Consumption plan before upgrading to .NET 10.",
      "migration_path": "1. If the app uses the in-process model, migrate it to the isolated worker model, then upgrade to .NET 10 (step 3). See [Migrate C# Apps from In-Process to Isolated Worker Model](https://learn.microsoft.com/azure/azure-functions/migrate-dotnet-to-isolated-model?tabs=net8).\n2. If the app is on a Linux Consumption plan, upgrade to the Flex Consumption plan before upgrading to .NET 10.\n3. If the app already uses the isolated worker model, upgrade it directly to .NET 10 by following [Update Language Versions in Azure Functions](https://learn.microsoft.com/azure/azure-functions/update-language-versions?tabs=azure-portal%2Cwindows&pivots=programming-language-csharp).\n4. Complete all required upgrades and confirm the app has moved off the in-process model before 10 Nov 2026.",
      "replacement": ".NET 10",
      "affected_versions": [
        "8",
        "9"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=572838",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-functions/language-support-policy",
        "https://learn.microsoft.com/azure/azure-functions/migrate-dotnet-to-isolated-model?tabs=net8",
        "https://learn.microsoft.com/azure/azure-functions/update-language-versions?tabs=azure-portal%2Cwindows&pivots=programming-language-csharp",
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy?pivots=programming-language-csharp",
        "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions"
      ],
      "vendor_ref": "572838",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-dotnet-8-and-9-end-of-support"
    },
    {
      "slug": "azure-functions-dotnet-in-process-model-end-of-support",
      "title": "Azure Functions: .NET in-process model end of support",
      "summary": "End of support date for the in-process model for .NET apps in Azure Functions: 10 Nov 2026. Apps on this model can still be used after that date but stop receiving security and feature updates.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2024-03-29",
      "effective_date": "2026-11-10",
      "effective_precision": "day",
      "impact": "From the end of support date, the in-process model for .NET apps in Azure Functions is no longer supported. .NET apps that use the in-process model can still be used after that date, but they no longer receive security and feature updates from Microsoft. Microsoft states that apps on this model need to transition to the isolated worker model by that date to continue being supported.",
      "migration_path": "Move .NET apps from the in-process model to the isolated worker model by 10 Nov 2026: [migrate to the isolated worker model](https://aka.ms/af-dotnet-isolated-migration).",
      "replacement": "Isolated worker model",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=retirement-support-for-the-inprocess-model-for-net-apps-in-azure-functions-ends-10-november-2026",
      "extra_source_urls": [
        "https://aka.ms/af-dotnet-isolated-migration"
      ],
      "vendor_ref": "retirement-support-for-the-inprocess-model-for-net-apps-in-azure-functions-ends-10-november-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-dotnet-in-process-model-end-of-support"
    },
    {
      "slug": "azure-functions-powershell-7-4-end-of-support",
      "title": "Azure Functions: PowerShell 7.4 end of support",
      "summary": "End of support date for PowerShell 7.4 on Azure Functions: 10 Nov 2026. Function apps keep running after that date but stop receiving security patches, updates and customer support.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-09-23",
      "effective_date": "2026-11-10",
      "effective_precision": "day",
      "impact": "After the end of support date, function apps on PowerShell 7.4 continue to run, but security patches and updates are no longer provided and customer support for PowerShell 7.4 is discontinued. Microsoft states that running function apps on an unsupported runtime or language version may lead to issues and degraded performance. Apps on a Linux Consumption plan must first upgrade to the Flex Consumption plan before upgrading to PowerShell 7.6.",
      "migration_path": "1. If the app is on a Linux Consumption plan, upgrade to the Flex Consumption plan first.\n2. Upgrade the app to PowerShell 7.6 before 10 Nov 2026. [Follow the steps to upgrade your app](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions?tabs=azure-portal%2Cwindows&pivots=programming-language-powershell).",
      "replacement": "PowerShell 7.6",
      "affected_versions": [
        "7.4"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=572770",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions?tabs=azure-portal%2Cwindows&pivots=programming-language-powershell",
        "https://learn.microsoft.com/azure/app-service/language-support-policy",
        "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions"
      ],
      "vendor_ref": "572770",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-powershell-7-4-end-of-support"
    },
    {
      "slug": "azure-static-web-apps-dotnet-8-and-9-end-of-support",
      "title": "Azure Static Web Apps: .NET 8 and .NET 9 end of support",
      "summary": "End of support date for .NET 8 and .NET 9 in Azure Static Web Apps managed Functions APIs: 10 Nov 2026. Apps keep operating after that date but stop receiving security updates and support.",
      "cloud": "azure",
      "service": "Azure Static Web Apps",
      "service_slug": "static-web-apps",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-11-09",
      "effective_date": "2026-11-10",
      "effective_precision": "day",
      "impact": "After the end of support date, Azure Static Web Apps managed Functions APIs on .NET 8 or .NET 9 continue to operate, but security updates are no longer provided and support for .NET 8 and .NET 9 on Azure Functions ends. Microsoft states that running apps on an unsupported runtime or language version might lead to security and performance issues. Microsoft also states that the default .NET runtime for Azure Static Web Apps managed Functions APIs is updated to .NET 10 in the same month, and that an explicit apiRuntime setting in staticwebapp.config.json ensures the app builds and runs on the intended runtime. Linked (bring-your-own) Function Apps have a separate deployment lifecycle and must be upgraded and deployed separately.",
      "migration_path": "1. If the API uses the in-process model, follow the .NET 10 steps in [Migrate C# apps from the in-process model to the isolated worker model](https://learn.microsoft.com/azure/azure-functions/migrate-dotnet-to-isolated-model?tabs=net10) to update the API project, packages, startup code, function code and configuration.\n2. If the API already uses the isolated worker model, follow the C# steps in [Update language versions in Azure Functions](https://learn.microsoft.com/azure/azure-functions/update-language-versions?pivots=programming-language-csharp) to target net10.0.\n3. Confirm that the API project targets net10.0, and update the Functions SDK and worker packages to meet the [.NET 10 isolated worker project and package requirements](https://learn.microsoft.com/azure/azure-functions/dotnet-isolated-process-guide#project-and-package-references). Build and test the API locally.\n4. Set `platform.apiRuntime` to `dotnet-isolated:10.0` in staticwebapp.config.json. It must describe the same runtime as the API project's TargetFramework.\n5. Redeploy the static web app so that the managed API is rebuilt and published on .NET 10. Complete all required upgrades and confirm the API has moved off the in-process model before 10 Nov 2026.\n6. Linked (bring-your-own) Function Apps have a separate deployment lifecycle. [Upgrade](https://learn.microsoft.com/azure/azure-functions/update-language-versions?pivots=programming-language-csharp) and deploy them separately. [Learn more](https://learn.microsoft.com/azure/static-web-apps/functions-bring-your-own).",
      "replacement": ".NET 10",
      "affected_versions": [
        "8",
        "9"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=575106",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-functions/language-support-policy",
        "https://learn.microsoft.com/azure/azure-functions/migrate-dotnet-to-isolated-model?tabs=net10",
        "https://learn.microsoft.com/azure/azure-functions/update-language-versions?pivots=programming-language-csharp",
        "https://learn.microsoft.com/azure/azure-functions/dotnet-isolated-process-guide#project-and-package-references",
        "https://learn.microsoft.com/azure/static-web-apps/languages-runtimes",
        "https://learn.microsoft.com/azure/static-web-apps/functions-bring-your-own"
      ],
      "vendor_ref": "575106",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-static-web-apps-dotnet-8-and-9-end-of-support"
    },
    {
      "slug": "aws-terraform-aws-6-73-0-breaking-change",
      "title": "Terraform AWS provider 6.73.0: breaking changes",
      "summary": "Release date for Terraform AWS provider 6.73.0: 11 Nov 2026. Breaking changes listed in the release notes: 3.",
      "cloud": "aws",
      "service": "Terraform AWS provider",
      "service_slug": "terraform-aws",
      "category": "iac_provider",
      "type": "breaking_change",
      "announced_date": "2026-11-11",
      "effective_date": "2026-11-11",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- `aws_wafv2_web_acl_rule`: Removes and_statement from statement blocks nested in and_statement, and or_statement from statement blocks nested in or_statement. These values are rejected by AWS.\n- `aws_wafv2_web_acl_rule`: Removes managed_rule_group_statement, rate_based_statement and rule_group_reference_statement from statement blocks nested in and_statement, not_statement and or_statement. These values are rejected by AWS.\n- `aws_wafv2_web_acl_rule`: Removes or_statement from statement blocks nested in or_statement. These values are rejected by AWS.",
      "migration_path": "1. Give the provider a version constraint in the `required_providers` block. HashiCorp recommends a version constraint for every provider a module depends on.\n2. In a root module, also specify the maximum provider version, to avoid accidental upgrades to incompatible new versions. The `~>` operator is a shorthand that allows the rightmost component of a version to increment. Do not use `~>` or other maximum-version constraints in modules you intend to reuse across many configurations. Specify a minimum version there and let the root module manage the maximum version.\n3. Commit the dependency lock file to version control with the configuration, so that Terraform always installs the same provider versions.\n4. To adopt 6.73.0, change the version in the `required_providers` block and re-run `terraform init`. HashiCorp states that this upgrades the provider version in the lock file. Without a change, Terraform re-selects the version recorded in the lock file, even if a newer version has become available. With the `-upgrade` option, `terraform init` disregards the recorded selection and selects the newest available version matching the version constraint. The [release notes](https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.73.0) list each breaking change.\n5. Review the changes Terraform made to the lock file in version control. If they are changes you made intentionally, send them through the usual code review process.",
      "replacement": null,
      "affected_versions": [
        "6.73.0"
      ],
      "source_url": "https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.73.0",
      "extra_source_urls": [],
      "vendor_ref": "v6.73.0",
      "last_checked_at": "2026-11-12T09:55:27.655Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-terraform-aws-6-73-0-breaking-change"
    },
    {
      "slug": "azure-avm-cognitiveservices-account-0-12-0-breaking-change",
      "title": "avm-res-cognitiveservices-account 0.12.0: breaking changes",
      "summary": "Release date of version 0.12.0 of the Azure Verified Module avm-res-cognitiveservices-account: 11 Nov 2026. Breaking changes listed in the release notes: 7.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-11-11",
      "effective_date": "2026-11-11",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- AzAPI now requires ~> 2.12 (previously ~> 2.5).\n- Enabled telemetry creates empty subscription-scoped Azure deployments and requires Microsoft.Resources/deployments/read, write, and delete permissions at the active subscription. Set enable_telemetry = false to disable these deployments.\n- Direct callers of modules/deployment and modules/rai_policy must supply location when telemetry is enabled. The parent module forwards its location and telemetry opt-out automatically.\n- Previously ignored private endpoint fields are now honored. An explicit role-assignment name can replace its assignment; non-default subresource names can change generated endpoint/NIC/connection names and replace resources. Lock notes and IP member names are now sent to ARM. Review the plan before upgrading.\n- Deployment and RAI-policy tags supplied per item now take effect; omitted/null tags retain provider defaults and do not inherit account tags.\n- The private-endpoint example replaces legacy VNet module 5.0.1 with AVM VNet 0.23.0, changing example VNet/subnet state addresses. Use fresh disposable example infrastructure or explicitly review and migrate existing example state before applying.\n- Legacy telemetry state is forgotten with destroy = false. Terraform can still require the retired providers during the first initialization of an existing state.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-cognitiveservices-account/releases/tag/v0.12.0) for 0.12.0: 7. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-cognitiveservices-account from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-cognitiveservices-account). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.12.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.12.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.12.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-cognitiveservices-account/releases/tag/v0.12.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-cognitiveservices-account"
      ],
      "vendor_ref": "v0.12.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-cognitiveservices-account-0-12-0-breaking-change"
    },
    {
      "slug": "azure-avm-network-publicipaddress-0-3-0-breaking-change",
      "title": "avm-res-network-publicipaddress 0.3.0: breaking changes",
      "summary": "Release date of version 0.3.0 of the Azure Verified Module avm-res-network-publicipaddress: 11 Nov 2026. Breaking changes listed in the release notes: 6.",
      "cloud": "azure",
      "service": "Azure Verified Modules",
      "service_slug": "avm",
      "category": "iac_module",
      "type": "breaking_change",
      "announced_date": "2026-11-11",
      "effective_date": "2026-11-11",
      "effective_precision": "day",
      "impact": "Breaking changes listed in the release notes:\n\n- This release moves the module from AzureRM to AzAPI. In-module moved blocks adopt the public IP, lock, role assignments and diagnostic settings in place. Read Upgrading from v0.2.1 and earlier before you upgrade.\n- Replaces the resource_group_name input with parent_id, the resource ID of the resource group.\n- Requires Terraform 1.9 or later and AzAPI ~> 2.12. The module no longer requires the AzureRM provider.\n- public_ip_address is null instead of \"\" while a dynamic public IP has no address.\n- tags = null no longer clears tags. Set tags = {} to clear them.\n- An existing domain_name_label or reverse_fqdn can't be removed, or switched to the other, in place.",
      "migration_path": "1. Breaking changes listed in the [release notes](https://github.com/Azure/terraform-azurerm-avm-res-network-publicipaddress/releases/tag/v0.3.0) for 0.3.0: 6. HashiCorp recommends explicitly constraining the acceptable version numbers to avoid unexpected or unwanted changes.\n2. Check the `version` argument of the module block that installs avm-res-network-publicipaddress from the [Terraform Registry](https://registry.terraform.io/modules/Azure/avm-res-network-publicipaddress). Terraform uses the newest installed version that meets the constraint. When no acceptable version is installed, it downloads the newest version that meets the constraint, so a constraint that allows 0.3.0 can bring in this release. A module block with no `version` argument defaults to the latest version available from the source.\n3. The AVM versioning specification requires that, until a module's first major version 1.0.0 is released, the minor version is bumped for breaking changes and the major version is not bumped.\n4. To stay on an earlier version for now, require a specific version. HashiCorp recommends this for third-party modules so that updates only happen when convenient to you.\n5. To adopt 0.3.0, set the `version` argument to it, then run `terraform init` so that Terraform can update the local code.",
      "replacement": null,
      "affected_versions": [
        "0.3.0"
      ],
      "source_url": "https://github.com/Azure/terraform-azurerm-avm-res-network-publicipaddress/releases/tag/v0.3.0",
      "extra_source_urls": [
        "https://registry.terraform.io/modules/Azure/avm-res-network-publicipaddress"
      ],
      "vendor_ref": "v0.3.0",
      "last_checked_at": "2026-11-12T09:56:15.145Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-avm-network-publicipaddress-0-3-0-breaking-change"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-gemini-3-6-flash-retirement",
      "title": "Gemini Enterprise Agent Platform: gemini-3.6-flash retirement",
      "summary": "Retirement date for gemini-3.6-flash on Gemini Enterprise Agent Platform: 19 Nov 2026. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2026-11-19",
      "effective_precision": "day",
      "impact": "Google lists gemini-3.6-flash with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": "gemini-3.8-flash",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-gemini-3-6-flash-retirement"
    },
    {
      "slug": "gcp-cloud-number-registry-discovery-without-designated-project-breaking-change",
      "title": "Cloud Number Registry: discovery stops without a designated project",
      "summary": "From 25 Nov 2026, Cloud Number Registry stops discovering resources if the configuration has no designated project. Existing discovered resources remain but are not updated.",
      "cloud": "gcp",
      "service": "Cloud Number Registry",
      "service_slug": "cloud-number-registry",
      "category": "feature",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2026-11-25",
      "effective_precision": "day",
      "impact": "From 25 Nov 2026, Cloud Number Registry stops discovering resources in configurations that have no designated project. Without a designated project, new resources are not discovered, and existing discovered resources remain but are not updated. For example, after a subnet is deleted, its discovered range remains in Cloud Number Registry. Cloud Number Registry is in Preview.",
      "migration_path": "To continue discovering and updating resources after the enforcement date, check or configure the designated project for your organization:\n\n1. [View the required roles to list and create project designations](https://docs.cloud.google.com/number-registry/designate-project-cloud-number-registry#required-roles). The designation is made by an IAM principal that has the Cloud Number Registry IPAM Admin role at the organization level.\n2. [List project designations](https://docs.cloud.google.com/number-registry/designate-project-cloud-number-registry#view-designated-project).\n3. [Designate a project](https://docs.cloud.google.com/number-registry/designate-project-cloud-number-registry#designate-project).",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/release-notes#October_30_2026",
      "extra_source_urls": [
        "https://docs.cloud.google.com/number-registry/overview#project-designation-enforcement"
      ],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:14.506Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-number-registry-discovery-without-designated-project-breaking-change"
    },
    {
      "slug": "aws-eks-kubernetes-1-31-extended-support-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.31 end of extended support",
      "summary": "End of extended support date for Kubernetes 1.31 on Amazon EKS: 26 Nov 2026. On that date, new clusters can no longer be created with this version, and Amazon EKS automatically updates control planes still on it at any time afterward.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-11-26",
      "effective_precision": "day",
      "impact": "On the end of extended support date, new Amazon EKS clusters can no longer be created with Kubernetes 1.31. Amazon EKS automatically updates existing control planes to the earliest supported version, at any time after that date.\n\n- Amazon EKS gives no specific time frame and sends no notification before the update.\n- The auto-upgrade includes only the Kubernetes control plane. Self-managed nodes and EKS managed node groups remain on the previous version.\n- EKS Auto Mode nodes may update automatically.\n- Fargate nodes and hybrid nodes are not upgraded with the control plane.\n- Clusters that were automatically upgraded at the end of extended support cannot be rolled back.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version.\n3. Proactively update the control plane without relying on the Amazon EKS automatic update process, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n4. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n5. If Amazon EKS updated the control plane automatically, manually update cluster add-ons and Amazon EC2 nodes.",
      "replacement": null,
      "affected_versions": [
        "1.31"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.31",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-31-extended-support-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-15-sp4-for-sap-image-end-of-support",
      "title": "Compute Engine: SLES 15 SP4 for SAP image end of support",
      "summary": "EOS and image deprecation date for the SLES 15 SP4 for SAP public image on Compute Engine: Dec 2026. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 15 SP4 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 15 SP4 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-15-sp4-sap",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-15-sp4-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-15-sp4-image-end-of-support",
      "title": "Compute Engine: SLES 15 SP4 image end of support",
      "summary": "EOS and image deprecation date for the SLES 15 SP4 public image on Compute Engine: Dec 2026. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 15 SP4 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 15 SP4"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-15-sp4-image-end-of-support"
    },
    {
      "slug": "aws-eks-kubernetes-1-34-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.34 end of standard support",
      "summary": "End of standard support date for Kubernetes 1.34 on Amazon EKS: 2 Dec 2026. After that date the version enters extended support for 12 months, at an additional cost per cluster hour.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-02",
      "effective_precision": "day",
      "impact": "Once Kubernetes 1.34 is past the end of standard support date, it enters extended support for the next 12 months, at an additional cost per cluster hour.\n\n- Extended support is enabled by default.\n- Billing starts at the beginning of the day that the version reaches end of standard support, in the UTC+0 timezone.\n- A cluster whose upgrade policy has extended support disabled is automatically upgraded to the next Kubernetes version at the end of standard support.\n- Extended support cannot be disabled once a cluster has entered it.\n- A cluster not updated before the extended support period ends is automatically updated by Amazon EKS to the earliest supported version.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version. Then upgrade the control plane to a version in the standard support period, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n3. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n4. To stay on Kubernetes 1.34, keep the cluster upgrade policy set to EXTENDED. An additional cost applies to clusters running in extended support, see the [pricing page](https://aws.amazon.com/eks/pricing/).\n5. To avoid extended support, set the upgrade policy to standard support while the cluster is still on standard support, as described in [Disable EKS extended support](https://docs.aws.amazon.com/eks/latest/userguide/disable-extended-support.html). The cluster is then auto upgraded at the end of standard support.",
      "replacement": null,
      "affected_versions": [
        "1.34"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.34",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-34-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-1-1-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.1.1.0 end of life",
      "summary": "End of life date for Engine version 1.1.1.0 on Amazon Neptune: 4 Dec 2026. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-04",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.1.1.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.1.1.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-1-1-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-2-0-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.2.0.0 end of life",
      "summary": "End of life date for Engine version 1.2.0.0 on Amazon Neptune: 4 Dec 2026. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-04",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.2.0.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.2.0.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-2-0-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-2-0-1-end-of-support",
      "title": "Amazon Neptune: Engine version 1.2.0.1 end of life",
      "summary": "End of life date for Engine version 1.2.0.1 on Amazon Neptune: 4 Dec 2026. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-04",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.2.0.1"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.2.0.1",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-2-0-1-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-2-0-2-end-of-support",
      "title": "Amazon Neptune: Engine version 1.2.0.2 end of life",
      "summary": "End of life date for Engine version 1.2.0.2 on Amazon Neptune: 4 Dec 2026. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-04",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.2.0.2"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.2.0.2",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-2-0-2-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-2-1-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.2.1.0 end of life",
      "summary": "End of life date for Engine version 1.2.1.0 on Amazon Neptune: 4 Dec 2026. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-04",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.2.1.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.2.1.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-2-1-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-2-1-1-end-of-support",
      "title": "Amazon Neptune: Engine version 1.2.1.1 end of life",
      "summary": "End of life date for Engine version 1.2.1.1 on Amazon Neptune: 4 Dec 2026. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-04",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.2.1.1"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.2.1.1",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-2-1-1-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-2-1-2-end-of-support",
      "title": "Amazon Neptune: Engine version 1.2.1.2 end of life",
      "summary": "End of life date for Engine version 1.2.1.2 on Amazon Neptune: 4 Dec 2026. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-04",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.2.1.2"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.2.1.2",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-2-1-2-end-of-support"
    },
    {
      "slug": "azure-aks-azure-linux-os-guard-retirement",
      "title": "Azure Kubernetes Service: Azure Linux with OS Guard retirement",
      "summary": "End of support date for Azure Linux with OS Guard in Azure Kubernetes Service: 10 Dec 2026. From that date, new Azure Linux with OS Guard node pools cannot be created and existing ones get no security patches. AKS removes the node images on March 10, 2027.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "os_image",
      "type": "retirement",
      "announced_date": "2026-09-11",
      "effective_date": "2026-12-10",
      "effective_precision": "day",
      "impact": "From 10 Dec 2026, new Azure Linux with OS Guard (preview) node pools cannot be created, AKS does not produce new node images for affected node pools, and existing node pools do not receive security patches. On March 10, 2027, AKS removes the Azure Linux with OS Guard node images. After the images are removed, scaling and remediation operations, including reimage and redeploy operations, fail for affected node pools.",
      "migration_path": "1. Option one: migrate an existing Azure Linux with OS Guard node pool in place by following the [Migrate nodes to Azure Container Linux for Azure Kubernetes Service documentation](https://learn.microsoft.com/en-us/azure/azure-linux/tutorial-migrate-azure-container-linux-aks). This operation performs a standard node image upgrade.\n2. Option two: create a new Azure Container Linux node pool, migrate and validate workloads, and then delete the Azure Linux with OS Guard node pool. Follow [Add Azure Container Linux node pools and remove existing node pools](https://learn.microsoft.com/azure/azure-linux/tutorial-migrate-azure-container-linux-aks#add-acl-node-pools-and-remove-existing-node-pools).\n3. For other available options, see the [AKS node operating system](https://learn.microsoft.com/azure/aks/core-aks-concepts#nodes-and-node-pools:~:text=in%20AKS.-,OS,-AKS%20supports%20two).",
      "replacement": "Azure Container Linux",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=571257",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-linux/tutorial-migrate-azure-container-linux-aks",
        "https://learn.microsoft.com/azure/azure-linux/tutorial-migrate-azure-container-linux-aks#add-acl-node-pools-and-remove-existing-node-pools",
        "https://learn.microsoft.com/azure/aks/core-aks-concepts#nodes-and-node-pools:~:text=in%20AKS.-,OS,-AKS%20supports%20two",
        "https://github.com/Azure/AKS"
      ],
      "vendor_ref": "571257",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-azure-linux-os-guard-retirement"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-gemini-live-2-5-flash-0ba631-retirement",
      "title": "Gemini Enterprise Agent Platform: gemini-live-2.5-flash-native-audio retirement",
      "summary": "Retirement date for gemini-live-2.5-flash-native-audio on Gemini Enterprise Agent Platform: 13 Dec 2026. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2026-12-13",
      "effective_precision": "day",
      "impact": "Google lists gemini-live-2.5-flash-native-audio with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": "gemini-3.8-live",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-gemini-live-2-5-flash-0ba631-retirement"
    },
    {
      "slug": "aws-rds-mariadb-10-6-end-of-support",
      "title": "Amazon RDS for MariaDB: MariaDB 10.6 end of standard support",
      "summary": "RDS end of standard support date for MariaDB 10.6 on Amazon RDS for MariaDB: 31 Dec 2026. AWS lists this date so that testing and upgrade cycles can be planned around it.",
      "cloud": "aws",
      "service": "Amazon RDS for MariaDB",
      "service_slug": "rds-mariadb",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2026-12-31",
      "effective_precision": "day",
      "impact": "31 Dec 2026 is the RDS end of standard support date that AWS lists for MariaDB 10.6. The AWS page does not state what happens to DB instances still on MariaDB 10.6 after that date.\n\n- RDS for MariaDB major versions remain available at least until community end of life for the corresponding community version.\n- A date with only a month and a year is approximate and is replaced by an exact date once known.\n- If AWS extends support for a version beyond the stated date, it plans to update its version table with the later date.\n- Deprecation policy: see the [Amazon RDS FAQs](https://aws.amazon.com/rds/faqs/).",
      "migration_path": "1. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command.\n2. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n3. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MariaDB](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MariaDB.Major.html). Major version upgrades are performed manually.\n4. Plan for downtime: database engine upgrades require downtime, and its duration varies with the size of the DB instance.\n5. Downtime for the upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. The engine cannot be reverted after the upgrade completes. To return to the previous version, restore the first DB snapshot taken during the upgrade to a new DB instance. Amazon RDS only takes these snapshots if the backup retention period of the DB instance is greater than 0.",
      "replacement": null,
      "affected_versions": [
        "10.6"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MariaDB.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mariadb"
      ],
      "vendor_ref": "amazon-rds-mariadb@10.6",
      "last_checked_at": "2026-11-12T09:55:39.673Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mariadb-10-6-end-of-support"
    },
    {
      "slug": "azure-app-service-php-8-2-end-of-support",
      "title": "Azure App Service: PHP 8.2 end of extended support",
      "summary": "End of extended support date for PHP 8.2 on Azure App Service: 31 Dec 2026. Apps keep running after that date but stop receiving security updates and customer service for PHP 8.2.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2024-09-26",
      "effective_date": "2026-12-31",
      "effective_precision": "day",
      "impact": "Apps hosted on App Service that use PHP 8.2 continue to run after the end of extended support date. After that date, security updates are no longer available for PHP 8.2. After that date, Microsoft no longer provides customer service for PHP 8.2.",
      "migration_path": "Upgrade apps to PHP 8.3, as the announcement title states. For details, see [Learn more](https://go.microsoft.com/fwlink/?linkid=2287013).",
      "replacement": "PHP 8.3",
      "affected_versions": [
        "8.2"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=php-82-app-svc",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy"
      ],
      "vendor_ref": "php-82-app-svc",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-php-8-2-end-of-support"
    },
    {
      "slug": "azure-fxt-edge-filer-end-of-support",
      "title": "Azure FXT Edge Filer end of support",
      "summary": "Retirement date for Azure FXT Edge Filer: 31 Dec 2026. After 2026 there is no hardware or software support. Microsoft does not disable the devices, and customers may continue to use them.",
      "cloud": "azure",
      "service": "Azure FXT Edge Filer",
      "service_slug": "fxt-edge-filer",
      "category": "service",
      "type": "end_of_support",
      "announced_date": "2023-09-15",
      "effective_date": "2026-12-31",
      "effective_precision": "day",
      "impact": "After 2026, there is no hardware or software support for FXT Edge Filers. Through 2026, hardware and software support is for customers who maintain support licenses, and the last yearly support license renewal was December 2025. Orders for FXT Edge Filers were accepted through December 2023. Microsoft does not disable the devices, and customers may continue to use the hardware.",
      "migration_path": "Microsoft has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=fxtretirement",
      "extra_source_urls": [],
      "vendor_ref": "fxtretirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-fxt-edge-filer-end-of-support"
    },
    {
      "slug": "azure-devops-server-tfs-2017-end-of-support",
      "title": "TFS 2017 end of support",
      "summary": "endoflife.date lists 11 Jan 2027 as the end of security support for TFS 2017. Microsoft publishes the specific end of support dates and details in its Lifecycle product search.",
      "cloud": "azure",
      "service": "Azure DevOps Server",
      "service_slug": "devops-server",
      "category": "other",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-01-11",
      "effective_precision": "day",
      "impact": "Prior to 2019, the product was known as Team Foundation Server (TFS). Microsoft publishes specific end of support dates and details in its [Lifecycle product search](https://learn.microsoft.com/en-us/lifecycle/products/). For releases under the Microsoft Fixed Lifecycle Policy, the policy states that, to be eligible for support, customers may be required to deploy the latest Service Pack or update.",
      "migration_path": "Follow [Upgrade your deployment to the latest version of Azure DevOps Server](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started):\n\n1. Have your Azure DevOps Server license and product key ready, and administrative access and credentials for the service accounts.\n2. Review the [system requirements](https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server) for the target server, which may include updates to operating systems, SQL Server versions, and hardware.\n3. Create a complete and consistent set of backups for all Azure DevOps databases.\n4. If you upgrade in place, perform a trial in a pre-production environment: [Pre-production dry run](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-server).\n5. Plan for downtime. The deployment is offline during the upgrade.",
      "replacement": null,
      "affected_versions": [
        "2017"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/visual-studio-team-foundation-server-2017",
      "extra_source_urls": [
        "https://endoflife.date/azure-devops-server"
      ],
      "vendor_ref": "azure-devops-server@2017",
      "last_checked_at": "2026-11-12T09:55:46.498Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-devops-server-tfs-2017-end-of-support"
    },
    {
      "slug": "azure-batch-windows-server-2016-images-end-of-support",
      "title": "Azure Batch: Windows Server 2016 Marketplace images end of support",
      "summary": "End of support date for Windows Server 2016 Marketplace images on Azure Batch pools: 12 Jan 2027. Microsoft states that the Windows Server 2016 Marketplace images are then no longer available.",
      "cloud": "azure",
      "service": "Azure Batch",
      "service_slug": "batch",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": "2026-03-16",
      "effective_date": "2027-01-12",
      "effective_precision": "day",
      "impact": "Azure Batch support for Windows Server 2016 ends on the end of support date. Microsoft states that Marketplace images for Windows Server 2016, published under the MicrosoftWindowsServer offer with the name WindowsServer, are then no longer available. Affected are Batch pools based on Windows Server 2016 Marketplace images; the relevant image SKUs include 2016-datacenter, 2016-datacenter-gensecond, 2016-datacenter-gs, 2016-datacenter-smalldisk, 2016-datacenter-smalldisk-g2, 2016-datacenter-with-containers and 2016-datacenter-with-containers-gs. Microsoft describes the required migration as a way to avoid service disruptions.",
      "migration_path": "1. Migrate Batch pools that use the affected Marketplace images to a supported Windows Server image by 12 Jan 2027. Microsoft recommends the latest version of Windows Server, if possible.\n2. Follow the Microsoft article on how to [update pool properties](https://learn.microsoft.com/azure/batch/batch-pool-update-properties) for migration guidance.\n3. Test the migration before updating production configurations.\n4. If the workload requires Windows Server 2016 after 12 Jan 2027, it may be possible to migrate to a Windows Server 2016 custom image with appropriate licensing and Azure ESU. See this [article](https://learn.microsoft.com/azure/batch/batch-sig-images). Azure Batch support for Windows Server 2016 still ends on 12 Jan 2027.",
      "replacement": "A supported Windows Server image",
      "affected_versions": [
        "2016"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=549077",
      "extra_source_urls": [
        "https://learn.microsoft.com/lifecycle/products/windows-server-2016",
        "https://learn.microsoft.com/azure/batch/batch-sig-images",
        "https://learn.microsoft.com/azure/batch/batch-pool-update-properties"
      ],
      "vendor_ref": "549077",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-batch-windows-server-2016-images-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-windows-server-2016-image-end-of-support",
      "title": "Compute Engine: Windows Server 2016 image end of support",
      "summary": "EOS and image deprecation date for the Windows Server 2016 public image on Compute Engine: 12 Jan 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-01-12",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Windows Server 2016 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Windows Server 2016"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "windows-2016",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-windows-server-2016-image-end-of-support"
    },
    {
      "slug": "azure-hpc-pack-2016-end-of-support",
      "title": "HPC Pack 2016 end of support",
      "summary": "End of support date for HPC Pack 2016: 12 Jan 2027. Microsoft retires the product on that date. It can still be used afterward but no longer receives support or updates from Microsoft.",
      "cloud": "azure",
      "service": "HPC Pack",
      "service_slug": "hpc-pack",
      "category": "other",
      "type": "end_of_support",
      "announced_date": "2024-03-22",
      "effective_date": "2027-01-12",
      "effective_precision": "day",
      "impact": "HPC Pack 2016 follows the Fixed Lifecycle Policy and is no longer supported from 12 Jan 2027. HPC Pack 2016 can still be used after that date, but it no longer receives updates from Microsoft.",
      "migration_path": "1. Follow Microsoft's [steps](https://learn.microsoft.com/en-us/powershell/high-performance-computing/hpc-pack-2016-to-hpc-pack-2019-retirement-migration-guide?view=hpc16-ps) to migrate to HPC Pack 2019.\n2. Stop the Azure deployment and create new ones with HPC Pack 2019 after 12 Jan 2027.",
      "replacement": "HPC Pack 2019",
      "affected_versions": [
        "2016"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=hpc-pack-2016-will-be-retired-on-12-january-2027",
      "extra_source_urls": [
        "https://learn.microsoft.com/lifecycle/products/hpc-pack-2016",
        "https://learn.microsoft.com/en-us/powershell/high-performance-computing/hpc-pack-2016-to-hpc-pack-2019-retirement-migration-guide?view=hpc16-ps"
      ],
      "vendor_ref": "hpc-pack-2016-will-be-retired-on-12-january-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-hpc-pack-2016-end-of-support"
    },
    {
      "slug": "multi-windows-server-2016-end-of-support",
      "title": "Windows Server 2016 end of support",
      "summary": "End of support for Windows Server 2016: 12 Jan 2027. Once a release reaches the end of support, security updates and bulletins end.",
      "cloud": "multi",
      "service": "Windows Server",
      "service_slug": "windows-server",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-01-12",
      "effective_precision": "day",
      "impact": "Windows Server Long Term Servicing Channel releases have a minimum of 10 years of support: five years of mainstream support and five years of extended support, which includes regular security updates. endoflife.date states that each Semi-Annual Channel release is supported for 18 months from the initial release, and that each Annual Channel release has 18 months of mainstream support plus 6 months of extended support. Once a release reaches the end of support, security updates and bulletins end, which Microsoft states can cause security or compliance issues.\n\n- endoflife.date states that for some releases, customers have the option to purchase Extended Security Updates. See [Lifecycle FAQ - Extended Security Updates](https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates).\n- Extended Security Updates do not include new features, customer-requested nonsecurity hotfixes, or design change requests.",
      "migration_path": "1. Choose an upgrade method with [Plan your Windows Server upgrade](https://learn.microsoft.com/en-us/windows-server/get-started/install-upgrade-migrate): in-place upgrade, clean install, migration, or cluster rolling upgrade.\n2. Check the [supported paths table](https://learn.microsoft.com/en-us/windows-server/get-started/install-upgrade-migrate#supported-in-place-upgrade-paths-by-version) and the [role and feature migration matrix](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-migrate-roles-features) for your configuration.\n3. Get a valid product key and activation method for the target version. Each Windows Server upgrade requires a separate license.\n4. Back up your system and important files before the in-place upgrade, clean install, or migration.\n5. For an in-place upgrade, follow [Perform an in-place upgrade of Windows Server](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-in-place).",
      "replacement": null,
      "affected_versions": [
        "2016"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/windows-server-2016",
      "extra_source_urls": [
        "https://endoflife.date/windows-server"
      ],
      "vendor_ref": "windows-server@2016",
      "last_checked_at": "2026-11-12T09:55:50.558Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-windows-server-2016-end-of-support"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-gemini-3-7-flash-retirement",
      "title": "Gemini Enterprise Agent Platform: gemini-3.7-flash retirement",
      "summary": "Retirement date for gemini-3.7-flash on Gemini Enterprise Agent Platform: 28 Jan 2027. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-01-28",
      "effective_precision": "day",
      "impact": "Google lists gemini-3.7-flash with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": "gemini-3.8-flash",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-gemini-3-7-flash-retirement"
    },
    {
      "slug": "aws-elasticache-redis-oss-6-end-of-support",
      "title": "Amazon ElastiCache for Redis OSS: Redis OSS 6 end of standard support",
      "summary": "End of standard support date for Redis OSS 6 on Amazon ElastiCache: 31 Jan 2027. Caches still running it after that date move to ElastiCache Extended Support, which carries an additional charge.",
      "cloud": "aws",
      "service": "Amazon ElastiCache for Redis OSS",
      "service_slug": "elasticache-redis",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-01-31",
      "effective_precision": "day",
      "impact": "After 31 Jan 2027, caches that still run Redis OSS 6 move to ElastiCache Extended Support automatically, at an additional cost. Extended Support provides:\n\n- Security updates for critical and high CVEs for the cache and cache engine\n- Bug fixes and patches for critical issues\n- Support cases and troubleshooting help within the standard ElastiCache service level agreement\n\nAWS states that customers are notified before Extended Support pricing starts. Extended Support lasts up to 3 years and covers only the latest supported patch version of each major Redis OSS version. After it ends, ElastiCache attempts to upgrade the engine to a newer version under standard support.",
      "migration_path": "1. Upgrade to a supported version. AWS states that you can opt out of Extended Support at any time this way. The end of standard support and end of Extended Support dates are in the [ElastiCache versions for Redis OSS end of life schedule](https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/engine-versions.html#deprecated-engine-versions).\n2. On a node-based cluster, start the upgrade by modifying the cluster or replication group and specifying a new engine version. See [Modifying a replication group](https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/Replication.Modify.html).\n3. Test the new version with your application before deploying it in production.\n4. AWS states that some existing ElastiCache for Redis OSS engines can also be upgraded to a Valkey engine.",
      "replacement": null,
      "affected_versions": [
        "6"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/engine-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-elasticache-redis"
      ],
      "vendor_ref": "amazon-elasticache-redis@6",
      "last_checked_at": "2026-11-12T09:55:41.392Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-elasticache-redis-oss-6-end-of-support"
    },
    {
      "slug": "azure-blueprints-retirement",
      "title": "Azure Blueprints retirement",
      "summary": "Retirement date for Azure Blueprints: 31 Jan 2027, after a phased retirement that began July 31, 2026. The API, Azure CLI and PowerShell commands stop working, and blueprint definitions, versions and assignments not exported are deleted.",
      "cloud": "azure",
      "service": "Azure Blueprints",
      "service_slug": "blueprints",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-06-25",
      "effective_date": "2027-01-31",
      "effective_precision": "day",
      "impact": "From 31 Jan 2027, the Blueprints API no longer responds, Azure CLI and PowerShell commands stop functioning, and Azure Blueprints is removed from the Azure portal. Blueprint definitions, versions and assignments that were not exported are deleted automatically, while resources created through blueprints are not deleted. The blueprint locks \"Do Not Delete\" and \"Read Only\" on resources stop functioning, which effectively sets them to a \"Don't Lock\" state. Microsoft extended the retirement from the July 11, 2026 date it announced in September 2023 and phased it: creating new blueprint definitions and versions is blocked from July 31, 2026, modifying definitions and creating assignments from October 31, 2026, and modifying existing assignments from December 31, 2026.",
      "migration_path": "1. Go to the [Blueprints portal](https://aka.ms/blueprintsportal) to identify impacted blueprint artifacts and export the data before the retirement date.\n2. [Migrate](https://aka.ms/AzureBlueprintsMigration) to Azure deployment stacks for resource grouping, lifecycle and \"deny assignments\" enforcement.\n3. Publish definitions as template specs, or store them in a template folder in Git for versioning.\n4. Complete these changes ahead of the phased dates: July 31, 2026, October 31, 2026 and December 31, 2026. Microsoft states that Blueprints functionality decreases as the [retirement](https://aka.ms/AzureBlueprintsRetirement) phases progress.",
      "replacement": "Azure deployment stacks",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=564806",
      "extra_source_urls": [
        "https://aka.ms/AzureBlueprintsMigration",
        "https://aka.ms/blueprintsportal",
        "https://aka.ms/AzureBlueprintsRetirement"
      ],
      "vendor_ref": "564806",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-blueprints-retirement"
    },
    {
      "slug": "azure-mysql-8-0-end-of-support",
      "title": "Azure Database for MySQL: MySQL 8.0 end of standard support",
      "summary": "Azure Standard Support End Date for MySQL 8.0 on Azure Database for MySQL: 31 Jan 2027. After that date, servers still running the version are automatically enrolled in Extended Support and charged for it.",
      "cloud": "azure",
      "service": "Azure Database for MySQL",
      "service_slug": "mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-01-31",
      "effective_precision": "day",
      "impact": "After the Standard Support end date, servers running MySQL 8.0 are automatically enrolled in Extended Support and automatically charged for it.\n\n- Extended Support provides critical security updates for up to three years after the end of Standard Support.\n- New features and minor version upgrades might not be guaranteed.\n- The charge is billed per vCore per hour, so read replicas and HA-enabled servers are billed for the additional vCores they consume.\n- Servers in stopped state are not charged for Extended Support.",
      "migration_path": "1. Choose a target MySQL version that is still within Standard Support. Upgrading to it avoids Extended Support charges.\n2. Upgrade read replicas that use an older MySQL version before upgrading the primary server.\n3. Check schema compatibility with the target version using the Validate feature in the Azure portal. Validation locks tables, and the page directs large-scale production environments to Oracle's client-side upgrade checker tool. Verify deprecated sql_mode values and remove or deselect them in the Server Parameters pane before upgrading, to avoid deployment failure.\n4. Ensure there are no active or pending XA transactions on the database. Ongoing XA transactions can cause the upgrade to fail.\n5. Trigger an on-demand backup before the major version upgrade of a production server, and perform the upgrade first on a restored server copy rather than on production directly.\n6. In the Azure portal, open the server, and on the Overview page select Upgrade. The major version upgrade is irreversible. Burstable SKU servers use a separate workflow that first upgrades the compute tier to a General-Purpose SKU. See [Major version upgrade in Azure Database for MySQL](https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-upgrade).",
      "replacement": null,
      "affected_versions": [
        "8.0"
      ],
      "source_url": "https://learn.microsoft.com/azure/mysql/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-mysql"
      ],
      "vendor_ref": "azure-database-for-mysql@8.0",
      "last_checked_at": "2026-11-12T09:55:37.239Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-mysql-8-0-end-of-support"
    },
    {
      "slug": "azure-postgresql-14-end-of-support",
      "title": "Azure Database for PostgreSQL: PostgreSQL 14 end of standard support",
      "summary": "Azure Standard Support End Date for PostgreSQL 14 on Azure Database for PostgreSQL: 31 Jan 2027. Once the Azure Standard Support period ends, eligible servers still running the version are automatically enrolled in extended support.",
      "cloud": "azure",
      "service": "Azure Database for PostgreSQL",
      "service_slug": "postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-01-31",
      "effective_precision": "day",
      "impact": "Once the Azure Standard Support period ends, an eligible server still running PostgreSQL 14 is automatically enrolled in extended support. The eligible versions table lists PostgreSQL 11, 12, 13 and 14.\n\n- Extended support provides security patches, critical bug fixes and technical support for up to three extra years. It does not include new features, performance enhancements or support for minor version upgrades.\n- Charges apply after any applicable grace period unless the server is upgraded to a supported version, and only to servers in a Succeeded (running) state. A one-month grace period is provided for versions 11, 12 and 13. A server that regional capacity constraints prevent from upgrading might be temporarily excluded from billing.\n- The version policy page lists restrictions that apply after the retirement date of a version, without stating whether that date is 31 Jan 2027: new servers cannot be created on a retired version, while point-in-time recoveries and read replicas of existing servers remain possible.\n- The same page says that when the community retires a version, Azure stops applying bug or security patches to the database engine. The extended support page lists security patches and critical bug fixes as part of extended support.",
      "migration_path": "1. Run the upgrade validation checks in the Azure portal or with the Azure CLI. See [Run upgrade validation checks](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/how-to-run-upgrade-validation-checks).\n2. Resolve any blocking issues the checks report, then rerun validation.\n3. Ensure the server has at least 10-20% free storage available before starting the upgrade.\n4. If the server uses geo-replication, delete the read replica (including any cascading read replica) before upgrading the primary server. The replica can be re-created after the upgrade.\n5. Run an in-place major version upgrade to a PostgreSQL version that Azure currently supports. The service can skip versions and upgrade directly to a later version. Servers that use TimescaleDB are limited to specific source and target version combinations, and an upgrade from PostgreSQL 11 first requires SCRAM authentication to be configured. Once the server runs a supported version, extended support charges no longer apply. See [Major version upgrades](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-major-version-upgrade).\n6. Plan for the fact that there is no automated way to revert after a successful upgrade. A point-in-time recovery to a time before the upgrade restores the previous version on a new server.",
      "replacement": null,
      "affected_versions": [
        "14"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-postgresql"
      ],
      "vendor_ref": "azure-database-for-postgresql@14",
      "last_checked_at": "2026-11-12T09:55:36.471Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-postgresql-14-end-of-support"
    },
    {
      "slug": "gcp-bigquery-shopify-connector-field-support-removal-breaking-change",
      "title": "BigQuery: Data Transfer Service Shopify connector field support removal",
      "summary": "From 31 Jan 2027, the BigQuery Data Transfer Service for Shopify connector no longer supports the legacyMode field of the DeliveryProfile dataset schema and the permitSkuSharing field of the FulfillmentService dataset schema.",
      "cloud": "gcp",
      "service": "BigQuery",
      "service_slug": "bigquery",
      "category": "feature",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-01-31",
      "effective_precision": "day",
      "impact": "From 31 Jan 2027, the Shopify connector of the BigQuery Data Transfer Service no longer supports two fields. The fields are legacyMode in the DeliveryProfile dataset schema and permitSkuSharing in the FulfillmentService dataset schema. The change applies to all transfer configurations of the Shopify connector. Google states that it follows changes to the Shopify API.",
      "migration_path": "Google has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/release-notes#November_06_2026",
      "extra_source_urls": [
        "https://docs.cloud.google.com/bigquery/docs/shopify-transfer",
        "https://docs.cloud.google.com/bigquery/docs/transfer-changes#Jan31-shopify"
      ],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:14.506Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-bigquery-shopify-connector-field-support-removal-breaking-change"
    },
    {
      "slug": "aws-rds-postgresql-14-20-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14.20 end of standard support",
      "summary": "End of standard support date for PostgreSQL 14.20 on Amazon RDS for PostgreSQL: Feb 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-02-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Feb 2027 as the RDS end of standard support date of minor version 14.20. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "14.20"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@14.20",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-20-end-of-support"
    },
    {
      "slug": "gcp-security-command-center-data-security-posture-management-retirement",
      "title": "Security Command Center: Data Security Posture Management (DSPM) shutdown",
      "summary": "Data Security Posture Management (DSPM) in Security Command Center is scheduled for shutdown on or after 1 Feb 2027. Organizations that already use DSPM retain full access until shutdown. DSPM is no longer available to new organizations.",
      "cloud": "gcp",
      "service": "Security Command Center",
      "service_slug": "security-command-center",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-02-01",
      "effective_precision": "day",
      "impact": "Data Security Posture Management (DSPM) in Security Command Center is scheduled for shutdown on or after 1 Feb 2027, and is no longer available after the shutdown. Organizations that already have DSPM enabled retain full access until the shutdown. DSPM is no longer available to new organizations. Google lists September 14, 2026 as the deprecated date.",
      "migration_path": "Google points to alternative detection capabilities in the [Data security and privacy essentials framework](https://docs.cloud.google.com/security-command-center/docs/dspm-data-security#data-security-framework) section of the DSPM overview. For the cloud controls of the Data security and privacy essentials framework, that section lists the Compliance Manager and Sensitive Data Protection detectors that provide comparable detection capability when combined. The same page describes how to [correlate findings from Compliance Manager and Sensitive Data Protection](https://docs.cloud.google.com/security-command-center/docs/dspm-data-security#correlate-findings) on the same resource.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/release-notes#November_05_2026",
      "extra_source_urls": [
        "https://docs.cloud.google.com/security-command-center/docs/deprecations",
        "https://docs.cloud.google.com/security-command-center/docs/dspm-data-security#data-security-framework"
      ],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:14.506Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-security-command-center-data-security-posture-management-retirement"
    },
    {
      "slug": "gcp-gke-kubernetes-1-32-extended-support-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.32 end of extended support",
      "summary": "End of extended support date for GKE Kubernetes 1.32: 11 Feb 2027. From that date the minor version receives no security patches, and GKE upgrades Extended channel clusters still running it to the next minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-02-11",
      "effective_precision": "day",
      "impact": "At the end of extended support, GKE does not provide any patches for security fixes, and the minor version is considered unsupported. GKE upgrades clusters still running it to the next minor version.\n\n- The upgrade happens regardless of the cluster's use of deprecated features or APIs.\n- Maintenance exclusions cannot be configured past this date, except as a temporary, emergency measure with the \"No upgrades\" scope.\n- That exclusion can delay the upgrade for up to 90 days after the end of support date. Google does not recommend it.\n- Dates in the GKE release schedule are updated monthly and subject to change.",
      "migration_path": "1. Google does not recommend enrolling a cluster in the Extended channel without plans to move to the next minor version, because GKE eventually upgrades the cluster to newer minor versions.\n2. Around 2 months before the end of extended support, GKE begins upgrading clusters in the Extended channel to the next minor version, unless the cluster is using deprecated features or APIs.\n3. Maintenance exclusions can prevent minor version upgrades until the end of extended support. A temporary, emergency exclusion with the \"No upgrades\" scope can delay the upgrade for up to 90 days after the end of support date. After that exclusion expires, GKE upgrades the cluster.\n4. At the end of extended support, GKE upgrades all clusters still running the minor version, regardless of blocking issues. See [GKE minor version lifecycle](https://docs.cloud.google.com/kubernetes-engine/versioning#lifecycle).",
      "replacement": null,
      "affected_versions": [
        "1.32"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [],
      "vendor_ref": "gke@1.32",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-32-extended-support-end-of-support"
    },
    {
      "slug": "azure-deployment-environments-retirement",
      "title": "Azure Deployment Environments retirement",
      "summary": "Retirement date for Azure Deployment Environments: 22 Feb 2027. After retirement, the service is no longer available. Microsoft gives September 14, 2026 as the start of the closing-down process.",
      "cloud": "azure",
      "service": "Azure Deployment Environments",
      "service_slug": "deployment-environments",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-10-08",
      "effective_date": "2027-02-22",
      "effective_precision": "day",
      "impact": "After the retirement date, Azure Deployment Environments is no longer available. Microsoft gives September 14, 2026 as the start of the closing-down process. Microsoft asks customers to review all current Azure Deployment Environments usage across subscriptions, projects, templates, and deployment workflows. Microsoft asks customers to identify an alternative approach for environment provisioning and developer self-service before the retirement date.",
      "migration_path": "1. Inventory your current environments, templates, catalogs, and provisioning workflows.\n2. Determine the target platform or service that replaces Azure Deployment Environments for your organization.\n3. Test your migration path, including governance, access control, infrastructure-as-code compatibility, and developer workflow readiness.\n4. Communicate internal timelines to platform engineering teams, developers, and administrators.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=567934",
      "extra_source_urls": [],
      "vendor_ref": "567934",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-deployment-environments-retirement"
    },
    {
      "slug": "aws-aurora-postgresql-14-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 14 end of standard support",
      "summary": "Aurora end of standard support date for PostgreSQL 14 on Amazon Aurora PostgreSQL: 28 Feb 2027. After that date, a database can keep running this major version under RDS Extended Support, for an additional cost.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-02-28",
      "effective_precision": "day",
      "impact": "RDS Extended Support allows a database to keep running this major version after 28 Feb 2027, for an [additional cost](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html).\n\n- Aurora automatically enrolls a DB instance after that date if RDS Extended Support was enabled at creation or restoration.\n- It provides security updates for critical and high CVEs, bug fixes for critical issues, and support cases.\n- Charges apply only to certain minor versions. The [release calendar](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html) lists the eligible minor versions for each major version.\n- Enrollment can be changed at any time, at the cluster level. Disabling it after that date upgrades the instance or cluster automatically to the next supported major version.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "14"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@14",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-14-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-14-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14 end of standard support",
      "summary": "RDS end of standard support date for PostgreSQL 14 on Amazon RDS for PostgreSQL: 28 Feb 2027. A database can keep running this version past that date under RDS Extended Support, for an additional cost, until the RDS end of Extended Support date.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-02-28",
      "effective_precision": "day",
      "impact": "A database can continue running PostgreSQL 14 past the RDS end of standard support date under RDS Extended Support, for an additional cost (see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html)), until the RDS end of Extended Support date.\n\n- If RDS Extended Support was enabled when the DB instance was created or restored, Amazon RDS enrolls it automatically after the RDS end of standard support date, with no change to the database engine, uptime or performance.\n- RDS Extended Support provides security updates for critical and high CVEs, bug fixes and patches for critical issues, and the ability to open support cases.\n- If enrollment is disabled for a DB instance or DB cluster that is already past its standard support end date, it automatically upgrades to the next supported major version.\n- After the RDS end of Extended Support date, Amazon RDS automatically upgrades databases not yet on a supported major version.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. To stay on PostgreSQL 14 under RDS Extended Support, the enrollment status of an existing DB instance or DB cluster can be changed with the EngineLifecycleSupport parameter using the AWS CLI or RDS API. For Multi-AZ DB clusters, modify the setting at the cluster level. RDS Extended Support has an additional cost, see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "replacement": null,
      "affected_versions": [
        "14"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@14",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-14-21-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14.21 end of standard support",
      "summary": "End of standard support date for PostgreSQL 14.21 on Amazon RDS for PostgreSQL: 28 Feb 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-02-28",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 28 Feb 2027 as the RDS end of standard support date of minor version 14.21. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "14.21"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@14.21",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-21-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-14-22-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14.22 end of standard support",
      "summary": "End of standard support date for PostgreSQL 14.22 on Amazon RDS for PostgreSQL: 28 Feb 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-02-28",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 28 Feb 2027 as the RDS end of standard support date of minor version 14.22. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "14.22"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@14.22",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-22-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-14-23-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14.23 end of standard support",
      "summary": "End of standard support date for PostgreSQL 14.23 on Amazon RDS for PostgreSQL: 28 Feb 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-02-28",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 28 Feb 2027 as the RDS end of standard support date of minor version 14.23. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "14.23"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@14.23",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-23-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-14-24-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14.24 end of standard support",
      "summary": "End of standard support date for PostgreSQL 14.24 on Amazon RDS for PostgreSQL: 28 Feb 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-02-28",
      "effective_precision": "day",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists 28 Feb 2027 as the RDS end of standard support date of minor version 14.24. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "14.24"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@14.24",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-24-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-15-15-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15.15 end of standard support",
      "summary": "End of standard support date for PostgreSQL 15.15 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 15.15. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "15.15"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@15.15",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-15-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-15-16-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15.16 end of standard support",
      "summary": "End of standard support date for PostgreSQL 15.16 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 15.16. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "15.16"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@15.16",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-16-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-15-17-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15.17 end of standard support",
      "summary": "End of standard support date for PostgreSQL 15.17 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 15.17. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "15.17"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@15.17",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-17-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-11-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16.11 end of standard support",
      "summary": "End of standard support date for PostgreSQL 16.11 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 16.11. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "16.11"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@16.11",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-11-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-12-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16.12 end of standard support",
      "summary": "End of standard support date for PostgreSQL 16.12 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 16.12. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "16.12"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@16.12",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-12-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-13-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16.13 end of standard support",
      "summary": "End of standard support date for PostgreSQL 16.13 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 16.13. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "16.13"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@16.13",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-13-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-7-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17.7 end of standard support",
      "summary": "End of standard support date for PostgreSQL 17.7 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 17.7. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "17.7"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@17.7",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-7-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-8-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17.8 end of standard support",
      "summary": "End of standard support date for PostgreSQL 17.8 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 17.8. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "17.8"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@17.8",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-8-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-9-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17.9 end of standard support",
      "summary": "End of standard support date for PostgreSQL 17.9 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 17.9. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "17.9"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@17.9",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-9-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-18-1-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 18.1 end of standard support",
      "summary": "End of standard support date for PostgreSQL 18.1 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 18.1. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "18.1"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@18.1",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-18-1-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-18-2-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 18.2 end of standard support",
      "summary": "End of standard support date for PostgreSQL 18.2 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 18.2. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "18.2"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@18.2",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-18-2-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-18-3-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 18.3 end of standard support",
      "summary": "End of standard support date for PostgreSQL 18.3 on Amazon RDS for PostgreSQL: Mar 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Mar 2027 as the RDS end of standard support date of minor version 18.3. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "18.3"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@18.3",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-18-3-end-of-support"
    },
    {
      "slug": "azure-blob-storage-azurednszone-endpoints-retirement",
      "title": "Azure Blob Storage: AzureDnsZone endpoints (preview) retirement",
      "summary": "AzureDnsZone endpoints (preview) for Azure Blob storage accounts enter retirement in Mar 2027. Microsoft asks customers to use Standard endpoints for new and existing blob storage account deployments.",
      "cloud": "azure",
      "service": "Azure Blob Storage",
      "service_slug": "blob-storage",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-04-02",
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "The retirement affects customers using AzureDnsZone endpoints (preview) on Azure Blob storage accounts. Microsoft states that it removes the ability to create new storage accounts with AzureDnsZone endpoints in the months after the announcement, and gives no specific date. Existing storage accounts are not impacted and are not deleted. Microsoft asks customers to transition all new and existing blob storage account deployments to Standard endpoints by April 1, 2027.",
      "migration_path": "1. Identify storage accounts with AzureDnsZone endpoints using the Azure Resource Graph query given in the source.\n2. [Follow Microsoft's instructions](https://aka.ms/AzStorageAccountCreate) to update deployments to Standard endpoints.\n3. For questions, use [Microsoft Q&A](https://aka.ms/classicstorageaccountmigration), or create a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest) if you have a support plan.",
      "replacement": "Standard endpoints",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=558276",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/storage/common/storage-account-overview#azure-dns-zone-endpoints-preview",
        "https://aka.ms/AzStorageAccountCreate"
      ],
      "vendor_ref": "558276",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-blob-storage-azurednszone-endpoints-retirement"
    },
    {
      "slug": "azure-aks-kubernetes-1-32-lts-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.32 LTS end of life",
      "summary": "LTS end of life date for Kubernetes 1.32 on Azure Kubernetes Service: Mar 2027. For clusters with long-term support enabled, support for the version continues only until that date. After it, those clusters must move to the next supported LTS version.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "After the LTS end of life date, long-term support for Kubernetes 1.32 ends. LTS-enabled clusters must then be upgraded to the next supported LTS version.\n\n- If a cluster is not upgraded, AKS upgrades it to the next supported LTS version through a platform-initiated upgrade. The cluster is not dropped to a community-supported version.\n- The LTS page places this after the 60-day grace period that follows the LTS end of life date. For the initial rollout, the grace period is the window through May 31, 2027, and no platform-initiated upgrade starts before June 1, 2027. After the initial rollout, every end-of-support event has a 60-day grace period before platform-initiated upgrades begin.\n- Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget.\n- The platform-initiated upgrade month in the AKS LTS release calendar is a planning estimate, not an exact upgrade date.",
      "migration_path": "1. List the versions AKS offers as upgrade targets with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. Test the workloads against deprecated APIs and other breaking changes between the current and target versions.\n3. Upgrade to an offered higher LTS version with `az aks upgrade --resource-group <resource-group-name> --name <cluster-name> --kubernetes-version <lts-kubernetes-version>`. An LTS cluster can skip minor versions when the upgrade satisfies version-skew requirements and validation checks. See [Long-term support for AKS versions](https://learn.microsoft.com/en-us/azure/aks/long-term-support).\n4. If the cluster is already past its LTS end of life date, skipping minor versions is conditional: the target must be listed by AKS and satisfy validation checks. AKS allows this upgrade but treats it as an unsupported recovery path.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To leave LTS instead, move the cluster to the Free or Standard tier and select the KubernetesOfficial support plan. This is possible while the cluster's Kubernetes version is still in community support. After that version exits community support, first upgrade the cluster to a community-supported version.",
      "replacement": "Next supported AKS LTS version",
      "affected_versions": [
        "1.32"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.32",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-32-lts-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-35-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.35 end of life",
      "summary": "End of life date for Kubernetes 1.35 on Azure Kubernetes Service: Mar 2027. After that date, community support for the version ends and clusters not enrolled in long-term support enter platform support, which covers AKS and Azure platform issues only.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "After the end of life date, community support for Kubernetes 1.35 ends. Clusters not enrolled in long-term support enter platform support.\n\n- Platform support covers AKS and Azure platform issues only, not Kubernetes functionality and components. New clusters cannot be created during the platform support period.\n- There is a 60-day platform support grace period after the published end of life date to upgrade to a supported minor version. For the initial rollout, the grace period is the window through May 31, 2027.\n- After the grace period, the cluster is eligible for a platform-initiated upgrade to the lowest supported community minor version. No such upgrade starts before June 1, 2027. Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget. Its month in the release calendar is a planning estimate, not an exact date.\n- Regional version removal can happen at a different time from the published date.",
      "migration_path": "1. List the versions AKS offers for the cluster with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. While the cluster is a supported non-LTS cluster, upgrade one minor version at a time. Minor versions cannot be skipped.\n3. Upgrade the control plane and all node pools with `az aks upgrade`, as described in [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n4. If the cluster is already on an unsupported version, use the oldest supported GA target that AKS offers and perform a full-cluster upgrade. Control-plane-only upgrades are not supported for this path. The version-skipping table in [Supported Kubernetes versions in Azure Kubernetes Service (AKS)](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions) labels this an unsupported recovery path: AKS allows the upgrade to proceed, but it is not supported and might carry risks. The platform support table on the same page lists upgrades from an N-3 version to a supported version as supported.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To get extended support for the version instead, enable [long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support). This requires moving the cluster to the Premium tier and explicitly selecting the LTS support plan. Microsoft-managed Calico is not supported in LTS. Once community support for the version has ended, LTS cannot be disabled for that version.",
      "replacement": null,
      "affected_versions": [
        "1.35"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.35",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-35-end-of-support"
    },
    {
      "slug": "azure-aks-windows-server-2022-retirement",
      "title": "Azure Kubernetes Service: Windows Server 2022 retirement",
      "summary": "Retirement date for Windows Server 2022 on AKS: Mar 2027, when Kubernetes 1.34 reaches the end of platform support. Windows Server 2022 node pools cannot be created on Kubernetes 1.35 and above.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "os_image",
      "type": "retirement",
      "announced_date": "2024-03-29",
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "Windows Server 2022 is retired on AKS when Kubernetes 1.34 reaches the end of platform support. After the retirement date, Windows Server 2022 is not supported. Windows Server 2022 node pools cannot be created on Kubernetes 1.35 and above. Until the retirement date, Windows Server 2022 can still be used on Kubernetes version 1.34 and below.",
      "migration_path": "1. Choose a supported Windows Server version: Windows Server 2025 or Windows Server Annual Channel.\n2. Follow the steps in the [AKS documentation](https://aka.ms/aks/ws2019-migration) to upgrade to that version before the retirement date.",
      "replacement": "Windows Server 2025 or Windows Server Annual Channel",
      "affected_versions": [
        "2022"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=ws2022-retirement-aks",
      "extra_source_urls": [
        "https://techcommunity.microsoft.com/t5/windows-server-news-and-best/introducing-windows-server-2025/ba-p/4026374",
        "https://techcommunity.microsoft.com/t5/windows-server-news-and-best/windows-server-annual-channel-for-containers/ba-p/3866248",
        "https://github.com/Azure/AKS/projects/1",
        "https://aka.ms/aks/ws2019-migration"
      ],
      "vendor_ref": "ws2022-retirement-aks",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-windows-server-2022-retirement"
    },
    {
      "slug": "gcp-compute-engine-cos-121-lts-image-end-of-support",
      "title": "Compute Engine: COS 121 LTS image end of support",
      "summary": "EOS and image deprecation date for the COS 121 LTS public image on Compute Engine: Mar 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of COS 121 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "COS 121 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "cos-121-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-cos-121-lts-image-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-go-1-24-retirement",
      "title": "Cloud Run: Go 1.24 decommission",
      "summary": "Decommission date for Go 1.24 on Cloud Run: 2 Mar 2027. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-03-02",
      "effective_precision": "day",
      "impact": "The decommission date of Go 1.24 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-go-1-24-retirement"
    },
    {
      "slug": "aws-neptune-engine-version-1-3-0-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.3.0.0 end of life",
      "summary": "End of life date for Engine version 1.3.0.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.3.0.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.3.0.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-3-0-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-3-1-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.3.1.0 end of life",
      "summary": "End of life date for Engine version 1.3.1.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.3.1.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.3.1.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-3-1-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-3-2-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.3.2.0 end of life",
      "summary": "End of life date for Engine version 1.3.2.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.3.2.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.3.2.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-3-2-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-3-2-1-end-of-support",
      "title": "Amazon Neptune: Engine version 1.3.2.1 end of life",
      "summary": "End of life date for Engine version 1.3.2.1 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.3.2.1"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.3.2.1",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-3-2-1-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-3-3-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.3.3.0 end of life",
      "summary": "End of life date for Engine version 1.3.3.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.3.3.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.3.3.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-3-3-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-3-4-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.3.4.0 end of life",
      "summary": "End of life date for Engine version 1.3.4.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.3.4.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.3.4.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-3-4-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-0-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.0.0 end of life",
      "summary": "End of life date for Engine version 1.4.0.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.0.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.0.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-0-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-1-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.1.0 end of life",
      "summary": "End of life date for Engine version 1.4.1.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.1.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.1.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-1-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-2-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.2.0 end of life",
      "summary": "End of life date for Engine version 1.4.2.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.2.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.2.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-2-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-3-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.3.0 end of life",
      "summary": "End of life date for Engine version 1.4.3.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.3.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.3.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-3-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-4-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.4.0 end of life",
      "summary": "End of life date for Engine version 1.4.4.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.4.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.4.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-4-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-5-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.5.0 end of life",
      "summary": "End of life date for Engine version 1.4.5.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.5.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.5.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-5-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-5-1-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.5.1 end of life",
      "summary": "End of life date for Engine version 1.4.5.1 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.5.1"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.5.1",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-5-1-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-6-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.6.0 end of life",
      "summary": "End of life date for Engine version 1.4.6.0 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.6.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.6.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-6-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-6-1-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.6.1 end of life",
      "summary": "End of life date for Engine version 1.4.6.1 on Amazon Neptune: 6 Mar 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-06",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.6.1"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.6.1",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-6-1-end-of-support"
    },
    {
      "slug": "azure-api-management-built-in-analytics-dashboards-retirement",
      "title": "Azure API Management: built-in analytics dashboards retirement",
      "summary": "Retirement date for the analytics dashboards built in to Azure API Management: 15 Mar 2027. The Azure Monitor-based dashboards that use Log Analytics workbooks take their place.",
      "cloud": "azure",
      "service": "Azure API Management",
      "service_slug": "api-management",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-03-29",
      "effective_date": "2027-03-15",
      "effective_precision": "day",
      "impact": "The analytics dashboards that are built in to Azure API Management are retired on 15 Mar 2027. Until the retirement date, both the built-in dashboards and the Azure Monitor-based dashboards are available in the Azure portal. Microsoft states that users who have not moved to the Azure Monitor-based dashboards lose access to API Management dashboards.",
      "migration_path": "Begin using the [Azure Monitor-based dashboards](https://aka.ms/builtinanalyticsv2-docs) in Azure API Management before the classic built-in dashboards are retired.",
      "replacement": "Azure Monitor-based dashboards (Log Analytics workbooks)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=begin-using-azure-monitor-based-dashboards-in-azure-api-management-before-the-builtin-analytics-dashboards-are-retired-on-15",
      "extra_source_urls": [
        "https://aka.ms/builtinanalyticsv2-docs"
      ],
      "vendor_ref": "begin-using-azure-monitor-based-dashboards-in-azure-api-management-before-the-builtin-analytics-dashboards-are-retired-on-15",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-api-management-built-in-analytics-dashboards-retirement"
    },
    {
      "slug": "azure-application-gateway-waf-v2-configuration-retirement",
      "title": "Azure Application Gateway: WAF v2 Configuration retirement",
      "summary": "Retirement date for the Application Gateway WAF v2 Configuration: 15 Mar 2027. To continue using the service, Microsoft directs customers to switch to the Application Gateway WAF v2 Policy before that date.",
      "cloud": "azure",
      "service": "Azure Application Gateway",
      "service_slug": "application-gateway",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-03-15",
      "effective_date": "2027-03-15",
      "effective_precision": "day",
      "impact": "The Application Gateway WAF v2 Configuration is retired on the retirement date. Until that date, existing WAF v2 Configurations can still be used and receive support. Creating new Application Gateway WAF v2 Configurations is not supported after 15 March 2025. Microsoft states that the move from WAF Configuration to WAF Policy can be done without downtime.",
      "migration_path": "1. Switch from the WAF Configuration to the Application Gateway WAF v2 Policy before the retirement date.\n2. Follow Microsoft's [migration instructions](https://aka.ms/ConfigUpgrade) for the change.",
      "replacement": "Application Gateway WAF v2 Policy",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=retirement-support-for-application-gateway-web-application-firewall-v2-configuration-is-ending",
      "extra_source_urls": [
        "https://aka.ms/ConfigUpgrade"
      ],
      "vendor_ref": "retirement-support-for-application-gateway-web-application-firewall-v2-configuration-is-ending",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-application-gateway-waf-v2-configuration-retirement"
    },
    {
      "slug": "azure-content-moderator-retirement",
      "title": "Azure Content Moderator retirement",
      "summary": "Retirement date for Azure Content Moderator: 15 Mar 2027. Existing resources keep working until that date. After it, Azure Content Moderator is not supported.",
      "cloud": "azure",
      "service": "Azure Content Moderator",
      "service_slug": "content-moderator",
      "category": "service",
      "type": "retirement",
      "announced_date": "2024-03-22",
      "effective_date": "2027-03-15",
      "effective_precision": "day",
      "impact": "Existing Azure Content Moderator projects operate and remain functional until 15 Mar 2027. After the retirement date, Azure Content Moderator is not supported. New Azure Content Moderator projects have not been available for creation since 15 March 2024.",
      "migration_path": "1. Review your current usage of Azure Content Moderator to understand the impact on your projects.\n2. Explore [Azure AI Content Safety](https://learn.microsoft.com/azure/ai-services/content-safety/overview) to cover your content moderation requirements.",
      "replacement": "Azure AI Content Safety",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-content-moderator-retirement",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/ai-services/content-safety/overview"
      ],
      "vendor_ref": "azure-content-moderator-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-content-moderator-retirement"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-gemini-2-5-flash-image-retirement",
      "title": "Gemini Enterprise Agent Platform: gemini-2.5-flash-image retirement",
      "summary": "Retirement date for gemini-2.5-flash-image on Gemini Enterprise Agent Platform: 15 Mar 2027. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-03-15",
      "effective_precision": "day",
      "impact": "Google lists gemini-2.5-flash-image with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": "gemini-3.1-flash-lite-image",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-gemini-2-5-flash-image-retirement"
    },
    {
      "slug": "azure-aks-ubuntu-20-04-node-pools-retirement",
      "title": "Azure Kubernetes Service: Ubuntu 20.04 node pools retirement",
      "summary": "Retirement date for Ubuntu 20.04 on Azure Kubernetes Service: 17 Mar 2027. From that date, AKS creates no new Ubuntu 20.04 node images, provides no security updates, and deletes existing node images.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "os_image",
      "type": "retirement",
      "announced_date": "2025-03-28",
      "effective_date": "2027-03-17",
      "effective_precision": "day",
      "impact": "From the retirement date, AKS no longer creates new node images for Ubuntu 20.04 or provides security updates. Existing node images are deleted. Node pools on Ubuntu 20.04 are unsupported and can no longer scale.",
      "migration_path": "1. Move node pools to a supported Ubuntu version by 17 Mar 2027. Microsoft lists the [newer supported versions](https://aka.ms/aks/supported-ubuntu-versions), including Ubuntu 22.04 and Ubuntu 24.04, and encourages a transition to Ubuntu 22.04 or later.\n2. For Ubuntu 20.04 with a [Confidential VM (CVM)](https://learn.microsoft.com/azure/aks/use-cvm): [upgrade](https://learn.microsoft.com/azure/aks/upgrade-aks-cluster?tabs=azure-cli) the Kubernetes version to 1.33 or later, where Ubuntu 24.04 is the default Ubuntu version for CVM workloads.\n3. For Ubuntu 20.04 with [Federal Information Process Standard (FIPS)](https://learn.microsoft.com/azure/aks/enable-fips-nodes): [upgrade](https://learn.microsoft.com/azure/aks/upgrade-aks-cluster?tabs=azure-cli) the Kubernetes version to 1.34 or later, where Ubuntu 22.04 is the default Ubuntu version for FIPS workloads.\n4. Microsoft's general instruction: upgrade the Kubernetes version to 1.34 or later by 17 Mar 2027 to avoid service disruptions and scaling restrictions and to remain supported. More detail: [AKS GitHub](https://aka.ms/aks/ubuntu2004-retirement).",
      "replacement": "Ubuntu 22.04 or Ubuntu 24.04",
      "affected_versions": [
        "20.04"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=485795",
      "extra_source_urls": [
        "https://aka.ms/aks/supported-ubuntu-versions",
        "https://learn.microsoft.com/azure/aks/use-cvm",
        "https://learn.microsoft.com/azure/aks/upgrade-aks-cluster?tabs=azure-cli",
        "https://learn.microsoft.com/azure/aks/enable-fips-nodes",
        "https://aka.ms/aks/ubuntu2004-retirement",
        "https://aka.ms/aks/ubuntu-version-retirement"
      ],
      "vendor_ref": "485795",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-ubuntu-20-04-node-pools-retirement"
    },
    {
      "slug": "aws-eks-kubernetes-1-32-extended-support-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.32 end of extended support",
      "summary": "End of extended support date for Kubernetes 1.32 on Amazon EKS: 23 Mar 2027. On that date, new clusters can no longer be created with this version, and Amazon EKS automatically updates control planes still on it at any time afterward.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-23",
      "effective_precision": "day",
      "impact": "On the end of extended support date, new Amazon EKS clusters can no longer be created with Kubernetes 1.32. Amazon EKS automatically updates existing control planes to the earliest supported version, at any time after that date.\n\n- Amazon EKS gives no specific time frame and sends no notification before the update.\n- The auto-upgrade includes only the Kubernetes control plane. Self-managed nodes and EKS managed node groups remain on the previous version.\n- EKS Auto Mode nodes may update automatically.\n- Fargate nodes and hybrid nodes are not upgraded with the control plane.\n- Clusters that were automatically upgraded at the end of extended support cannot be rolled back.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version.\n3. Proactively update the control plane without relying on the Amazon EKS automatic update process, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n4. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n5. If Amazon EKS updated the control plane automatically, manually update cluster add-ons and Amazon EC2 nodes.",
      "replacement": null,
      "affected_versions": [
        "1.32"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.32",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-32-extended-support-end-of-support"
    },
    {
      "slug": "aws-eks-kubernetes-1-35-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.35 end of standard support",
      "summary": "End of standard support date for Kubernetes 1.35 on Amazon EKS: 27 Mar 2027. After that date the version enters extended support for 12 months, at an additional cost per cluster hour.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-27",
      "effective_precision": "day",
      "impact": "Once Kubernetes 1.35 is past the end of standard support date, it enters extended support for the next 12 months, at an additional cost per cluster hour.\n\n- Extended support is enabled by default.\n- Billing starts at the beginning of the day that the version reaches end of standard support, in the UTC+0 timezone.\n- A cluster whose upgrade policy has extended support disabled is automatically upgraded to the next Kubernetes version at the end of standard support.\n- Extended support cannot be disabled once a cluster has entered it.\n- A cluster not updated before the extended support period ends is automatically updated by Amazon EKS to the earliest supported version.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version. Then upgrade the control plane to a version in the standard support period, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n3. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n4. To stay on Kubernetes 1.35, keep the cluster upgrade policy set to EXTENDED. An additional cost applies to clusters running in extended support, see the [pricing page](https://aws.amazon.com/eks/pricing/).\n5. To avoid extended support, set the upgrade policy to standard support while the cluster is still on standard support, as described in [Disable EKS extended support](https://docs.aws.amazon.com/eks/latest/userguide/disable-extended-support.html). The cluster is then auto upgraded at the end of standard support.",
      "replacement": null,
      "affected_versions": [
        "1.35"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.35",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-35-end-of-support"
    },
    {
      "slug": "azure-cache-for-redis-enterprise-retirement",
      "title": "Azure Cache for Redis: Enterprise and Enterprise Flash tiers retirement",
      "summary": "Retirement date for the Azure Cache for Redis Enterprise and Enterprise Flash tiers: 30 Mar 2027. New creation requests are blocked starting April 1, 2026. Microsoft recommends migrating workloads to Azure Managed Redis.",
      "cloud": "azure",
      "service": "Azure Cache for Redis",
      "service_slug": "cache-for-redis",
      "category": "service",
      "type": "retirement",
      "announced_date": "2025-10-08",
      "effective_date": "2027-03-30",
      "effective_precision": "day",
      "impact": "The Enterprise and Enterprise Flash tiers of Azure Cache for Redis are retired on the retirement date. New creation requests are blocked starting April 1, 2026. Remaining Enterprise and Enterprise Flash instances are migrated to Azure Managed Redis automatically after April 1, 2027. The source title and the source text state retirement dates that are one day apart.",
      "migration_path": "Migrate workloads to Azure Managed Redis by the retirement date. Microsoft links further detail under [Learn more](https://aka.ms/AzureCacheForRedisRetirement).",
      "replacement": "Azure Managed Redis",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=499606",
      "extra_source_urls": [
        "https://aka.ms/AzureCacheForRedisRetirement"
      ],
      "vendor_ref": "499606",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-cache-for-redis-enterprise-retirement"
    },
    {
      "slug": "azure-managed-grafana-essential-sku-retirement",
      "title": "Azure Managed Grafana: Essential SKU retirement",
      "summary": "Retirement date for the Azure Managed Grafana Essential SKU: 30 Mar 2027. On that date, all Azure Managed Grafana instances using the Essential SKU are deleted.",
      "cloud": "azure",
      "service": "Azure Managed Grafana",
      "service_slug": "managed-grafana",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-04-13",
      "effective_date": "2027-03-30",
      "effective_precision": "day",
      "impact": "The Azure Managed Grafana Essential SKU is retired on 30 Mar 2027. Until that date, existing Essential SKU resources can be used without disruption. On the retirement date, all Azure Managed Grafana instances using the Essential SKU are deleted. Microsoft names loss of access to dashboards as part of the service disruption that a transition before the retirement date avoids.",
      "migration_path": "Transition from the Essential SKU to the Azure Managed Grafana Standard SKU or to Azure Monitor Dashboards with Grafana before the retirement date. Microsoft states that migration guidance is available in the Azure portal and product documentation.",
      "replacement": "Azure Managed Grafana Standard SKU or Azure Monitor Dashboards with Grafana",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=559395",
      "extra_source_urls": [],
      "vendor_ref": "559395",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-managed-grafana-essential-sku-retirement"
    },
    {
      "slug": "aws-lambda-ruby3-3-end-of-support",
      "title": "AWS Lambda: Ruby 3.3 (ruby3.3) deprecation",
      "summary": "Deprecation date for Ruby 3.3 (ruby3.3) on AWS Lambda: 31 Mar 2027. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "After deprecation (31 Mar 2027), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 29 Jul 2027, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2027, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2027), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "ruby3.3"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "ruby3.3",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-ruby3-3-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-11-extended-support-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 11 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for PostgreSQL 11 on Amazon Aurora PostgreSQL: 31 Mar 2027. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 31 Mar 2027. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- New major PostgreSQL versions might contain database changes that are not backward-compatible with existing applications.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "11"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@11",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-11-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-11-extended-support-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 11 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for PostgreSQL 11 on Amazon RDS for PostgreSQL: 31 Mar 2027. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "After the RDS end of Extended Support date (31 Mar 2027), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 11.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "11"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@11",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-11-extended-support-end-of-support"
    },
    {
      "slug": "azure-app-service-python-on-windows-retirement",
      "title": "Azure App Service and Azure Functions: Python on Windows retirement",
      "summary": "From 31 Mar 2027, Python applications hosted on Azure App Service on Windows and Azure Functions on Windows no longer run. Microsoft supports Python on the Linux versions of both services.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "retirement",
      "announced_date": "2026-04-02",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "From 31 Mar 2027, Python applications hosted on Azure App Service on Windows and Azure Functions on Windows no longer run. After that date, application configuration and content remain intact, but the apps stop running and technical support for these workloads is no longer available. Microsoft states that Python on App Service for Windows has not been supported since December 2021 and that this change formally retires the runtime.",
      "migration_path": "1. Create a new Linux based application on Azure App Service on Linux or Azure Functions on Linux.\n2. Redeploy your Python workloads to the Linux application before the retirement date.",
      "replacement": "Azure App Service on Linux and Azure Functions on Linux",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=558027",
      "extra_source_urls": [],
      "vendor_ref": "558027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-python-on-windows-retirement"
    },
    {
      "slug": "azure-app-service-docker-compose-retirement",
      "title": "Azure App Service: Docker Compose feature retirement",
      "summary": "Retirement date for the Docker Compose feature in Azure App Service: 31 Mar 2027. After that date, Docker Compose applications that were not migrated to sidecar containers face disruptions and HTTP 5xx errors.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-03-26",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "Docker Compose web applications on Azure App Service are supported through the retirement date. After that date, Docker Compose applications that have not been migrated to sidecar containers start facing disruptions that result in HTTP 5xx errors.",
      "migration_path": "Move Docker Compose applications to sidecar containers in Azure App Service before the retirement date. [Learn more](https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-the-general-availability-of-sidecar-extensibility-in-azure-app-servic/4267985).",
      "replacement": "Sidecar containers in Azure App Service",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=485167",
      "extra_source_urls": [
        "https://techcommunity.microsoft.com/blog/appsonazureblog/announcing-the-general-availability-of-sidecar-extensibility-in-azure-app-servic/4267985"
      ],
      "vendor_ref": "485167",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-docker-compose-retirement"
    },
    {
      "slug": "azure-cloud-services-extended-support-retirement",
      "title": "Azure Cloud Services: Cloud Services (extended support) retirement",
      "summary": "Retirement date for the Cloud Services (extended support) deployment model: 31 Mar 2027. Microsoft directs customers to migrate services deployed with this model to Service Fabric managed cluster by that date.",
      "cloud": "azure",
      "service": "Azure Cloud Services",
      "service_slug": "cloud-services",
      "category": "service",
      "type": "retirement",
      "announced_date": "2025-03-31",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "The Cloud Services (extended support) deployment model is retired on the retirement date. Services that were deployed using this model are affected and need to be migrated. The source states the migration deadline in one sentence as before the retirement date and in another as by the retirement date. Microsoft describes migration to Service Fabric managed cluster as the way to avoid service disruptions.",
      "migration_path": "1. View impacted resources in the Azure portal under [Cloud services (extended support)](https://ms.portal.azure.com/#browse/Microsoft.Compute%2FcloudServices).\n2. Follow the [migration instructions](https://aka.ms/cses-retirement-march-2025) to move to Service Fabric managed cluster.",
      "replacement": "Service Fabric managed cluster",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=486344",
      "extra_source_urls": [
        "https://aka.ms/cses-retirement-march-2025"
      ],
      "vendor_ref": "486344",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-cloud-services-extended-support-retirement"
    },
    {
      "slug": "azure-front-door-classic-retirement",
      "title": "Azure Front Door: Front Door (classic) retirement",
      "summary": "Retirement date for Azure Front Door (classic) in the public cloud: 31 Mar 2027. Microsoft directs customers to migrate to Front Door Standard or Premium by that date.",
      "cloud": "azure",
      "service": "Azure Front Door",
      "service_slug": "front-door",
      "category": "service",
      "type": "retirement",
      "announced_date": "2024-03-27",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "Azure Front Door (classic) is retired for the public cloud on the retirement date. Since 1 April 2025, new Front Door (classic) resources cannot be created via the Azure portal, Terraform, or any command line tools. Existing resources can still be modified until Front Door (classic) is fully retired. Microsoft describes migration as the way to avoid potential disruptions in service.",
      "migration_path": "1. Review the [Front Door Standard and Premium comparison](https://learn.microsoft.com/azure/frontdoor/front-door-cdn-comparison#service-comparison) and the [pricing](https://learn.microsoft.com/azure/frontdoor/understanding-pricing) of each tier.\n2. [Migrate to Azure Front Door Standard or Premium](https://learn.microsoft.com/azure/frontdoor/migrate-tier).\n3. Create new resources on Front Door Standard or Premium, and use the Standard or Premium API and command line tools in DevOps workflows.",
      "replacement": "Azure Front Door Standard or Premium",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-front-door-classic-will-be-retired-on-31-march-2027",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/frontdoor/front-door-cdn-comparison#service-comparison",
        "https://learn.microsoft.com/azure/frontdoor/understanding-pricing",
        "https://learn.microsoft.com/azure/frontdoor/migrate-tier"
      ],
      "vendor_ref": "azure-front-door-classic-will-be-retired-on-31-march-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-front-door-classic-retirement"
    },
    {
      "slug": "azure-application-insights-api-key-query-access-retirement",
      "title": "Azure Monitor Application Insights: API key query access retirement",
      "summary": "Retirement date for API keys used to query Application Insights: 31 Mar 2027. Querying an Application Insights resource after that date requires Microsoft Entra authentication.",
      "cloud": "azure",
      "service": "Azure Monitor Application Insights",
      "service_slug": "application-insights",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2023-05-15",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "API keys used to query Application Insights are retired on the retirement date. Continuing to query an Application Insights resource requires a switch to Microsoft Entra authentication. Microsoft states that it extended the retirement date.",
      "migration_path": "Switch to [Microsoft Entra authentication for Application Insights](https://learn.microsoft.com/en-us/azure/azure-monitor/app/azure-ad-authentication?tabs=aspnetcore) by 31 Mar 2027 to keep querying the resource. Microsoft points to [Microsoft Q&A](https://aka.ms/livemetricapikey-qna) for questions and, with a support plan, a [support request](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) with service type Application Insights.",
      "replacement": "Microsoft Entra ID authentication",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=transition-to-azure-ad-to-query-data-from-azure-monitor-application-insights-by-31-march-2026",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-monitor/app/azure-ad-authentication?tabs=aspnetcore"
      ],
      "vendor_ref": "transition-to-azure-ad-to-query-data-from-azure-monitor-application-insights-by-31-march-2026",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-application-insights-api-key-query-access-retirement"
    },
    {
      "slug": "azure-monitor-prometheus-remote-write-sidecar-retirement",
      "title": "Azure Monitor: sidecar for Prometheus remote-write retirement",
      "summary": "Azure Monitor deprecates the sidecar for remote-write of Prometheus metrics to Azure Monitor Workspace on 31 Mar 2027. Microsoft recommends direct remote-write from self-hosted Prometheus or Prometheus Operator.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-03-30",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "Azure Monitor deprecates the sidecar for remote-write of Prometheus metrics to Azure Monitor Workspace on 31 Mar 2027. Microsoft recommends that self-hosted Prometheus or Prometheus Operator setups remote-write directly to Azure Monitor Workspace instead of using the sidecar. Microsoft encourages a transition to direct Prometheus remote-write to ensure uninterrupted service.",
      "migration_path": "1. Configure self-hosted Prometheus or Prometheus Operator to remote-write directly to Azure Monitor Workspace.\n2. Follow the configuration guidance in [the official documentation](https://learn.microsoft.com/azure/azure-monitor/metrics/prometheus-remote-write?tabs=system-managed-identity). All authentication methods are supported in the Prometheus remote-write configuration.\n3. Direct remote-write removes the need for the sidecar.",
      "replacement": "Direct Prometheus remote-write to Azure Monitor Workspace",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=550519",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-monitor/metrics/prometheus-remote-write?tabs=system-managed-identity"
      ],
      "vendor_ref": "550519",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-prometheus-remote-write-sidecar-retirement"
    },
    {
      "slug": "azure-sql-database-elastic-query-shard-map-manager-end-of-support",
      "title": "Azure SQL Database: Elastic query Shard_Map_Manager mode end of support",
      "summary": "End of support date for Azure SQL Elastic query in Shard_Map_Manager mode: 31 Mar 2027. Existing workloads keep running after that date but no longer receive updates or support from Microsoft.",
      "cloud": "azure",
      "service": "Azure SQL Database",
      "service_slug": "sql-database",
      "category": "feature",
      "type": "end_of_support",
      "announced_date": "2026-03-20",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "Elastic query with the Shard_Map_Manager external data source type reaches end of support on 31 Mar 2027. Existing workloads that use this mode can continue to run. They no longer receive updates or support from Microsoft.",
      "migration_path": "Microsoft has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=558086",
      "extra_source_urls": [],
      "vendor_ref": "558086",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sql-database-elastic-query-shard-map-manager-end-of-support"
    },
    {
      "slug": "azure-service-fabric-windows-server-2019-end-of-support",
      "title": "Azure Service Fabric: Windows Server 2019 end of support",
      "summary": "End of support date for Service Fabric clusters running on Windows Server 2019: 31 Mar 2027. Virtual Machine Scale Sets continue to function on Windows Server 2019 after that date, but Service Fabric support does not.",
      "cloud": "azure",
      "service": "Azure Service Fabric",
      "service_slug": "service-fabric",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": "2026-04-01",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "Service Fabric ends support for all clusters running on Windows Server 2019 on 31 Mar 2027. Virtual Machine Scale Sets continue to function on Windows Server 2019 after that date, but Service Fabric support does not. The support end date applies to all Service Fabric environments. Service Fabric no longer supports Windows Server OS images beyond their mainstream support end date.",
      "migration_path": "1. Upgrade all Service Fabric clusters running Windows Server 2019 to Windows Server 2025 before 31 Mar 2027 to remain in a supported state.\n2. Perform the OS image upgrade by scaling the cluster node types. See [Scale up a Service Fabric primary node type](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-scale-up-primary-node-type) and [Scale up a Service Fabric non-primary node type](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-scale-up-non-primary-node-type).\n3. Some documentation references an upgrade from Windows Server 2019 to 2022. The same process applies to all supported Windows Server OS image upgrades, including Windows Server 2025.\n4. For questions, visit [Azure Service Fabric - Microsoft Q&A](https://learn.microsoft.com/en-us/answers/tags/39/azure-service-fabric).",
      "replacement": "Windows Server 2025",
      "affected_versions": [
        "2019"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=558246",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-scale-up-primary-node-type",
        "https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-scale-up-non-primary-node-type",
        "https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request#open-a-support-request-from-the-global-header"
      ],
      "vendor_ref": "558246",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-service-fabric-windows-server-2019-end-of-support"
    },
    {
      "slug": "azure-service-fabric-windows-server-2022-end-of-support",
      "title": "Azure Service Fabric: Windows Server 2022 end of support",
      "summary": "End of support date for Service Fabric clusters running on Windows Server 2022: 31 Mar 2027. Virtual Machine Scale Sets continue to function on Windows Server 2022 after that date, but Service Fabric support does not.",
      "cloud": "azure",
      "service": "Azure Service Fabric",
      "service_slug": "service-fabric",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": "2026-04-01",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "Service Fabric ends support for all clusters running on Windows Server 2022 on 31 Mar 2027. Virtual Machine Scale Sets continue to function on Windows Server 2022 after that date, but Service Fabric support does not. The support end date applies to all Service Fabric environments. Service Fabric no longer supports Windows Server OS images beyond their mainstream support end date.",
      "migration_path": "1. Upgrade all Service Fabric clusters running Windows Server 2022 to Windows Server 2025 before 31 Mar 2027 to remain in a supported state.\n2. Perform the OS image upgrade by scaling the cluster node types. See [Scale up a Service Fabric primary node type](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-scale-up-primary-node-type) and [Scale up a Service Fabric non-primary node type](https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-scale-up-non-primary-node-type).\n3. Some documentation references an upgrade from Windows Server 2019 to 2022. The same process applies to all supported Windows Server OS image upgrades, including Windows Server 2025.\n4. For questions, visit [Azure Service Fabric - Microsoft Q&A](https://learn.microsoft.com/en-us/answers/tags/39/azure-service-fabric).",
      "replacement": "Windows Server 2025",
      "affected_versions": [
        "2022"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=558247",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-scale-up-primary-node-type",
        "https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-scale-up-non-primary-node-type",
        "https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request#open-a-support-request-from-the-global-header"
      ],
      "vendor_ref": "558247",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-service-fabric-windows-server-2022-end-of-support"
    },
    {
      "slug": "azure-vpn-gateway-sstp-protocol-retirement",
      "title": "Azure VPN Gateway: SSTP protocol support retirement",
      "summary": "Retirement date for SSTP protocol support on Azure VPN Gateway: 31 Mar 2027. From that date, existing SSTP-enabled gateways can no longer be used to establish SSTP connections.",
      "cloud": "azure",
      "service": "Azure VPN Gateway",
      "service_slug": "vpn-gateway",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-10-03",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "From 31 Mar 2027, existing SSTP-enabled gateways can no longer be used to establish SSTP connections. Enabling the SSTP protocol on a VPN gateway stopped being supported on Mar 31, 2026. VPN gateways with the SSTP protocol enabled are affected.",
      "migration_path": "Follow the [instructions to migrate](https://learn.microsoft.com/azure/vpn-gateway/ikev2-openvpn-from-sstp) from SSTP to IKEv2 or OpenVPN before 31 Mar 2027.",
      "replacement": "IKEv2 or OpenVPN",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=499923",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/vpn-gateway/ikev2-openvpn-from-sstp"
      ],
      "vendor_ref": "499923",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-vpn-gateway-sstp-protocol-retirement"
    },
    {
      "slug": "azure-virtual-machines-standard-m192idms-v2-retirement",
      "title": "Azure Virtual Machines: Standard_M192idms_v2 retirement",
      "summary": "Retirement date for the Standard_M192idms_v2 isolated VM size: 31 Mar 2027. On that date, workloads running on this size are deleted and associated application data is lost.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2024-03-22",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "On the retirement date, workloads running Standard_M192idms_v2 are deleted and associated application data is lost. Until that date, Standard_M192idms_v2 can be used without disruption. The hardware that this isolated VM size runs on has been replaced by a new generation.",
      "migration_path": "Follow the Microsoft [instructions](https://learn.microsoft.com/azure/virtual-machines/msv2-mdsv2-isolated-retirement) to migrate to [Standard_M176ds_4_v3](https://learn.microsoft.com/azure/virtual-machines/msv3-mdsv3-medium-series) before the retirement date.",
      "replacement": "Standard_M176ds_4_v3",
      "affected_versions": [
        "Standard_M192idms_v2"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=support-for-standardm192idmsv2-will-be-retired-on-31-march-2027",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/virtual-machines/msv3-mdsv3-medium-series",
        "https://learn.microsoft.com/azure/virtual-machines/isolation",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/msv3-mdsv3-medium-series",
        "https://learn.microsoft.com/azure/virtual-machines/msv2-mdsv2-isolated-retirement"
      ],
      "vendor_ref": "support-for-standardm192idmsv2-will-be-retired-on-31-march-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-standard-m192idms-v2-retirement"
    },
    {
      "slug": "azure-virtual-machines-standard-m192ids-v2-retirement",
      "title": "Azure Virtual Machines: Standard_M192ids_v2 isolated size retirement",
      "summary": "Retirement date for the Standard_M192ids_v2 isolated VM size: 31 Mar 2027. On that date, workloads running on this size are deleted and their application data is lost.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2024-03-22",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "On 31 Mar 2027, workloads running the Standard_M192ids_v2 virtual machine size are deleted and the associated application data is lost. Standard_M192ids_v2 is an isolated VM size, and isolated sizes are tied to the hardware generation they were designed for. Microsoft states that this hardware has been replaced by a new generation and that it can no longer offer the size. Until 31 Mar 2027, Standard_M192ids_v2 can be used without disruption.",
      "migration_path": "1. Choose a replacement size. Microsoft names Mdsv3 Medium Memory Series ([Msv3 and Mdsv3 Medium Memory series](https://learn.microsoft.com/azure/virtual-machines/msv3-mdsv3-medium-series)).\n2. Follow Microsoft's [instructions to migrate](https://learn.microsoft.com/azure/virtual-machines/msv2-mdsv2-isolated-retirement) to your selected replacement product before 31 Mar 2027.",
      "replacement": "Mdsv3 Medium Memory Series",
      "affected_versions": [
        "Standard_M192ids_v2"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=community-support-for-standardm192idsv2-is-ending-on-31-march-2027",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/virtual-machines/msv3-mdsv3-medium-series",
        "https://learn.microsoft.com/azure/virtual-machines/isolation",
        "https://learn.microsoft.com/azure/virtual-machines/msv2-mdsv2-isolated-retirement",
        "https://aka.ms/ServicesRetirementWorkbook"
      ],
      "vendor_ref": "community-support-for-standardm192idsv2-is-ending-on-31-march-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-standard-m192ids-v2-retirement"
    },
    {
      "slug": "azure-virtual-machines-standard-m192ims-v2-retirement",
      "title": "Azure Virtual Machines: Standard_M192ims_v2 isolated size retirement",
      "summary": "Retirement date for the Standard_M192ims_v2 isolated VM size: 31 Mar 2027. On that date, workloads running on this size are deleted and their application data is lost.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2024-03-22",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "On 31 Mar 2027, workloads running the Standard_M192ims_v2 virtual machine size are deleted and the associated application data is lost. Standard_M192ims_v2 is an isolated VM size, and isolated sizes are tied to the hardware generation they were designed for. Microsoft states that this hardware has been replaced by a new generation and that it can no longer offer the size. Until 31 Mar 2027, Standard_M192ims_v2 can be used without disruption.",
      "migration_path": "1. Plan the move to [Standard_M176s_4_v3](https://learn.microsoft.com/en-us/azure/virtual-machines/msv3-mdsv3-medium-series), the replacement size Microsoft names.\n2. Follow Microsoft's [instructions to migrate](https://learn.microsoft.com/en-us/azure/virtual-machines/msv2-mdsv2-isolated-retirement) to Standard_M176s_4_v3 by 31 Mar 2027.",
      "replacement": "Standard_M176s_4_v3",
      "affected_versions": [
        "Standard_M192ims_v2"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=community-support-for-standardm192imsv2-is-ending-on-31-march-2027",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/msv3-mdsv3-medium-series",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/isolation",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/msv2-mdsv2-isolated-retirement"
      ],
      "vendor_ref": "community-support-for-standardm192imsv2-is-ending-on-31-march-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-standard-m192ims-v2-retirement"
    },
    {
      "slug": "azure-virtual-machines-standard-m192is-v2-retirement",
      "title": "Azure Virtual Machines: Standard_M192is_v2 isolated size retirement",
      "summary": "Retirement date for the Standard_M192is_v2 isolated VM size: 31 Mar 2027. On that date, workloads running on this size are deleted and their application data is lost.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2024-03-22",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "On 31 Mar 2027, workloads running the Standard_M192is_v2 virtual machine size are deleted and the associated application data is lost. Standard_M192is_v2 is an isolated VM size, and isolated sizes are tied to the hardware generation they were designed for. Microsoft states that this hardware has been replaced by a new generation and that it can no longer offer the size. Until 31 Mar 2027, Standard_M192is_v2 can be used without disruption.",
      "migration_path": "1. Choose a replacement size. Microsoft names Msv3 Medium Memory Series ([Msv3 and Mdsv3 Medium Memory series](https://learn.microsoft.com/en-us/azure/virtual-machines/msv3-mdsv3-medium-series)).\n2. Follow Microsoft's [instructions to migrate](https://learn.microsoft.com/en-us/azure/virtual-machines/msv2-mdsv2-isolated-retirement) to your selected replacement product before 31 Mar 2027.",
      "replacement": "Msv3 Medium Memory Series",
      "affected_versions": [
        "Standard_M192is_v2"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=community-support-for-standardm192isv2-is-ending-on-31-march-2027",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/msv3-mdsv3-medium-series",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/isolation",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/msv2-mdsv2-isolated-retirement"
      ],
      "vendor_ref": "community-support-for-standardm192isv2-is-ending-on-31-march-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-standard-m192is-v2-retirement"
    },
    {
      "slug": "azure-emissions-impact-dashboard-for-azure-retirement",
      "title": "Emissions Impact Dashboard for Azure retirement",
      "summary": "Retirement date for the Emissions Impact Dashboard for Azure hosted by Power BI: 31 Mar 2027. After that date the dashboard is no longer accessible and technical support is discontinued.",
      "cloud": "azure",
      "service": "Emissions Impact Dashboard for Azure",
      "service_slug": "emissions-impact-dashboard-for-azure",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-03-18",
      "effective_date": "2027-03-31",
      "effective_precision": "day",
      "impact": "From 31 Mar 2027, the Emissions Impact Dashboard for Azure hosted by Power BI is retired. After that date, the dashboard is no longer accessible and technical support is discontinued.",
      "migration_path": "1. Export your emissions data before the retirement date to retain historical reporting.\n2. Explore Azure Carbon Optimizer as an alternative. See [Carbon optimization in Azure](https://learn.microsoft.com/en-us/azure/carbon-optimization/).",
      "replacement": "Azure Carbon Optimizer",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=558278",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/carbon-optimization/"
      ],
      "vendor_ref": "558278",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-emissions-impact-dashboard-for-azure-retirement"
    },
    {
      "slug": "azure-data-factory-memory-optimized-data-flows-retirement",
      "title": "Azure Data Factory: Memory Optimized Data Flows retirement",
      "summary": "Retirement of Memory Optimized Data Flows in Azure Data Factory: 1 Apr 2027. Microsoft states that all Azure Data Factory Data Flows use the General Purpose SKU going forward.",
      "cloud": "azure",
      "service": "Azure Data Factory",
      "service_slug": "data-factory",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-03-29",
      "effective_date": "2027-04-01",
      "effective_precision": "day",
      "impact": "Azure Data Factory Memory Optimized Data Flows are fully retired on 1 Apr 2027. Microsoft states that all Azure Data Factory Data Flows use the General Purpose SKU going forward. Creation of new Memory Optimized Data Flows was discontinued beginning 1 April 2024; until retirement, existing pipelines can continue to use existing memory optimized data flows, but new Azure Integration Runtimes using Memory Optimized cannot be created. Customers using Azure Data Factory Memory Optimized Data Flows are affected.",
      "migration_path": "Assign General Purpose integration runtimes to existing and new data flows instead of using Memory Optimized. The announcement's action list also includes the step \"To create new data flows, create a new Azure Integration Runtime using Memory Optimized instead of General Purpose\", and the same list states that new Azure Integration Runtimes using Memory Optimized cannot be created.",
      "replacement": "General Purpose Azure Data Factory Data Flows",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=were-retiring-memory-optimized-data-flows-in-azure-data-factory-use-general-purpose-for-better-performance-at-a-lower-price",
      "extra_source_urls": [],
      "vendor_ref": "were-retiring-memory-optimized-data-flows-in-azure-data-factory-use-general-purpose-for-better-performance-at-a-lower-price",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-data-factory-memory-optimized-data-flows-retirement"
    },
    {
      "slug": "gcp-cloud-run-go-1-25-retirement",
      "title": "Cloud Run: Go 1.25 decommission",
      "summary": "Decommission date for Go 1.25 on Cloud Run: 1 Apr 2027. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-04-01",
      "effective_precision": "day",
      "impact": "The decommission date of Go 1.25 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-go-1-25-retirement"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-22-04-lts-accelerated-with-c72514-end-of-support",
      "title": "Compute Engine: Ubuntu 22.04 LTS Accelerated with NVIDIA driver version 580 image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu 22.04 LTS Accelerated with NVIDIA driver version 580 public image on Compute Engine: Apr 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu 22.04 LTS Accelerated with NVIDIA driver version 580 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu 22.04 LTS Accelerated with NVIDIA driver version 580"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-accelerator-2204-amd64-with-nvidia-580",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-22-04-lts-accelerated-with-c72514-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-22-04-lts-image-end-of-support",
      "title": "Compute Engine: Ubuntu 22.04 LTS image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu 22.04 LTS public image on Compute Engine: Apr 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu 22.04 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu 22.04 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-2204-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-22-04-lts-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-22-04-lts-optimized-for-tpus-image-end-of-support",
      "title": "Compute Engine: Ubuntu 22.04 LTS optimized for TPUs image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu 22.04 LTS optimized for TPUs public image on Compute Engine: Apr 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu 22.04 LTS optimized for TPUs in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu 22.04 LTS optimized for TPUs"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-accel-2204-amd64-tpu-v5e-v5p-v6e",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-22-04-lts-optimized-for-tpus-image-end-of-support"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-multimodalembedding-001-retirement",
      "title": "Gemini Enterprise Agent Platform: multimodalembedding@001 retirement",
      "summary": "Retirement date for multimodalembedding@001 on Gemini Enterprise Agent Platform: 1 Apr 2027. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-04-01",
      "effective_precision": "day",
      "impact": "Google lists multimodalembedding@001 with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-multimodalembedding-001-retirement"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-text-embedding-004-retirement",
      "title": "Gemini Enterprise Agent Platform: text-embedding-004 retirement",
      "summary": "Retirement date for text-embedding-004 on Gemini Enterprise Agent Platform: 1 Apr 2027. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-04-01",
      "effective_precision": "day",
      "impact": "Google lists text-embedding-004 with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-text-embedding-004-retirement"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-text-embedding-005-retirement",
      "title": "Gemini Enterprise Agent Platform: text-embedding-005 retirement",
      "summary": "Retirement date for text-embedding-005 on Gemini Enterprise Agent Platform: 1 Apr 2027. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-04-01",
      "effective_precision": "day",
      "impact": "Google lists text-embedding-005 with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-text-embedding-005-retirement"
    },
    {
      "slug": "gcp-gemini-enterprise-agent-platform-text-multilingual-embedding-002-retirement",
      "title": "Gemini Enterprise Agent Platform: text-multilingual-embedding-002 retirement",
      "summary": "Retirement date for text-multilingual-embedding-002 on Gemini Enterprise Agent Platform: 1 Apr 2027. Google's model versions page mentions errors caused by models reaching their retirement dates, without describing them, and links a migration guide.",
      "cloud": "gcp",
      "service": "Gemini Enterprise Agent Platform",
      "service_slug": "gemini-enterprise-agent-platform",
      "category": "feature",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-04-01",
      "effective_precision": "day",
      "impact": "Google lists text-multilingual-embedding-002 with a retirement date in the model tables of its model versions page for Gemini Enterprise Agent Platform. The page does not describe what happens to requests to a retired model. It mentions only \"errors caused by models reaching their retirement dates\".",
      "migration_path": "Google links [Migrate to the latest Gemini models](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/migrate) as the guide for moving to a latest stable model. For cases where there is no time to follow the guide, the page gives a shorter path:\n\n1. Update your application to point to the recommended upgrade. Where the table names a replacement for a model, it is in the \"Replacement model ID\" column.\n2. Test all mission critical features to make sure everything works as expected.\n3. Deploy the updates like you normally would.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/model-versions",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gemini-enterprise-agent-platform-text-multilingual-embedding-002-retirement"
    },
    {
      "slug": "gcp-cloud-run-python-3-10-retirement",
      "title": "Cloud Run: Python 3.10 decommission",
      "summary": "Decommission date for Python 3.10 on Cloud Run: 4 Apr 2027. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-04-04",
      "effective_precision": "day",
      "impact": "The decommission date of Python 3.10 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-python-3-10-retirement"
    },
    {
      "slug": "gcp-gke-kubernetes-1-35-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.35 end of standard support",
      "summary": "End of standard support date for GKE Kubernetes 1.35: 11 Apr 2027. After that date the minor version is unsupported for clusters not enrolled in the Extended channel, and GKE automatically upgrades them to the next supported minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-04-11",
      "effective_precision": "day",
      "impact": "After the standard support period, the minor version becomes unsupported and unavailable for all clusters not enrolled in the Extended channel. GKE automatically upgrades those clusters to the next supported minor version.\n\n- Those clusters receive no security patches or bug fixes for the minor version after the end of standard support.\n- The automatic upgrade also applies to clusters not enrolled in any release channel. Nodes are typically scheduled for an automated upgrade within one month of the end of support date, and actual timing can vary.\n- As a temporary, emergency measure that Google does not recommend, a \"No upgrades\" maintenance exclusion can delay the upgrade for up to 90 days after the end of support date.\n- Extended channel clusters receive security patches until the end of extended support, for an additional fee per cluster.\n- Release schedule dates are subject to change.",
      "migration_path": "1. Upgrade the cluster and nodes to a supported version. Google requires this before you engage Cloud Customer Care about a cluster or nodes on an unsupported version.\n2. Without action, GKE schedules an automatic upgrade to the next supported minor version before the end of support. The timing depends on the schedule for the cluster's release channel.\n3. During the standard support period, a maintenance exclusion at the cluster level can prevent this minor version upgrade. GKE also does not upgrade clusters that use deprecated features or APIs during that period.\n4. To keep using the minor version until the end of extended support, change the cluster to the Extended channel. Extended support adds approximately 10 months after the standard support period, for up to 24 months of support in total.\n5. Review the [pricing for extended support](https://cloud.google.com/kubernetes-engine/pricing#extended-support-period) first, because pay-per-use costs apply in the extended support period.\n6. Review the limitations of the Extended channel: clusters that use certain features cannot be enrolled, the extended support period does not extend the cluster's credential expiry date, and GKE pauses patch node auto-upgrades when it updates the Container-Optimized OS milestone that the minor version uses.",
      "replacement": null,
      "affected_versions": [
        "1.35"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [
        "https://endoflife.date/google-kubernetes-engine"
      ],
      "vendor_ref": "gke@1.35",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-35-end-of-support"
    },
    {
      "slug": "azure-machine-learning-prompt-flow-retirement",
      "title": "Azure Machine Learning and Microsoft Foundry: Prompt Flow retirement",
      "summary": "Retirement date for Prompt Flow in Azure Machine Learning, Microsoft Foundry, and VS Code: 20 Apr 2027. Microsoft names Microsoft Agent Framework as the replacement.",
      "cloud": "azure",
      "service": "Azure Machine Learning",
      "service_slug": "machine-learning",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-04-27",
      "effective_date": "2027-04-20",
      "effective_precision": "day",
      "impact": "Prompt Flow is fully retired from Azure ML, Microsoft Foundry, and VS Code on the retirement date. Microsoft recommends rebuilding key workloads and moving deployments to supported alternatives ahead of retirement. The announcement does not describe what happens to existing flows and deployments after that date. Microsoft Agent Framework reached general availability on April 3, 2026.",
      "migration_path": "1. Use Microsoft Agent Framework for most orchestration scenarios. Review the Microsoft Foundry options if you also depend on evaluation or tracing.\n2. Follow a phased approach: rebuild key workloads, validate them thoroughly, and move deployments to supported alternatives ahead of retirement.\n3. Use the [Migration guide](https://aka.ms/PFtoMAFMigration) and the [Migration code samples](https://aka.ms/PFMigrationCodeSamples).",
      "replacement": "Microsoft Agent Framework",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=502936",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/agent-framework/",
        "https://aka.ms/PFtoMAFMigration",
        "https://aka.ms/PFMigrationCodeSamples"
      ],
      "vendor_ref": "502936",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-machine-learning-prompt-flow-retirement"
    },
    {
      "slug": "azure-app-service-node-22-end-of-support",
      "title": "Azure App Service: Node 22 LTS end of support",
      "summary": "End of support date for Node 22 LTS on Azure App Service: 30 Apr 2027. Apps hosted on App Service keep running after that date but stop receiving security updates and customer service for Node 22 LTS.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-08-24",
      "effective_date": "2027-04-30",
      "effective_precision": "day",
      "impact": "After the end of support date for Node 22 LTS, apps hosted on App Service continue to run, but security updates are no longer available. Microsoft no longer provides customer service for Node 22 LTS after that date.",
      "migration_path": "Upgrade the app to Node 24 LTS before 30 Apr 2027. [Follow the steps to upgrade your app to Node 24 LTS](https://aka.ms/nodeversion).",
      "replacement": "Node 24 LTS",
      "affected_versions": [
        "22"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=567334",
      "extra_source_urls": [
        "https://aka.ms/nodeversion",
        "https://learn.microsoft.com/azure/app-service/language-support-policy",
        "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy"
      ],
      "vendor_ref": "567334",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-node-22-end-of-support"
    },
    {
      "slug": "azure-functions-node-22-end-of-support",
      "title": "Azure Functions: Node.js 22 end of support",
      "summary": "End of support date for Node.js 22 on Azure Functions: 30 Apr 2027. Function apps keep running after that date but stop receiving security patches, updates and customer support.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-09-22",
      "effective_date": "2027-04-30",
      "effective_precision": "day",
      "impact": "After the end of support date, function apps on Node.js 22 continue to run, but security patches and updates are no longer provided and customer support for Node.js 22 is discontinued. Microsoft states that running function apps on an unsupported runtime or language version may lead to issues and degraded performance. An upgrade is required to maintain support eligibility.",
      "migration_path": "Upgrade the app to Node.js 24 before 30 Apr 2027. [Follow the steps to upgrade your app](https://learn.microsoft.com/azure/azure-functions/update-language-versions?tabs=azure-portal%2Cwindows&pivots=programming-language-javascript).",
      "replacement": "Node.js 24",
      "affected_versions": [
        "22"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=572771",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-functions/update-language-versions?tabs=azure-portal%2Cwindows&pivots=programming-language-javascript",
        "https://learn.microsoft.com/azure/azure-functions/language-support-policy?pivots=programming-language-javascript",
        "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions"
      ],
      "vendor_ref": "572771",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-node-22-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-10-0-eus-image-end-of-support",
      "title": "Compute Engine: RHEL 10.0 EUS image end of support",
      "summary": "EOS and image deprecation date for the RHEL 10.0 EUS public image on Compute Engine: May 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 10.0 EUS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 10.0 EUS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-10-0-eus",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-10-0-eus-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-8-8-for-sap-image-end-of-support",
      "title": "Compute Engine: RHEL 8.8 for SAP image end of support",
      "summary": "EOS and image deprecation date for the RHEL 8.8 for SAP public image on Compute Engine: May 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 8.8 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 8.8 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-8-8-sap-ha",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-8-8-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-9-2-for-sap-image-end-of-support",
      "title": "Compute Engine: RHEL 9.2 for SAP image end of support",
      "summary": "EOS and image deprecation date for the RHEL 9.2 for SAP public image on Compute Engine: May 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 9.2 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 9.2 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-9-2-sap-ha",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-9-2-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-9-6-eus-image-end-of-support",
      "title": "Compute Engine: RHEL 9.6 EUS image end of support",
      "summary": "EOS and image deprecation date for the RHEL 9.6 EUS public image on Compute Engine: May 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 9.6 EUS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 9.6 EUS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-9-6-eus",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-9-6-eus-image-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-dotnet-8-retirement",
      "title": "Cloud Run: .NET 8 decommission",
      "summary": "Decommission date for .NET 8 on Cloud Run: 10 May 2027. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-05-10",
      "effective_precision": "day",
      "impact": "The decommission date of .NET 8 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-dotnet-8-retirement"
    },
    {
      "slug": "aws-lambda-nodejs22-x-end-of-support",
      "title": "AWS Lambda: Node.js 22 (nodejs22.x) deprecation",
      "summary": "Deprecation date for Node.js 22 (nodejs22.x) on AWS Lambda: 30 May 2027. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-05-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 May 2027), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 29 Jul 2027, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2027, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2027), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "nodejs22.x"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "nodejs22.x",
      "last_checked_at": "2026-11-13T11:22:40.364Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-nodejs22-x-end-of-support"
    },
    {
      "slug": "azure-app-service-tls-1-0-and-tls-1-1-retirement",
      "title": "Azure App Service, Functions and Logic Apps: TLS 1.0 and 1.1 retirement",
      "summary": "After 31 May 2027, Azure App Service, Azure Functions, and Azure Logic Apps no longer accept connections that use TLS 1.0 or TLS 1.1. Clients need to support TLS 1.2 or later.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-05-21",
      "effective_date": "2027-05-31",
      "effective_precision": "day",
      "impact": "After 31 May 2027, Azure App Service, Azure Functions, and Azure Logic Apps no longer accept connections that use TLS 1.0 or TLS 1.1. Any client, application, or service that still uses these TLS versions is unable to connect to these services after that date. Resources in a subscription that still allow TLS 1.0 or 1.1 are listed in the Azure Retirement Workbook.",
      "migration_path": "1. Find the resources in your subscription that still allow TLS 1.0 or 1.1 in the [Azure Retirement Workbook](https://aka.ms/ServicesRetirementWorkbook).\n2. Review the applications and services that connect to App Service, Functions, or Logic Apps and make sure they support TLS 1.2 or later before the retirement date.\n3. Test client compatibility with TLS 1.2 or later.\n4. Review the [TLS version deprecation overview](https://aka.ms/tls-deprecation-appservice) for configuration guidance.\n5. For common questions, see the Q&A for [App Service](https://aka.ms/tls-deprecation-appservice/qa), [Functions](https://aka.ms/tls-deprecation-functions/qa) and [Logic Apps](https://aka.ms/tls-deprecation-logicapps/qa).",
      "replacement": "TLS 1.2 or later",
      "affected_versions": [
        "1.0",
        "1.1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=557852",
      "extra_source_urls": [
        "https://aka.ms/ServicesRetirementWorkbook",
        "https://aka.ms/tls-deprecation-appservice",
        "https://aka.ms/tls-deprecation-appservice/qa",
        "https://aka.ms/tls-deprecation-functions/qa",
        "https://aka.ms/tls-deprecation-logicapps/qa"
      ],
      "vendor_ref": "557852",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-tls-1-0-and-tls-1-1-retirement"
    },
    {
      "slug": "azure-batch-hbv2-hc-np-series-vm-retirement",
      "title": "Azure Batch: HBv2, HC and NP-series VM retirement",
      "summary": "Retirement date for HBv2-series, HC-series and NP-series virtual machines in Azure Batch pools: 31 May 2027. After that date, new pools with these VM sizes cannot be created and existing pools are subject to forced resize to zero nodes.",
      "cloud": "azure",
      "service": "Azure Batch",
      "service_slug": "batch",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-04-15",
      "effective_date": "2027-05-31",
      "effective_precision": "day",
      "impact": "Microsoft retires support for HBv2-series, HC-series and NP-series VMs in Azure Batch pools on 31 May 2027. After that date, new Batch pools with these VM sizes cannot be created, and existing pools are subject to forced resize to zero nodes. Existing pools cannot be updated in place, so a new pool is required. The NP-series has no direct replacement.",
      "migration_path": "1. Migrate Batch pools to supported VM sizes before 31 May 2027.\n2. Move HBv2-series pools to HBv3-series or HBv4-series, and HC-series pools to HX-series.\n3. For NP-series pools, evaluate GPU-based NC/ND-series VMs or partner FPGA solutions.\n4. Create a new pool, because existing pools cannot be updated in place.\n5. Microsoft refers to the Batch pool VM sizes documentation and the update pool properties guide for instructions.",
      "replacement": "HBv3-series or HBv4-series for HBv2; HX-series for HC; no direct replacement for NP",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=559751",
      "extra_source_urls": [],
      "vendor_ref": "559751",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-batch-hbv2-hc-np-series-vm-retirement"
    },
    {
      "slug": "azure-virtual-machines-hbv2-series-retirement",
      "title": "Azure Virtual Machines: HBv2-series retirement",
      "summary": "Retirement date for HBv2-series Azure Virtual Machines: 31 May 2027. After that date, remaining HBv2-series VMs are set to a deallocated state and stop working.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-03-19",
      "effective_date": "2027-05-31",
      "effective_precision": "day",
      "impact": "The retirement covers the sizes Standard_HB120rs_v2, Standard_HB120-96rs_v2, Standard_HB120-64rs_v2, Standard_HB120-32rs_v2 and Standard_HB120-16rs_v2. After the retirement date, remaining HBv2-series VMs are set to a deallocated state, stop working and no longer incur billing charges. After the retirement date, HBv2-series is no longer under SLA and no longer has support included. Purchases of 1-year and 3-year reserved instances ended on April 2, 2026.",
      "migration_path": "1. Resize or deallocate your HBv2-series VMs.\n2. Microsoft recommends migrating the workloads to newer HPC-optimized SKUs such as HBv5, HBv4, HX and HBv3-series virtual machines, or an alternative that meets your workload requirements.\n3. Microsoft recommends the current-generation HPC families [HBv5-series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/high-performance-compute/hbv5-series?tabs=sizebasic) and [HX-series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/high-performance-compute/hx-series?tabs=sizebasic), the latter for high-memory HPC workloads.",
      "replacement": "HBv5-series or HX-series VMs",
      "affected_versions": [
        "Standard_HB120rs_v2",
        "Standard_HB120-96rs_v2",
        "Standard_HB120-64rs_v2",
        "Standard_HB120-32rs_v2",
        "Standard_HB120-16rs_v2"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=548525",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/high-performance-compute/hbv5-series?tabs=sizebasic",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/high-performance-compute/hx-series?tabs=sizebasic"
      ],
      "vendor_ref": "548525",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-hbv2-series-retirement"
    },
    {
      "slug": "azure-virtual-machines-hc-series-retirement",
      "title": "Azure Virtual Machines: HC-series retirement",
      "summary": "Retirement date for HC-series Azure Virtual Machines: 31 May 2027. After that date, remaining HC-series VMs are set to a deallocated state and stop working.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-03-19",
      "effective_date": "2027-05-31",
      "effective_precision": "day",
      "impact": "The retirement covers the sizes Standard_HC44rs, Standard_HC44-16rs and Standard_HC44-32rs. After the retirement date, remaining HC-series VMs are set to a deallocated state, stop working and no longer incur billing charges. After the retirement date, HC-series is no longer under SLA and no longer has support included. Purchases of 1-year and 3-year reserved instances ended on April 2, 2026.",
      "migration_path": "1. Resize or deallocate your HC-series VMs.\n2. Microsoft recommends migrating the workloads to newer HPC-optimized SKUs such as HBv5, HBv4, HX and HBv3-series virtual machines, or an alternative that meets your workload requirements.\n3. Microsoft recommends the current-generation HPC families [HBv5-series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/high-performance-compute/hbv5-series?tabs=sizebasic) and [HX-series](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/high-performance-compute/hx-series?tabs=sizebasic), the latter for high-memory HPC workloads.",
      "replacement": "HBv5-series or HX-series VMs",
      "affected_versions": [
        "Standard_HC44rs",
        "Standard_HC44-16rs",
        "Standard_HC44-32rs"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=548543",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/high-performance-compute/hbv5-series?tabs=sizebasic",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/high-performance-compute/hx-series?tabs=sizebasic"
      ],
      "vendor_ref": "548543",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-hc-series-retirement"
    },
    {
      "slug": "azure-virtual-machines-np-series-retirement",
      "title": "Azure Virtual Machines: NP-series retirement",
      "summary": "Retirement date for NP-series Azure Virtual Machines: 31 May 2027. After that date, remaining NP-series VMs are set to a deallocated state and stop working.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-03-19",
      "effective_date": "2027-05-31",
      "effective_precision": "day",
      "impact": "The retirement covers the sizes Standard_NP10s, Standard_NP20s and Standard_NP40s. After the retirement date, remaining NP-series VMs are set to a deallocated state, stop working and no longer incur billing charges. After the retirement date, NP-series is no longer under SLA and no longer has support included. Purchases of 1-year and 3-year reserved instances ended on April 2, 2026.",
      "migration_path": "1. Resize or deallocate your NP-series VMs.\n2. Change your VM sizes to a product that meets your workload requirements.\n3. Microsoft recommends one of these Azure GPU VM families, based on workload needs: [NDv2 VMs](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/ndv2-series?tabs=sizebasic), [NCads_H100_v5](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/ncadsh100v5-series?tabs=sizebasic) or [NCasT4_v3](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/ncast4v3-series?tabs=sizebasic).",
      "replacement": "NDv2, NCads_H100_v5 or NCasT4_v3 VMs",
      "affected_versions": [
        "Standard_NP10s",
        "Standard_NP20s",
        "Standard_NP40s"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=548497",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/ndv2-series?tabs=sizebasic",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/ncadsh100v5-series?tabs=sizebasic",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/gpu-accelerated/ncast4v3-series?tabs=sizebasic"
      ],
      "vendor_ref": "548497",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-np-series-retirement"
    },
    {
      "slug": "gcp-compute-engine-centos-stream-9-image-end-of-support",
      "title": "Compute Engine: CentOS Stream 9 image end of support",
      "summary": "EOS and image deprecation date for the CentOS Stream 9 public image on Compute Engine: 31 May 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-05-31",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of CentOS Stream 9 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "CentOS Stream 9"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "centos-stream-9",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-centos-stream-9-image-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-29-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.29 platform-initiated upgrade",
      "summary": "Microsoft lists Jun 2027 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.29 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-06-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.29"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.29",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-29-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-aks-kubernetes-1-30-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.30 platform-initiated upgrade",
      "summary": "Microsoft lists Jun 2027 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.30 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-06-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.30"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.30",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-30-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-aks-kubernetes-1-31-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.31 platform-initiated upgrade",
      "summary": "Microsoft lists Jun 2027 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.31 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-06-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.31"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.31",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-31-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-aks-kubernetes-1-32-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.32 platform-initiated upgrade",
      "summary": "Microsoft lists Jun 2027 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.32 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-06-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.32"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.32",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-32-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-aks-kubernetes-1-33-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.33 platform-initiated upgrade",
      "summary": "Microsoft lists Jun 2027 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.33 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-06-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.33"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.33",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-33-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-aks-kubernetes-1-34-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.34 platform-initiated upgrade",
      "summary": "Microsoft lists Jun 2027 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.34 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-06-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.34"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.34",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-34-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-aks-kubernetes-1-35-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.35 platform-initiated upgrade",
      "summary": "Microsoft lists Jun 2027 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.35 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-06-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.35"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.35",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-35-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-aks-kubernetes-1-36-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.36 end of life",
      "summary": "End of life date for Kubernetes 1.36 on Azure Kubernetes Service: Jun 2027. After that date, community support for the version ends and clusters not enrolled in long-term support enter platform support, which covers AKS and Azure platform issues only.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-01",
      "effective_precision": "month",
      "impact": "After the end of life date, community support for Kubernetes 1.36 ends. Clusters not enrolled in long-term support enter platform support.\n\n- Platform support covers AKS and Azure platform issues only, not Kubernetes functionality and components. New clusters cannot be created during the platform support period.\n- There is a 60-day platform support grace period after the published end of life date to upgrade to a supported minor version. For the initial rollout, the grace period is the window through May 31, 2027.\n- After the grace period, the cluster is eligible for a platform-initiated upgrade to the lowest supported community minor version. No such upgrade starts before June 1, 2027. Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget. Its month in the release calendar is a planning estimate, not an exact date.\n- Regional version removal can happen at a different time from the published date.",
      "migration_path": "1. List the versions AKS offers for the cluster with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. While the cluster is a supported non-LTS cluster, upgrade one minor version at a time. Minor versions cannot be skipped.\n3. Upgrade the control plane and all node pools with `az aks upgrade`, as described in [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n4. If the cluster is already on an unsupported version, use the oldest supported GA target that AKS offers and perform a full-cluster upgrade. Control-plane-only upgrades are not supported for this path. The version-skipping table in [Supported Kubernetes versions in Azure Kubernetes Service (AKS)](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions) labels this an unsupported recovery path: AKS allows the upgrade to proceed, but it is not supported and might carry risks. The platform support table on the same page lists upgrades from an N-3 version to a supported version as supported.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To get extended support for the version instead, enable [long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support). This requires moving the cluster to the Premium tier and explicitly selecting the LTS support plan. Microsoft-managed Calico is not supported in LTS. Once community support for the version has ended, LTS cannot be disabled for that version.",
      "replacement": null,
      "affected_versions": [
        "1.36"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.36",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-36-end-of-support"
    },
    {
      "slug": "azure-fluid-relay-retirement",
      "title": "Azure Fluid Relay retirement",
      "summary": "Retirement date for Azure Fluid Relay: 2 Jun 2027. After that date the service reaches end of availability; the source says the service can be used until June 1, 2027, and the named replacement is a self-hosted Fluid service solution.",
      "cloud": "azure",
      "service": "Azure Fluid Relay",
      "service_slug": "fluid-relay",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-11-02",
      "effective_date": "2027-06-02",
      "effective_precision": "day",
      "impact": "The source names two days: the retirement date for Azure Fluid Relay, 2 Jun 2027, and June 1, 2027, the day until which the service can be used. After the retirement date, the service reaches end of availability, and applications that still use it may experience service disruption. The Fluid Framework remains available as an open-source framework. With the self-hosted solution, the customer is responsible for hosting and operating the Fluid service, and costs depend on deployment architecture, scale, and operational requirements.",
      "migration_path": "1. Review your Azure subscriptions and identify applications that use Azure Fluid Relay.\n2. Plan and complete the transition of workloads that depend on Azure Fluid Relay to a [self-hosted Fluid service solution](https://github.com/microsoft/FluidFramework/tree/main/tools/selfhost) before the retirement date.\n3. Use the self-hosted Fluid service solution in the Fluid Framework GitHub repository as the migration and replacement resource.",
      "replacement": "Self-hosted Fluid service solution",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=570498",
      "extra_source_urls": [
        "https://github.com/microsoft/FluidFramework/tree/main/tools/selfhost"
      ],
      "vendor_ref": "570498",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-fluid-relay-retirement"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-6-2-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.6.2 end of life",
      "summary": "End of life date for Engine version 1.4.6.2 on Amazon Neptune: 3 Jun 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-03",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.6.2"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.6.2",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-6-2-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-6-3-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.6.3 end of life",
      "summary": "End of life date for Engine version 1.4.6.3 on Amazon Neptune: 3 Jun 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-03",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.6.3"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.6.3",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-6-3-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-7-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.7.0 end of life",
      "summary": "End of life date for Engine version 1.4.7.0 on Amazon Neptune: 3 Jun 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-03",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.7.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.7.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-7-0-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-7-1-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.7.1 end of life",
      "summary": "End of life date for Engine version 1.4.7.1 on Amazon Neptune: 3 Jun 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-03",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.7.1"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.7.1",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-7-1-end-of-support"
    },
    {
      "slug": "gcp-gke-kubernetes-1-33-extended-support-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.33 end of extended support",
      "summary": "End of extended support date for GKE Kubernetes 1.33: 12 Jun 2027. From that date the minor version receives no security patches, and GKE upgrades Extended channel clusters still running it to the next minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-12",
      "effective_precision": "day",
      "impact": "At the end of extended support, GKE does not provide any patches for security fixes, and the minor version is considered unsupported. GKE upgrades clusters still running it to the next minor version.\n\n- The upgrade happens regardless of the cluster's use of deprecated features or APIs.\n- Maintenance exclusions cannot be configured past this date, except as a temporary, emergency measure with the \"No upgrades\" scope.\n- That exclusion can delay the upgrade for up to 90 days after the end of support date. Google does not recommend it.\n- Dates in the GKE release schedule are updated monthly and subject to change.",
      "migration_path": "1. Google does not recommend enrolling a cluster in the Extended channel without plans to move to the next minor version, because GKE eventually upgrades the cluster to newer minor versions.\n2. Around 2 months before the end of extended support, GKE begins upgrading clusters in the Extended channel to the next minor version, unless the cluster is using deprecated features or APIs.\n3. Maintenance exclusions can prevent minor version upgrades until the end of extended support. A temporary, emergency exclusion with the \"No upgrades\" scope can delay the upgrade for up to 90 days after the end of support date. After that exclusion expires, GKE upgrades the cluster.\n4. At the end of extended support, GKE upgrades all clusters still running the minor version, regardless of blocking issues. See [GKE minor version lifecycle](https://docs.cloud.google.com/kubernetes-engine/versioning#lifecycle).",
      "replacement": null,
      "affected_versions": [
        "1.33"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [],
      "vendor_ref": "gke@1.33",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-33-extended-support-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-customer-supplied-encryption-keys-cseks-retirement",
      "title": "Compute Engine: customer-supplied encryption keys (CSEKs) shutdown",
      "summary": "Shutdown date for customer-supplied encryption keys (CSEKs) in the Compute Engine deprecations table: 16 Jun 2027. Google's CSEK deprecation page gives July 20, 2027 for complete removal and names customer-managed encryption keys (CMEK) as the alternative.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-06-15",
      "effective_date": "2027-06-16",
      "effective_precision": "day",
      "impact": "Using customer-supplied encryption keys (CSEK) to encrypt Persistent Disks, images, machine images, standard and archive snapshots, and instant snapshots in Compute Engine is deprecated. The CSEK on an existing resource cannot be removed and replaced with a CMEK: a copy of the resource has to be created and encrypted with the CMEK. Google's two pages give different dates:\n\n- Compute Engine deprecations table: deprecated June 15, 2026, shutdown date 16 Jun 2027.\n- CSEK deprecation page: as of July 20, 2026, a CSEK can no longer be used to encrypt any of these resources, and CSEK is completely removed from Compute Engine on July 20, 2027.",
      "migration_path": "1. Make sure you have at least one Cloud KMS key ring and key. To create them, see [Creating key rings and keys](https://docs.cloud.google.com/kms/docs/creating-keys).\n2. Disks: create a standard snapshot of the CSEK-encrypted disk and create a new CMEK-encrypted disk from that snapshot. If the source disk is the boot disk of a running instance, stop the instance. Detach the source disk, attach the new disk, and verify that the new disk works as expected. Replacing the disk often requires stopping the instance.\n3. Images, standard snapshots and archive snapshots: create a new CMEK-encrypted disk from the image or snapshot, then create an image or snapshot of the new disk and encrypt it with a CMEK.\n4. Machine images: using REST or the Google Cloud CLI, create a temporary instance from the CSEK-encrypted machine image and specify a Cloud KMS key for each disk. Verify the instance, create a CMEK-encrypted machine image from it, then delete the temporary instance.\n5. Instant snapshots: create a temporary CSEK-encrypted standard snapshot from the instant snapshot, create a temporary CMEK-encrypted disk from it, create a CMEK-encrypted instant snapshot of that disk, then delete the temporary snapshot and disk.\n6. Test the migration steps in a non-production environment first, and delete the resources you no longer need afterward. Google's steps are in [migrate your CSEK-encrypted Compute Engine resources to use CMEKs](https://docs.cloud.google.com/compute/docs/deprecations/csek-deprecation-in-compute-engine#migrate-csek-cmeks-overview).",
      "replacement": "Customer-managed encryption keys (CMEK) in Cloud Key Management Service",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/compute/docs/deprecations",
      "extra_source_urls": [
        "https://docs.cloud.google.com/compute/docs/deprecations/csek-deprecation-in-compute-engine"
      ],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-customer-supplied-encryption-keys-cseks-retirement"
    },
    {
      "slug": "aws-lambda-java11-end-of-support",
      "title": "AWS Lambda: Java 11 (java11) deprecation",
      "summary": "Deprecation date for Java 11 (java11) on AWS Lambda: 30 Jun 2027. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2027), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 29 Jul 2027, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2027, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2027), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "java11"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "java11",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-java11-end-of-support"
    },
    {
      "slug": "aws-lambda-java17-end-of-support",
      "title": "AWS Lambda: Java 17 (java17) deprecation",
      "summary": "Deprecation date for Java 17 (java17) on AWS Lambda: 30 Jun 2027. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2027), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 29 Jul 2027, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2027, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2027), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "java17"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "java17",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-java17-end-of-support"
    },
    {
      "slug": "aws-lambda-java8-al2-end-of-support",
      "title": "AWS Lambda: Java 8 (java8.al2) deprecation",
      "summary": "Deprecation date for Java 8 (java8.al2) on AWS Lambda: 30 Jun 2027. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2027), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 29 Jul 2027, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2027, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2027), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "java8.al2"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "java8.al2",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-java8-al2-end-of-support"
    },
    {
      "slug": "aws-lambda-python3-11-end-of-support",
      "title": "AWS Lambda: Python 3.11 (python3.11) deprecation",
      "summary": "Deprecation date for Python 3.11 (python3.11) on AWS Lambda: 30 Jun 2027. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2027), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 29 Jul 2027, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2027, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2027), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "python3.11"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "python3.11",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-python3-11-end-of-support"
    },
    {
      "slug": "azure-aks-ubuntu-22-04-retirement",
      "title": "Azure Kubernetes Service: Ubuntu 22.04 retirement",
      "summary": "AKS retires Ubuntu 22.04 on 30 Jun 2027. After that date, new Ubuntu 22.04 node pools cannot be created, AKS produces no new Ubuntu 22.04 node images, and existing Ubuntu 22.04 node pools receive no security patches.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "os_image",
      "type": "retirement",
      "announced_date": "2026-04-16",
      "effective_date": "2027-06-30",
      "effective_precision": "day",
      "impact": "After the retirement date, new Ubuntu 22.04 node pools cannot be created, AKS produces no new node images, and existing node pools receive no security patches. On April 30, 2028, AKS removes Ubuntu 22.04 node images and existing code, which causes scaling and remediation operations to fail. Enabling long-term support with Kubernetes version 1.33 or later requires updating node pools to Ubuntu 24.04 first.",
      "migration_path": "1. Follow the [OS version upgrade guide](https://learn.microsoft.com/azure/aks/upgrade-os-version) to transition to Ubuntu 24.04 or later by the retirement date.\n2. If the OS SKU is 'Ubuntu', upgrade the Kubernetes version to 1.35 or later. The migration to Ubuntu 24.04 is then automatic.\n3. If the OS SKU is 'Ubuntu2204', update it to 'Ubuntu' for Kubernetes 1.35 or later, or to 'Ubuntu2404' for Kubernetes 1.32 or later.",
      "replacement": "Ubuntu 24.04 or later",
      "affected_versions": [
        "22.04"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=557928",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/aks/upgrade-os-version",
        "https://aka.ms/aks/supported-ubuntu-versions",
        "https://aka.ms/aks/ubuntu2204-retirement-github",
        "https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request#open-a-support-request-from-the-global-header",
        "https://aka.ms/ServicesRetirementWorkbook"
      ],
      "vendor_ref": "557928",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-ubuntu-22-04-retirement"
    },
    {
      "slug": "gcp-cloud-run-php-8-2-retirement",
      "title": "Cloud Run: PHP 8.2 decommission",
      "summary": "Decommission date for PHP 8.2 on Cloud Run: 30 Jun 2027. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-06-30",
      "effective_precision": "day",
      "impact": "The decommission date of PHP 8.2 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-php-8-2-retirement"
    },
    {
      "slug": "azure-aks-kubernetes-1-33-lts-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.33 LTS end of life",
      "summary": "LTS end of life date for Kubernetes 1.33 on Azure Kubernetes Service: Jul 2027. For clusters with long-term support enabled, support for the version continues only until that date. After it, those clusters must move to the next supported LTS version.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-07-01",
      "effective_precision": "month",
      "impact": "After the LTS end of life date, long-term support for Kubernetes 1.33 ends. LTS-enabled clusters must then be upgraded to the next supported LTS version.\n\n- If a cluster is not upgraded, AKS upgrades it to the next supported LTS version through a platform-initiated upgrade. The cluster is not dropped to a community-supported version.\n- The LTS page places this after the 60-day grace period that follows the LTS end of life date. For the initial rollout, the grace period is the window through May 31, 2027, and no platform-initiated upgrade starts before June 1, 2027. After the initial rollout, every end-of-support event has a 60-day grace period before platform-initiated upgrades begin.\n- Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget.\n- The platform-initiated upgrade month in the AKS LTS release calendar is a planning estimate, not an exact upgrade date.",
      "migration_path": "1. List the versions AKS offers as upgrade targets with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. Test the workloads against deprecated APIs and other breaking changes between the current and target versions.\n3. Upgrade to an offered higher LTS version with `az aks upgrade --resource-group <resource-group-name> --name <cluster-name> --kubernetes-version <lts-kubernetes-version>`. An LTS cluster can skip minor versions when the upgrade satisfies version-skew requirements and validation checks. See [Long-term support for AKS versions](https://learn.microsoft.com/en-us/azure/aks/long-term-support).\n4. If the cluster is already past its LTS end of life date, skipping minor versions is conditional: the target must be listed by AKS and satisfy validation checks. AKS allows this upgrade but treats it as an unsupported recovery path.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To leave LTS instead, move the cluster to the Free or Standard tier and select the KubernetesOfficial support plan. This is possible while the cluster's Kubernetes version is still in community support. After that version exits community support, first upgrade the cluster to a community-supported version.",
      "replacement": "Next supported AKS LTS version",
      "affected_versions": [
        "1.33"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.33",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-33-lts-end-of-support"
    },
    {
      "slug": "aws-eks-kubernetes-1-33-extended-support-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.33 end of extended support",
      "summary": "End of extended support date for Kubernetes 1.33 on Amazon EKS: 29 Jul 2027. On that date, new clusters can no longer be created with this version, and Amazon EKS automatically updates control planes still on it at any time afterward.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-07-29",
      "effective_precision": "day",
      "impact": "On the end of extended support date, new Amazon EKS clusters can no longer be created with Kubernetes 1.33. Amazon EKS automatically updates existing control planes to the earliest supported version, at any time after that date.\n\n- Amazon EKS gives no specific time frame and sends no notification before the update.\n- The auto-upgrade includes only the Kubernetes control plane. Self-managed nodes and EKS managed node groups remain on the previous version.\n- EKS Auto Mode nodes may update automatically.\n- Fargate nodes and hybrid nodes are not upgraded with the control plane.\n- Clusters that were automatically upgraded at the end of extended support cannot be rolled back.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version.\n3. Proactively update the control plane without relying on the Amazon EKS automatic update process, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n4. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n5. If Amazon EKS updated the control plane automatically, manually update cluster add-ons and Amazon EC2 nodes.",
      "replacement": null,
      "affected_versions": [
        "1.33"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.33",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-33-extended-support-end-of-support"
    },
    {
      "slug": "oci-oracle-database-21c-end-of-support",
      "title": "Oracle Database 21c end of Premier Support",
      "summary": "End of Premier Support date for Oracle Database 21c: 31 Jul 2027. This is the date that endoflife.date lists under Premier Support for the release.",
      "cloud": "oci",
      "service": "Oracle Database",
      "service_slug": "oracle-database",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-07-31",
      "effective_precision": "day",
      "impact": "The date is the one that endoflife.date lists under Premier Support for Oracle Database 21c, for Oracle Database On-Premises Server Releases for Linux x86-64. endoflife.date notes that release dates may vary across cloud and on-premises offers and support stages, and reports two release types:\n\n- Long-Term Releases (LTR) have Extended Support after Premier Support.\n- Oracle may offer, for some LTR, one year of free Extended Support.\n- Innovation Releases have no Extended Support.\n- The endoflife.date table marks Long-Term Releases with LTR and shows the Extended Support status of each release.",
      "migration_path": "The Oracle Database documentation lists Install and Upgrade guides by release: [Oracle Database documentation](https://docs.oracle.com/en/database/oracle/oracle-database/).",
      "replacement": null,
      "affected_versions": [
        "21"
      ],
      "source_url": "https://endoflife.date/oracle-database",
      "extra_source_urls": [
        "https://support.oracle.com/knowledgefs?docId=742060"
      ],
      "vendor_ref": "oracle-database@21",
      "last_checked_at": "2026-11-12T09:55:56.483Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/oci-oracle-database-21c-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-nvidia-p4-retirement",
      "title": "Compute Engine: NVIDIA P4 GPU shutdown",
      "summary": "Shutdown date for NVIDIA P4 GPUs on Google Cloud: 1 Aug 2027. From that date, resources that run NVIDIA P4 GPUs cannot be created, launched, or accessed.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-08-01",
      "effective_date": "2027-08-01",
      "effective_precision": "day",
      "impact": "From 1 Aug 2027, you cannot create, launch, or access any Google Cloud resources that run NVIDIA P4 GPUs. At that date, Google Cloud shuts down any remaining compute instances and resources that run NVIDIA P4 GPUs. Besides Compute Engine instances, the affected resources include Google Kubernetes Engine nodes, Cloud Workstations workstations and Dataflow pipeline jobs. Committed use discounts (CUDs) for NVIDIA P4 GPUs:\n\n- 3-year committed use discounts can no longer be purchased or renewed.\n- Existing active 1-year and 3-year commitments remain valid until their expiration date.\n- For active commitments that expire after the platform's End of Life (EOL) date, Google says to contact your account team or Technical Account Manager (TAM).",
      "migration_path": "1. Choose a new GPU model. Google recommends the G4 or G2 machine series.\n2. Check that the selected GPU model is available in your locations. For services other than Gemini Enterprise Agent Platform and Cloud Workstations, see [GPU regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones). For those services, see [Gemini Enterprise Agent Platform accelerator locations](https://docs.cloud.google.com/gemini-enterprise-agent-platform/machine-learning/general/locations#accelerators) and [Cloud Workstations GPU availability by region and zone](https://docs.cloud.google.com/workstations/docs/available-gpus#gpu_availability_by_region_and_zone).\n3. For Compute Engine, if the existing instance uses Local SSD disks with data you want to keep, first move the contents to a Persistent Disk volume. Then create a new compute instance. An existing instance cannot be changed in place from an N1 general-purpose machine type to an accelerator-optimized machine type. See [Create a G2 or G4 instance](https://docs.cloud.google.com/compute/docs/gpus/create-gpu-vm-g-series).\n4. Move Persistent Disk volumes to the new instance, reassign static IP addresses, and install GPU drivers and your applications on it.\n5. Delete the old compute instance.\n6. For other Google Cloud services, update your configurations to reference a supported GPU model, then restart or recreate your resources.",
      "replacement": "G2 (NVIDIA L4) or G4 (NVIDIA RTX PRO 6000) machine series",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/compute/docs/deprecations",
      "extra_source_urls": [
        "https://docs.cloud.google.com/compute/docs/eol/p4-eos"
      ],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-nvidia-p4-retirement"
    },
    {
      "slug": "gcp-compute-engine-nvidia-t4-retirement",
      "title": "Compute Engine: NVIDIA T4 GPU shutdown",
      "summary": "Shutdown date for NVIDIA T4 GPUs on Google Cloud: 1 Aug 2027. From that date, resources that run NVIDIA T4 GPUs cannot be created, launched, or accessed.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-08-01",
      "effective_date": "2027-08-01",
      "effective_precision": "day",
      "impact": "From 1 Aug 2027, you cannot create, launch, or access any Google Cloud resources that run NVIDIA T4 GPUs. At that date, Google Cloud shuts down any remaining compute instances and resources that run NVIDIA T4 GPUs. Affected services listed by Google: Compute Engine, Google Kubernetes Engine, Gemini Enterprise Agent Platform (including Workbench), Colab Enterprise, Cloud Workstations, Dataflow, Managed Service for Apache Spark, and Deep Learning VM and Container-Optimized OS VM instances. Committed use discounts (CUDs) for NVIDIA T4 GPUs:\n\n- 3-year committed use discounts can no longer be purchased or renewed.\n- Existing active 1-year and 3-year commitments remain valid until their expiration date.\n- For active commitments that expire after the platform's End of Life (EOL) date, Google says to contact your account team or Technical Account Manager (TAM).",
      "migration_path": "1. Choose a new GPU model. Google recommends the G4 or G2 machine series.\n2. Check that the selected GPU model is available in your locations. For services other than Gemini Enterprise Agent Platform, Colab Enterprise and Cloud Workstations, see [GPU regions and zones](https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones). For those services, see [Gemini Enterprise Agent Platform accelerator locations](https://docs.cloud.google.com/gemini-enterprise-agent-platform/machine-learning/general/locations#accelerators) and [Cloud Workstations GPU availability by region and zone](https://docs.cloud.google.com/workstations/docs/available-gpus#gpu_availability_by_region_and_zone).\n3. For Compute Engine, if the existing instance uses Local SSD disks with data you want to keep, first move the contents to a Persistent Disk volume. Then create a new compute instance. An existing instance cannot be changed in place from an N1 general-purpose machine type to an accelerator-optimized machine type. See [Create a G2 or G4 instance](https://docs.cloud.google.com/compute/docs/gpus/create-gpu-vm-g-series).\n4. Move Persistent Disk volumes to the new instance, reassign static IP addresses, and install GPU drivers and your applications on it.\n5. Delete the old compute instance.\n6. For other Google Cloud services, update your configurations to reference a supported GPU model, then restart or recreate your resources.",
      "replacement": "G2 (NVIDIA L4) or G4 (NVIDIA RTX PRO 6000) machine series",
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/compute/docs/deprecations",
      "extra_source_urls": [
        "https://docs.cloud.google.com/compute/docs/eol/t4-eos"
      ],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-nvidia-t4-retirement"
    },
    {
      "slug": "aws-eks-kubernetes-1-36-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.36 end of standard support",
      "summary": "End of standard support date for Kubernetes 1.36 on Amazon EKS: 2 Aug 2027. After that date the version enters extended support for 12 months, at an additional cost per cluster hour.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-08-02",
      "effective_precision": "day",
      "impact": "Once Kubernetes 1.36 is past the end of standard support date, it enters extended support for the next 12 months, at an additional cost per cluster hour.\n\n- Extended support is enabled by default.\n- Billing starts at the beginning of the day that the version reaches end of standard support, in the UTC+0 timezone.\n- A cluster whose upgrade policy has extended support disabled is automatically upgraded to the next Kubernetes version at the end of standard support.\n- Extended support cannot be disabled once a cluster has entered it.\n- A cluster not updated before the extended support period ends is automatically updated by Amazon EKS to the earliest supported version.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version. Then upgrade the control plane to a version in the standard support period, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n3. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n4. To stay on Kubernetes 1.36, keep the cluster upgrade policy set to EXTENDED. An additional cost applies to clusters running in extended support, see the [pricing page](https://aws.amazon.com/eks/pricing/).\n5. To avoid extended support, set the upgrade policy to standard support while the cluster is still on standard support, as described in [Disable EKS extended support](https://docs.aws.amazon.com/eks/latest/userguide/disable-extended-support.html). The cluster is then auto upgraded at the end of standard support.",
      "replacement": null,
      "affected_versions": [
        "1.36"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.36",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-36-end-of-support"
    },
    {
      "slug": "gcp-gke-kubernetes-1-36-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.36 end of standard support",
      "summary": "End of standard support date for GKE Kubernetes 1.36: 9 Aug 2027. After that date the minor version is unsupported for clusters not enrolled in the Extended channel, and GKE automatically upgrades them to the next supported minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-08-09",
      "effective_precision": "day",
      "impact": "After the standard support period, the minor version becomes unsupported and unavailable for all clusters not enrolled in the Extended channel. GKE automatically upgrades those clusters to the next supported minor version.\n\n- Those clusters receive no security patches or bug fixes for the minor version after the end of standard support.\n- The automatic upgrade also applies to clusters not enrolled in any release channel. Nodes are typically scheduled for an automated upgrade within one month of the end of support date, and actual timing can vary.\n- As a temporary, emergency measure that Google does not recommend, a \"No upgrades\" maintenance exclusion can delay the upgrade for up to 90 days after the end of support date.\n- Extended channel clusters receive security patches until the end of extended support, for an additional fee per cluster.\n- Release schedule dates are subject to change.",
      "migration_path": "1. Upgrade the cluster and nodes to a supported version. Google requires this before you engage Cloud Customer Care about a cluster or nodes on an unsupported version.\n2. Without action, GKE schedules an automatic upgrade to the next supported minor version before the end of support. The timing depends on the schedule for the cluster's release channel.\n3. During the standard support period, a maintenance exclusion at the cluster level can prevent this minor version upgrade. GKE also does not upgrade clusters that use deprecated features or APIs during that period.\n4. To keep using the minor version until the end of extended support, change the cluster to the Extended channel. Extended support adds approximately 10 months after the standard support period, for up to 24 months of support in total.\n5. Review the [pricing for extended support](https://cloud.google.com/kubernetes-engine/pricing#extended-support-period) first, because pay-per-use costs apply in the extended support period.\n6. Review the limitations of the Extended channel: clusters that use certain features cannot be enrolled, the extended support period does not extend the cluster's credential expiry date, and GKE pauses patch node auto-upgrades when it updates the Container-Optimized OS milestone that the minor version uses.",
      "replacement": null,
      "affected_versions": [
        "1.36"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [
        "https://endoflife.date/google-kubernetes-engine"
      ],
      "vendor_ref": "gke@1.36",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-36-end-of-support"
    },
    {
      "slug": "azure-hpc-pack-all-versions-end-of-support",
      "title": "Microsoft HPC Pack: all versions end of support",
      "summary": "End of support date for all versions of Microsoft HPC Pack: 27 Aug 2027. After that date HPC Pack receives no updates, fixes, or technical support. Existing deployments remain operational but unsupported.",
      "cloud": "azure",
      "service": "Microsoft HPC Pack",
      "service_slug": "hpc-pack",
      "category": "service",
      "type": "end_of_support",
      "announced_date": "2026-09-29",
      "effective_date": "2027-08-27",
      "effective_precision": "day",
      "impact": "The end of support covers all versions of HPC Pack. After the end of support date, HPC Pack receives no updates, fixes, or technical support. Existing deployments remain operational but unsupported. Until that date, Microsoft provides limited, retirement-only support: security updates, guidance from existing documentation, and case-by-case evaluation of long-term support options where available, with no non-security fixes, new features, validation of new operating systems, hardware, dependencies, architectures, or integrations, migration planning or consulting, or unsupported configurations.",
      "migration_path": "1. Assess your HPC Pack workloads and begin transitioning them.\n2. Consider Azure Batch for managed parallel and HPC scheduling, or another appropriate Azure service. No alternative guarantees one-to-one feature parity.\n3. Engage your Microsoft account team or Cloud Solution Architect for planning.\n4. Share needs and transition challenges through the [ESU Extend Request](https://forms.cloud.microsoft/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR0FNZgYky3lJpHzezA6g7ExUOFlFRk1MOU1GU1hGVlRRRkc2UVJBSTBRSi4u) form.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=570046",
      "extra_source_urls": [],
      "vendor_ref": "570046",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-hpc-pack-all-versions-end-of-support"
    },
    {
      "slug": "azure-vmware-solution-av36-node-retirement",
      "title": "Azure VMware Solution: AV36 node retirement",
      "summary": "Retirement date for the Azure VMware Solution AV36 node type: 30 Aug 2027. All AV36 SDDCs are retired after that date and access to them is removed the following day.",
      "cloud": "azure",
      "service": "Azure VMware Solution",
      "service_slug": "vmware-solution",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-06-02",
      "effective_date": "2027-08-30",
      "effective_precision": "day",
      "impact": "All AV36 SDDCs are retired after 30 Aug 2027, regardless of individual RI expiration dates, to align with the AVS License-included service retirement. On August 31, 2027, these SDDCs are no longer accessible, and Microsoft retains the data for up to 60 days so the customer can retrieve it. Broadcom ends support for the current AV36 VCF version on September 30, 2027, and the AV36 SKU is not compatible with VMware Cloud Foundation (VCF) 9. June 30, 2026 was the last day to buy a 1-year RI for AV36 VCF BYOL.",
      "migration_path": "1. Review your current AV36 SDDCs and work with your Microsoft Account Team, which also provides key dates for AV36 PayGo subscriptions.\n2. Identify available AVS node types on the [Azure Product by Region](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/table) page.\n3. Read the [AVS Documentation page](https://learn.microsoft.com/en-us/azure/azure-vmware/architecture-migrate) to learn about HCX migrations between AVS node types.",
      "replacement": null,
      "affected_versions": [
        "AV36"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=564735",
      "extra_source_urls": [
        "https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/table",
        "https://learn.microsoft.com/en-us/azure/azure-vmware/architecture-migrate",
        "https://azure.microsoft.com/updates?id=503883"
      ],
      "vendor_ref": "564735",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-vmware-solution-av36-node-retirement"
    },
    {
      "slug": "azure-vmware-solution-license-included-retirement",
      "title": "Azure VMware Solution: license-included service retirement",
      "summary": "Retirement date for the Azure VMware Solution (AVS) license-included service: 30 Aug 2027. License-included PayGo SKUs retire on October 31, 2026; Reserved Instance customers are required to buy portable Broadcom VCF licenses and move to an AVS VCF BYOL SKU before the retirement date.",
      "cloud": "azure",
      "service": "Azure VMware Solution",
      "service_slug": "vmware-solution",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-08-18",
      "effective_date": "2027-08-30",
      "effective_precision": "day",
      "impact": "Retirement date for the AVS license-included service: 30 Aug 2027, as a result of a Broadcom VCF licensing change. The source names the retirement date as the last day of all AVS license-included services. Customers using license-included Reserved Instance (RI) SKUs are required to purchase portable Broadcom VCF licenses and transition to an AVS VCF BYOL SKU before that date; the source names August 31, 2027 as the day of service disruption otherwise. AVS license-included PayGo SKUs retire on October 31, 2026. Microsoft allows the exchange of reservations that expire after the retirement date, and the source gives the same date for the AV36 SKU retirement.",
      "migration_path": "1. Purchase portable VCF licenses from Broadcom and complete the transition to an AVS VCF BYOL SKU before the retirement date.\n2. If you are evaluating modernization, assess current AVS environments and develop a transition roadmap.\n3. Contact your account team to plan your transition.\n4. See the page Microsoft links for more: [Learn more](https://aka.ms/AVS_License-included_retirement).",
      "replacement": "AVS VCF BYOL SKU",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=569535",
      "extra_source_urls": [
        "https://techcommunity.microsoft.com/blog/azuremigrationblog/broadcom-vmware-licensing-changes-what-azure-vmware-solution-customers-need-to-k/4448784",
        "https://aka.ms/AVS_License-included_retirement"
      ],
      "vendor_ref": "569535",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-vmware-solution-license-included-retirement"
    },
    {
      "slug": "aws-rds-postgresql-15-18-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15.18 end of standard support",
      "summary": "End of standard support date for PostgreSQL 15.18 on Amazon RDS for PostgreSQL: Sep 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Sep 2027 as the RDS end of standard support date of minor version 15.18. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "15.18"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@15.18",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-18-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-15-19-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15.19 end of standard support",
      "summary": "End of standard support date for PostgreSQL 15.19 on Amazon RDS for PostgreSQL: Sep 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Sep 2027 as the RDS end of standard support date of minor version 15.19. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "15.19"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@15.19",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-19-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-14-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16.14 end of standard support",
      "summary": "End of standard support date for PostgreSQL 16.14 on Amazon RDS for PostgreSQL: Sep 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Sep 2027 as the RDS end of standard support date of minor version 16.14. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "16.14"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@16.14",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-14-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-15-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16.15 end of standard support",
      "summary": "End of standard support date for PostgreSQL 16.15 on Amazon RDS for PostgreSQL: Sep 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Sep 2027 as the RDS end of standard support date of minor version 16.15. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "16.15"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@16.15",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-15-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-10-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17.10 end of standard support",
      "summary": "End of standard support date for PostgreSQL 17.10 on Amazon RDS for PostgreSQL: Sep 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Sep 2027 as the RDS end of standard support date of minor version 17.10. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "17.10"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@17.10",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-10-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-11-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17.11 end of standard support",
      "summary": "End of standard support date for PostgreSQL 17.11 on Amazon RDS for PostgreSQL: Sep 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Sep 2027 as the RDS end of standard support date of minor version 17.11. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "17.11"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@17.11",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-11-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-18-4-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 18.4 end of standard support",
      "summary": "End of standard support date for PostgreSQL 18.4 on Amazon RDS for PostgreSQL: Sep 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Sep 2027 as the RDS end of standard support date of minor version 18.4. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "18.4"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@18.4",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-18-4-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-18-6-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 18.6 end of standard support",
      "summary": "End of standard support date for PostgreSQL 18.6 on Amazon RDS for PostgreSQL: Sep 2027. AWS lists it in the minor version table of its release calendar, where dates with only a month and a year are approximate.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The AWS release calendar for Amazon RDS for PostgreSQL lists Sep 2027 as the RDS end of standard support date of minor version 18.6. Minor versions can reach the end of standard support before the corresponding major versions. Dates that show only a month and a year are approximate, and AWS updates them with the exact date when it is known. For the policy on deprecating database engine versions, AWS refers to Database Engine Versions in the Amazon RDS FAQs.",
      "migration_path": "1. Find the valid upgrade targets for the database. The AWS Management Console shows them when you upgrade a database. The AWS CLI command `aws rds describe-db-engine-versions`, run with the `--engine postgres`, `--engine-version` and `--query` options that the AWS page gives, also identifies them. See [Finding valid upgrade targets](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.html#USER_UpgradeDBInstance.PostgreSQL.FindingTargets).\n2. If the database has read replicas, upgrade all of the read replicas before you upgrade the source instance or cluster.\n3. Start the minor version upgrade manually by modifying the database. For a Multi-AZ DB instance deployment, the database might not be available for several minutes while the upgrade completes. See [Manually upgrading the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Upgrading.html#USER_UpgradeDBInstance.Upgrading.Manual).\n4. The Auto minor version upgrade option can be enabled when you create or modify the database. A database with this option is upgraded automatically during its maintenance window if it runs a minor version lower than the current automatic upgrade minor version. AWS states that RDS designates an automatic upgrade version for some major versions in some AWS Regions. The AWS page gives an AWS CLI command that determines the current automatic minor upgrade target for a minor version in a Region: if no version in its output has an AutoUpgrade value of True, RDS has not designated an automatic upgrade version for that major version in that Region. RDS does not automatically set newer released minor versions as the automatic upgrade version. See [Automatic minor version upgrades for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.Minor.html).\n5. After an upgrade is complete, you cannot revert to the previous version of the DB engine. To return to it, restore the DB snapshot taken before the upgrade to create a new database. Amazon RDS takes that snapshot only if the backup retention period is greater than 0. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "18.6"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [],
      "vendor_ref": "amazon-rds-postgresql@18.6",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-18-6-end-of-support"
    },
    {
      "slug": "azure-app-service-java-8-11-17-end-of-support",
      "title": "Azure App Service: Java 8, 11 and 17 end of support",
      "summary": "End of support date for Java 8, 11 and 17 on Azure App Service: 1 Sep 2027. Apps hosted on App Service keep running after that date but stop receiving security updates and customer service for these versions.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": "2026-10-06",
      "effective_date": "2027-09-01",
      "effective_precision": "day",
      "impact": "After the end of support date for Java 8, 11 and 17, apps hosted on App Service continue to run, but security updates are no longer available. Microsoft no longer provides customer service for Java 8, 11 and 17 after that date.",
      "migration_path": "Upgrade the app to Java 25 before 1 Sep 2027. [Follow the steps to upgrade your app](https://aka.ms/javasupport).",
      "replacement": "Java 25",
      "affected_versions": [
        "8",
        "11",
        "17"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=568585",
      "extra_source_urls": [
        "https://aka.ms/javasupport",
        "https://learn.microsoft.com/azure/app-service/language-support-policy",
        "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy"
      ],
      "vendor_ref": "568585",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-java-8-11-17-end-of-support"
    },
    {
      "slug": "azure-automanage-best-practices-retirement",
      "title": "Azure Automanage: Best Practices retirement",
      "summary": "Retirement date for Azure Automanage Best Practices: Sep 2027. Microsoft encourages customers to transition to Azure Policy before the retirement date.",
      "cloud": "azure",
      "service": "Azure Automanage",
      "service_slug": "automanage",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-09-26",
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "The retirement affects virtual machines managed with Azure Automanage Best Practices. Microsoft describes it as automatically onboarding VMs to services like Azure Monitor, Backup and Microsoft Defender and correcting configuration drift. Microsoft states that all Automanage Best Practices features are available in Azure Policy. Automanage Best Practices is cost-free, but paid services enabled through Automanage may incur usage charges billed directly by those services.",
      "migration_path": "Transition to Azure Policy before the retirement date. Microsoft links further details under [Learn more](https://go.microsoft.com/fwlink/?linkid=2287112).",
      "replacement": "Azure Policy",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-automanage-best-practices-retirement-migrate-to-azure-policy",
      "extra_source_urls": [
        "https://azure.microsoft.com/en-us/pricing/details/azure-automanage/"
      ],
      "vendor_ref": "azure-automanage-best-practices-retirement-migrate-to-azure-policy",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-automanage-best-practices-retirement"
    },
    {
      "slug": "azure-functions-java-11-end-of-support",
      "title": "Azure Functions: Java 11 end of support",
      "summary": "End of support date for Java 11 on Azure Functions: Sep 2027. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Java 11 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "11"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@java:11",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-java-11-end-of-support"
    },
    {
      "slug": "azure-functions-java-17-end-of-support",
      "title": "Azure Functions: Java 17 end of support",
      "summary": "End of support date for Java 17 on Azure Functions: Sep 2027. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Java 17 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "17"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@java:17",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-java-17-end-of-support"
    },
    {
      "slug": "azure-functions-java-8-end-of-support",
      "title": "Azure Functions: Java 8 end of support",
      "summary": "End of support date for Java 8 on Azure Functions: Sep 2027. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Java 8 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "8"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@java:8",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-java-8-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-36-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.36 platform-initiated upgrade",
      "summary": "Microsoft lists Sep 2027 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.36 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.36"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.36",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-36-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-load-balancer-numberofprobes-property-end-of-support",
      "title": "Azure Load Balancer: numberOfProbes property end of support",
      "summary": "End of support date for the Azure Load Balancer numberOfProbes property: 1 Sep 2027. Microsoft does not support the property after that date and names the probeThreshold property as the one to use.",
      "cloud": "azure",
      "service": "Azure Load Balancer",
      "service_slug": "load-balancer",
      "category": "feature",
      "type": "end_of_support",
      "announced_date": "2024-10-10",
      "effective_date": "2027-09-01",
      "effective_precision": "day",
      "impact": "Support for the Azure Load Balancer numberOfProbes property ends on 1 Sep 2027. Microsoft does not support the property after that date. To avoid service disruption, Microsoft advises upgrading apps to API version 2022-05-01 or higher and using the Azure Load Balancer probeThreshold property.",
      "migration_path": "1. Upgrade your apps to API version 2022-05-01 or higher. Microsoft links guidance on [updating your API](https://aka.ms/VersionHowTo).\n2. Before 1 Sep 2027, stop using the numberOfProbes property, migrate to the probeThreshold property, or both.",
      "replacement": "probeThreshold property",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=end-of-support-announcement-for-azure-load-balancer-numberofprobes-property-on-1-september-2027",
      "extra_source_urls": [
        "https://aka.ms/VersionHowTo"
      ],
      "vendor_ref": "end-of-support-announcement-for-azure-load-balancer-numberofprobes-property-on-1-september-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-load-balancer-numberofprobes-property-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-cos-125-lts-image-end-of-support",
      "title": "Compute Engine: COS 125 LTS image end of support",
      "summary": "EOS and image deprecation date for the COS 125 LTS public image on Compute Engine: Sep 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-09-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of COS 125 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "COS 125 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "cos-125-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-cos-125-lts-image-end-of-support"
    },
    {
      "slug": "azure-ai-document-intelligence-v2-1-api-retirement",
      "title": "Azure AI Document Intelligence: GA API v2.1 retirement",
      "summary": "Retirement date for the Azure AI Document Intelligence GA API v2.1: 15 Sep 2027. From that date, all requests to the service with that API version fail.",
      "cloud": "azure",
      "service": "Azure AI Document Intelligence",
      "service_slug": "ai-document-intelligence",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2024-09-12",
      "effective_date": "2027-09-15",
      "effective_precision": "day",
      "impact": "The Document Intelligence GA API v2.1 is retired on the retirement date, and all requests to the service with that API version fail. Microsoft recommends re-training custom models with a newer GA API.",
      "migration_path": "1. [Migrate to a newer GA API version of Document Intelligence](https://go.microsoft.com/fwlink/?linkid=2285844) by 15 Sep 2027.\n2. If you use custom models, re-train them with a newer GA API, as Microsoft recommends.",
      "replacement": "A newer GA API version of Document Intelligence",
      "affected_versions": [
        "2.1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=azure-docuement-intelligence-v2-retirement",
      "extra_source_urls": [],
      "vendor_ref": "azure-docuement-intelligence-v2-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-document-intelligence-v2-1-api-retirement"
    },
    {
      "slug": "azure-site-recovery-classic-alerts-retirement",
      "title": "Azure Site Recovery: Classic Alerts retirement",
      "summary": "Retirement date for Classic Alerts in Azure Site Recovery: 23 Sep 2027. Microsoft recommends moving to the alerting solution based on Azure Monitor.",
      "cloud": "azure",
      "service": "Azure Site Recovery",
      "service_slug": "site-recovery",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-09-26",
      "effective_date": "2027-09-23",
      "effective_precision": "day",
      "impact": "The Classic Alerts solution for Azure Site Recovery retires on the retirement date. Anyone still using the older classic alerts solution is affected. The replacement is an alerting solution based on Azure Monitor.",
      "migration_path": "Move from classic alerts to Azure Monitor alerts. Microsoft provides a guided experience through Business Continuity Center and Recovery Services Vault: [Migrate to Azure Monitor Alerts](https://go.microsoft.com/fwlink/?linkid=2287019).",
      "replacement": "Azure Monitor alerts",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-site-recovery-classic-alerts-retirement",
      "extra_source_urls": [],
      "vendor_ref": "azure-site-recovery-classic-alerts-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-site-recovery-classic-alerts-retirement"
    },
    {
      "slug": "azure-sphere-legacy-service-interfaces-retirement",
      "title": "Azure Sphere: Legacy API and CLI interfaces retirement",
      "summary": "Retirement date for the Azure Sphere Legacy service interfaces, including the Azure Sphere (Legacy) API (PAPI) and the Azure Sphere (Legacy) CLI (azsphere): 27 Sep 2027. Device management moves to Azure Sphere (Integrated).",
      "cloud": "azure",
      "service": "Azure Sphere",
      "service_slug": "sphere",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2024-10-03",
      "effective_date": "2027-09-27",
      "effective_precision": "day",
      "impact": "After the retirement date, Azure Sphere devices can no longer be managed with the Azure Sphere (Legacy) API and CLI interfaces. This covers the Azure Sphere (Legacy) API, also known as PAPI, and the Azure Sphere (Legacy) CLI, also known as azsphere. Until the retirement date, Azure Sphere (Legacy) is fully supported. Azure Sphere (Integrated) supports all Azure Sphere (Legacy) features.",
      "migration_path": "1. Migrate from Azure Sphere (Legacy) to Azure Sphere (Integrated) before the retirement date.\n2. Manage Azure Sphere devices in Azure portal and the Azure CLI.\n3. Update custom automation and applications to use the Azure Sphere (Integrated) API.\n4. For how to migrate, see [this blog post](https://go.microsoft.com/fwlink/?linkid=2289217).",
      "replacement": "Azure Sphere (Integrated)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-sphere-legacy-interface-retirement",
      "extra_source_urls": [],
      "vendor_ref": "azure-sphere-legacy-interface-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sphere-legacy-service-interfaces-retirement"
    },
    {
      "slug": "azure-container-apps-functions-v1-retirement",
      "title": "Azure Container Apps: Functions on Azure Container Apps V1 retirement",
      "summary": "Retirement date for Functions on Azure Container Apps V1: 29 Sep 2027. After that date, existing V1 apps stop running and no longer process requests or event-driven triggers.",
      "cloud": "azure",
      "service": "Azure Container Apps",
      "service_slug": "container-apps",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-09-29",
      "effective_date": "2027-09-29",
      "effective_precision": "day",
      "impact": "After the retirement date, existing Functions on Azure Container Apps V1 apps stop running and no longer process requests or event-driven triggers. Functions on Azure Container Apps V2 uses a native Azure Container App configured with `kind=functionapp`. The existing container image can be reused, and the standard migration path does not require function code changes.",
      "migration_path": "1. Review your Azure environments and migrate all affected apps to the Functions on Azure Container Apps V2 hosting model before the retirement date. See [Migrate to Azure Functions v2 on Azure Container Apps](https://learn.microsoft.com/azure/container-apps/migrate-functions).\n2. Option A: use the [Azure Functions on Azure Container Apps v1 migration assistant](https://github.com/Azure-Samples/functions-on-container-apps-v1-migration-assistant) to help migrate function apps from the V1 to the V2 model.\n3. Option B, manual: record the V1 app's configuration, including secrets, identity, networking, and scaling.\n4. Manual: create a V2 app with `kind=functionapp` and reapply the configuration.\n5. Manual: test all triggers, shift production traffic, and then decommission the V1 app.\n6. Complete migration and production validation before the retirement date.",
      "replacement": "Functions on Azure Container Apps V2",
      "affected_versions": [
        "V1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=570800",
      "extra_source_urls": [
        "https://github.com/Azure-Samples/functions-on-container-apps-v1-migration-assistant",
        "https://learn.microsoft.com/azure/container-apps/migrate-functions",
        "https://learn.microsoft.com/azure/container-apps/functions-usage"
      ],
      "vendor_ref": "570800",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-container-apps-functions-v1-retirement"
    },
    {
      "slug": "azure-arc-open-service-mesh-extension-retirement",
      "title": "Azure Arc: Open Service Mesh extension for Arc-enabled Kubernetes retirement",
      "summary": "Retirement date for the Open Service Mesh extension for Azure Arc-enabled Kubernetes: 30 Sep 2027. The extension gets no new minor versions or features, and security patch updates end on that date.",
      "cloud": "azure",
      "service": "Azure Arc",
      "service_slug": "arc",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2024-09-26",
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "The retirement affects clusters that use the Open Service Mesh extension for Azure Arc-enabled Kubernetes. The extension receives no new minor version releases or new features. Security patch updates are provided only up to the retirement date. The existing extension can be used until the retirement date.",
      "migration_path": "Transition to an open-source alternative such as Istio before the retirement date. Microsoft publishes [migration guidance from Open Service Mesh configurations to Istio](https://go.microsoft.com/fwlink/?linkid=2286591).",
      "replacement": "An open-source alternative such as Istio",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=open-service-mesh-extension-for-aks-retirement",
      "extra_source_urls": [],
      "vendor_ref": "open-service-mesh-extension-for-aks-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-arc-open-service-mesh-extension-retirement"
    },
    {
      "slug": "azure-automation-state-configuration-retirement",
      "title": "Azure Automation: State Configuration retirement",
      "summary": "Retirement date for Azure Automation State Configuration: 30 Sep 2027. On that date, all configurations and node registrations in the feature are deleted. Microsoft names Azure Machine Configuration as the replacement.",
      "cloud": "azure",
      "service": "Azure Automation",
      "service_slug": "automation",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-10-03",
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "On the retirement date, all configurations and node registrations in Azure Automation State Configuration are deleted and the associated historical data is lost. The announcement covers only the State Configuration features of Azure Automation. It does not affect other Azure Automation services such as runbooks or hybrid runbook workers, the Windows DSC Extension or PowerShell Desired State Configuration.",
      "migration_path": "1. In the Azure portal, open \"Automation Accounts\", select each account, then \"Configuration Management\" and \"State Configuration\" to list the stored configurations and the server nodes they are assigned to.\n2. Follow Microsoft's instructions to [migrate](https://go.microsoft.com/fwlink/?linkid=2283717) to Azure Machine Configuration before the retirement date.",
      "replacement": "Azure Machine Configuration",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=planned-service-retirement-azure-automation-state-configuration-16-september-2027",
      "extra_source_urls": [],
      "vendor_ref": "planned-service-retirement-azure-automation-state-configuration-16-september-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-automation-state-configuration-retirement"
    },
    {
      "slug": "azure-content-delivery-network-standard-from-microsoft-classic-retirement",
      "title": "Azure CDN Standard from Microsoft (classic) retirement",
      "summary": "Retirement date for Azure CDN Standard from Microsoft (classic): 30 Sep 2027. Microsoft directs customers to migrate to Azure Front Door Standard or Premium by that date to avoid service disruptions.",
      "cloud": "azure",
      "service": "Azure Content Delivery Network",
      "service_slug": "content-delivery-network",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-09-26",
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "Azure CDN Standard from Microsoft (classic) is retired on 30 Sep 2027. Since October 1st, 2025, new Azure CDN Standard from Microsoft (classic) resources can no longer be created via the Azure portal, Terraform or command line tools, and all new resources need to be created using Azure Front Door Standard or Premium.",
      "migration_path": "[Migrate to Azure Front Door Standard or Premium](https://go.microsoft.com/fwlink/?linkid=2287306) by 30 Sep 2027 to avoid service disruptions.",
      "replacement": "Azure Front Door Standard or Premium",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-cdn-standard-from-microsoft-classic-will-be-retired-on-30-september-2027",
      "extra_source_urls": [],
      "vendor_ref": "azure-cdn-standard-from-microsoft-classic-will-be-retired-on-30-september-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-content-delivery-network-standard-from-microsoft-classic-retirement"
    },
    {
      "slug": "azure-aks-open-service-mesh-add-on-retirement",
      "title": "Azure Kubernetes Service: Open Service Mesh add-on retirement",
      "summary": "Retirement date for the Open Service Mesh add-on for Azure Kubernetes Service (AKS): 30 Sep 2027. Security patch updates end on that date. The add-on receives no new minor versions or features.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-09-26",
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "The Open Service Mesh add-on for AKS is retired on 30 Sep 2027, following the upstream archival of the open-source Open Service Mesh project. The add-on no longer receives new minor version releases or new features. Security patch updates end on the retirement date. Microsoft states that the existing add-on can continue to be used until the retirement date, and that there are no changes in pricing between the Open Service Mesh add-on and the Istio add-on.",
      "migration_path": "1. Continue to use the existing Open Service Mesh add-on until the retirement date, or transition to the Istio add-on for Azure Kubernetes Service (AKS) before that time.\n2. Use the Microsoft [migration guidance from Open Service Mesh (OSM) configurations to Istio](https://go.microsoft.com/fwlink/?linkid=2286684).",
      "replacement": "Istio add-on for Azure Kubernetes Service (AKS)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=open-service-mesh-add-on-for-aks-will-be-retired-on-september-30-2027",
      "extra_source_urls": [
        "https://azure.microsoft.com/en-us/updates/ga-istiobased-service-mesh-addon-for-azure-kubernetes-service/"
      ],
      "vendor_ref": "open-service-mesh-add-on-for-aks-will-be-retired-on-september-30-2027",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-open-service-mesh-add-on-retirement"
    },
    {
      "slug": "azure-aks-pod-name-metric-dimension-retirement",
      "title": "Azure Kubernetes Service: pod name dimension on pod metrics retirement",
      "summary": "From 30 Sep 2027, the pod name dimension is retired on two AKS Azure Monitor platform metrics, kube_pod_status_phase and kube_pod_status_ready. The metrics become aggregate pod counters.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-10-06",
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "From 30 Sep 2027, support for the pod name dimension is retired on the Azure Monitor platform metrics kube_pod_status_phase (number of pods by phase) and kube_pod_status_ready (number of pods in Ready state). After the change, the pod name dimension is not available for filtering, grouping, or alerting, while metric names stay the same, aggregate pod counts remain available, and namespace-level monitoring scenarios remain supported. Until the retirement date, AKS maintains both the existing and the new aggregate implementations, both are populated with data, and existing monitoring experiences continue to function. Dashboards, workbooks, alerts, automation, or monitoring workflows that filter, split or group these metrics by the pod name dimension may be affected.",
      "migration_path": "1. Check whether any dashboard, workbook, alert, automation, or monitoring workflow uses kube_pod_status_phase or kube_pod_status_ready and filters, splits or groups on the pod name dimension.\n2. If you use aggregate pod counts, no action is required.\n3. If you use the pod name dimension, update dashboards, alerts, workbooks, and automation before the retirement date.\n4. For pod-level monitoring and troubleshooting, Microsoft recommends [Azure Monitor Managed Prometheus](https://learn.microsoft.com/azure/azure-monitor/metrics/prometheus-metrics-overview#azure-monitor-managed-service-for-prometheus) and [Kubernetes-native pod metrics](https://learn.microsoft.com/azure/azure-monitor/containers/prometheus-metrics-scrape-default#kube-state).",
      "replacement": "Azure Monitor Managed Prometheus and Kubernetes-native pod metrics (for pod-level monitoring)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=570232",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/aks/monitor-aks-reference#category-pods",
        "https://learn.microsoft.com/azure/azure-monitor/metrics/prometheus-metrics-overview#azure-monitor-managed-service-for-prometheus",
        "https://learn.microsoft.com/azure/azure-monitor/containers/prometheus-metrics-scrape-default#kube-state"
      ],
      "vendor_ref": "570232",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-pod-name-metric-dimension-retirement"
    },
    {
      "slug": "azure-load-balancer-inbound-nat-pools-retirement",
      "title": "Azure Load Balancer: Inbound NAT pools retirement",
      "summary": "Retirement date for Inbound NAT pools in Azure Load Balancer (port forwarding to Virtual Machine Scale Set instances): 30 Sep 2027. New Inbound NAT pools cannot be created from November 15, 2026. Single-VM Inbound NAT rules version 1 are not affected.",
      "cloud": "azure",
      "service": "Azure Load Balancer",
      "service_slug": "load-balancer",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-06-11",
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "Inbound NAT pools in Azure Load Balancer, which forward ports to Virtual Machine Scale Set instances, are retired on 30 Sep 2027. Existing configuration continues to function until that date. Starting November 15, 2026, new Inbound NAT pools cannot be created. Inbound NAT rules version 1 that forward ports to a single virtual machine are not affected.",
      "migration_path": "Microsoft recommends that you [migrate to Inbound NAT rules version 2](https://learn.microsoft.com/azure/load-balancer/load-balancer-nat-pool-migration) in Azure Load Balancer by the retirement date.",
      "replacement": "Inbound NAT rules version 2",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=565482",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/load-balancer/load-balancer-nat-pool-migration"
      ],
      "vendor_ref": "565482",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-load-balancer-inbound-nat-pools-retirement"
    },
    {
      "slug": "azure-network-watcher-nsg-flow-logs-retirement",
      "title": "Azure Network Watcher: NSG flow logs retirement",
      "summary": "Network security group (NSG) flow logs in Azure Network Watcher are retired on 30 Sep 2027. New NSG flow logs can no longer be created, and Microsoft recommends virtual network flow logs instead.",
      "cloud": "azure",
      "service": "Azure Network Watcher",
      "service_slug": "network-watcher",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-09-26",
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "Network security group (NSG) flow logs in Azure Network Watcher are retired on the retirement date. Creating new NSG flow logs has been blocked since June 30th, 2025. Microsoft states that migrating to virtual network flow logs by the retirement date avoids service disruptions.",
      "migration_path": "1. Migrate to [virtual network flow logs](https://go.microsoft.com/fwlink/?linkid=2287108) in Network Watcher, which Microsoft recommends, before the retirement date: [migrate to virtual network flow logs](https://go.microsoft.com/fwlink/?linkid=2287109).\n2. See service retirements that may impact your resources in the [Azure Retirement Workbook](https://go.microsoft.com/fwlink/?linkid=2279408). A retirement can take up to two weeks after its announcement to appear there.",
      "replacement": "Virtual network flow logs",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-nsg-flow-logs-retirement",
      "extra_source_urls": [],
      "vendor_ref": "azure-nsg-flow-logs-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-network-watcher-nsg-flow-logs-retirement"
    },
    {
      "slug": "azure-sql-database-sql-data-sync-retirement",
      "title": "Azure SQL Database: SQL Data Sync retirement",
      "summary": "Retirement date for SQL Data Sync: 30 Sep 2027. On that date, workloads running SQL Data Sync are deleted and the associated application data is lost.",
      "cloud": "azure",
      "service": "Azure SQL Database",
      "service_slug": "sql-database",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-10-03",
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "SQL Data Sync can be used without disruption until the retirement date. On 30 Sep 2027, workloads running SQL Data Sync are deleted and the associated application data is lost. Microsoft states that the right alternative depends on the individual use case.",
      "migration_path": "1. Choose an alternative data replication or synchronization solution for your use case. The source lists Azure Data Factory, Azure Functions, read replicas, and SQL features such as linked server, mirroring, Always-On, and transaction replication.\n2. Follow the [Microsoft migration instructions](https://go.microsoft.com/fwlink/?linkid=2288253) to move to a replacement option before 30 Sep 2027.\n3. For technical help with a support plan, create a [support request](https://go.microsoft.com/fwlink/?linkid=2287207) with the problem subtype SQL Data Sync.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=sql-data-sync-retirement",
      "extra_source_urls": [],
      "vendor_ref": "sql-data-sync-retirement",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sql-database-sql-data-sync-retirement"
    },
    {
      "slug": "gcp-cloud-run-ruby-3-3-retirement",
      "title": "Cloud Run: Ruby 3.3 decommission",
      "summary": "Decommission date for Ruby 3.3 on Cloud Run: 30 Sep 2027. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-09-30",
      "effective_precision": "day",
      "impact": "The decommission date of Ruby 3.3 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-ruby-3-3-retirement"
    },
    {
      "slug": "azure-functions-python-3-11-end-of-support",
      "title": "Azure Functions: Python 3.11 end of support",
      "summary": "End of support date for Python 3.11 on Azure Functions: Oct 2027. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-10-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Python 3.11 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "3.11"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@python:3.11",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-python-3-11-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-37-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.37 end of life",
      "summary": "End of life date for Kubernetes 1.37 on Azure Kubernetes Service: Oct 2027. After that date, community support for the version ends and clusters not enrolled in long-term support enter platform support, which covers AKS and Azure platform issues only.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-10-01",
      "effective_precision": "month",
      "impact": "After the end of life date, community support for Kubernetes 1.37 ends. Clusters not enrolled in long-term support enter platform support.\n\n- Platform support covers AKS and Azure platform issues only, not Kubernetes functionality and components. New clusters cannot be created during the platform support period.\n- There is a 60-day platform support grace period after the published end of life date to upgrade to a supported minor version. For the initial rollout, the grace period is the window through May 31, 2027.\n- After the grace period, the cluster is eligible for a platform-initiated upgrade to the lowest supported community minor version. No such upgrade starts before June 1, 2027. Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget. Its month in the release calendar is a planning estimate, not an exact date.\n- Regional version removal can happen at a different time from the published date.",
      "migration_path": "1. List the versions AKS offers for the cluster with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. While the cluster is a supported non-LTS cluster, upgrade one minor version at a time. Minor versions cannot be skipped.\n3. Upgrade the control plane and all node pools with `az aks upgrade`, as described in [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n4. If the cluster is already on an unsupported version, use the oldest supported GA target that AKS offers and perform a full-cluster upgrade. Control-plane-only upgrades are not supported for this path. The version-skipping table in [Supported Kubernetes versions in Azure Kubernetes Service (AKS)](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions) labels this an unsupported recovery path: AKS allows the upgrade to proceed, but it is not supported and might carry risks. The platform support table on the same page lists upgrades from an N-3 version to a supported version as supported.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To get extended support for the version instead, enable [long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support). This requires moving the cluster to the Premium tier and explicitly selecting the LTS support plan. Microsoft-managed Calico is not supported in LTS. Once community support for the version has ended, LTS cannot be disabled for that version.",
      "replacement": null,
      "affected_versions": [
        "1.37"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.37",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-37-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-12-sp5-for-sap-image-end-of-support",
      "title": "Compute Engine: SLES 12 SP5 for SAP image end of support",
      "summary": "EOS and image deprecation date for the SLES 12 SP5 for SAP public image on Compute Engine: Oct 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-10-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 12 SP5 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 12 SP5 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-12-sp5-sap",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-12-sp5-for-sap-image-end-of-support"
    },
    {
      "slug": "azure-arc-key-vault-secrets-provider-extension-end-of-support",
      "title": "Azure Arc: Key Vault Secrets Provider Extension end of support",
      "summary": "End of support date for the Azure Key Vault Secrets Provider Extension for Azure Arc-enabled Kubernetes: 9 Oct 2027. Microsoft calls this a retirement. After that date the extension no longer receives new features, bug fixes, security updates, or technical support.",
      "cloud": "azure",
      "service": "Azure Arc",
      "service_slug": "arc",
      "category": "api_sdk",
      "type": "end_of_support",
      "announced_date": "2026-10-09",
      "effective_date": "2027-10-09",
      "effective_precision": "day",
      "impact": "After retirement, the Azure Key Vault Secrets Provider Extension no longer receives new features, bug fixes, security updates, or technical support. The change affects customers using the extension on Azure Arc-enabled Kubernetes clusters. Microsoft states that the Azure Key Vault Secret Store Extension provides equivalent functionality for accessing and synchronizing secrets from Azure Key Vault.",
      "migration_path": "1. Plan to migrate to the [Azure Key Vault Secret Store Extension](https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/secret-store-extension?tabs=arc-k8s%2Csimplified-configuration) before the retirement date.\n2. Use the [migration guidance](https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/secret-store-extension-migration?tabs=direct) to transition workloads and configurations to the Azure Key Vault Secret Store Extension.",
      "replacement": "Azure Key Vault Secret Store Extension",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=570313",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/tutorial-akv-secrets-provider",
        "https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/secret-store-extension?tabs=arc-k8s%2Csimplified-configuration",
        "https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/secret-store-extension-migration?tabs=direct"
      ],
      "vendor_ref": "570313",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-arc-key-vault-secrets-provider-extension-end-of-support"
    },
    {
      "slug": "multi-sql-server-2017-end-of-support",
      "title": "SQL Server 2017 end of support",
      "summary": "End of extended support for SQL Server 2017: 12 Oct 2027. After the end of support, Microsoft no longer provides servicing and support for the product.",
      "cloud": "multi",
      "service": "SQL Server",
      "service_slug": "sql-server",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-10-12",
      "effective_precision": "day",
      "impact": "Each version of SQL Server gets mainstream support followed by extended support, and extended support includes only security updates. End of support means the product reached the end of its support lifecycle, and Microsoft no longer provides servicing and support for it.\n\n- For some releases, customers have the option to purchase Extended Security Updates.\n- Extended Security Updates do not include new features, functional improvements, or customer-requested fixes. Security fixes are limited to fixes rated as Critical.",
      "migration_path": "Microsoft lists these options in [SQL Server end of support options](https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview):\n\n1. Upgrade to a current version of SQL Server, for example with [Upgrade SQL Server Using the Installation Wizard (Setup)](https://learn.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup?view=sql-server-ver17). The [SQL Server migration component in SQL Server Management Studio](https://learn.microsoft.com/en-us/ssms/migrate-sql-server-component) can help detect compatibility problems in the new version.\n2. Or [migrate](https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/) the workload to Azure SQL Managed Instance, Azure SQL Database, or an Azure Virtual Machine.\n3. Or, where Extended Security Updates are offered for the release, subscribe to them and stay on the current environment until you can upgrade or migrate. Only customers with Software Assurance or subscription licenses can use this option, and only for three years.",
      "replacement": null,
      "affected_versions": [
        "14.0"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/sql-server-2017",
      "extra_source_urls": [
        "https://endoflife.date/mssqlserver"
      ],
      "vendor_ref": "mssqlserver@14.0",
      "last_checked_at": "2026-11-12T09:55:53.034Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-sql-server-2017-end-of-support"
    },
    {
      "slug": "aws-neptune-engine-version-1-4-8-0-end-of-support",
      "title": "Amazon Neptune: Engine version 1.4.8.0 end of life",
      "summary": "End of life date for Engine version 1.4.8.0 on Amazon Neptune: 27 Oct 2027. After that date, the version can no longer be used for new clusters or instances, and databases on it are upgraded automatically during a maintenance window.",
      "cloud": "aws",
      "service": "Amazon Neptune",
      "service_slug": "neptune",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-10-27",
      "effective_precision": "day",
      "impact": "When an engine version reaches its end of life, AWS requires an upgrade of the Neptune database to a newer version. From that point:\n\n- New clusters or instances cannot be created with the version.\n- Autoscaling cannot create instances with the version.\n- DB clusters still on the version are upgraded automatically during a maintenance window.\n\nAWS states that it sends a notification at least 3 months before the end of life, naming the automatic upgrade target version. Separately, patch releases are always installed automatically during the next maintenance window. Minor version updates are applied automatically when AutoMinorVersionUpgrade is true on the writer instance (not in a global database). AWS states that AutoMinorVersionUpgrade is only effective for minor version upgrades above engine release 1.3.0.0.",
      "migration_path": "1. Find the engine version in the table on [Engine releases for Amazon Neptune](https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html). The table has an \"Upgrade to\" column. Check the end of life date of the target version in the same table.\n2. When the target is a new major or minor engine version, test your Neptune applications on it before upgrading. AWS points to the [Neptune Blue-Green deployment solution](https://docs.aws.amazon.com/neptune/latest/userguide/neptune-BG-deployments.html) for this.\n3. Create a manual snapshot of the DB cluster before the upgrade.\n4. Upgrade the DB cluster with the console or the AWS CLI, see [Installing updates to your Neptune engine manually](https://docs.aws.amazon.com/neptune/latest/userguide/engine-updates-manually.html). With the CLI, specify the target engine version. Pending updates are listed in the Maintenance column of the Neptune console.\n5. Plan for downtime: an update restarts the database on all instances of the DB cluster. AWS gives a range from 20 or 30 seconds to several minutes.",
      "replacement": null,
      "affected_versions": [
        "1.4.8.0"
      ],
      "source_url": "https://docs.aws.amazon.com/neptune/latest/userguide/engine-releases.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-neptune"
      ],
      "vendor_ref": "amazon-neptune@1.4.8.0",
      "last_checked_at": "2026-11-12T09:55:44.884Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-neptune-engine-version-1-4-8-0-end-of-support"
    },
    {
      "slug": "azure-sql-database-always-encrypted-intel-sgx-enclaves-retirement",
      "title": "Azure SQL Database: Always Encrypted with Intel SGX enclaves retirement",
      "summary": "Retirement date for Always Encrypted with Intel SGX enclaves in Azure SQL Database: 31 Oct 2027. After retirement, workloads using Intel SGX enclaves no longer have enclave functionality.",
      "cloud": "azure",
      "service": "Azure SQL Database",
      "service_slug": "sql-database",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-10-06",
      "effective_date": "2027-10-31",
      "effective_precision": "day",
      "impact": "After retirement, workloads using Intel SGX enclaves no longer have enclave functionality. Databases running on DC-series compute tiers should be migrated to supported compute tiers to continue using enclave-enabled features. Microsoft ties the retirement to the phase-out of support for SGX-enabled DC-series hardware.",
      "migration_path": "1. Migrate from DC-series to a supported Standard-series (non-DC) compute tier.\n2. Enable VBS enclaves for Always Encrypted. No attestation is required.\n3. Update client drivers to versions that support VBS enclaves.\n4. Update connection strings to remove SGX attestation parameters and use VBS enclave mode.\n5. As an alternative, consider SQL Server on Confidential VMs.",
      "replacement": "Virtualization-Based Security (VBS) enclaves",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=569236",
      "extra_source_urls": [],
      "vendor_ref": "569236",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sql-database-always-encrypted-intel-sgx-enclaves-retirement"
    },
    {
      "slug": "azure-stream-analytics-powerbi-output-connector-retirement",
      "title": "Azure Stream Analytics: Power BI output connector retirement",
      "summary": "Retirement date for the Azure Stream Analytics Power BI output connector: 31 Oct 2027. On that date, Stream Analytics jobs that run with the Power BI output connector are stopped.",
      "cloud": "azure",
      "service": "Azure Stream Analytics",
      "service_slug": "stream-analytics",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2024-11-01",
      "effective_date": "2027-10-31",
      "effective_precision": "day",
      "impact": "On 31 Oct 2027, existing Azure Stream Analytics jobs that use the Power BI output connector are stopped. From the same date, existing customers cannot create new Stream Analytics jobs with Power BI as the output connector. New customers have not been able to create such jobs since October 31, 2024. Microsoft gives the Power BI retirement of real time streaming as the reason.",
      "migration_path": "1. Plan a transition to Fabric Real Time Intelligence, which the source describes as including Eventstream, KQL Database, DataActivator and Real Time Dashboards.\n2. Follow the Microsoft [migration instructions](https://go.microsoft.com/fwlink/?linkid=2296200) to move to real time intelligence before 31 Oct 2027.\n3. Read the Power BI notice on [real time streaming in Power BI](https://go.microsoft.com/fwlink/?linkid=2295913) for details of the streaming datasets retirement.",
      "replacement": "Fabric Real Time Intelligence",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=466774",
      "extra_source_urls": [],
      "vendor_ref": "466774",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-stream-analytics-powerbi-output-connector-retirement"
    },
    {
      "slug": "gcp-cloud-run-node-22-retirement",
      "title": "Cloud Run: Node.js 22 decommission",
      "summary": "Decommission date for Node.js 22 on Cloud Run: 31 Oct 2027. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2027-10-31",
      "effective_precision": "day",
      "impact": "The decommission date of Node.js 22 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-node-22-retirement"
    },
    {
      "slug": "azure-aks-kubernetes-1-34-lts-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.34 LTS end of life",
      "summary": "LTS end of life date for Kubernetes 1.34 on Azure Kubernetes Service: Nov 2027. For clusters with long-term support enabled, support for the version continues only until that date. After it, those clusters must move to the next supported LTS version.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-01",
      "effective_precision": "month",
      "impact": "After the LTS end of life date, long-term support for Kubernetes 1.34 ends. LTS-enabled clusters must then be upgraded to the next supported LTS version.\n\n- If a cluster is not upgraded, AKS upgrades it to the next supported LTS version through a platform-initiated upgrade. The cluster is not dropped to a community-supported version.\n- The LTS page places this after the 60-day grace period that follows the LTS end of life date. For the initial rollout, the grace period is the window through May 31, 2027, and no platform-initiated upgrade starts before June 1, 2027. After the initial rollout, every end-of-support event has a 60-day grace period before platform-initiated upgrades begin.\n- Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget.\n- The platform-initiated upgrade month in the AKS LTS release calendar is a planning estimate, not an exact upgrade date.",
      "migration_path": "1. List the versions AKS offers as upgrade targets with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. Test the workloads against deprecated APIs and other breaking changes between the current and target versions.\n3. Upgrade to an offered higher LTS version with `az aks upgrade --resource-group <resource-group-name> --name <cluster-name> --kubernetes-version <lts-kubernetes-version>`. An LTS cluster can skip minor versions when the upgrade satisfies version-skew requirements and validation checks. See [Long-term support for AKS versions](https://learn.microsoft.com/en-us/azure/aks/long-term-support).\n4. If the cluster is already past its LTS end of life date, skipping minor versions is conditional: the target must be listed by AKS and satisfy validation checks. AKS allows this upgrade but treats it as an unsupported recovery path.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To leave LTS instead, move the cluster to the Free or Standard tier and select the KubernetesOfficial support plan. This is possible while the cluster's Kubernetes version is still in community support. After that version exits community support, first upgrade the cluster to a community-supported version.",
      "replacement": "Next supported AKS LTS version",
      "affected_versions": [
        "1.34"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.34",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-34-lts-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-1-5-and-2-3-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 1.5 and 2.3 end of extended support",
      "summary": "End of extended support date for Elasticsearch 1.5 and 2.3 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for Elasticsearch 1.5 and 2.3 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 1.5 and 2.3"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 1.5 and 2.3",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-1-5-and-2-3-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-5-1-to-5-5-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 5.1 to 5.5 end of extended support",
      "summary": "End of extended support date for Elasticsearch 5.1 to 5.5 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for Elasticsearch 5.1 to 5.5 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 5.1 to 5.5"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 5.1 to 5.5",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-5-1-to-5-5-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-6-0-to-6-7-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 6.0 to 6.7 end of extended support",
      "summary": "End of extended support date for Elasticsearch 6.0 to 6.7 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for Elasticsearch 6.0 to 6.7 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 6.0 to 6.7"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 6.0 to 6.7",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-6-0-to-6-7-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-6-8-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 6.8 end of standard support",
      "summary": "End of standard support date for Elasticsearch 6.8 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, Elasticsearch 6.8 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 6.8"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 6.8",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-6-8-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-7-1-to-7-8-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 7.1 to 7.8 end of extended support",
      "summary": "End of extended support date for Elasticsearch 7.1 to 7.8 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for Elasticsearch 7.1 to 7.8 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 7.1 to 7.8"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 7.1 to 7.8",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-7-1-to-7-8-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-7-10-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 7.10 end of standard support",
      "summary": "End of standard support date for Elasticsearch 7.10 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, Elasticsearch 7.10 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 7.10"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 7.10",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-7-10-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-7-9-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 7.9 end of standard support",
      "summary": "End of standard support date for Elasticsearch 7.9 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, Elasticsearch 7.9 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 7.9"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 7.9",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-7-9-end-of-support"
    },
    {
      "slug": "aws-opensearch-1-0-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 1.0 end of extended support",
      "summary": "End of extended support date for OpenSearch 1.0 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for OpenSearch 1.0 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "1.0"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@1.0",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-1-0-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-1-1-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 1.1 end of extended support",
      "summary": "End of extended support date for OpenSearch 1.1 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for OpenSearch 1.1 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "1.1"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@1.1",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-1-1-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-1-2-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 1.2 end of extended support",
      "summary": "End of extended support date for OpenSearch 1.2 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for OpenSearch 1.2 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "1.2"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@1.2",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-1-2-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-1-3-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 1.3 end of standard support",
      "summary": "End of standard support date for OpenSearch 1.3 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, OpenSearch 1.3 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "1.3"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@1.3",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-1-3-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-11-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.11 end of standard support",
      "summary": "End of standard support date for OpenSearch 2.11 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, OpenSearch 2.11 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.11"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.11",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-11-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-13-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.13 end of standard support",
      "summary": "End of standard support date for OpenSearch 2.13 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, OpenSearch 2.13 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.13"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.13",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-13-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-15-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.15 end of standard support",
      "summary": "End of standard support date for OpenSearch 2.15 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, OpenSearch 2.15 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.15"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.15",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-15-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-17-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.17 end of standard support",
      "summary": "End of standard support date for OpenSearch 2.17 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, OpenSearch 2.17 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.17"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.17",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-17-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-19-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.19 end of standard support",
      "summary": "End of standard support date for OpenSearch 2.19 on Amazon OpenSearch Service: 7 Nov 2027. Extended support charges apply automatically to a domain that runs a version no longer under standard support.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "AWS provides bug fixes and security updates for versions under standard support. After 7 Nov 2027, OpenSearch 2.19 is no longer under standard support:\n\n- For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends.\n- Extended support charges apply automatically when a domain runs a version that is no longer under standard support.\n- The charge comes in addition to the standard instance cost. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs).\n\nThe same schedule also lists end of extended support dates.",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.19"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.19",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-19-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-3-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.3 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.3 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for OpenSearch 2.3 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.3"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.3",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-3-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-5-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.5 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.5 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for OpenSearch 2.5 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.5"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.5",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-5-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-7-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.7 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.7 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for OpenSearch 2.7 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.7"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.7",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-7-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-9-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.9 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.9 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2027. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2027 is the end of extended support date for OpenSearch 2.9 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.9"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.9",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-9-extended-support-end-of-support"
    },
    {
      "slug": "azure-postgresql-15-end-of-support",
      "title": "Azure Database for PostgreSQL: PostgreSQL 15 end of standard support",
      "summary": "Azure Standard Support End Date for PostgreSQL 15 on Azure Database for PostgreSQL: 11 Nov 2027. Once the Azure Standard Support period ends, eligible servers still running the version are automatically enrolled in extended support.",
      "cloud": "azure",
      "service": "Azure Database for PostgreSQL",
      "service_slug": "postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-11",
      "effective_precision": "day",
      "impact": "Once the Azure Standard Support period ends, an eligible server still running PostgreSQL 15 is automatically enrolled in extended support. The eligible versions table lists PostgreSQL 11, 12, 13 and 14.\n\n- Extended support provides security patches, critical bug fixes and technical support for up to three extra years. It does not include new features, performance enhancements or support for minor version upgrades.\n- Charges apply after any applicable grace period unless the server is upgraded to a supported version, and only to servers in a Succeeded (running) state. A one-month grace period is provided for versions 11, 12 and 13. A server that regional capacity constraints prevent from upgrading might be temporarily excluded from billing.\n- The version policy page lists restrictions that apply after the retirement date of a version, without stating whether that date is 11 Nov 2027: new servers cannot be created on a retired version, while point-in-time recoveries and read replicas of existing servers remain possible.\n- The same page says that when the community retires a version, Azure stops applying bug or security patches to the database engine. The extended support page lists security patches and critical bug fixes as part of extended support.",
      "migration_path": "1. Run the upgrade validation checks in the Azure portal or with the Azure CLI. See [Run upgrade validation checks](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/how-to-run-upgrade-validation-checks).\n2. Resolve any blocking issues the checks report, then rerun validation.\n3. Ensure the server has at least 10-20% free storage available before starting the upgrade.\n4. If the server uses geo-replication, delete the read replica (including any cascading read replica) before upgrading the primary server. The replica can be re-created after the upgrade.\n5. Run an in-place major version upgrade to a PostgreSQL version that Azure currently supports. The service can skip versions and upgrade directly to a later version. Servers that use TimescaleDB are limited to specific source and target version combinations, and an upgrade from PostgreSQL 11 first requires SCRAM authentication to be configured. Once the server runs a supported version, extended support charges no longer apply. See [Major version upgrades](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-major-version-upgrade).\n6. Plan for the fact that there is no automated way to revert after a successful upgrade. A point-in-time recovery to a time before the upgrade restores the previous version on a new server.",
      "replacement": null,
      "affected_versions": [
        "15"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-postgresql"
      ],
      "vendor_ref": "azure-database-for-postgresql@15",
      "last_checked_at": "2026-11-12T09:55:36.471Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-postgresql-15-end-of-support"
    },
    {
      "slug": "gcp-gke-kubernetes-1-34-extended-support-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.34 end of extended support",
      "summary": "End of extended support date for GKE Kubernetes 1.34: 25 Nov 2027. From that date the minor version receives no security patches, and GKE upgrades Extended channel clusters still running it to the next minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-11-25",
      "effective_precision": "day",
      "impact": "At the end of extended support, GKE does not provide any patches for security fixes, and the minor version is considered unsupported. GKE upgrades clusters still running it to the next minor version.\n\n- The upgrade happens regardless of the cluster's use of deprecated features or APIs.\n- Maintenance exclusions cannot be configured past this date, except as a temporary, emergency measure with the \"No upgrades\" scope.\n- That exclusion can delay the upgrade for up to 90 days after the end of support date. Google does not recommend it.\n- Dates in the GKE release schedule are updated monthly and subject to change.",
      "migration_path": "1. Google does not recommend enrolling a cluster in the Extended channel without plans to move to the next minor version, because GKE eventually upgrades the cluster to newer minor versions.\n2. Around 2 months before the end of extended support, GKE begins upgrading clusters in the Extended channel to the next minor version, unless the cluster is using deprecated features or APIs.\n3. Maintenance exclusions can prevent minor version upgrades until the end of extended support. A temporary, emergency exclusion with the \"No upgrades\" scope can delay the upgrade for up to 90 days after the end of support date. After that exclusion expires, GKE upgrades the cluster.\n4. At the end of extended support, GKE upgrades all clusters still running the minor version, regardless of blocking issues. See [GKE minor version lifecycle](https://docs.cloud.google.com/kubernetes-engine/versioning#lifecycle).",
      "replacement": null,
      "affected_versions": [
        "1.34"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [],
      "vendor_ref": "gke@1.34",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-34-extended-support-end-of-support"
    },
    {
      "slug": "aws-eks-kubernetes-1-37-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.37 end of standard support",
      "summary": "End of standard support date for Kubernetes 1.37 on Amazon EKS: 1 Dec 2027. After that date the version enters extended support for 12 months, at an additional cost per cluster hour.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-12-01",
      "effective_precision": "day",
      "impact": "Once Kubernetes 1.37 is past the end of standard support date, it enters extended support for the next 12 months, at an additional cost per cluster hour.\n\n- Extended support is enabled by default.\n- Billing starts at the beginning of the day that the version reaches end of standard support, in the UTC+0 timezone.\n- A cluster whose upgrade policy has extended support disabled is automatically upgraded to the next Kubernetes version at the end of standard support.\n- Extended support cannot be disabled once a cluster has entered it.\n- A cluster not updated before the extended support period ends is automatically updated by Amazon EKS to the earliest supported version.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version. Then upgrade the control plane to a version in the standard support period, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n3. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n4. To stay on Kubernetes 1.37, keep the cluster upgrade policy set to EXTENDED. An additional cost applies to clusters running in extended support, see the [pricing page](https://aws.amazon.com/eks/pricing/).\n5. To avoid extended support, set the upgrade policy to standard support while the cluster is still on standard support, as described in [Disable EKS extended support](https://docs.aws.amazon.com/eks/latest/userguide/disable-extended-support.html). The cluster is then auto upgraded at the end of standard support.",
      "replacement": null,
      "affected_versions": [
        "1.37"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.37",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-37-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-15-sp5-for-sap-image-end-of-support",
      "title": "Compute Engine: SLES 15 SP5 for SAP image end of support",
      "summary": "EOS and image deprecation date for the SLES 15 SP5 for SAP public image on Compute Engine: Dec 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-12-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 15 SP5 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 15 SP5 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-15-sp5-sap",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-15-sp5-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-15-sp5-image-end-of-support",
      "title": "Compute Engine: SLES 15 SP5 image end of support",
      "summary": "EOS and image deprecation date for the SLES 15 SP5 public image on Compute Engine: Dec 2027. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-12-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 15 SP5 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 15 SP5"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-15-sp5-image-end-of-support"
    },
    {
      "slug": "aws-eks-kubernetes-1-34-extended-support-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.34 end of extended support",
      "summary": "End of extended support date for Kubernetes 1.34 on Amazon EKS: 2 Dec 2027. On that date, new clusters can no longer be created with this version, and Amazon EKS automatically updates control planes still on it at any time afterward.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-12-02",
      "effective_precision": "day",
      "impact": "On the end of extended support date, new Amazon EKS clusters can no longer be created with Kubernetes 1.34. Amazon EKS automatically updates existing control planes to the earliest supported version, at any time after that date.\n\n- Amazon EKS gives no specific time frame and sends no notification before the update.\n- The auto-upgrade includes only the Kubernetes control plane. Self-managed nodes and EKS managed node groups remain on the previous version.\n- EKS Auto Mode nodes may update automatically.\n- Fargate nodes and hybrid nodes are not upgraded with the control plane.\n- Clusters that were automatically upgraded at the end of extended support cannot be rolled back.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version.\n3. Proactively update the control plane without relying on the Amazon EKS automatic update process, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n4. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n5. If Amazon EKS updated the control plane automatically, manually update cluster add-ons and Amazon EC2 nodes.",
      "replacement": null,
      "affected_versions": [
        "1.34"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.34",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-34-extended-support-end-of-support"
    },
    {
      "slug": "gcp-gke-kubernetes-1-37-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.37 end of standard support",
      "summary": "End of standard support date for GKE Kubernetes 1.37: 22 Dec 2027. After that date the minor version is unsupported for clusters not enrolled in the Extended channel, and GKE automatically upgrades them to the next supported minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2027-12-22",
      "effective_precision": "day",
      "impact": "After the standard support period, the minor version becomes unsupported and unavailable for all clusters not enrolled in the Extended channel. GKE automatically upgrades those clusters to the next supported minor version.\n\n- Those clusters receive no security patches or bug fixes for the minor version after the end of standard support.\n- The automatic upgrade also applies to clusters not enrolled in any release channel. Nodes are typically scheduled for an automated upgrade within one month of the end of support date, and actual timing can vary.\n- As a temporary, emergency measure that Google does not recommend, a \"No upgrades\" maintenance exclusion can delay the upgrade for up to 90 days after the end of support date.\n- Extended channel clusters receive security patches until the end of extended support, for an additional fee per cluster.\n- Release schedule dates are subject to change.",
      "migration_path": "1. Upgrade the cluster and nodes to a supported version. Google requires this before you engage Cloud Customer Care about a cluster or nodes on an unsupported version.\n2. Without action, GKE schedules an automatic upgrade to the next supported minor version before the end of support. The timing depends on the schedule for the cluster's release channel.\n3. During the standard support period, a maintenance exclusion at the cluster level can prevent this minor version upgrade. GKE also does not upgrade clusters that use deprecated features or APIs during that period.\n4. To keep using the minor version until the end of extended support, change the cluster to the Extended channel. Extended support adds approximately 10 months after the standard support period, for up to 24 months of support in total.\n5. Review the [pricing for extended support](https://cloud.google.com/kubernetes-engine/pricing#extended-support-period) first, because pay-per-use costs apply in the extended support period.\n6. Review the limitations of the Extended channel: clusters that use certain features cannot be enrolled, the extended support period does not extend the cluster's credential expiry date, and GKE pauses patch node auto-upgrades when it updates the Container-Optimized OS milestone that the minor version uses.",
      "replacement": null,
      "affected_versions": [
        "1.37"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [
        "https://endoflife.date/google-kubernetes-engine"
      ],
      "vendor_ref": "gke@1.37",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-37-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-37-platform-initiated-upgrade-breaking-change",
      "title": "Azure Kubernetes Service: Kubernetes 1.37 platform-initiated upgrade",
      "summary": "Microsoft lists Jan 2028 as the planned rollout month, a planning estimate, of the platform-initiated upgrade for clusters still running Kubernetes 1.37 on Azure Kubernetes Service. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "breaking_change",
      "announced_date": null,
      "effective_date": "2028-01-01",
      "effective_precision": "month",
      "impact": "From June 1, 2027, AKS automatically upgrades any cluster that stays on an unsupported Kubernetes version after its 60-day platform support grace period ends. It applies to AKS in the Azure public cloud. Upgrades can occur during or after the listed month. Clusters enrolled in long-term support (LTS) follow the month in the LTS versions table. A platform-initiated upgrade:\n\n- does not follow the maintenance window\n- does not stop for deprecated API usage\n- can override a Pod Disruption Budget if a node drain times out or fails\n- cannot be canceled once started, and cannot be rolled back\n- moves the cluster to the lowest supported version within its current support tier",
      "migration_path": "1. Find clusters that are out of support or approaching end of life with the Azure Resource Graph query and the [release calendar](https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions#aks-kubernetes-release-calendar-and-upcoming-versions).\n2. Remove dependencies on deprecated APIs: update workloads, manifests, clients, controllers and self-managed add-ons that use APIs removed from the target Kubernetes version.\n3. Check the Kubernetes version compatibility of each self-managed add-on, and upgrade or replace an incompatible add-on.\n4. Review [VM family quota, regional SKU availability, and subnet IP capacity](https://learn.microsoft.com/en-us/azure/aks/quotas-skus-regions), and test that Pod Disruption Budgets allow a node drain to complete.\n5. Upgrade the cluster to a supported version on your own schedule, before the platform-initiated upgrade month. See [Upgrade an AKS cluster control plane](https://learn.microsoft.com/en-us/azure/aks/upgrade-aks-control-plane).\n6. If a specific minor version must stay supported for longer, evaluate [AKS long-term support](https://learn.microsoft.com/en-us/azure/aks/long-term-support), an opt-in that requires the Premium tier. LTS clusters get a platform-initiated upgrade after the LTS end-of-life date and its 60-day grace period.",
      "replacement": null,
      "affected_versions": [
        "1.37"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [],
      "vendor_ref": "azure-kubernetes-service@1.37",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-37-platform-initiated-upgrade-breaking-change"
    },
    {
      "slug": "azure-devops-server-tfs-2018-end-of-support",
      "title": "TFS 2018 end of support",
      "summary": "endoflife.date lists 11 Jan 2028 as the end of security support for TFS 2018. Microsoft publishes the specific end of support dates and details in its Lifecycle product search.",
      "cloud": "azure",
      "service": "Azure DevOps Server",
      "service_slug": "devops-server",
      "category": "other",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-01-11",
      "effective_precision": "day",
      "impact": "Prior to 2019, the product was known as Team Foundation Server (TFS). Microsoft publishes specific end of support dates and details in its [Lifecycle product search](https://learn.microsoft.com/en-us/lifecycle/products/). For releases under the Microsoft Fixed Lifecycle Policy, the policy states that, to be eligible for support, customers may be required to deploy the latest Service Pack or update.",
      "migration_path": "Follow [Upgrade your deployment to the latest version of Azure DevOps Server](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started):\n\n1. Have your Azure DevOps Server license and product key ready, and administrative access and credentials for the service accounts.\n2. Review the [system requirements](https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server) for the target server, which may include updates to operating systems, SQL Server versions, and hardware.\n3. Create a complete and consistent set of backups for all Azure DevOps databases.\n4. If you upgrade in place, perform a trial in a pre-production environment: [Pre-production dry run](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-server).\n5. Plan for downtime. The deployment is offline during the upgrade.",
      "replacement": null,
      "affected_versions": [
        "2018"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/visual-studio-team-foundation-server-2018",
      "extra_source_urls": [
        "https://endoflife.date/azure-devops-server"
      ],
      "vendor_ref": "azure-devops-server@2018",
      "last_checked_at": "2026-11-12T09:55:46.498Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-devops-server-tfs-2018-end-of-support"
    },
    {
      "slug": "aws-rds-mariadb-10-11-end-of-support",
      "title": "Amazon RDS for MariaDB: MariaDB 10.11 end of standard support",
      "summary": "RDS end of standard support date for MariaDB 10.11 on Amazon RDS for MariaDB: Feb 2028. AWS lists this date so that testing and upgrade cycles can be planned around it.",
      "cloud": "aws",
      "service": "Amazon RDS for MariaDB",
      "service_slug": "rds-mariadb",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-02-01",
      "effective_precision": "month",
      "impact": "Feb 2028 is the RDS end of standard support date that AWS lists for MariaDB 10.11. The AWS page does not state what happens to DB instances still on MariaDB 10.11 after that date.\n\n- RDS for MariaDB major versions remain available at least until community end of life for the corresponding community version.\n- A date with only a month and a year is approximate and is replaced by an exact date once known.\n- If AWS extends support for a version beyond the stated date, it plans to update its version table with the later date.\n- Deprecation policy: see the [Amazon RDS FAQs](https://aws.amazon.com/rds/faqs/).",
      "migration_path": "1. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command.\n2. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n3. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MariaDB](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MariaDB.Major.html). Major version upgrades are performed manually.\n4. Plan for downtime: database engine upgrades require downtime, and its duration varies with the size of the DB instance.\n5. Downtime for the upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. The engine cannot be reverted after the upgrade completes. To return to the previous version, restore the first DB snapshot taken during the upgrade to a new DB instance. Amazon RDS only takes these snapshots if the backup retention period of the DB instance is greater than 0.",
      "replacement": null,
      "affected_versions": [
        "10.11"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MariaDB.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mariadb"
      ],
      "vendor_ref": "amazon-rds-mariadb@10.11",
      "last_checked_at": "2026-11-12T09:55:39.673Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mariadb-10-11-end-of-support"
    },
    {
      "slug": "gcp-gke-kubernetes-1-35-extended-support-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.35 end of extended support",
      "summary": "End of extended support date for GKE Kubernetes 1.35: 11 Feb 2028. From that date the minor version receives no security patches, and GKE upgrades Extended channel clusters still running it to the next minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-02-11",
      "effective_precision": "day",
      "impact": "At the end of extended support, GKE does not provide any patches for security fixes, and the minor version is considered unsupported. GKE upgrades clusters still running it to the next minor version.\n\n- The upgrade happens regardless of the cluster's use of deprecated features or APIs.\n- Maintenance exclusions cannot be configured past this date, except as a temporary, emergency measure with the \"No upgrades\" scope.\n- That exclusion can delay the upgrade for up to 90 days after the end of support date. Google does not recommend it.\n- Dates in the GKE release schedule are updated monthly and subject to change.",
      "migration_path": "1. Google does not recommend enrolling a cluster in the Extended channel without plans to move to the next minor version, because GKE eventually upgrades the cluster to newer minor versions.\n2. Around 2 months before the end of extended support, GKE begins upgrading clusters in the Extended channel to the next minor version, unless the cluster is using deprecated features or APIs.\n3. Maintenance exclusions can prevent minor version upgrades until the end of extended support. A temporary, emergency exclusion with the \"No upgrades\" scope can delay the upgrade for up to 90 days after the end of support date. After that exclusion expires, GKE upgrades the cluster.\n4. At the end of extended support, GKE upgrades all clusters still running the minor version, regardless of blocking issues. See [GKE minor version lifecycle](https://docs.cloud.google.com/kubernetes-engine/versioning#lifecycle).",
      "replacement": null,
      "affected_versions": [
        "1.35"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [],
      "vendor_ref": "gke@1.35",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-35-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-12-extended-support-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 12 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for PostgreSQL 12 on Amazon Aurora PostgreSQL: 29 Feb 2028. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-02-29",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 29 Feb 2028. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- New major PostgreSQL versions might contain database changes that are not backward-compatible with existing applications.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "12"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@12",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-12-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-15-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 15 end of standard support",
      "summary": "Aurora end of standard support date for PostgreSQL 15 on Amazon Aurora PostgreSQL: 29 Feb 2028. After that date, a database can keep running this major version under RDS Extended Support, for an additional cost.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-02-29",
      "effective_precision": "day",
      "impact": "RDS Extended Support allows a database to keep running this major version after 29 Feb 2028, for an [additional cost](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html).\n\n- Aurora automatically enrolls a DB instance after that date if RDS Extended Support was enabled at creation or restoration.\n- It provides security updates for critical and high CVEs, bug fixes for critical issues, and support cases.\n- Charges apply only to certain minor versions. The [release calendar](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html) lists the eligible minor versions for each major version.\n- Enrollment can be changed at any time, at the cluster level. Disabling it after that date upgrades the instance or cluster automatically to the next supported major version.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "15"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@15",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-15-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-12-extended-support-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 12 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for PostgreSQL 12 on Amazon RDS for PostgreSQL: 29 Feb 2028. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-02-29",
      "effective_precision": "day",
      "impact": "After the RDS end of Extended Support date (29 Feb 2028), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 12.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "12"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@12",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-12-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-15-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15 end of standard support",
      "summary": "RDS end of standard support date for PostgreSQL 15 on Amazon RDS for PostgreSQL: 29 Feb 2028. A database can keep running this version past that date under RDS Extended Support, for an additional cost, until the RDS end of Extended Support date.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-02-29",
      "effective_precision": "day",
      "impact": "A database can continue running PostgreSQL 15 past the RDS end of standard support date under RDS Extended Support, for an additional cost (see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html)), until the RDS end of Extended Support date.\n\n- If RDS Extended Support was enabled when the DB instance was created or restored, Amazon RDS enrolls it automatically after the RDS end of standard support date, with no change to the database engine, uptime or performance.\n- RDS Extended Support provides security updates for critical and high CVEs, bug fixes and patches for critical issues, and the ability to open support cases.\n- If enrollment is disabled for a DB instance or DB cluster that is already past its standard support end date, it automatically upgrades to the next supported major version.\n- After the RDS end of Extended Support date, Amazon RDS automatically upgrades databases not yet on a supported major version.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. To stay on PostgreSQL 15 under RDS Extended Support, the enrollment status of an existing DB instance or DB cluster can be changed with the EngineLifecycleSupport parameter using the AWS CLI or RDS API. For Multi-AZ DB clusters, modify the setting at the cluster level. RDS Extended Support has an additional cost, see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "replacement": null,
      "affected_versions": [
        "15"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@15",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-35-lts-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.35 LTS end of life",
      "summary": "LTS end of life date for Kubernetes 1.35 on Azure Kubernetes Service: Mar 2028. For clusters with long-term support enabled, support for the version continues only until that date. After it, those clusters must move to the next supported LTS version.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-03-01",
      "effective_precision": "month",
      "impact": "After the LTS end of life date, long-term support for Kubernetes 1.35 ends. LTS-enabled clusters must then be upgraded to the next supported LTS version.\n\n- If a cluster is not upgraded, AKS upgrades it to the next supported LTS version through a platform-initiated upgrade. The cluster is not dropped to a community-supported version.\n- The LTS page places this after the 60-day grace period that follows the LTS end of life date. For the initial rollout, the grace period is the window through May 31, 2027, and no platform-initiated upgrade starts before June 1, 2027. After the initial rollout, every end-of-support event has a 60-day grace period before platform-initiated upgrades begin.\n- Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget.\n- The platform-initiated upgrade month in the AKS LTS release calendar is a planning estimate, not an exact upgrade date.",
      "migration_path": "1. List the versions AKS offers as upgrade targets with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. Test the workloads against deprecated APIs and other breaking changes between the current and target versions.\n3. Upgrade to an offered higher LTS version with `az aks upgrade --resource-group <resource-group-name> --name <cluster-name> --kubernetes-version <lts-kubernetes-version>`. An LTS cluster can skip minor versions when the upgrade satisfies version-skew requirements and validation checks. See [Long-term support for AKS versions](https://learn.microsoft.com/en-us/azure/aks/long-term-support).\n4. If the cluster is already past its LTS end of life date, skipping minor versions is conditional: the target must be listed by AKS and satisfy validation checks. AKS allows this upgrade but treats it as an unsupported recovery path.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To leave LTS instead, move the cluster to the Free or Standard tier and select the KubernetesOfficial support plan. This is possible while the cluster's Kubernetes version is still in community support. After that version exits community support, first upgrade the cluster to a community-supported version.",
      "replacement": "Next supported AKS LTS version",
      "affected_versions": [
        "1.35"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.35",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-35-lts-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-cos-129-lts-image-end-of-support",
      "title": "Compute Engine: COS 129 LTS image end of support",
      "summary": "EOS and image deprecation date for the COS 129 LTS public image on Compute Engine: Mar 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-03-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of COS 129 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "COS 129 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "cos-129-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-cos-129-lts-image-end-of-support"
    },
    {
      "slug": "aws-eks-kubernetes-1-35-extended-support-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.35 end of extended support",
      "summary": "End of extended support date for Kubernetes 1.35 on Amazon EKS: 27 Mar 2028. On that date, new clusters can no longer be created with this version, and Amazon EKS automatically updates control planes still on it at any time afterward.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-03-27",
      "effective_precision": "day",
      "impact": "On the end of extended support date, new Amazon EKS clusters can no longer be created with Kubernetes 1.35. Amazon EKS automatically updates existing control planes to the earliest supported version, at any time after that date.\n\n- Amazon EKS gives no specific time frame and sends no notification before the update.\n- The auto-upgrade includes only the Kubernetes control plane. Self-managed nodes and EKS managed node groups remain on the previous version.\n- EKS Auto Mode nodes may update automatically.\n- Fargate nodes and hybrid nodes are not upgraded with the control plane.\n- Clusters that were automatically upgraded at the end of extended support cannot be rolled back.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version.\n3. Proactively update the control plane without relying on the Amazon EKS automatic update process, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n4. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n5. If Amazon EKS updated the control plane automatically, manually update cluster add-ons and Amazon EC2 nodes.",
      "replacement": null,
      "affected_versions": [
        "1.35"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.35",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-35-extended-support-end-of-support"
    },
    {
      "slug": "azure-arc-aks-on-windows-server-current-architecture-retirement",
      "title": "Azure Arc: AKS on Windows Server 2019 and 2022 current architecture retirement",
      "summary": "Retirement date for the current architecture of Azure Kubernetes Service on Windows Server 2019 and Windows Server 2022: 27 Mar 2028. From that date, existing clusters get no support or updates, and the current architecture cannot be deployed, upgraded or scaled.",
      "cloud": "azure",
      "service": "Azure Arc",
      "service_slug": "arc",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-03-28",
      "effective_date": "2028-03-27",
      "effective_precision": "day",
      "impact": "From 27 Mar 2028, existing Azure Kubernetes Service clusters on the current architecture on Windows Server 2019 and Windows Server 2022 no longer get support, security updates or quality updates. Deploying, upgrading and scaling the current architecture on Windows Server 2019 and Windows Server 2022 is no longer possible. Microsoft also asks customers with clusters on Azure Local, version 22H2 to replace them. Azure Local, version 22H2 has its own end of service date of May 31, 2025.",
      "migration_path": "1. [Deploy a supported version of Azure Local](https://learn.microsoft.com/azure/azure-local/overview), which is required before deploying Azure Kubernetes Service clusters on Azure Local.\n2. Replace existing Azure Kubernetes Service clusters on Windows Server 2019, Windows Server 2022 or Azure Local, version 22H2 with Azure Kubernetes Service on Azure Local, version 23H2 or later.\n3. If you run AKS on Azure Local, version 22H2, [update to the latest version of Azure Local](https://learn.microsoft.com/azure/azure-local/upgrade/about-upgrades-23h2) to continue receiving updates.\n4. Review the pricing changes on the [pricing page](https://azure.microsoft.com/pricing/details/azure-stack/aks-hci/).",
      "replacement": "Azure Kubernetes Service on Azure Local, version 23H2 or later",
      "affected_versions": [
        "Windows Server 2019",
        "Windows Server 2022"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=485893",
      "extra_source_urls": [
        "https://azure.microsoft.com/pricing/details/azure-stack/aks-hci/",
        "https://learn.microsoft.com/azure/azure-local/overview",
        "https://learn.microsoft.com/azure/azure-local/upgrade/about-upgrades-23h2"
      ],
      "vendor_ref": "485893",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-arc-aks-on-windows-server-current-architecture-retirement"
    },
    {
      "slug": "aws-lambda-ruby3-4-end-of-support",
      "title": "AWS Lambda: Ruby 3.4 (ruby3.4) deprecation",
      "summary": "Deprecation date for Ruby 3.4 (ruby3.4) on AWS Lambda: 31 Mar 2028. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "After deprecation (31 Mar 2028), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 30 Apr 2028, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 May 2028, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 May 2028), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "ruby3.4"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "ruby3.4",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-ruby3-4-end-of-support"
    },
    {
      "slug": "azure-app-service-custom-backup-linked-databases-retirement",
      "title": "Azure App Service: linked databases in custom backups retirement",
      "summary": "From 31 Mar 2028, the Azure App Service custom backup feature no longer backs up linked databases. Microsoft recommends the native backup and restore tools of each database instead.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-03-31",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "From 31 Mar 2028, the Azure App Service custom backup feature no longer backs up linked databases. App Service web applications with existing custom backups that already include linked databases keep backing up those databases until that date. Before that date, the option to include linked databases in new custom backup configurations is removed: November 2025 for linked MySQL and PostgreSQL databases, and April 2026 for linked Azure SQL and SQL Server databases.",
      "migration_path": "1. Implement a backup strategy for the databases linked to your App Service web applications before the retirement date.\n2. Use the native backup and restore tools available with the respective databases.\n3. For further information, see the [Microsoft guidance](https://aka.ms/AppSvcDBBkp).",
      "replacement": "Native backup and restore tools of the respective databases",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=485047",
      "extra_source_urls": [
        "https://aka.ms/AppSvcDBBkp",
        "https://aka.ms/ServicesRetirementWorkbook"
      ],
      "vendor_ref": "485047",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-custom-backup-linked-databases-retirement"
    },
    {
      "slug": "azure-container-registry-docker-content-trust-retirement",
      "title": "Azure Container Registry: Docker Content Trust retirement",
      "summary": "Retirement date for Docker Content Trust in Azure Container Registry: 31 Mar 2028. On that date the function is removed and the data stored for signing and verifying signatures with it is permanently deleted.",
      "cloud": "azure",
      "service": "Azure Container Registry",
      "service_slug": "container-registry",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-03-26",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "Docker Content Trust is completely removed from Azure Container Registry on 31 Mar 2028. Data stored in the registry for signing and verifying signatures with Docker Content Trust is permanently deleted on the same date. Since September 30, 2025, customers have not been able to enable Docker Content Trust on Azure Container Registry. Registries that currently use Docker Content Trust to sign images or verify signatures are affected.",
      "migration_path": "1. Move from Docker Content Trust to the [Notary Project](https://notaryproject.dev/) ecosystem, including its open-source tool [Notation](https://github.com/notaryproject/notation).\n2. For signing, use Azure Key Vault with [self-signed certificates](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tutorial-sign-build-push#create-a-self-signed-certificate-azure-cli) or [CA-issued certificates](https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tutorial-sign-trusted-ca).\n3. To sign in pipelines, see [Sign in ADO pipelines](https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/notation-ado-task-sign) and [Sign in GitHub workflows](https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/notation-sign-gha).\n4. For verification, see [Verify in ADO pipelines](https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/notation-ado-task-sign), [Verify in GitHub workflows](https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/verify-gha) and [Verify on AKS](https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/validating-image-signatures-using-ratify-aks).",
      "replacement": "Notary Project (Notation) with Azure Key Vault",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=485241",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tutorial-sign-build-push#create-a-self-signed-certificate-azure-cli",
        "https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tutorial-sign-trusted-ca",
        "https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/notation-ado-task-sign",
        "https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/notation-sign-gha",
        "https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/verify-gha",
        "https://learn.microsoft.com/en-us/azure/security/container-secure-supply-chain/articles/validating-image-signatures-using-ratify-aks"
      ],
      "vendor_ref": "485241",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-container-registry-docker-content-trust-retirement"
    },
    {
      "slug": "azure-functions-durable-functions-netherite-end-of-support",
      "title": "Azure Functions: Durable Functions Netherite backend end of support",
      "summary": "End of support date for the Netherite backend provider of Durable Functions: 31 Mar 2028. Function apps using Netherite keep working after that date, but support cases can no longer be opened for them.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "feature",
      "type": "end_of_support",
      "announced_date": "2025-04-16",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "Netherite is one of several backend providers supported by Durable Functions, and it is no longer supported after 31 Mar 2028. Function apps using Netherite continue to work after that date but are no longer supported. Support cases can no longer be opened for Netherite-enabled apps.",
      "migration_path": "1. For function apps that need the higher throughput previously offered by Netherite, read the [durable task scheduler](https://aka.ms/dts-documentation) documentation and evaluate it for the workloads that use Netherite.\n2. When the announcement was published, the durable task scheduler was in public preview. Microsoft stated that it becomes generally available before the Netherite end of support date, to allow time for migration. Microsoft recommends waiting until it is generally available before using it for production workloads.",
      "replacement": "Durable task scheduler",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=489009",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-functions/durable/durable-functions-storage-providers#netherite",
        "https://aka.ms/dts-documentation"
      ],
      "vendor_ref": "489009",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-durable-functions-netherite-end-of-support"
    },
    {
      "slug": "azure-aks-kubenet-networking-retirement",
      "title": "Azure Kubernetes Service: kubenet networking retirement",
      "summary": "Retirement date for kubenet networking on Azure Kubernetes Service (AKS): 31 Mar 2028. From that date, workloads running on kubenet for AKS are no longer supported.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-03-18",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "Kubenet networking for Azure Kubernetes Service (AKS) is retired on 31 Mar 2028. From that date, workloads running on kubenet for AKS are no longer supported. Microsoft states that an upgrade before that date is needed to avoid service disruptions.",
      "migration_path": "Follow the Microsoft instructions to [upgrade to Azure Container Networking Interface (CNI) overlay](https://learn.microsoft.com/azure/aks/upgrade-aks-ipam-and-dataplane) before the retirement date. Azure CNI overlay provides the same IP address overlay architecture as kubenet.",
      "replacement": "Azure CNI overlay",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=485172",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/aks/upgrade-aks-ipam-and-dataplane"
      ],
      "vendor_ref": "485172",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubenet-networking-retirement"
    },
    {
      "slug": "azure-maps-route-apis-v1-0-retirement",
      "title": "Azure Maps: Route APIs version 1.0 retirement",
      "summary": "Retirement date for Azure Maps Route APIs version 1.0: 31 Mar 2028. After that date the version 1.0 Route APIs are no longer available or supported, and API calls fail.",
      "cloud": "azure",
      "service": "Azure Maps",
      "service_slug": "maps",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2025-03-26",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "After the retirement date, Azure Maps Route APIs version 1.0 are no longer available or supported, and API calls fail. The retirement covers nine version 1.0 operations: Get Route Directions, Get Route Directions Batch, Post Route Directions, Post Route Direction Batch, Post Route Directions Batch Sync, Get Route Matrix, Post Route Matrix, Post Route Matrix Sync and Get Route Range. All other Azure Maps services are unaffected.",
      "migration_path": "1. Review the [migration instructions](https://aka.ms/AzureMapsRoutev1MigrationGuide).\n2. Move your calls to [Azure Maps Route APIs version 2025-01-01](https://learn.microsoft.com/en-us/rest/api/maps/route?view=rest-maps-2025-01-01).\n3. Stop using Azure Maps Route APIs version 1.0 before the retirement date.",
      "replacement": "Azure Maps Route APIs version 2025-01-01",
      "affected_versions": [
        "1.0"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=485819",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/rest/api/maps/route?view=rest-maps-1.0",
        "https://learn.microsoft.com/en-us/rest/api/maps/route?view=rest-maps-2025-01-01",
        "https://aka.ms/AzureMapsRoutev1MigrationGuide"
      ],
      "vendor_ref": "485819",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-maps-route-apis-v1-0-retirement"
    },
    {
      "slug": "azure-maps-traffic-apis-version-1-0-retirement",
      "title": "Azure Maps: Traffic APIs version 1.0 retirement",
      "summary": "Retirement date for the Azure Maps Traffic APIs version 1.0: 31 Mar 2028. After that date the APIs are no longer available and calls to them fail.",
      "cloud": "azure",
      "service": "Azure Maps",
      "service_slug": "maps",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2025-03-28",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "Five Azure Maps Traffic APIs version 1.0 are retired: Get Traffic Flow Segment, Get Traffic Flow Tile, Get Traffic Incident Detail, Get Traffic Incident Tile and Get Traffic Incident Viewport. After the retirement date, these APIs are no longer available and/or supported, and API calls fail. Until that date, they remain usable without disruption. All other Azure Maps services are unaffected.",
      "migration_path": "1. Stop using the Azure Maps Traffic APIs version 1.0 before the retirement date.\n2. Transition to [Azure Maps Traffic Incident API version 2025-01-01](https://learn.microsoft.com/en-us/rest/api/maps/traffic?view=rest-maps-2025-01-01), [Azure Maps Get Map Tile API version 2024-04-01](https://learn.microsoft.com/rest/api/maps/render/get-map-tile?view=rest-maps-2024-04-01), or both.\n3. Follow the Microsoft [migration instructions](https://aka.ms/AzureMapsTrafficv1.0MigrationGuide).",
      "replacement": "Azure Maps Traffic Incident API version 2025-01-01 and/or Azure Maps Get Map Tile API version 2024-04-01",
      "affected_versions": [
        "1.0"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=485810",
      "extra_source_urls": [
        "https://learn.microsoft.com/rest/api/maps/traffic?view=rest-maps-1.0",
        "https://learn.microsoft.com/en-us/rest/api/maps/traffic?view=rest-maps-2025-01-01",
        "https://learn.microsoft.com/rest/api/maps/render/get-map-tile?view=rest-maps-2024-04-01",
        "https://aka.ms/AzureMapsTrafficv1.0MigrationGuide"
      ],
      "vendor_ref": "485810",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-maps-traffic-apis-version-1-0-retirement"
    },
    {
      "slug": "azure-log-analytics-batch-api-retirement",
      "title": "Azure Monitor Log Analytics: batch API retirement",
      "summary": "Retirement date for the batch API in Azure Monitor Log Analytics: 31 Mar 2028. After that date, queries that use this API no longer work.",
      "cloud": "azure",
      "service": "Azure Monitor Log Analytics",
      "service_slug": "log-analytics",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2025-04-01",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "The batch API in Azure Monitor Log Analytics is retired on 31 Mar 2028. After that date, queries that use this API no longer work. Workloads that call the batch API are affected, including usage through the Azure Monitor Query client SDKs, which Microsoft asks customers to review.",
      "migration_path": "1. Review any use of the batch API, including through the [Azure Monitor Query client SDKs](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/overview#try-the-log-analytics-api).\n2. Move to the standard request API and format for the Azure Monitor Log Analytics data access API.\n3. Split batch queries into single queries and follow the [request](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/request-format) and [response](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/response-format) API formats.\n4. See the Microsoft [documentation](https://aka.ms/laapideprecation) for more information.",
      "replacement": "Standard request API for the Azure Monitor Log Analytics data access API",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=486080",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/batch-queries",
        "https://learn.microsoft.com/en-us/azure/developer/intro/azure-service-sdk-tool-versioning",
        "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/request-format",
        "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/response-format",
        "https://learn.microsoft.com/en-us/azure/azure-monitor/logs/api/overview#try-the-log-analytics-api",
        "https://aka.ms/laapideprecation"
      ],
      "vendor_ref": "486080",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-log-analytics-batch-api-retirement"
    },
    {
      "slug": "azure-spring-apps-retirement",
      "title": "Azure Spring Apps retirement",
      "summary": "Retirement date for the Azure Spring Apps Basic, Standard and Enterprise plans: 31 Mar 2028. After that date the service is not supported and instances are no longer accessible.",
      "cloud": "azure",
      "service": "Azure Spring Apps",
      "service_slug": "spring-apps",
      "category": "service",
      "type": "retirement",
      "announced_date": "2024-10-03",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "The Azure Spring Apps Basic, Standard and Enterprise plans retire on 31 Mar 2028, at the end of a 3-year sunset period. New customers have not been able to sign up for these plans since March 31, 2025, and existing customers remain operational until the retirement date. After the retirement date of each plan, instances are no longer accessible. The Standard consumption and dedicated plan (preview) had an earlier retirement date of March 31, 2025.",
      "migration_path": "1. Move workloads running on Azure Spring Apps to Azure Container Apps, the primary migration target Microsoft recommends, by 31 Mar 2028 for the Basic, Standard and Enterprise plans.\n2. If you use Spring Commercial support or a Tanzu component as part of Azure Spring Apps Enterprise, switch to Tanzu Platform Spring Essentials on Azure Container Apps.\n3. Review the [retirement guide](https://go.microsoft.com/fwlink/?linkid=2289911) for migration solutions and the transition guide.",
      "replacement": "Azure Container Apps",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=azure-spring-apps-will-be-retired-on-march-31-2028",
      "extra_source_urls": [],
      "vendor_ref": "azure-spring-apps-will-be-retired-on-march-31-2028",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-spring-apps-retirement"
    },
    {
      "slug": "azure-spring-apps-basic-standard-enterprise-plans-retirement",
      "title": "Azure Spring Apps: Basic, Standard and Enterprise plans retirement",
      "summary": "Retirement date for the Azure Spring Apps Basic, Standard and Enterprise plans: 31 Mar 2028. After that date the plans are not supported and Azure Spring Apps instances are no longer accessible.",
      "cloud": "azure",
      "service": "Azure Spring Apps",
      "service_slug": "spring-apps",
      "category": "service",
      "type": "retirement",
      "announced_date": "2025-03-18",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "After the retirement date, the Azure Spring Apps Basic, Standard and Enterprise plans are not supported and Azure Spring Apps instances are no longer accessible. The plans entered a 3-year sunset period on March 17, 2025. New customers have not been able to sign up for the service since March 17, 2025. Existing customers remain operational until the plans are phased out on the retirement date.",
      "migration_path": "1. Move workloads running on Azure Spring Apps to [Azure Container Apps](https://azure.microsoft.com/en-us/products/container-apps/?msockid=2d9407b2d07368ad23631375d1ac693e) or [Azure Kubernetes Service](https://azure.microsoft.com/en-us/products/kubernetes-service/) by the retirement date. For more information, see [Learn more](https://aka.ms/asaretirement).\n2. For technical help, [open a support ticket](https://go.microsoft.com/fwlink/?linkid=2280908) through the Azure portal.",
      "replacement": "Azure Container Apps or Azure Kubernetes Service",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=485865",
      "extra_source_urls": [
        "https://azure.microsoft.com/en-us/updates/?id=azure-spring-apps-will-be-retired-on-march-31-2028",
        "https://azure.microsoft.com/en-us/products/container-apps/?msockid=2d9407b2d07368ad23631375d1ac693e",
        "https://azure.microsoft.com/en-us/products/kubernetes-service/",
        "https://aka.ms/asaretirement"
      ],
      "vendor_ref": "485865",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-spring-apps-basic-standard-enterprise-plans-retirement"
    },
    {
      "slug": "azure-vpn-gateway-manually-registered-vpn-clients-retirement",
      "title": "Azure VPN Gateway: manually registered Azure VPN clients retirement",
      "summary": "Retirement date for manually registered Azure VPN clients for point-to-site connections with Microsoft Entra ID authentication: 31 Mar 2028. After that date, only Microsoft-registered VPN clients are supported.",
      "cloud": "azure",
      "service": "Azure VPN Gateway",
      "service_slug": "vpn-gateway",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-03-31",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "On 31 Mar 2028, manually registered Azure VPN clients for point-to-site connections with Microsoft Entra ID authentication are retired. After that date, only Microsoft-registered VPN clients are supported. Since 30 December 2025, it is no longer possible to create point-to-site connections with a manually registered client. Subscriptions that use a manually registered Azure VPN client for point-to-site VPN connections are affected.",
      "migration_path": "[Migrate manually registered Azure VPN clients](https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-entra-gateway-update) to a Microsoft-registered VPN client for point-to-site connections with Microsoft Entra ID authentication before 31 Mar 2028.",
      "replacement": "Microsoft-registered VPN client",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=485535",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-entra-gateway-update",
        "https://aka.ms/ServicesRetirementWorkbook%22%20/t%20%22_blank",
        "https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request"
      ],
      "vendor_ref": "485535",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-vpn-gateway-manually-registered-vpn-clients-retirement"
    },
    {
      "slug": "azure-virtual-machines-dsc-extension-retirement",
      "title": "Azure Virtual Machines: Desired State Configuration extension retirement",
      "summary": "Microsoft retires the Desired State Configuration Extension for Azure Virtual Machines on 31 Mar 2028. After that date the extension is no longer supported. Microsoft names Azure Machine Configuration as the replacement.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2025-03-26",
      "effective_date": "2028-03-31",
      "effective_precision": "day",
      "impact": "The Desired State Configuration Extension for Azure Virtual Machines is retired on the retirement date. After that date, the extension is no longer supported. Until that date, the extension can be used without disruption. Microsoft advises migrating to Azure Machine Configuration by that date to avoid service disruptions.",
      "migration_path": "1. In the Azure portal, open \"Virtual machines\", select each virtual machine, then \"Settings\" and \"Extensions + Applications\" to list the extensions assigned.\n2. Follow Microsoft's instructions to [migrate](https://aka.ms/dscext2gc) to Azure Machine Configuration before the retirement date.",
      "replacement": "Azure Machine Configuration",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=485828",
      "extra_source_urls": [
        "https://aka.ms/dscext2gc"
      ],
      "vendor_ref": "485828",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-dsc-extension-retirement"
    },
    {
      "slug": "gcp-compute-engine-rhel-9-4-for-sap-image-end-of-support",
      "title": "Compute Engine: RHEL 9.4 for SAP image end of support",
      "summary": "EOS and image deprecation date for the RHEL 9.4 for SAP public image on Compute Engine: Apr 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 9.4 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 9.4 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-9-4-sap-ha",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-9-4-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-pro-18-04-lts-image-end-of-support",
      "title": "Compute Engine: Ubuntu Pro 18.04 LTS image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu Pro 18.04 LTS public image on Compute Engine: Apr 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu Pro 18.04 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu Pro 18.04 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-pro-1804-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-pro-18-04-lts-image-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-python-3-11-retirement",
      "title": "Cloud Run: Python 3.11 decommission",
      "summary": "Decommission date for Python 3.11 on Cloud Run: 24 Apr 2028. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2028-04-24",
      "effective_precision": "day",
      "impact": "The decommission date of Python 3.11 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-python-3-11-retirement"
    },
    {
      "slug": "aws-lambda-nodejs24-x-end-of-support",
      "title": "AWS Lambda: Node.js 24 (nodejs24.x) deprecation",
      "summary": "Deprecation date for Node.js 24 (nodejs24.x) on AWS Lambda: 30 Apr 2028. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-04-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Apr 2028), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 1 Jun 2028, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 1 Jul 2028, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 1 Jul 2028), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "nodejs24.x"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "nodejs24.x",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-nodejs24-x-end-of-support"
    },
    {
      "slug": "aws-aurora-mysql-version-3-end-of-support",
      "title": "Amazon Aurora MySQL: version 3 end of standard support",
      "summary": "Aurora end of standard support date for Amazon Aurora MySQL version 3: 30 Apr 2028. AWS states that a major version can keep running past this date under RDS Extended Support, for a fee.",
      "cloud": "aws",
      "service": "Amazon Aurora MySQL",
      "service_slug": "aurora-mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-04-30",
      "effective_precision": "day",
      "impact": "AWS states that a major version can keep running past its standard support end date under RDS Extended Support, for an [additional cost](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html). The [release calendar](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html#AuroraMySQL.release-calendars.major) lists Extended Support dates and eligible minor versions; some are \"To be determined\".\n\n- Aurora automatically enrolls a DB instance after that date if RDS Extended Support was enabled at creation or restoration.\n- It provides security updates for critical and high CVEs, bug fixes for critical issues, and support cases.\n- Charges apply only to certain minor versions.\n- Enrollment can be changed at any time, at the cluster level. Disabling it after that date upgrades the instance or cluster automatically to the next supported major version.",
      "migration_path": "1. Look up your type and version of cluster in [Aurora MySQL major version upgrade paths](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Compatibility). The table says whether the cluster can use the in-place upgrade mechanism and which action applies.\n2. Where the table points to a major version upgrade, plan it with [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). A major version upgrade needs more planning and testing than a minor version upgrade.\n3. Before an in-place upgrade, create a clone of the original cluster, perform an in-place upgrade of the clone immediately after creating it, and test application compatibility, performance and administration procedures on it.\n4. When the test cluster works properly, perform the in-place upgrade for the production cluster. See [How to perform an in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Upgrading.Procedure.html).\n5. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "3"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-mysql"
      ],
      "vendor_ref": "amazon-aurora-mysql@3",
      "last_checked_at": "2026-11-12T09:55:40.805Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-mysql-version-3-end-of-support"
    },
    {
      "slug": "azure-app-service-node-24-end-of-support",
      "title": "Azure App Service: Node 24 end of support",
      "summary": "End of support date for Node 24 on Azure App Service: 30 Apr 2028. Apps that use this version continue to run unchanged, but App Service can't provide security patches or related customer support for it past that date.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-04-30",
      "effective_precision": "day",
      "impact": "After 30 Apr 2028, apps that use Node 24 continue to run unchanged, but App Service can't provide security patches or related customer support for that runtime version.\n\n- An app on an unsupported language version must be upgraded to a supported version before it can get App Service support.\n- App Service sends reminder notifications about end-of-support dates to subscription owners.\n- Contributors, readers, or other roles don't directly receive notifications unless they opt in through Service Health Alerts.\n- For Java, the page adds that developers who use a supported Java runtime that is retired receive a deprecation notice at least six months before the runtime is retired.",
      "migration_path": "1. Find the language version the app uses. The [language runtime support policy](https://learn.microsoft.com/en-us/azure/app-service/language-support-policy) links \"Show language version\" resources for .NET, Java, Node, Python and PHP.\n2. Choose a supported version of Node. The same page links the support timeline of each language community.\n3. Set the new language version for the app. The same page links \"Set language versions\" resources for .NET, Java, Node, Python and PHP.",
      "replacement": null,
      "affected_versions": [
        "24"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy",
      "extra_source_urls": [
        "https://github.com/nodejs/release"
      ],
      "vendor_ref": "appservice@node:24",
      "last_checked_at": "2026-11-12T09:56:00.082Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-node-24-end-of-support"
    },
    {
      "slug": "azure-functions-node-24-end-of-support",
      "title": "Azure Functions: Node.js 24 end of support",
      "summary": "End of support date for Node.js 24 on Azure Functions: 30 Apr 2028. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-04-30",
      "effective_precision": "day",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Node.js 24 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "24"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@node:24",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-node-24-end-of-support"
    },
    {
      "slug": "azure-batch-d-ds-dv2-dsv2-ls-series-vm-retirement",
      "title": "Azure Batch: D, Ds, Dv2, Dsv2 and Ls-series VM retirement",
      "summary": "Retirement date for the D, Ds, Dv2, Dsv2 and Ls virtual machine series in Azure Batch pools: 1 May 2028. After that date, pools on these series cannot be created or scaled out and may be resized to zero nodes.",
      "cloud": "azure",
      "service": "Azure Batch",
      "service_slug": "batch",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-06-11",
      "effective_date": "2028-05-01",
      "effective_precision": "day",
      "impact": "The retirement affects Azure Batch pools that rely on the D-series, Ds-series, Dv2-series, Dsv2-series and Ls-series. After the retirement date, new Batch pools using these VM series cannot be created, existing pools cannot scale out, and pools may be forcibly resized to zero nodes. Remaining VMs are stopped/deallocated and are no longer covered by the SLA. Affected pools may become unusable.",
      "migration_path": "1. Migrate Batch pools to supported VM families before the retirement date.\n2. For general-purpose pools (D, Ds, Dv2, Dsv2), use Dsv5/Ddsv5 or Dasv5/Dadsv5, or Dsv6/Ddsv6 or Dasv6/Dadsv6 for NVMe workloads.\n3. For storage-optimized pools (Ls), use Lsv3/Lasv3 or Lsv4/Lasv4.\n4. Either scale the pool to zero and update the VM size using the Batch API (2024-07-01 or later), or create a new pool with supported VM sizes and migrate the workloads.\n5. Check Azure VM pricing, because VM pricing may change after migration.",
      "replacement": "Dsv5/Ddsv5 or Dasv5/Dadsv5 (Dsv6/Ddsv6 or Dasv6/Dadsv6 for NVMe workloads); Lsv3/Lasv3 or Lsv4/Lasv4 for Ls",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=564772",
      "extra_source_urls": [],
      "vendor_ref": "564772",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-batch-d-ds-dv2-dsv2-ls-series-vm-retirement"
    },
    {
      "slug": "azure-virtual-machines-d-ds-dv2-dsv2-and-ls-series-retirement",
      "title": "Azure Virtual Machines: D, Ds, Dv2, Dsv2 and Ls series retirement",
      "summary": "Retirement date for D, Ds, Dv2, Dsv2 and Ls series Azure Virtual Machines: 1 May 2028. After that date these VMs can no longer be used or purchased.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2025-03-31",
      "effective_date": "2028-05-01",
      "effective_precision": "day",
      "impact": "After the retirement date, D, Ds, Dv2, Dsv2 and Ls series VMs can no longer be used or purchased. Three-year reserved instances for these VMs cannot be purchased or renewed from May 1, 2025. One-year reserved VM instances for these VMs are not available for purchase or renewal from July 1, 2026. An existing three-year reservation keeps its benefit for the remainder of the contract, and usage is billed at pay-as-you-go rates after that.",
      "migration_path": "1. Migrate D, Ds, Dv2, Dsv2 and Ls series VM workloads to a newer VM generation, following the [migration guide](https://aka.ms/VirtualMachinesMigrationGuide).\n2. Review your [current reservation orders](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/manage-reserved-vm-instance) to identify impacted VMs and their expiration dates.",
      "replacement": null,
      "affected_versions": [
        "D",
        "Ds",
        "Dv2",
        "Dsv2",
        "Ls"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=485569",
      "extra_source_urls": [
        "https://aka.ms/VirtualMachinesMigrationGuide",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/prepay-reserved-vm-instances?toc=%2Fazure%2Fcost-management-billing%2Freservations%2Ftoc.json",
        "https://azure.microsoft.com/en-us/updates?id=560948",
        "https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/manage-reserved-vm-instance",
        "https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux-previous/",
        "https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request"
      ],
      "vendor_ref": "485569",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-d-ds-dv2-dsv2-and-ls-series-retirement"
    },
    {
      "slug": "gcp-compute-engine-rhel-10-2-eus-image-end-of-support",
      "title": "Compute Engine: RHEL 10.2 EUS image end of support",
      "summary": "EOS and image deprecation date for the RHEL 10.2 EUS public image on Compute Engine: May 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 10.2 EUS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 10.2 EUS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-10-2-eus",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-10-2-eus-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-10-2-eus-with-out-of-tree-gvnic-3dc0d3-end-of-support",
      "title": "Compute Engine: RHEL 10.2 EUS with out-of-tree gVNIC driver image end of support",
      "summary": "EOS and image deprecation date for the RHEL 10.2 EUS with out-of-tree gVNIC driver public image on Compute Engine: May 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 10.2 EUS with out-of-tree gVNIC driver in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 10.2 EUS with out-of-tree gVNIC driver"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-10-2-eus-oot-gve",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-10-2-eus-with-out-of-tree-gvnic-3dc0d3-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-9-8-eus-image-end-of-support",
      "title": "Compute Engine: RHEL 9.8 EUS image end of support",
      "summary": "EOS and image deprecation date for the RHEL 9.8 EUS public image on Compute Engine: May 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 9.8 EUS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 9.8 EUS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-9-8-eus",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-9-8-eus-image-end-of-support"
    },
    {
      "slug": "aws-rds-mariadb-11-8-end-of-support",
      "title": "Amazon RDS for MariaDB: MariaDB 11.8 end of standard support",
      "summary": "RDS end of standard support date for MariaDB 11.8 on Amazon RDS for MariaDB: Jun 2028. AWS lists this date so that testing and upgrade cycles can be planned around it.",
      "cloud": "aws",
      "service": "Amazon RDS for MariaDB",
      "service_slug": "rds-mariadb",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-06-01",
      "effective_precision": "month",
      "impact": "Jun 2028 is the RDS end of standard support date that AWS lists for MariaDB 11.8. The AWS page does not state what happens to DB instances still on MariaDB 11.8 after that date.\n\n- RDS for MariaDB major versions remain available at least until community end of life for the corresponding community version.\n- A date with only a month and a year is approximate and is replaced by an exact date once known.\n- If AWS extends support for a version beyond the stated date, it plans to update its version table with the later date.\n- Deprecation policy: see the [Amazon RDS FAQs](https://aws.amazon.com/rds/faqs/).",
      "migration_path": "1. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command.\n2. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n3. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MariaDB](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MariaDB.Major.html). Major version upgrades are performed manually.\n4. Plan for downtime: database engine upgrades require downtime, and its duration varies with the size of the DB instance.\n5. Downtime for the upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. The engine cannot be reverted after the upgrade completes. To return to the previous version, restore the first DB snapshot taken during the upgrade to a new DB instance. Amazon RDS only takes these snapshots if the backup retention period of the DB instance is greater than 0.",
      "replacement": null,
      "affected_versions": [
        "11.8"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MariaDB.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mariadb"
      ],
      "vendor_ref": "amazon-rds-mariadb@11.8",
      "last_checked_at": "2026-11-12T09:55:39.673Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mariadb-11-8-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-36-lts-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.36 LTS end of life",
      "summary": "LTS end of life date for Kubernetes 1.36 on Azure Kubernetes Service: Jun 2028. For clusters with long-term support enabled, support for the version continues only until that date. After it, those clusters must move to the next supported LTS version.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-06-01",
      "effective_precision": "month",
      "impact": "After the LTS end of life date, long-term support for Kubernetes 1.36 ends. LTS-enabled clusters must then be upgraded to the next supported LTS version.\n\n- If a cluster is not upgraded, AKS upgrades it to the next supported LTS version through a platform-initiated upgrade. The cluster is not dropped to a community-supported version.\n- The LTS page places this after the 60-day grace period that follows the LTS end of life date. For the initial rollout, the grace period is the window through May 31, 2027, and no platform-initiated upgrade starts before June 1, 2027. After the initial rollout, every end-of-support event has a 60-day grace period before platform-initiated upgrades begin.\n- Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget.\n- The platform-initiated upgrade month in the AKS LTS release calendar is a planning estimate, not an exact upgrade date.",
      "migration_path": "1. List the versions AKS offers as upgrade targets with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. Test the workloads against deprecated APIs and other breaking changes between the current and target versions.\n3. Upgrade to an offered higher LTS version with `az aks upgrade --resource-group <resource-group-name> --name <cluster-name> --kubernetes-version <lts-kubernetes-version>`. An LTS cluster can skip minor versions when the upgrade satisfies version-skew requirements and validation checks. See [Long-term support for AKS versions](https://learn.microsoft.com/en-us/azure/aks/long-term-support).\n4. If the cluster is already past its LTS end of life date, skipping minor versions is conditional: the target must be listed by AKS and satisfy validation checks. AKS allows this upgrade but treats it as an unsupported recovery path.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To leave LTS instead, move the cluster to the Free or Standard tier and select the KubernetesOfficial support plan. This is possible while the cluster's Kubernetes version is still in community support. After that version exits community support, first upgrade the cluster to a community-supported version.",
      "replacement": "Next supported AKS LTS version",
      "affected_versions": [
        "1.36"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.36",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-36-lts-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-10-accelerated-with-30ccd5-end-of-support",
      "title": "Compute Engine: Rocky Linux 10 Accelerated with NVIDIA driver version 580 image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 10 Accelerated with NVIDIA driver version 580 public image on Compute Engine: Jun 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-06-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 10 Accelerated with NVIDIA driver version 580 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 10 Accelerated with NVIDIA driver version 580"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-10-optimized-gcp-nvidia-580",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-10-accelerated-with-30ccd5-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-8-accelerated-with-832e57-end-of-support",
      "title": "Compute Engine: Rocky Linux 8 Accelerated with NVIDIA driver version 580 image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 8 Accelerated with NVIDIA driver version 580 public image on Compute Engine: Jun 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-06-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 8 Accelerated with NVIDIA driver version 580 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 8 Accelerated with NVIDIA driver version 580"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-8-optimized-gcp-nvidia-580",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-8-accelerated-with-832e57-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-9-accelerated-with-3dec91-end-of-support",
      "title": "Compute Engine: Rocky Linux 9 Accelerated with NVIDIA driver version 580 image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 9 Accelerated with NVIDIA driver version 580 public image on Compute Engine: Jun 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-06-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 9 Accelerated with NVIDIA driver version 580 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 9 Accelerated with NVIDIA driver version 580"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-9-optimized-gcp-nvidia-580",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-9-accelerated-with-3dec91-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-24-04-lts-accelerated-with-b0fa9d-end-of-support",
      "title": "Compute Engine: Ubuntu 24.04 LTS Accelerated with NVIDIA driver version 580 image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu 24.04 LTS Accelerated with NVIDIA driver version 580 public image on Compute Engine: Jun 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-06-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu 24.04 LTS Accelerated with NVIDIA driver version 580 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu 24.04 LTS Accelerated with NVIDIA driver version 580"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-accelerator-2404-amd64-with-nvidia-580",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-24-04-lts-accelerated-with-b0fa9d-end-of-support"
    },
    {
      "slug": "gcp-gke-kubernetes-1-36-extended-support-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.36 end of extended support",
      "summary": "End of extended support date for GKE Kubernetes 1.36: 9 Jun 2028. From that date the minor version receives no security patches, and GKE upgrades Extended channel clusters still running it to the next minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-06-09",
      "effective_precision": "day",
      "impact": "At the end of extended support, GKE does not provide any patches for security fixes, and the minor version is considered unsupported. GKE upgrades clusters still running it to the next minor version.\n\n- The upgrade happens regardless of the cluster's use of deprecated features or APIs.\n- Maintenance exclusions cannot be configured past this date, except as a temporary, emergency measure with the \"No upgrades\" scope.\n- That exclusion can delay the upgrade for up to 90 days after the end of support date. Google does not recommend it.\n- Dates in the GKE release schedule are updated monthly and subject to change.",
      "migration_path": "1. Google does not recommend enrolling a cluster in the Extended channel without plans to move to the next minor version, because GKE eventually upgrades the cluster to newer minor versions.\n2. Around 2 months before the end of extended support, GKE begins upgrading clusters in the Extended channel to the next minor version, unless the cluster is using deprecated features or APIs.\n3. Maintenance exclusions can prevent minor version upgrades until the end of extended support. A temporary, emergency exclusion with the \"No upgrades\" scope can delay the upgrade for up to 90 days after the end of support date. After that exclusion expires, GKE upgrades the cluster.\n4. At the end of extended support, GKE upgrades all clusters still running the minor version, regardless of blocking issues. See [GKE minor version lifecycle](https://docs.cloud.google.com/kubernetes-engine/versioning#lifecycle).",
      "replacement": null,
      "affected_versions": [
        "1.36"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [],
      "vendor_ref": "gke@1.36",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-36-extended-support-end-of-support"
    },
    {
      "slug": "azure-monitor-vm-insights-map-dependency-agent-retirement",
      "title": "Azure Monitor: VM Insights Map and Dependency Agent retirement",
      "summary": "Retirement date for VM Insights Map and the Dependency Agent in Azure Monitor: 30 Jun 2028. After that date, the Map tab, the Service Map API and new Dependency Agent data are no longer available.",
      "cloud": "azure",
      "service": "Azure Monitor",
      "service_slug": "monitor",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-07-02",
      "effective_date": "2028-06-30",
      "effective_precision": "day",
      "impact": "All functionality associated with VM Insights Map and the Dependency Agent is retired on 30 Jun 2028, and both are no longer supported. After the retirement date, customers cannot access the Map tab in VM Insights or the Connections Overview workbook, cannot install the Dependency Agent on new VMs from the Azure portal, cannot send new data to Azure Monitor Log Analytics using the Dependency Agent, and cannot query the Service Map API. Existing data stays in the Log Analytics workspace according to the configured retention policy. No new operating system versions are supported from June 30, 2025, and new VMs cannot be onboarded from the Azure portal after September 30, 2025.",
      "migration_path": "1. Read the [retirement and migration guidance](https://aka.ms/DependencyAgentRetirement).\n2. To keep collecting data about processes running on virtual machines and external process dependencies, consider a replacement solution from the Azure Marketplace.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=491629",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/azure-monitor/vm/vminsights-dependency-agent-maintenance",
        "https://learn.microsoft.com/azure/azure-monitor/vm/vminsights-maps",
        "https://aka.ms/DependencyAgentRetirement"
      ],
      "vendor_ref": "491629",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-monitor-vm-insights-map-dependency-agent-retirement"
    },
    {
      "slug": "gcp-cloud-run-php-8-3-retirement",
      "title": "Cloud Run: PHP 8.3 decommission",
      "summary": "Decommission date for PHP 8.3 on Cloud Run: 30 Jun 2028. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2028-06-30",
      "effective_precision": "day",
      "impact": "The decommission date of PHP 8.3 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-php-8-3-retirement"
    },
    {
      "slug": "gcp-compute-engine-debian-12-image-end-of-support",
      "title": "Compute Engine: Debian 12 image end of support",
      "summary": "EOS and image deprecation date for the Debian 12 public image on Compute Engine: 30 Jun 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-06-30",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Debian 12 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Debian 12"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "debian-12",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-debian-12-image-end-of-support"
    },
    {
      "slug": "azure-dedicated-hsm-retirement",
      "title": "Azure Dedicated HSM retirement",
      "summary": "Retirement date for Azure Dedicated HSM: 31 Jul 2028. Microsoft provides full support to existing customers until that date and names Azure Cloud HSM as the successor service.",
      "cloud": "azure",
      "service": "Azure Dedicated HSM",
      "service_slug": "dedicated-hsm",
      "category": "service",
      "type": "retirement",
      "announced_date": "2025-08-01",
      "effective_date": "2028-07-31",
      "effective_precision": "day",
      "impact": "Azure Dedicated HSM retires on 31 Jul 2028. Microsoft provides full support for all existing Azure Dedicated HSM customers until that date. Microsoft no longer accepts new customer onboardings to Azure Dedicated HSM, effective from the announcement.",
      "migration_path": "1. Make a plan to transition to [Azure Cloud HSM](https://learn.microsoft.com/en-us/azure/cloud-hsm/overview) by July 31, 2026. Microsoft also names Azure Managed HSM as a target, depending on workload and compliance requirements.\n2. Transition to Azure Cloud HSM by 31 Jul 2028.\n3. New customers onboard to Azure Cloud HSM, Azure Managed HSM or Azure Key Vault, [depending on their use case](https://learn.microsoft.com/en-us/azure/security/fundamentals/key-management-choose).",
      "replacement": "Azure Cloud HSM",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=499214",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/cloud-hsm/overview",
        "https://learn.microsoft.com/en-us/azure/security/fundamentals/key-management-choose"
      ],
      "vendor_ref": "499214",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-dedicated-hsm-retirement"
    },
    {
      "slug": "aws-eks-kubernetes-1-36-extended-support-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.36 end of extended support",
      "summary": "End of extended support date for Kubernetes 1.36 on Amazon EKS: 2 Aug 2028. On that date, new clusters can no longer be created with this version, and Amazon EKS automatically updates control planes still on it at any time afterward.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-08-02",
      "effective_precision": "day",
      "impact": "On the end of extended support date, new Amazon EKS clusters can no longer be created with Kubernetes 1.36. Amazon EKS automatically updates existing control planes to the earliest supported version, at any time after that date.\n\n- Amazon EKS gives no specific time frame and sends no notification before the update.\n- The auto-upgrade includes only the Kubernetes control plane. Self-managed nodes and EKS managed node groups remain on the previous version.\n- EKS Auto Mode nodes may update automatically.\n- Fargate nodes and hybrid nodes are not upgraded with the control plane.\n- Clusters that were automatically upgraded at the end of extended support cannot be rolled back.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version.\n3. Proactively update the control plane without relying on the Amazon EKS automatic update process, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n4. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n5. If Amazon EKS updated the control plane automatically, manually update cluster add-ons and Amazon EC2 nodes.",
      "replacement": null,
      "affected_versions": [
        "1.36"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.36",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-36-extended-support-end-of-support"
    },
    {
      "slug": "azure-app-service-java-21-end-of-support",
      "title": "Azure App Service: Java 21 end of support",
      "summary": "End of support date for Java 21 on Azure App Service: Sep 2028. Apps that use this version continue to run unchanged, but App Service can't provide security patches or related customer support for it past that date.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-09-01",
      "effective_precision": "month",
      "impact": "After Sep 2028, apps that use Java 21 continue to run unchanged, but App Service can't provide security patches or related customer support for that runtime version.\n\n- An app on an unsupported language version must be upgraded to a supported version before it can get App Service support.\n- App Service sends reminder notifications about end-of-support dates to subscription owners.\n- Contributors, readers, or other roles don't directly receive notifications unless they opt in through Service Health Alerts.\n- For Java, the page adds that developers who use a supported Java runtime that is retired receive a deprecation notice at least six months before the runtime is retired.",
      "migration_path": "1. Find the language version the app uses. The [language runtime support policy](https://learn.microsoft.com/en-us/azure/app-service/language-support-policy) links \"Show language version\" resources for .NET, Java, Node, Python and PHP.\n2. Choose a supported version of Java. The same page links the support timeline of each language community.\n3. Set the new language version for the app. The same page links \"Set language versions\" resources for .NET, Java, Node, Python and PHP.",
      "replacement": null,
      "affected_versions": [
        "21"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/java/openjdk/support"
      ],
      "vendor_ref": "appservice@java:21",
      "last_checked_at": "2026-11-12T09:56:00.082Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-java-21-end-of-support"
    },
    {
      "slug": "azure-functions-java-21-end-of-support",
      "title": "Azure Functions: Java 21 end of support",
      "summary": "End of support date for Java 21 on Azure Functions: Sep 2028. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-09-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Java 21 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "21"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@java:21",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-java-21-end-of-support"
    },
    {
      "slug": "azure-ai-language-entity-linking-retirement",
      "title": "Azure AI Language: Entity Linking retirement",
      "summary": "Retirement date for Entity Linking in Azure AI Language: 8 Sep 2028. Microsoft supports existing Entity Linking until that date and recommends Named Entity Recognition or another replacement solution.",
      "cloud": "azure",
      "service": "Azure AI Language",
      "service_slug": "ai-language",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-09-26",
      "effective_date": "2028-09-08",
      "effective_precision": "day",
      "impact": "Entity Linking in Azure AI Language is retired on the retirement date, and Microsoft provides full support for existing Entity Linking until then. Since the announcement, Microsoft no longer accepts new customer onboardings to Entity Linking. Existing Entity Linking customers need to transition off by the retirement date.",
      "migration_path": "1. Make a transition plan for [Named Entity Recognition](https://learn.microsoft.com/en-us/azure/ai-services/language-service/named-entity-recognition/overview) or another replacement solution. The source asks for this plan by September 08, 2026.\n2. Choose the replacement according to your workload and compliance requirements.\n3. Transition off Entity Linking by 8 Sep 2028.",
      "replacement": "Named Entity Recognition or another replacement solution",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=499851",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/ai-services/language-service/named-entity-recognition/overview"
      ],
      "vendor_ref": "499851",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-language-entity-linking-retirement"
    },
    {
      "slug": "azure-disk-storage-os-disks-on-standard-hdd-retirement",
      "title": "Azure Disk Storage: OS disks on Standard HDD retirement",
      "summary": "Service for operating system (OS) disks on Standard HDD is retired on 8 Sep 2028. OS disks not migrated by then are converted to Standard SSD of equivalent size.",
      "cloud": "azure",
      "service": "Azure Disk Storage",
      "service_slug": "disk-storage",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-09-08",
      "effective_date": "2028-09-08",
      "effective_precision": "day",
      "impact": "From 8 Sep 2028, service for operating system (OS) disks running on Standard HDD is retired. After the retirement date, OS disks still on Standard HDD are converted to Standard SSD of equivalent size. Microsoft states that migrating before the retirement date avoids a potential service disruption after that date. Standard HDD data disks (non-boot volumes) and ephemeral OS disks are not affected.",
      "migration_path": "1. Stop using Standard HDD OS disks for new virtual machines.\n2. Migrate existing HDD OS disks to Standard SSD or Premium SSD before the retirement date. See [Convert managed disks storage between different disk types](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-convert-types?tabs=azure-powershell).\n3. Review the [Azure Disk Storage billing guidance](https://learn.microsoft.com/en-us/azure/virtual-machines/disks-understand-billing) to select the disk type that fits the workload and budget.\n4. Microsoft states that additional details are shared in its [public documentation](https://aka.ms/standard-hdd-os-disk-retirement) before the retirement date.",
      "replacement": "Standard SSD or Premium SSD",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=500157",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks",
        "https://aka.ms/standard-hdd-os-disk-retirement",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-convert-types?tabs=azure-powershell",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/disks-understand-billing"
      ],
      "vendor_ref": "500157",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-disk-storage-os-disks-on-standard-hdd-retirement"
    },
    {
      "slug": "azure-key-vault-hsmplatform-1-keys-retirement",
      "title": "Azure Key Vault: support for hsmPlatform 1 keys retirement",
      "summary": "Retirement date for support of hsmPlatform 1 keys in Azure Key Vault: 15 Sep 2028. Microsoft recommends moving to hsmPlatform 2 keys.",
      "cloud": "azure",
      "service": "Azure Key Vault",
      "service_slug": "key-vault",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-09-15",
      "effective_date": "2028-09-15",
      "effective_precision": "day",
      "impact": "Support for hsmPlatform 1 keys in Azure Key Vault is retired on 15 Sep 2028. Affected keys can be found by listing keys and checking the HSMPlatform value. Keys cannot be transferred directly from hsmPlatform 1 to hsmPlatform 2.",
      "migration_path": "1. List your keys and check the HSMPlatform value to find the keys that need migration. See [Azure Key Vault Key Attributes](https://learn.microsoft.com/en-us/azure/key-vault/keys/about-keys-details#key-attributes).\n2. Create new keys on hsmPlatform 2.\n3. Rekey or roll your operations to use the new keys, following the [migration documentation](https://learn.microsoft.com/en-us/azure/key-vault/general/migrate-key-workloads).\n4. Do not delete the old tenant key until it is no longer needed for content or documents protected under it.\n5. To migrate existing documents, remove the protection applied with the old tenant key and reapply protection using the new tenant key.",
      "replacement": "hsmPlatform 2 keys",
      "affected_versions": [
        "hsmPlatform 1"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=494676",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/key-vault/keys/about-keys-details#key-attributes",
        "https://learn.microsoft.com/en-us/azure/key-vault/general/migrate-key-workloads"
      ],
      "vendor_ref": "494676",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-key-vault-hsmplatform-1-keys-retirement"
    },
    {
      "slug": "azure-virtual-machines-disk-encryption-retirement",
      "title": "Azure Virtual Machines: Azure Disk Encryption retirement",
      "summary": "Azure Disk Encryption is retired on 15 Sep 2028. From that date, workloads that use it keep running but fail to unlock after a reboot. Microsoft recommends Encryption at Host.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-09-24",
      "effective_date": "2028-09-15",
      "effective_precision": "day",
      "impact": "Azure Disk Encryption is retired on the retirement date. Until that date, Azure Disk Encryption can be used without disruption. From the retirement date, workloads running Azure Disk Encryption continue to run but fail to unlock after reboots.",
      "migration_path": "1. Move to Encryption at Host, the option Microsoft recommends.\n2. Alternatively, consider Confidential Virtual Machine sizes with OS disk encryption.\n3. Follow Microsoft's [instructions to migrate](https://aka.ms/ademigrate) before the retirement date.",
      "replacement": "Encryption at Host",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=493779",
      "extra_source_urls": [
        "https://aka.ms/ademigrate"
      ],
      "vendor_ref": "493779",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-disk-encryption-retirement"
    },
    {
      "slug": "azure-dev-box-retirement",
      "title": "Microsoft Dev Box retirement",
      "summary": "Retirement date for Microsoft Dev Box: 18 Sep 2028. After retirement, the service is no longer available. Microsoft recommends Windows 365 as the path forward for virtualized developer environments.",
      "cloud": "azure",
      "service": "Microsoft Dev Box",
      "service_slug": "dev-box",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-10-08",
      "effective_date": "2028-09-18",
      "effective_precision": "day",
      "impact": "After the retirement date, Microsoft Dev Box is no longer available. Microsoft gives September 14, 2026 as the start of the closing-down process and describes the service as in maintenance mode, with no new feature development planned. Customers who use Microsoft Dev Box can continue using their existing deployments during the transition period.",
      "migration_path": "1. Review your current Dev Box usage, including dev centers, projects, pools, images, and developer workflows.\n2. Identify which scenarios can transition directly to Windows 365 and which require additional planning.\n3. Validate identity, device management, networking, image, and licensing requirements for your future-state environment.\n4. Test replacement workflows before retirement.\n5. For questions or support, contact your Microsoft representative.",
      "replacement": "Windows 365",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=567933",
      "extra_source_urls": [],
      "vendor_ref": "567933",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-dev-box-retirement"
    },
    {
      "slug": "azure-ai-custom-vision-service-retirement",
      "title": "Azure AI Custom Vision retirement",
      "summary": "Retirement date for the Azure Custom Vision service: 25 Sep 2028. Microsoft provides full support for existing Azure Custom Vision customers until that date.",
      "cloud": "azure",
      "service": "Azure AI Custom Vision",
      "service_slug": "ai-custom-vision",
      "category": "service",
      "type": "retirement",
      "announced_date": "2025-10-13",
      "effective_date": "2028-09-25",
      "effective_precision": "day",
      "impact": "The Azure Custom Vision service is retired on the retirement date. Existing Azure Custom Vision customers receive full support until the retirement date. During that support window, Microsoft encourages customers to plan and carry out a transition to alternative solutions.",
      "migration_path": "1. For custom image classification and object detection models, Microsoft points to Azure Machine Learning AutoML.\n2. To use generative models, pick a model from the [Azure AI Foundry model catalog](https://ai.azure.com/catalog/models) and build your own solution for customized vision.\n3. For a managed generative solution for image classification, Microsoft points to [Azure AI Content Understanding](https://aka.ms/cu-foundry), which was in public preview when the retirement was announced.\n4. See the [Azure Custom Vision documentation](https://aka.ms/custom-vision-migration) for more context on the alternatives.",
      "replacement": "Azure Machine Learning AutoML, Azure AI Foundry models or Azure AI Content Understanding",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=502914",
      "extra_source_urls": [
        "https://aka.ms/cu-foundry",
        "https://aka.ms/custom-vision-migration"
      ],
      "vendor_ref": "502914",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-custom-vision-service-retirement"
    },
    {
      "slug": "azure-computer-vision-image-analysis-retirement",
      "title": "Azure Computer Vision: Image Analysis retirement",
      "summary": "Retirement date for the Azure Computer Vision Image Analysis service: 25 Sep 2028. Microsoft provides full support for existing customers until that date.",
      "cloud": "azure",
      "service": "Azure Computer Vision",
      "service_slug": "computer-vision",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-10-23",
      "effective_date": "2028-09-25",
      "effective_precision": "day",
      "impact": "Microsoft has announced the retirement of the Azure Computer Vision Image Analysis service, with the retirement date 25 Sep 2028. All existing Image Analysis customers have full support until that date. Microsoft encourages customers to plan and carry out a transition to another Azure product during the support window. The transition plan depends on the specific use cases for Image Analysis.",
      "migration_path": "1. For OCR and Read capabilities, use [Document Intelligence](https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/prebuilt/read?view=doc-intel-4.0.0&tabs=sample-code).\n2. For Face scenarios, use the [Face API](https://learn.microsoft.com/en-us/azure/ai-services/computer-vision/overview-identity).\n3. For other Computer Vision scenarios, use the [GPT model series in Microsoft Foundry](https://ai.azure.com/catalog/models).\n4. [Azure AI Content Understanding](https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/overview), a product in preview at the time of the announcement, also supports many image analysis use cases.\n5. See the [Azure Computer Vision Image Analysis documentation](https://aka.ms/computer-vision-migration) for more information on your specific use case.",
      "replacement": "Document Intelligence, Face API or GPT models in Microsoft Foundry, depending on the use case",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=502909",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/prebuilt/read?view=doc-intel-4.0.0&tabs=sample-code",
        "https://learn.microsoft.com/en-us/azure/ai-services/computer-vision/overview-identity",
        "https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/overview",
        "https://aka.ms/computer-vision-migration"
      ],
      "vendor_ref": "502909",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-computer-vision-image-analysis-retirement"
    },
    {
      "slug": "azure-cache-for-redis-retirement",
      "title": "Azure Cache for Redis (Basic, Standard and Premium) retirement",
      "summary": "Retirement date for Azure Cache for Redis (Basic, Standard and Premium): 30 Sep 2028. Instances that are not migrated by that date are shut down.",
      "cloud": "azure",
      "service": "Azure Cache for Redis",
      "service_slug": "cache-for-redis",
      "category": "service",
      "type": "retirement",
      "announced_date": "2025-10-08",
      "effective_date": "2028-09-30",
      "effective_precision": "day",
      "impact": "Azure Cache for Redis (Basic, Standard and Premium) is retired on 30 Sep 2028. Azure Cache for Redis instances that are not migrated by the retirement date are shut down.",
      "migration_path": "Migrate workloads to Azure Managed Redis before the retirement date. Microsoft links further details under [Learn more](https://aka.ms/AzureCacheForRedisRetirement).",
      "replacement": "Azure Managed Redis",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=499577",
      "extra_source_urls": [
        "https://aka.ms/AzureCacheForRedisRetirement"
      ],
      "vendor_ref": "499577",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-cache-for-redis-retirement"
    },
    {
      "slug": "azure-communication-services-standalone-services-retirement",
      "title": "Azure Communication Services: standalone services retirement",
      "summary": "Retirement date for several standalone Azure Communication Services offerings, including Email, SMS, Chat and Rooms: 30 Sep 2028. From that date they no longer function, and calling services work only with Microsoft Teams on the latest SDKs.",
      "cloud": "azure",
      "service": "Azure Communication Services",
      "service_slug": "communication-services",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-09-24",
      "effective_date": "2028-09-30",
      "effective_precision": "day",
      "impact": "From 30 Sep 2028, these Azure Communication Services offerings no longer function: Email, SMS, Advanced Messaging with WhatsApp, Chat, Chat for Teams Meeting Interop, Rooms, Number Management (Direct Offer), Direct Routing, Job Router, Web UI Library SDK and Mobile UI Library SDK. Voice/Video Calling SDK, Call Diagnostics, Call Automation, Audio Streaming, Call Recording and Closed Captions continue to function only when used with Microsoft Teams, and applications must be updated to the latest SDKs. Standalone calling implementations, and implementations not updated to the latest SDKs by 30 Sep 2028, are no longer supported and stop functioning after that date.",
      "migration_path": "Review the [ACS Retirement and Breaking Change FAQ](https://aka.ms/acs-retirement-and-breaking-changes-guide). For calling services that continue with Microsoft Teams, update applications to the latest SDKs.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=557117",
      "extra_source_urls": [
        "https://aka.ms/acs-retirement-and-breaking-changes-guide"
      ],
      "vendor_ref": "557117",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-communication-services-standalone-services-retirement"
    },
    {
      "slug": "azure-functions-linux-consumption-plan-retirement",
      "title": "Azure Functions: Linux Consumption hosting plan retirement",
      "summary": "The Linux Consumption hosting plan of Azure Functions is retired on 30 Sep 2028. After that date there is no technical support and new Linux Consumption function apps cannot be created.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2025-09-26",
      "effective_date": "2028-09-30",
      "effective_precision": "day",
      "impact": "Retirement date for the Azure Functions Linux Consumption hosting plan: 30 Sep 2028. After that date, there is no technical support and new Linux Consumption function apps cannot be created. Microsoft asks customers to migrate to Flex Consumption by the retirement date to avoid service disruptions. Microsoft stated that after September 30, 2025 Linux Consumption gets no new features and is removed from the Azure portal, Visual Studio and VS Code, while it can still be managed through infrastructure as code and Azure CLI. Affected resources are App Service plans with Pricing Tier Dynamic (Y1: 0) and Operating System Linux.",
      "migration_path": "1. In the Azure portal, find App Service plans with Pricing Tier: Dynamic (Y1: 0) and Operating System: Linux.\n2. [Migrate to Flex Consumption](https://aka.ms/flexconsumption/migration) by the retirement date to avoid service disruptions.",
      "replacement": "Flex Consumption plan",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=499451",
      "extra_source_urls": [
        "https://aka.ms/flexconsumption/migration"
      ],
      "vendor_ref": "499451",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-linux-consumption-plan-retirement"
    },
    {
      "slug": "azure-aks-network-policy-manager-linux-end-of-support",
      "title": "Azure Kubernetes Service: Network Policy Manager on Linux nodes end of support",
      "summary": "End of support date for Azure Network Policy Manager (NPM) on Linux nodes in AKS: 30 Sep 2028. Microsoft directs AKS clusters running Linux nodes to migrate from NPM to Cilium Network Policy.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "feature",
      "type": "end_of_support",
      "announced_date": "2025-10-01",
      "effective_date": "2028-09-30",
      "effective_precision": "day",
      "impact": "Microsoft ends support for Azure Network Policy Manager (NPM) on Linux nodes in AKS on the end of support date. AKS clusters running Linux nodes with NPM are affected. Impacted resources can be listed with the Azure Resource Graph query linked in the source.",
      "migration_path": "1. Run the Azure Resource Graph query linked in the source to view impacted resources.\n2. [Migrate AKS clusters running Linux nodes from NPM to Cilium Network Policy](https://learn.microsoft.com/en-us/azure/aks/migrate-from-npm-to-cilium-network-policy) before the end of support date. The source describes Cilium Network Policy for AKS clusters using Azure CNI powered by Cilium.",
      "replacement": "Cilium Network Policy (AKS clusters using Azure CNI powered by Cilium)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=500268",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/aks/migrate-from-npm-to-cilium-network-policy",
        "https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request"
      ],
      "vendor_ref": "500268",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-network-policy-manager-linux-end-of-support"
    },
    {
      "slug": "azure-application-insights-url-ping-tests-retirement",
      "title": "Azure Monitor Application Insights: URL ping tests retirement",
      "summary": "Retirement date for URL ping tests in Application Insights: 30 Sep 2028. On that date, existing URL ping tests are removed from Application Insights resources. Standard tests replace them for single-step availability testing.",
      "cloud": "azure",
      "service": "Azure Monitor Application Insights",
      "service_slug": "application-insights",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2023-09-22",
      "effective_date": "2028-09-30",
      "effective_precision": "day",
      "impact": "On the retirement date, existing URL ping tests are removed from Application Insights resources. Microsoft directs customers to transition to standard tests before the retirement date to continue running single-step availability tests in Application Insights resources. The retirement was originally planned for September 30, 2026 and was extended by 24 months.",
      "migration_path": "1. Review the [pricing](https://azure.microsoft.com/pricing/details/monitor/) of standard tests.\n2. [Transition](https://learn.microsoft.com/en-us/azure/azure-monitor/app/availability#migrate-classic-url-ping-tests-to-standard-tests) from URL ping tests to standard tests before the retirement date.",
      "replacement": "Standard tests",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=transition-to-using-standard-tests-for-singlestep-availability-testing-in-azure-monitor-application-insights-by-30-september",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/previous-versions/azure/azure-monitor/app/monitor-web-app-availability",
        "https://azure.microsoft.com/pricing/details/monitor/#pricing",
        "https://learn.microsoft.com/en-us/azure/azure-monitor/app/availability#migrate-classic-url-ping-tests-to-standard-tests",
        "https://azure.microsoft.com/pricing/details/monitor/",
        "https://aka.ms/availabilitytestmigration"
      ],
      "vendor_ref": "transition-to-using-standard-tests-for-singlestep-availability-testing-in-azure-monitor-application-insights-by-30-september",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-application-insights-url-ping-tests-retirement"
    },
    {
      "slug": "gcp-cloud-run-ruby-3-4-retirement",
      "title": "Cloud Run: Ruby 3.4 decommission",
      "summary": "Decommission date for Ruby 3.4 on Cloud Run: 30 Sep 2028. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2028-09-30",
      "effective_precision": "day",
      "impact": "The decommission date of Ruby 3.4 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-ruby-3-4-retirement"
    },
    {
      "slug": "azure-functions-python-3-12-end-of-support",
      "title": "Azure Functions: Python 3.12 end of support",
      "summary": "End of support date for Python 3.12 on Azure Functions: Oct 2028. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-10-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Python 3.12 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "3.12"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@python:3.12",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-python-3-12-end-of-support"
    },
    {
      "slug": "azure-aks-kubernetes-1-37-lts-end-of-support",
      "title": "Azure Kubernetes Service: Kubernetes 1.37 LTS end of life",
      "summary": "LTS end of life date for Kubernetes 1.37 on Azure Kubernetes Service: Oct 2028. For clusters with long-term support enabled, support for the version continues only until that date. After it, those clusters must move to the next supported LTS version.",
      "cloud": "azure",
      "service": "Azure Kubernetes Service",
      "service_slug": "aks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-10-01",
      "effective_precision": "month",
      "impact": "After the LTS end of life date, long-term support for Kubernetes 1.37 ends. LTS-enabled clusters must then be upgraded to the next supported LTS version.\n\n- If a cluster is not upgraded, AKS upgrades it to the next supported LTS version through a platform-initiated upgrade. The cluster is not dropped to a community-supported version.\n- The LTS page places this after the 60-day grace period that follows the LTS end of life date. For the initial rollout, the grace period is the window through May 31, 2027, and no platform-initiated upgrade starts before June 1, 2027. After the initial rollout, every end-of-support event has a 60-day grace period before platform-initiated upgrades begin.\n- Platform-initiated upgrades apply to AKS in the Azure public cloud; availability in Azure Government and Azure operated by 21Vianet is announced separately.\n- A platform-initiated upgrade does not follow the maintenance window, does not stop for deprecated API usage and can override a Pod Disruption Budget.\n- The platform-initiated upgrade month in the AKS LTS release calendar is a planning estimate, not an exact upgrade date.",
      "migration_path": "1. List the versions AKS offers as upgrade targets with `az aks get-upgrades --resource-group <resource-group-name> --name <cluster-name> --output table`.\n2. Test the workloads against deprecated APIs and other breaking changes between the current and target versions.\n3. Upgrade to an offered higher LTS version with `az aks upgrade --resource-group <resource-group-name> --name <cluster-name> --kubernetes-version <lts-kubernetes-version>`. An LTS cluster can skip minor versions when the upgrade satisfies version-skew requirements and validation checks. See [Long-term support for AKS versions](https://learn.microsoft.com/en-us/azure/aks/long-term-support).\n4. If the cluster is already past its LTS end of life date, skipping minor versions is conditional: the target must be listed by AKS and satisfy validation checks. AKS allows this upgrade but treats it as an unsupported recovery path.\n5. If no target is available for an unsupported cluster, create a new cluster with a supported version and migrate the workloads.\n6. To leave LTS instead, move the cluster to the Free or Standard tier and select the KubernetesOfficial support plan. This is possible while the cluster's Kubernetes version is still in community support. After that version exits community support, first upgrade the cluster to a community-supported version.",
      "replacement": "Next supported AKS LTS version",
      "affected_versions": [
        "1.37"
      ],
      "source_url": "https://learn.microsoft.com/azure/aks/supported-kubernetes-versions",
      "extra_source_urls": [
        "https://endoflife.date/azure-kubernetes-service"
      ],
      "vendor_ref": "azure-kubernetes-service@1.37",
      "last_checked_at": "2026-11-12T09:55:33.220Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-aks-kubernetes-1-37-lts-end-of-support"
    },
    {
      "slug": "gcp-gke-kubernetes-1-37-extended-support-end-of-support",
      "title": "Google Kubernetes Engine: Kubernetes 1.37 end of extended support",
      "summary": "End of extended support date for GKE Kubernetes 1.37: 22 Oct 2028. From that date the minor version receives no security patches, and GKE upgrades Extended channel clusters still running it to the next minor version.",
      "cloud": "gcp",
      "service": "Google Kubernetes Engine",
      "service_slug": "gke",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-10-22",
      "effective_precision": "day",
      "impact": "At the end of extended support, GKE does not provide any patches for security fixes, and the minor version is considered unsupported. GKE upgrades clusters still running it to the next minor version.\n\n- The upgrade happens regardless of the cluster's use of deprecated features or APIs.\n- Maintenance exclusions cannot be configured past this date, except as a temporary, emergency measure with the \"No upgrades\" scope.\n- That exclusion can delay the upgrade for up to 90 days after the end of support date. Google does not recommend it.\n- Dates in the GKE release schedule are updated monthly and subject to change.",
      "migration_path": "1. Google does not recommend enrolling a cluster in the Extended channel without plans to move to the next minor version, because GKE eventually upgrades the cluster to newer minor versions.\n2. Around 2 months before the end of extended support, GKE begins upgrading clusters in the Extended channel to the next minor version, unless the cluster is using deprecated features or APIs.\n3. Maintenance exclusions can prevent minor version upgrades until the end of extended support. A temporary, emergency exclusion with the \"No upgrades\" scope can delay the upgrade for up to 90 days after the end of support date. After that exclusion expires, GKE upgrades the cluster.\n4. At the end of extended support, GKE upgrades all clusters still running the minor version, regardless of blocking issues. See [GKE minor version lifecycle](https://docs.cloud.google.com/kubernetes-engine/versioning#lifecycle).",
      "replacement": null,
      "affected_versions": [
        "1.37"
      ],
      "source_url": "https://cloud.google.com/kubernetes-engine/docs/release-schedule",
      "extra_source_urls": [],
      "vendor_ref": "gke@1.37",
      "last_checked_at": "2026-11-12T09:55:57.551Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-gke-kubernetes-1-37-extended-support-end-of-support"
    },
    {
      "slug": "aws-lambda-python3-12-end-of-support",
      "title": "AWS Lambda: Python 3.12 (python3.12) deprecation",
      "summary": "Deprecation date for Python 3.12 (python3.12) on AWS Lambda: 31 Oct 2028. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-10-31",
      "effective_precision": "day",
      "impact": "After deprecation (31 Oct 2028), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 30 Nov 2028, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 10 Jan 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 10 Jan 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "python3.12"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "python3.12",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-python3-12-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-node-24-retirement",
      "title": "Cloud Run: Node.js 24 decommission",
      "summary": "Decommission date for Node.js 24 on Cloud Run: 31 Oct 2028. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2028-10-31",
      "effective_precision": "day",
      "impact": "The decommission date of Node.js 24 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-node-24-retirement"
    },
    {
      "slug": "gcp-compute-engine-cos-133-lts-image-end-of-support",
      "title": "Compute Engine: COS 133 LTS image end of support",
      "summary": "EOS and image deprecation date for the COS 133 LTS public image on Compute Engine: Nov 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of COS 133 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "COS 133 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "cos-133-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-cos-133-lts-image-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-7-9-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 7.9 end of extended support",
      "summary": "End of extended support date for Elasticsearch 7.9 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2028. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2028 is the end of extended support date for Elasticsearch 7.9 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 7.9"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 7.9",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-7-9-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-11-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.11 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.11 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2028. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2028 is the end of extended support date for OpenSearch 2.11 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.11"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.11",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-11-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-13-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.13 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.13 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2028. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2028 is the end of extended support date for OpenSearch 2.13 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.13"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.13",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-13-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-15-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.15 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.15 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2028. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2028 is the end of extended support date for OpenSearch 2.15 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.15"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.15",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-15-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-17-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.17 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.17 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2028. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2028 is the end of extended support date for OpenSearch 2.17 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.17"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.17",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-17-extended-support-end-of-support"
    },
    {
      "slug": "azure-postgresql-16-end-of-support",
      "title": "Azure Database for PostgreSQL: PostgreSQL 16 end of standard support",
      "summary": "Azure Standard Support End Date for PostgreSQL 16 on Azure Database for PostgreSQL: 9 Nov 2028. Once the Azure Standard Support period ends, eligible servers still running the version are automatically enrolled in extended support.",
      "cloud": "azure",
      "service": "Azure Database for PostgreSQL",
      "service_slug": "postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-09",
      "effective_precision": "day",
      "impact": "Once the Azure Standard Support period ends, an eligible server still running PostgreSQL 16 is automatically enrolled in extended support. The eligible versions table lists PostgreSQL 11, 12, 13 and 14.\n\n- Extended support provides security patches, critical bug fixes and technical support for up to three extra years. It does not include new features, performance enhancements or support for minor version upgrades.\n- Charges apply after any applicable grace period unless the server is upgraded to a supported version, and only to servers in a Succeeded (running) state. A one-month grace period is provided for versions 11, 12 and 13. A server that regional capacity constraints prevent from upgrading might be temporarily excluded from billing.\n- The version policy page lists restrictions that apply after the retirement date of a version, without stating whether that date is 9 Nov 2028: new servers cannot be created on a retired version, while point-in-time recoveries and read replicas of existing servers remain possible.\n- The same page says that when the community retires a version, Azure stops applying bug or security patches to the database engine. The extended support page lists security patches and critical bug fixes as part of extended support.",
      "migration_path": "1. Run the upgrade validation checks in the Azure portal or with the Azure CLI. See [Run upgrade validation checks](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/how-to-run-upgrade-validation-checks).\n2. Resolve any blocking issues the checks report, then rerun validation.\n3. Ensure the server has at least 10-20% free storage available before starting the upgrade.\n4. If the server uses geo-replication, delete the read replica (including any cascading read replica) before upgrading the primary server. The replica can be re-created after the upgrade.\n5. Run an in-place major version upgrade to a PostgreSQL version that Azure currently supports. The service can skip versions and upgrade directly to a later version. Servers that use TimescaleDB are limited to specific source and target version combinations, and an upgrade from PostgreSQL 11 first requires SCRAM authentication to be configured. Once the server runs a supported version, extended support charges no longer apply. See [Major version upgrades](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-major-version-upgrade).\n6. Plan for the fact that there is no automated way to revert after a successful upgrade. A point-in-time recovery to a time before the upgrade restores the previous version on a new server.",
      "replacement": null,
      "affected_versions": [
        "16"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-postgresql"
      ],
      "vendor_ref": "azure-database-for-postgresql@16",
      "last_checked_at": "2026-11-12T09:55:36.471Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-postgresql-16-end-of-support"
    },
    {
      "slug": "aws-lambda-dotnet10-end-of-support",
      "title": "AWS Lambda: .NET 10 (dotnet10) deprecation",
      "summary": "Deprecation date for .NET 10 (dotnet10) on AWS Lambda: 14 Nov 2028. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-14",
      "effective_precision": "day",
      "impact": "After deprecation (14 Nov 2028), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 14 Dec 2028, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 15 Jan 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 15 Jan 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "dotnet10"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "dotnet10",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-dotnet10-end-of-support"
    },
    {
      "slug": "azure-app-service-dotnet-10-end-of-support",
      "title": "Azure App Service: .NET 10 end of support",
      "summary": "End of support date for .NET 10 on Azure App Service: 14 Nov 2028. Apps that use this version continue to run unchanged, but App Service can't provide security patches or related customer support for it past that date.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-14",
      "effective_precision": "day",
      "impact": "After 14 Nov 2028, apps that use .NET 10 continue to run unchanged, but App Service can't provide security patches or related customer support for that runtime version.\n\n- An app on an unsupported language version must be upgraded to a supported version before it can get App Service support.\n- App Service sends reminder notifications about end-of-support dates to subscription owners.\n- Contributors, readers, or other roles don't directly receive notifications unless they opt in through Service Health Alerts.\n- For Java, the page adds that developers who use a supported Java runtime that is retired receive a deprecation notice at least six months before the runtime is retired.",
      "migration_path": "1. Find the language version the app uses. The [language runtime support policy](https://learn.microsoft.com/en-us/azure/app-service/language-support-policy) links \"Show language version\" resources for .NET, Java, Node, Python and PHP.\n2. Choose a supported version of .NET. The same page links the support timeline of each language community.\n3. Set the new language version for the app. The same page links \"Set language versions\" resources for .NET, Java, Node, Python and PHP.",
      "replacement": null,
      "affected_versions": [
        "10"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy",
      "extra_source_urls": [
        "https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core"
      ],
      "vendor_ref": "appservice@dotnet:10",
      "last_checked_at": "2026-11-12T09:56:00.082Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-dotnet-10-end-of-support"
    },
    {
      "slug": "azure-functions-dotnet-10-end-of-support",
      "title": "Azure Functions: .NET 10 end of support",
      "summary": "End of support date for .NET 10 on Azure Functions: 14 Nov 2028. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-14",
      "effective_precision": "day",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on .NET 10 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "10"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@dotnet:10",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-dotnet-10-end-of-support"
    },
    {
      "slug": "azure-functions-powershell-7-6-end-of-support",
      "title": "Azure Functions: PowerShell 7.6 end of support",
      "summary": "End of support date for PowerShell 7.6 on Azure Functions: 14 Nov 2028. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-11-14",
      "effective_precision": "day",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on PowerShell 7.6 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "7.6"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@powershell:7.6",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-powershell-7-6-end-of-support"
    },
    {
      "slug": "azure-batch-av2-f-fs-fsv2-g-gs-lsv2-series-vm-retirement",
      "title": "Azure Batch: Av2, F, Fs, Fsv2, G, Gs and Lsv2-series VM retirement",
      "summary": "Retirement date for the Av2, F, Fs, Fsv2, G, Gs and Lsv2 virtual machine series in Azure Batch pools: 15 Nov 2028. After that date, pools on these series cannot be created or scaled out and may be resized to zero nodes.",
      "cloud": "azure",
      "service": "Azure Batch",
      "service_slug": "batch",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-06-11",
      "effective_date": "2028-11-15",
      "effective_precision": "day",
      "impact": "The retirement affects Azure Batch pools that rely on the Av2-series, F-series, Fs-series, Fsv2-series, G-series, Gs-series and Lsv2-series. After the retirement date, new Batch pools using these VM series cannot be created, existing pools cannot scale out, and pools may be forcibly resized to zero nodes. Remaining VMs are stopped/deallocated and are no longer covered by the SLA. Affected pools may become unusable.",
      "migration_path": "1. Migrate Batch pools to supported VM families before the retirement date.\n2. Pick a replacement series: Dsv5/Ddsv5 or Dasv5/Dadsv5 for Av2; Dlsv6/Dldsv6, Falsv6 or Dsv5/Ddsv5 for F, Fs and Fsv2; Lsv3/Lasv3 or Easv5/Edsv5 for G and Gs; Lsv3/Lasv3 for Lsv2.\n3. Either scale the pool to zero and update the VM size using the Batch API (07-01-24 or later), or create a new pool with supported VM sizes and migrate the workloads.\n4. Check Azure VM pricing, because VM pricing may change after migration.",
      "replacement": "Dsv5/Ddsv5, Dasv5/Dadsv5, Dlsv6/Dldsv6, Falsv6, Lsv3/Lasv3 or Easv5/Edsv5 series, depending on the retired series",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=564774",
      "extra_source_urls": [],
      "vendor_ref": "564774",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-batch-av2-f-fs-fsv2-g-gs-lsv2-series-vm-retirement"
    },
    {
      "slug": "azure-virtual-machines-f-fs-fsv2-lsv2-g-gs-av2-amv2-b-series-retirement",
      "title": "Azure Virtual Machines: F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, B series retirement",
      "summary": "Retirement date for the F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B series of Azure Virtual Machines: 15 Nov 2028. After that date these VMs can no longer be used or purchased.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2025-10-15",
      "effective_date": "2028-11-15",
      "effective_precision": "day",
      "impact": "After the retirement date, the F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B series VMs can no longer be used or purchased. Three-year reserved instances for these VMs can no longer be purchased or renewed starting on November 15th, 2025, and one-year reserved VM instances starting July 1, 2026 (previously November 15, 2027, [details](https://azure.microsoft.com/en-us/updates?id=560948)). An existing three-year reserved instance contract keeps its benefit for the remainder of the contract. After that, the VMs are billed at pay-as-you-go rates.",
      "migration_path": "1. Migrate workloads on these series to a newer VM series, following the [migration guide](https://aka.ms/VirtualMachinesMigrationGuide_Sept2025).\n2. Review your [current reserved instance orders](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/manage-reserved-vm-instance) to identify impacted VMs and their expiration dates.\n3. For pricing details, see the [VM pricing pages](https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux-previous/) and the [pricing calculator](https://azure.microsoft.com/en-us/pricing/calculator/).",
      "replacement": null,
      "affected_versions": [
        "F",
        "Fs",
        "Fsv2",
        "Lsv2",
        "G",
        "Gs",
        "Av2",
        "Amv2",
        "B"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=500682",
      "extra_source_urls": [
        "https://aka.ms/VirtualMachinesMigrationGuide_Sept2025",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/prepay-reserved-vm-instances?toc=%2Fazure%2Fcost-management-billing%2Freservations%2Ftoc.json",
        "https://azure.microsoft.com/en-us/updates?id=560948",
        "https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/manage-reserved-vm-instance",
        "https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux-previous/",
        "https://azure.microsoft.com/en-us/pricing/calculator/",
        "https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request"
      ],
      "vendor_ref": "500682",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-f-fs-fsv2-lsv2-g-gs-av2-amv2-b-series-retirement"
    },
    {
      "slug": "aws-eks-kubernetes-1-37-extended-support-end-of-support",
      "title": "Amazon EKS: Kubernetes 1.37 end of extended support",
      "summary": "End of extended support date for Kubernetes 1.37 on Amazon EKS: 1 Dec 2028. On that date, new clusters can no longer be created with this version, and Amazon EKS automatically updates control planes still on it at any time afterward.",
      "cloud": "aws",
      "service": "Amazon EKS",
      "service_slug": "eks",
      "category": "kubernetes",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-12-01",
      "effective_precision": "day",
      "impact": "On the end of extended support date, new Amazon EKS clusters can no longer be created with Kubernetes 1.37. Amazon EKS automatically updates existing control planes to the earliest supported version, at any time after that date.\n\n- Amazon EKS gives no specific time frame and sends no notification before the update.\n- The auto-upgrade includes only the Kubernetes control plane. Self-managed nodes and EKS managed node groups remain on the previous version.\n- EKS Auto Mode nodes may update automatically.\n- Fargate nodes and hybrid nodes are not upgraded with the control plane.\n- Clusters that were automatically upgraded at the end of extended support cannot be rolled back.",
      "migration_path": "1. Use Amazon EKS upgrade insights to identify issues before the upgrade.\n2. Before updating the control plane, make sure the Kubernetes minor version of the managed nodes and Fargate nodes is the same as the control plane version.\n3. Proactively update the control plane without relying on the Amazon EKS automatic update process, one minor version at a time, following [Update existing cluster to new Kubernetes version](https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html).\n4. After the cluster update is complete, update the nodes to the same Kubernetes minor version as the cluster. Then update the Amazon VPC CNI plugin for Kubernetes, CoreDNS, and kube-proxy add-ons.\n5. If Amazon EKS updated the control plane automatically, manually update cluster add-ons and Amazon EC2 nodes.",
      "replacement": null,
      "affected_versions": [
        "1.37"
      ],
      "source_url": "https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-eks"
      ],
      "vendor_ref": "amazon-eks@1.37",
      "last_checked_at": "2026-11-12T09:55:34.831Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-eks-kubernetes-1-37-extended-support-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-15-sp6-for-sap-image-end-of-support",
      "title": "Compute Engine: SLES 15 SP6 for SAP image end of support",
      "summary": "EOS and image deprecation date for the SLES 15 SP6 for SAP public image on Compute Engine: Dec 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-12-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 15 SP6 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 15 SP6 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-15-sp6-sap",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-15-sp6-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-15-sp6-image-end-of-support",
      "title": "Compute Engine: SLES 15 SP6 image end of support",
      "summary": "EOS and image deprecation date for the SLES 15 SP6 public image on Compute Engine: Dec 2028. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2028-12-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 15 SP6 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 15 SP6"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-15",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-15-sp6-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-windows-server-2019-image-end-of-support",
      "title": "Compute Engine: Windows Server 2019 image end of support",
      "summary": "EOS and image deprecation date for the Windows Server 2019 public image on Compute Engine: 9 Jan 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-01-09",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Windows Server 2019 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Windows Server 2019"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "windows-2019",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-windows-server-2019-image-end-of-support"
    },
    {
      "slug": "multi-windows-server-2019-end-of-support",
      "title": "Windows Server 2019 end of support",
      "summary": "End of support for Windows Server 2019: 9 Jan 2029. Once a release reaches the end of support, security updates and bulletins end.",
      "cloud": "multi",
      "service": "Windows Server",
      "service_slug": "windows-server",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-01-09",
      "effective_precision": "day",
      "impact": "Windows Server Long Term Servicing Channel releases have a minimum of 10 years of support: five years of mainstream support and five years of extended support, which includes regular security updates. endoflife.date states that each Semi-Annual Channel release is supported for 18 months from the initial release, and that each Annual Channel release has 18 months of mainstream support plus 6 months of extended support. Once a release reaches the end of support, security updates and bulletins end, which Microsoft states can cause security or compliance issues.\n\n- endoflife.date states that for some releases, customers have the option to purchase Extended Security Updates. See [Lifecycle FAQ - Extended Security Updates](https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates).\n- Extended Security Updates do not include new features, customer-requested nonsecurity hotfixes, or design change requests.",
      "migration_path": "1. Choose an upgrade method with [Plan your Windows Server upgrade](https://learn.microsoft.com/en-us/windows-server/get-started/install-upgrade-migrate): in-place upgrade, clean install, migration, or cluster rolling upgrade.\n2. Check the [supported paths table](https://learn.microsoft.com/en-us/windows-server/get-started/install-upgrade-migrate#supported-in-place-upgrade-paths-by-version) and the [role and feature migration matrix](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-migrate-roles-features) for your configuration.\n3. Get a valid product key and activation method for the target version. Each Windows Server upgrade requires a separate license.\n4. Back up your system and important files before the in-place upgrade, clean install, or migration.\n5. For an in-place upgrade, follow [Perform an in-place upgrade of Windows Server](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-in-place).",
      "replacement": null,
      "affected_versions": [
        "2019"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/windows-server-2019",
      "extra_source_urls": [
        "https://endoflife.date/windows-server"
      ],
      "vendor_ref": "windows-server@2019",
      "last_checked_at": "2026-11-12T09:55:50.558Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-windows-server-2019-end-of-support"
    },
    {
      "slug": "aws-elasticache-redis-oss-4-extended-support-end-of-support",
      "title": "Amazon ElastiCache for Redis OSS: Redis OSS 4 end of extended support",
      "summary": "End of Extended Support and version end of life for Redis OSS 4 on Amazon ElastiCache: 31 Jan 2029. After that date, ElastiCache attempts to upgrade caches still running it to a newer engine version under standard support.",
      "cloud": "aws",
      "service": "Amazon ElastiCache for Redis OSS",
      "service_slug": "elasticache-redis",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-01-31",
      "effective_precision": "day",
      "impact": "31 Jan 2029 is the end of Extended Support and the version end of life for Redis OSS 4. If the engine is not upgraded, after that date Amazon ElastiCache attempts to upgrade it to a newer engine version that is supported under standard support. If that upgrade fails, AWS reserves the right to delete the cache, and states that it preserves the data from that engine before doing so.",
      "migration_path": "1. Upgrade the engine to a newer engine version before the end of Extended Support date. AWS lists this as the customer's responsibility.\n2. On a node-based cluster, start the upgrade by modifying the cluster or replication group and specifying a new engine version. See [Modifying a replication group](https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/Replication.Modify.html).\n3. Test the new version with your application before deploying it in production.\n4. AWS states that some existing ElastiCache for Redis OSS engines can also be upgraded to a Valkey engine.",
      "replacement": null,
      "affected_versions": [
        "4"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/engine-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-elasticache-redis"
      ],
      "vendor_ref": "amazon-elasticache-redis@4",
      "last_checked_at": "2026-11-12T09:55:41.392Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-elasticache-redis-oss-4-extended-support-end-of-support"
    },
    {
      "slug": "aws-elasticache-redis-oss-5-extended-support-end-of-support",
      "title": "Amazon ElastiCache for Redis OSS: Redis OSS 5 end of extended support",
      "summary": "End of Extended Support and version end of life for Redis OSS 5 on Amazon ElastiCache: 31 Jan 2029. After that date, ElastiCache attempts to upgrade caches still running it to a newer engine version under standard support.",
      "cloud": "aws",
      "service": "Amazon ElastiCache for Redis OSS",
      "service_slug": "elasticache-redis",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-01-31",
      "effective_precision": "day",
      "impact": "31 Jan 2029 is the end of Extended Support and the version end of life for Redis OSS 5. If the engine is not upgraded, after that date Amazon ElastiCache attempts to upgrade it to a newer engine version that is supported under standard support. If that upgrade fails, AWS reserves the right to delete the cache, and states that it preserves the data from that engine before doing so.",
      "migration_path": "1. Upgrade the engine to a newer engine version before the end of Extended Support date. AWS lists this as the customer's responsibility.\n2. On a node-based cluster, start the upgrade by modifying the cluster or replication group and specifying a new engine version. See [Modifying a replication group](https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/Replication.Modify.html).\n3. Test the new version with your application before deploying it in production.\n4. AWS states that some existing ElastiCache for Redis OSS engines can also be upgraded to a Valkey engine.",
      "replacement": null,
      "affected_versions": [
        "5"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/engine-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-elasticache-redis"
      ],
      "vendor_ref": "amazon-elasticache-redis@5",
      "last_checked_at": "2026-11-12T09:55:41.392Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-elasticache-redis-oss-5-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-13-extended-support-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 13 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for PostgreSQL 13 on Amazon Aurora PostgreSQL: 28 Feb 2029. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-02-28",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 28 Feb 2029. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- New major PostgreSQL versions might contain database changes that are not backward-compatible with existing applications.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "13"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@13",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-13-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-16-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 16 end of standard support",
      "summary": "Aurora end of standard support date for PostgreSQL 16 on Amazon Aurora PostgreSQL: 28 Feb 2029. After that date, a database can keep running this major version under RDS Extended Support, for an additional cost.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-02-28",
      "effective_precision": "day",
      "impact": "RDS Extended Support allows a database to keep running this major version after 28 Feb 2029, for an [additional cost](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html).\n\n- Aurora automatically enrolls a DB instance after that date if RDS Extended Support was enabled at creation or restoration.\n- It provides security updates for critical and high CVEs, bug fixes for critical issues, and support cases.\n- Charges apply only to certain minor versions. The [release calendar](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html) lists the eligible minor versions for each major version.\n- Enrollment can be changed at any time, at the cluster level. Disabling it after that date upgrades the instance or cluster automatically to the next supported major version.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "16"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@16",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-16-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-13-extended-support-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 13 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for PostgreSQL 13 on Amazon RDS for PostgreSQL: 28 Feb 2029. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-02-28",
      "effective_precision": "day",
      "impact": "After the RDS end of Extended Support date (28 Feb 2029), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 13.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "13"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@13",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-13-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16 end of standard support",
      "summary": "RDS end of standard support date for PostgreSQL 16 on Amazon RDS for PostgreSQL: 28 Feb 2029. A database can keep running this version past that date under RDS Extended Support, for an additional cost, until the RDS end of Extended Support date.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-02-28",
      "effective_precision": "day",
      "impact": "A database can continue running PostgreSQL 16 past the RDS end of standard support date under RDS Extended Support, for an additional cost (see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html)), until the RDS end of Extended Support date.\n\n- If RDS Extended Support was enabled when the DB instance was created or restored, Amazon RDS enrolls it automatically after the RDS end of standard support date, with no change to the database engine, uptime or performance.\n- RDS Extended Support provides security updates for critical and high CVEs, bug fixes and patches for critical issues, and the ability to open support cases.\n- If enrollment is disabled for a DB instance or DB cluster that is already past its standard support end date, it automatically upgrades to the next supported major version.\n- After the RDS end of Extended Support date, Amazon RDS automatically upgrades databases not yet on a supported major version.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. To stay on PostgreSQL 16 under RDS Extended Support, the enrollment status of an existing DB instance or DB cluster can be changed with the EngineLifecycleSupport parameter using the AWS CLI or RDS API. For Multi-AZ DB clusters, modify the setting at the cluster level. RDS Extended Support has an additional cost, see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "replacement": null,
      "affected_versions": [
        "16"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@16",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-end-of-support"
    },
    {
      "slug": "aws-documentdb-engine-version-3-6-extended-support-end-of-support",
      "title": "Amazon DocumentDB: engine version 3.6 end of extended support",
      "summary": "End of Extended Support date for engine version 3.6 on Amazon DocumentDB: 30 Mar 2029. After that date, Amazon DocumentDB upgrades the engine version of clusters that have not moved to a supported version.",
      "cloud": "aws",
      "service": "Amazon DocumentDB",
      "service_slug": "documentdb",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-03-30",
      "effective_precision": "day",
      "impact": "Amazon DocumentDB Extended Support lets clusters keep running an engine version for an additional cost, for up to 3 years past its end of standard support date. After that time, Amazon DocumentDB upgrades the engine version of any cluster that has not been upgraded to a supported version. Separately, AWS states that Amazon DocumentDB upgrades a cluster to the last engine version released before the end of the Extended Support date, if the cluster is not already on that version, and that this upgrade period does not occur until after the standard support date for that engine version. The support dates table lists a start date for year 1 pricing and a start date for year 3 pricing, see [Amazon DocumentDB engine version support dates](https://docs.aws.amazon.com/documentdb/latest/devguide/docdb-version-support-dates.html) and [Extended Support charges](https://docs.aws.amazon.com/documentdb/latest/devguide/support-charges.html).",
      "migration_path": "1. Upgrade each enrolled cluster to a newer engine version that is still under standard support. For a major engine version, AWS documents two routes: [Upgrading a major engine version](https://docs.aws.amazon.com/documentdb/latest/devguide/docdb-mvu.html) and [Upgrading using AWS DMS](https://docs.aws.amazon.com/documentdb/latest/devguide/docdb-migration.versions.html).\n2. Plan for downtime with the in-place major version upgrade: the cluster is unavailable during the upgrade, and a downgrade to a previous version is not possible afterwards.\n3. Enrollment in Extended Support can be ended at any time. It ends the day the upgrade completes.\n4. Check the supported versions and their dates in [Amazon DocumentDB engine version support dates](https://docs.aws.amazon.com/documentdb/latest/devguide/docdb-version-support-dates.html).",
      "replacement": null,
      "affected_versions": [
        "3.6"
      ],
      "source_url": "https://docs.aws.amazon.com/documentdb/latest/devguide/docdb-version-support-dates.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-documentdb"
      ],
      "vendor_ref": "amazon-documentdb@3.6",
      "last_checked_at": "2026-11-12T09:55:44.202Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-documentdb-engine-version-3-6-extended-support-end-of-support"
    },
    {
      "slug": "azure-ai-document-intelligence-v3-0-api-retirement",
      "title": "Azure AI Document Intelligence: v3.0 API retirement",
      "summary": "Retirement date for the Azure Document Intelligence v3.0 API: 30 Mar 2029. After that date the v3.0 API is no longer supported and becomes unusable.",
      "cloud": "azure",
      "service": "Azure AI Document Intelligence",
      "service_slug": "ai-document-intelligence",
      "category": "api_sdk",
      "type": "retirement",
      "announced_date": "2026-05-06",
      "effective_date": "2029-03-30",
      "effective_precision": "day",
      "impact": "After the retirement date, the Azure Document Intelligence v3.0 API is no longer supported and becomes unusable. Microsoft asks customers to migrate to v4.0, the latest generally available API version, by the retirement date.",
      "migration_path": "Migrate to the latest generally available Azure Document Intelligence API version, v4.0, by the retirement date.",
      "replacement": "Azure Document Intelligence API v4.0",
      "affected_versions": [
        "3.0"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=561176",
      "extra_source_urls": [],
      "vendor_ref": "561176",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-document-intelligence-v3-0-api-retirement"
    },
    {
      "slug": "aws-lambda-ruby4-0-end-of-support",
      "title": "AWS Lambda: Ruby 4.0 (ruby4.0) deprecation",
      "summary": "Deprecation date for Ruby 4.0 (ruby4.0) on AWS Lambda: 31 Mar 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-03-31",
      "effective_precision": "day",
      "impact": "After deprecation (31 Mar 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 30 Apr 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 May 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 May 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "ruby4.0"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "ruby4.0",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-ruby4-0-end-of-support"
    },
    {
      "slug": "azure-ai-language-eight-features-retirement",
      "title": "Azure AI Language: retirement of eight features",
      "summary": "Retirement date for eight Azure AI Language features, including Key Phrase Extraction, Sentiment Analysis, CLU, Custom Question Answering and Summarization: 31 Mar 2029. After that date, requests to these features return errors.",
      "cloud": "azure",
      "service": "Azure AI Language",
      "service_slug": "ai-language",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-04-01",
      "effective_date": "2029-03-31",
      "effective_precision": "day",
      "impact": "Eight Azure AI Language features are retired on the retirement date: Key Phrase Extraction, Sentiment Analysis and Opinion Mining, Custom Text Classification, Conversational Language Understanding (CLU), Custom Question Answering (CQA), Orchestration Workflow, Summarization (extractive and abstractive, for documents and conversations), and Entity Linking. After the retirement date, requests to these features return errors. The related authoring and runtime capabilities in Language Studio, Microsoft Foundry, and the REST APIs are no longer available. Other Azure AI Language features, including Language Detection, PII Detection, Text Analytics for Health, Prebuilt NER, and Custom NER, continue to be supported.",
      "migration_path": "Plan migrations ahead of the retirement date using supported alternatives in Microsoft Foundry.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=557394",
      "extra_source_urls": [],
      "vendor_ref": "557394",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-ai-language-eight-features-retirement"
    },
    {
      "slug": "azure-cosmos-db-for-postgresql-retirement",
      "title": "Azure Cosmos DB for PostgreSQL retirement",
      "summary": "Retirement date for Azure Cosmos DB for PostgreSQL: 31 Mar 2029. Customers need to migrate to Azure Database for PostgreSQL Elastic Cluster by that date.",
      "cloud": "azure",
      "service": "Azure Cosmos DB for PostgreSQL",
      "service_slug": "cosmos-db-for-postgresql",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-03-30",
      "effective_date": "2029-03-31",
      "effective_precision": "day",
      "impact": "Azure Cosmos DB for PostgreSQL is retired on 31 Mar 2029. Customers with existing Azure Cosmos DB for PostgreSQL databases need to migrate to Azure Database for PostgreSQL Elastic Cluster by that date. Microsoft states that Elastic Cluster delivers the same distributed PostgreSQL capabilities, with full feature parity built on the Citus extension.",
      "migration_path": "1. Review your current Azure Cosmos DB for PostgreSQL clusters, versions, and any required extensions.\n2. Provision an Azure Database for PostgreSQL Elastic Cluster destination environment.\n3. Use the provided migration tool to move schema and data, validate application behavior, and complete cutover.\n4. Decommission your source clusters after successful validation of your new environment.",
      "replacement": "Azure Database for PostgreSQL Elastic Cluster",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=556085",
      "extra_source_urls": [],
      "vendor_ref": "556085",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-cosmos-db-for-postgresql-retirement"
    },
    {
      "slug": "azure-cosmos-db-synapse-link-for-nosql-retirement",
      "title": "Azure Cosmos DB: Azure Synapse Link for NoSQL retirement",
      "summary": "End of life date for Azure Synapse Link for Azure Cosmos DB NoSQL: 31 Mar 2029. Existing customers remain fully supported until that date.",
      "cloud": "azure",
      "service": "Azure Cosmos DB",
      "service_slug": "cosmos-db",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-06-10",
      "effective_date": "2029-03-31",
      "effective_precision": "day",
      "impact": "Azure Synapse Link for Azure Cosmos DB NoSQL reaches end of life on 31 Mar 2029, and existing customers remain fully supported until then. Since March 31, 2026, new Azure Cosmos DB NoSQL accounts can no longer enable Azure Synapse Link. Azure Cosmos DB NoSQL accounts that have Azure Synapse Link enabled are affected.",
      "migration_path": "1. Migrate to Mirroring for Microsoft Fabric, the solution Microsoft recommends for Cosmos DB analytics workloads.\n2. Follow the migration guidance at [Cosmos Mirror Synapse Migration](https://aka.ms/CosmosMirrorSynapseMigration).\n3. For questions about the retirement or the migration path, contact your Microsoft account manager or cosmosdbsynapselink@microsoft.com.",
      "replacement": "Mirroring for Microsoft Fabric",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=558560",
      "extra_source_urls": [
        "https://aka.ms/CosmosMirrorSynapseMigration"
      ],
      "vendor_ref": "558560",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-cosmos-db-synapse-link-for-nosql-retirement"
    },
    {
      "slug": "azure-mysql-5-7-extended-support-end-of-support",
      "title": "Azure Database for MySQL: MySQL 5.7 end of extended support",
      "summary": "Azure Extended Support End Date for MySQL 5.7 on Azure Database for MySQL: 31 Mar 2029. After the extended support period ends, no further security or support updates are provided for the retired version.",
      "cloud": "azure",
      "service": "Azure Database for MySQL",
      "service_slug": "mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-03-31",
      "effective_precision": "day",
      "impact": "After the extended support period ends, no further security or support updates are provided for MySQL 5.7 on servers still running it.\n\n- Azure cannot patch the retired database engine, and support for engine-related issues is no longer available.\n- Azure continues periodic maintenance and patching for the host, OS, containers and other service-related components.\n- New database servers cannot be created for the retired version. Point-in-time recoveries and read replicas for existing servers remain possible.\n- If an engine vulnerability in the retired version seriously threatens the service, Azure might stop the compute node of the server and ask for an upgrade before bringing it online.\n- Uptime SLAs apply only to service-related issues, not to downtime caused by database engine bugs.",
      "migration_path": "1. Upgrade to a supported major version. Upgrade read replicas that use an older MySQL version before upgrading the primary server.\n2. Check schema compatibility with the target version using the Validate feature in the Azure portal. Validation locks tables, and the page directs large-scale production environments to Oracle's client-side upgrade checker tool. Verify deprecated sql_mode values and remove or deselect them in the Server Parameters pane before upgrading, to avoid deployment failure.\n3. Ensure there are no active or pending XA transactions on the database. Ongoing XA transactions can cause the upgrade to fail.\n4. Trigger an on-demand backup before the major version upgrade of a production server.\n5. Perform the upgrade first on a restored server copy rather than on production directly.\n6. In the Azure portal, open the server, and on the Overview page select Upgrade. The major version upgrade is irreversible. Burstable SKU servers use a separate workflow that first upgrades the compute tier to a General-Purpose SKU. See [Major version upgrade in Azure Database for MySQL](https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-upgrade).",
      "replacement": null,
      "affected_versions": [
        "5.7"
      ],
      "source_url": "https://learn.microsoft.com/azure/mysql/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-mysql"
      ],
      "vendor_ref": "azure-database-for-mysql@5.7",
      "last_checked_at": "2026-11-12T09:55:37.239Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-mysql-5-7-extended-support-end-of-support"
    },
    {
      "slug": "azure-vpn-gateway-manually-registered-vpn-clients-gov-21vianet-retirement",
      "title": "Azure VPN Gateway: manually registered VPN clients retirement (Gov, 21Vianet)",
      "summary": "Retirement date for manually registered Azure VPN clients in Azure Government and Microsoft Azure operated by 21Vianet: 31 Mar 2029. After that date, only Microsoft-registered VPN clients are supported.",
      "cloud": "azure",
      "service": "Azure VPN Gateway",
      "service_slug": "vpn-gateway",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-03-31",
      "effective_date": "2029-03-31",
      "effective_precision": "day",
      "impact": "On 31 Mar 2029, manually registered Azure VPN clients for point-to-site connections with Microsoft Entra ID authentication are retired in the Azure Government and Microsoft Azure operated by 21Vianet clouds. After that date, only Microsoft-registered VPN clients are supported.",
      "migration_path": "[Migrate manually registered Azure VPN clients](https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-entra-gateway-update) to a Microsoft-registered VPN client for point-to-site connections with Microsoft Entra ID authentication before 31 Mar 2029.",
      "replacement": "Microsoft-registered VPN client",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=557395",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-entra-gateway-update"
      ],
      "vendor_ref": "557395",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-vpn-gateway-manually-registered-vpn-clients-gov-21vianet-retirement"
    },
    {
      "slug": "azure-functions-python-3-14-end-of-support",
      "title": "Azure Functions: Python 3.14 end of support",
      "summary": "End of support date for Python 3.14 on Azure Functions: Apr 2029. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-04-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Python 3.14 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "3.14"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@python:3.14",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-python-3-14-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-python-3-12-retirement",
      "title": "Cloud Run: Python 3.12 decommission",
      "summary": "Decommission date for Python 3.12 on Cloud Run: 2 Apr 2029. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2029-04-02",
      "effective_precision": "day",
      "impact": "The decommission date of Python 3.12 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-python-3-12-retirement"
    },
    {
      "slug": "azure-devops-server-2019-update-1-end-of-support",
      "title": "Azure DevOps Server 2019 Update 1 end of support",
      "summary": "endoflife.date lists 10 Apr 2029 as the end of security support for Azure DevOps Server 2019 Update 1. Microsoft publishes the specific end of support dates and details in its Lifecycle product search.",
      "cloud": "azure",
      "service": "Azure DevOps Server",
      "service_slug": "devops-server",
      "category": "other",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-04-10",
      "effective_precision": "day",
      "impact": "Prior to 2019, the product was known as Team Foundation Server (TFS). Microsoft publishes specific end of support dates and details in its [Lifecycle product search](https://learn.microsoft.com/en-us/lifecycle/products/). For releases under the Microsoft Fixed Lifecycle Policy, the policy states that, to be eligible for support, customers may be required to deploy the latest Service Pack or update.",
      "migration_path": "Follow [Upgrade your deployment to the latest version of Azure DevOps Server](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started):\n\n1. Have your Azure DevOps Server license and product key ready, and administrative access and credentials for the service accounts.\n2. Review the [system requirements](https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server) for the target server, which may include updates to operating systems, SQL Server versions, and hardware.\n3. Create a complete and consistent set of backups for all Azure DevOps databases.\n4. If you upgrade in place, perform a trial in a pre-production environment: [Pre-production dry run](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-server).\n5. Plan for downtime. The deployment is offline during the upgrade.",
      "replacement": null,
      "affected_versions": [
        "2019.1"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/azure-devops-server-2019",
      "extra_source_urls": [
        "https://endoflife.date/azure-devops-server"
      ],
      "vendor_ref": "azure-devops-server@2019.1",
      "last_checked_at": "2026-11-12T09:55:46.498Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-devops-server-2019-update-1-end-of-support"
    },
    {
      "slug": "azure-app-service-node-26-end-of-support",
      "title": "Azure App Service: Node 26 end of support",
      "summary": "End of support date for Node 26 on Azure App Service: 30 Apr 2029. Apps that use this version continue to run unchanged, but App Service can't provide security patches or related customer support for it past that date.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-04-30",
      "effective_precision": "day",
      "impact": "After 30 Apr 2029, apps that use Node 26 continue to run unchanged, but App Service can't provide security patches or related customer support for that runtime version.\n\n- An app on an unsupported language version must be upgraded to a supported version before it can get App Service support.\n- App Service sends reminder notifications about end-of-support dates to subscription owners.\n- Contributors, readers, or other roles don't directly receive notifications unless they opt in through Service Health Alerts.\n- For Java, the page adds that developers who use a supported Java runtime that is retired receive a deprecation notice at least six months before the runtime is retired.",
      "migration_path": "1. Find the language version the app uses. The [language runtime support policy](https://learn.microsoft.com/en-us/azure/app-service/language-support-policy) links \"Show language version\" resources for .NET, Java, Node, Python and PHP.\n2. Choose a supported version of Node. The same page links the support timeline of each language community.\n3. Set the new language version for the app. The same page links \"Set language versions\" resources for .NET, Java, Node, Python and PHP.",
      "replacement": null,
      "affected_versions": [
        "26"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy",
      "extra_source_urls": [
        "https://github.com/nodejs/release"
      ],
      "vendor_ref": "appservice@node:26",
      "last_checked_at": "2026-11-12T09:56:00.082Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-node-26-end-of-support"
    },
    {
      "slug": "aws-rds-mariadb-11-4-end-of-support",
      "title": "Amazon RDS for MariaDB: MariaDB 11.4 end of standard support",
      "summary": "RDS end of standard support date for MariaDB 11.4 on Amazon RDS for MariaDB: May 2029. AWS lists this date so that testing and upgrade cycles can be planned around it.",
      "cloud": "aws",
      "service": "Amazon RDS for MariaDB",
      "service_slug": "rds-mariadb",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "May 2029 is the RDS end of standard support date that AWS lists for MariaDB 11.4. The AWS page does not state what happens to DB instances still on MariaDB 11.4 after that date.\n\n- RDS for MariaDB major versions remain available at least until community end of life for the corresponding community version.\n- A date with only a month and a year is approximate and is replaced by an exact date once known.\n- If AWS extends support for a version beyond the stated date, it plans to update its version table with the later date.\n- Deprecation policy: see the [Amazon RDS FAQs](https://aws.amazon.com/rds/faqs/).",
      "migration_path": "1. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command.\n2. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n3. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MariaDB](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MariaDB.Major.html). Major version upgrades are performed manually.\n4. Plan for downtime: database engine upgrades require downtime, and its duration varies with the size of the DB instance.\n5. Downtime for the upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. The engine cannot be reverted after the upgrade completes. To return to the previous version, restore the first DB snapshot taken during the upgrade to a new DB instance. Amazon RDS only takes these snapshots if the backup retention period of the DB instance is greater than 0.",
      "replacement": null,
      "affected_versions": [
        "11.4"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MariaDB.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mariadb"
      ],
      "vendor_ref": "amazon-rds-mariadb@11.4",
      "last_checked_at": "2026-11-12T09:55:39.673Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mariadb-11-4-end-of-support"
    },
    {
      "slug": "azure-functions-java-25-end-of-support",
      "title": "Azure Functions: Java 25 end of support",
      "summary": "End of support date for Java 25 on Azure Functions: May 2029. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Java 25 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "25"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@java:25",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-java-25-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-almalinux-8-image-end-of-support",
      "title": "Compute Engine: AlmaLinux 8 image end of support",
      "summary": "EOS and image deprecation date for the AlmaLinux 8 public image on Compute Engine: May 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of AlmaLinux 8 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "AlmaLinux 8"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "almalinux-8",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-almalinux-8-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-10-0-for-sap-image-end-of-support",
      "title": "Compute Engine: RHEL 10.0 for SAP image end of support",
      "summary": "EOS and image deprecation date for the RHEL 10.0 for SAP public image on Compute Engine: May 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 10.0 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 10.0 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-10-0-sap-ha",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-10-0-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-8-image-end-of-support",
      "title": "Compute Engine: RHEL 8 image end of support",
      "summary": "EOS and image deprecation date for the RHEL 8 public image on Compute Engine: May 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 8 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 8"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-8",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-8-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-8-10-for-sap-image-end-of-support",
      "title": "Compute Engine: RHEL 8.10 for SAP image end of support",
      "summary": "EOS and image deprecation date for the RHEL 8.10 for SAP public image on Compute Engine: May 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 8.10 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 8.10 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-8-10-sap-ha",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-8-10-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-9-6-for-sap-image-end-of-support",
      "title": "Compute Engine: RHEL 9.6 for SAP image end of support",
      "summary": "EOS and image deprecation date for the RHEL 9.6 for SAP public image on Compute Engine: May 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 9.6 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 9.6 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-9-6-sap-ha",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-9-6-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-8-image-end-of-support",
      "title": "Compute Engine: Rocky Linux 8 image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 8 public image on Compute Engine: May 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 8 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 8"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-8",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-8-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-8-optimized-for-google-cloud-image-end-of-support",
      "title": "Compute Engine: Rocky Linux 8 optimized for Google Cloud image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 8 optimized for Google Cloud public image on Compute Engine: May 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 8 optimized for Google Cloud in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 8 optimized for Google Cloud"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-8-optimized-gcp",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-8-optimized-for-google-cloud-image-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-dotnet-10-retirement",
      "title": "Cloud Run: .NET 10 decommission",
      "summary": "Decommission date for .NET 10 on Cloud Run: 14 May 2029. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2029-05-14",
      "effective_precision": "day",
      "impact": "The decommission date of .NET 10 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-dotnet-10-retirement"
    },
    {
      "slug": "azure-mysql-8-0-extended-support-end-of-support",
      "title": "Azure Database for MySQL: MySQL 8.0 end of extended support",
      "summary": "Azure Extended Support End Date for MySQL 8.0 on Azure Database for MySQL: 31 May 2029. After the extended support period ends, no further security or support updates are provided for the retired version.",
      "cloud": "azure",
      "service": "Azure Database for MySQL",
      "service_slug": "mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-05-31",
      "effective_precision": "day",
      "impact": "After the extended support period ends, no further security or support updates are provided for MySQL 8.0 on servers still running it.\n\n- Azure cannot patch the retired database engine, and support for engine-related issues is no longer available.\n- Azure continues periodic maintenance and patching for the host, OS, containers and other service-related components.\n- New database servers cannot be created for the retired version. Point-in-time recoveries and read replicas for existing servers remain possible.\n- If an engine vulnerability in the retired version seriously threatens the service, Azure might stop the compute node of the server and ask for an upgrade before bringing it online.\n- Uptime SLAs apply only to service-related issues, not to downtime caused by database engine bugs.",
      "migration_path": "1. Upgrade to a supported major version. Upgrade read replicas that use an older MySQL version before upgrading the primary server.\n2. Check schema compatibility with the target version using the Validate feature in the Azure portal. Validation locks tables, and the page directs large-scale production environments to Oracle's client-side upgrade checker tool. Verify deprecated sql_mode values and remove or deselect them in the Server Parameters pane before upgrading, to avoid deployment failure.\n3. Ensure there are no active or pending XA transactions on the database. Ongoing XA transactions can cause the upgrade to fail.\n4. Trigger an on-demand backup before the major version upgrade of a production server.\n5. Perform the upgrade first on a restored server copy rather than on production directly.\n6. In the Azure portal, open the server, and on the Overview page select Upgrade. The major version upgrade is irreversible. Burstable SKU servers use a separate workflow that first upgrades the compute tier to a General-Purpose SKU. See [Major version upgrade in Azure Database for MySQL](https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-upgrade).",
      "replacement": null,
      "affected_versions": [
        "8.0"
      ],
      "source_url": "https://learn.microsoft.com/azure/mysql/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-mysql"
      ],
      "vendor_ref": "azure-database-for-mysql@8.0",
      "last_checked_at": "2026-11-12T09:55:37.239Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-mysql-8-0-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-mariadb-12-3-end-of-support",
      "title": "Amazon RDS for MariaDB: MariaDB 12.3 end of standard support",
      "summary": "RDS end of standard support date for MariaDB 12.3 on Amazon RDS for MariaDB: Jun 2029. AWS lists this date so that testing and upgrade cycles can be planned around it.",
      "cloud": "aws",
      "service": "Amazon RDS for MariaDB",
      "service_slug": "rds-mariadb",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-01",
      "effective_precision": "month",
      "impact": "Jun 2029 is the RDS end of standard support date that AWS lists for MariaDB 12.3. The AWS page does not state what happens to DB instances still on MariaDB 12.3 after that date.\n\n- RDS for MariaDB major versions remain available at least until community end of life for the corresponding community version.\n- A date with only a month and a year is approximate and is replaced by an exact date once known.\n- If AWS extends support for a version beyond the stated date, it plans to update its version table with the later date.\n- Deprecation policy: see the [Amazon RDS FAQs](https://aws.amazon.com/rds/faqs/).",
      "migration_path": "1. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command.\n2. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n3. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MariaDB](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MariaDB.Major.html). Major version upgrades are performed manually.\n4. Plan for downtime: database engine upgrades require downtime, and its duration varies with the size of the DB instance.\n5. Downtime for the upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. The engine cannot be reverted after the upgrade completes. To return to the previous version, restore the first DB snapshot taken during the upgrade to a new DB instance. Amazon RDS only takes these snapshots if the backup retention period of the DB instance is greater than 0.",
      "replacement": null,
      "affected_versions": [
        "12.3"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MariaDB.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mariadb"
      ],
      "vendor_ref": "amazon-rds-mariadb@12.3",
      "last_checked_at": "2026-11-12T09:55:39.673Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mariadb-12-3-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-24-04-lts-image-end-of-support",
      "title": "Compute Engine: Ubuntu 24.04 LTS image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu 24.04 LTS public image on Compute Engine: Jun 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu 24.04 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu 24.04 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-2404-lts-amd64",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-24-04-lts-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-24-04-lts-optimized-for-tpus-image-end-of-support",
      "title": "Compute Engine: Ubuntu 24.04 LTS optimized for TPUs image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu 24.04 LTS optimized for TPUs public image on Compute Engine: Jun 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu 24.04 LTS optimized for TPUs in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu 24.04 LTS optimized for TPUs"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-accel-2404-amd64-tpu-tpu7x",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-24-04-lts-optimized-for-tpus-image-end-of-support"
    },
    {
      "slug": "aws-lambda-java11-al2023-end-of-support",
      "title": "AWS Lambda: Java 11 (java11.al2023) deprecation",
      "summary": "Deprecation date for Java 11 (java11.al2023) on AWS Lambda: 30 Jun 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 31 Jul 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "java11.al2023"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "java11.al2023",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-java11-al2023-end-of-support"
    },
    {
      "slug": "aws-lambda-java17-al2023-end-of-support",
      "title": "AWS Lambda: Java 17 (java17.al2023) deprecation",
      "summary": "Deprecation date for Java 17 (java17.al2023) on AWS Lambda: 30 Jun 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 31 Jul 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "java17.al2023"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "java17.al2023",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-java17-al2023-end-of-support"
    },
    {
      "slug": "aws-lambda-java21-end-of-support",
      "title": "AWS Lambda: Java 21 (java21) deprecation",
      "summary": "Deprecation date for Java 21 (java21) on AWS Lambda: 30 Jun 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 31 Jul 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "java21"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "java21",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-java21-end-of-support"
    },
    {
      "slug": "aws-lambda-java25-end-of-support",
      "title": "AWS Lambda: Java 25 (java25) deprecation",
      "summary": "Deprecation date for Java 25 (java25) on AWS Lambda: 30 Jun 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 31 Jul 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "java25"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "java25",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-java25-end-of-support"
    },
    {
      "slug": "aws-lambda-java8-al2023-end-of-support",
      "title": "AWS Lambda: Java 8 (java8.al2023) deprecation",
      "summary": "Deprecation date for Java 8 (java8.al2023) on AWS Lambda: 30 Jun 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 31 Jul 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "java8.al2023"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "java8.al2023",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-java8-al2023-end-of-support"
    },
    {
      "slug": "aws-lambda-provided-al2023-end-of-support",
      "title": "AWS Lambda: OS-only (provided.al2023) deprecation",
      "summary": "Deprecation date for OS-only (provided.al2023) on AWS Lambda: 30 Jun 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 31 Jul 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "provided.al2023"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "provided.al2023",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-provided-al2023-end-of-support"
    },
    {
      "slug": "aws-lambda-python3-13-end-of-support",
      "title": "AWS Lambda: Python 3.13 (python3.13) deprecation",
      "summary": "Deprecation date for Python 3.13 (python3.13) on AWS Lambda: 30 Jun 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 31 Jul 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "python3.13"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "python3.13",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-python3-13-end-of-support"
    },
    {
      "slug": "aws-lambda-python3-14-end-of-support",
      "title": "AWS Lambda: Python 3.14 (python3.14) deprecation",
      "summary": "Deprecation date for Python 3.14 (python3.14) on AWS Lambda: 30 Jun 2029. After deprecation, AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support.",
      "cloud": "aws",
      "service": "AWS Lambda",
      "service_slug": "lambda",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "After deprecation (30 Jun 2029), AWS may no longer apply security patches or updates to the runtime, and functions using it are no longer eligible for technical support. Functions can still be invoked indefinitely, but may experience degraded performance or other issues, such as a certificate expiry, that can cause them to stop working properly.\n\n- Deprecation: the Lambda console no longer creates or updates functions with this runtime. The AWS CLI, AWS SAM, and CloudFormation still do.\n- Block function create (date: 31 Jul 2029, at least 30 days after deprecation): Lambda begins blocking creation of new functions.\n- Block function update (date: 31 Aug 2029, at least 60 days after deprecation): Lambda begins blocking the update of code and configuration for existing functions.\n- Lambda does not block creates or updates before the dates in its runtime tables. Forecast dates are subject to change.",
      "migration_path": "1. List the affected function versions with Trusted Advisor or with [Retrieve data about Lambda Event Functions that use a deprecated runtime](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-list-deprecated.html).\n2. Test each function with the new runtime before applying changes in production environments.\n3. Update the function to a newer supported runtime. This is possible at any time after the runtime is deprecated. In the Block function update phase (date: 31 Aug 2029), Lambda begins blocking the update of code and configuration for existing functions, but the function configuration can still be upgraded to a supported runtime. See [Managing AWS Lambda runtime upgrades](https://aws.amazon.com/blogs/compute/managing-aws-lambda-runtime-upgrades/).\n4. Use function [versions](https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html) and [aliases](https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html) to enable deployment with rollback. After function updates are blocked, reverting to the deprecated runtime is not possible.",
      "replacement": null,
      "affected_versions": [
        "python3.14"
      ],
      "source_url": "https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html",
      "extra_source_urls": [
        "https://endoflife.date/aws-lambda"
      ],
      "vendor_ref": "python3.14",
      "last_checked_at": "2026-11-12T09:55:56.604Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-lambda-python3-14-end-of-support"
    },
    {
      "slug": "aws-aurora-mysql-version-2-extended-support-end-of-support",
      "title": "Amazon Aurora MySQL: version 2 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for Amazon Aurora MySQL version 2: 30 Jun 2029. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora MySQL",
      "service_slug": "aurora-mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 30 Jun 2029. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- Support dates for a major engine version can also be read with the AWS CLI or the RDS API. See [Viewing support dates for engine versions in Amazon RDS Extended Support](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-viewing-support-dates.html).",
      "migration_path": "1. Look up your type and version of cluster in [Aurora MySQL major version upgrade paths](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Compatibility). The table says whether the cluster can use the in-place upgrade mechanism and which action applies.\n2. Where the table points to a major version upgrade, plan it with [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). A major version upgrade needs more planning and testing than a minor version upgrade.\n3. Before an in-place upgrade, create a clone of the original cluster, perform an in-place upgrade of the clone immediately after creating it, and test application compatibility, performance and administration procedures on it.\n4. When the test cluster works properly, perform the in-place upgrade for the production cluster. See [How to perform an in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Upgrading.Procedure.html).\n5. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "2"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-mysql"
      ],
      "vendor_ref": "amazon-aurora-mysql@2",
      "last_checked_at": "2026-11-12T09:55:40.805Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-mysql-version-2-extended-support-end-of-support"
    },
    {
      "slug": "aws-amazon-linux-2023-end-of-support",
      "title": "Amazon Linux 2023 end of support",
      "summary": "End of support date for Amazon Linux 2023: 30 Jun 2029. This is the date that endoflife.date lists under Security Support for the release.",
      "cloud": "aws",
      "service": "Amazon Linux",
      "service_slug": "amazon-linux",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "The date is the one that endoflife.date lists under Security Support for Amazon Linux 2023. endoflife.date lists a separate Standard Support date for each release in its own column. endoflife.date notes that Amazon provides security advisories for all versions on the Amazon Linux Security Center.",
      "migration_path": "AWS has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [
        "2023"
      ],
      "source_url": "https://docs.aws.amazon.com/linux/al2023/ug/release-cadence.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-linux"
      ],
      "vendor_ref": "amazon-linux@2023",
      "last_checked_at": "2026-11-12T09:55:45.836Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-amazon-linux-2023-end-of-support"
    },
    {
      "slug": "aws-rds-mysql-5-7-extended-support-end-of-support",
      "title": "Amazon RDS for MySQL: MySQL 5.7 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for MySQL 5.7 on Amazon RDS for MySQL: 30 Jun 2029. AWS states that once the RDS Extended Support period of a major engine version is over, Amazon RDS automatically upgrades the major engine version of a database not upgraded to a supported version.",
      "cloud": "aws",
      "service": "Amazon RDS for MySQL",
      "service_slug": "rds-mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "30 Jun 2029 is the RDS end of Extended Support date that AWS lists for MySQL 5.7. AWS states that once the RDS Extended Support period of a major engine version is over, Amazon RDS automatically upgrades the major engine version of a database not upgraded to a supported version. The pages do not state which version that automatic upgrade targets, or how soon after the end of the period it runs.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- A completed upgrade cannot be reverted to the previous engine version.\n- Minor versions can reach end of Extended Support earlier.\n- RDS Extended Support is a paid offering up to that date: see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "migration_path": "1. Test the upgrade first: create a DB snapshot of the DB instance, restore it to a new DB instance, and start a version upgrade on that new instance.\n2. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command. AWS lists the supported major version upgrades on its [MySQL on Amazon RDS versions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html) page.\n3. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n4. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MySQL.Major.html).\n5. Downtime for the major version upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. Enrollment in RDS Extended Support ends the day an upgrade completes to an engine version that is still under RDS standard support. An upgrade to a version that is itself under RDS Extended Support does not end it: check the support dates of the target version in [Supported MySQL major versions on Amazon RDS](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html#MySQL.Concepts.VersionMgmt.ReleaseCalendar).",
      "replacement": null,
      "affected_versions": [
        "5.7"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mysql"
      ],
      "vendor_ref": "amazon-rds-mysql@5.7",
      "last_checked_at": "2026-11-12T09:55:38.611Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mysql-5-7-extended-support-end-of-support"
    },
    {
      "slug": "azure-vmware-solution-av36p-and-av52-node-retirement",
      "title": "Azure VMware Solution: AV36P and AV52 node retirement",
      "summary": "Retirement date for the Azure VMware Solution AV36P and AV52 node types: 30 Jun 2029. License-included customers have an earlier deadline: transition to the AV36P and AV52 VCF BYOL SKUs by August 30, 2027.",
      "cloud": "azure",
      "service": "Azure VMware Solution",
      "service_slug": "vmware-solution",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-03-17",
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "The AV36P and AV52 VCF BYOL node types are retired on 30 Jun 2029, and all migrations off them need to be completed by that date. The AVS license-included SKUs are retired on August 30, 2027, the last day of the AVS License-included service. AV36P and AV52 License-included customers need to purchase portable VCF licenses from Broadcom and transition to the AV36P and AV52 VCF BYOL SKUs by that date; the source ties this deadline to avoiding a service impact on August 31, 2027. June 30, 2026 was the last day to buy a 3-year RI and June 30, 2028 is the last day to buy a 1-year RI for AV36P or AV52 VCF BYOL, which requires a portable VCF license from Broadcom.",
      "migration_path": "1. Review your current RI expiration timeline and work with your Microsoft Account Team on next steps.\n2. If you use AV36P or AV52 License-included SKUs, purchase portable VCF licenses from Broadcom and transition to the VCF BYOL SKUs by August 30, 2027.\n3. Identify available AVS node types on the [Azure Product by Region page](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/table).\n4. Transition from AV36P and AV52 nodes to a new AVS node type before the end of your current RI term.\n5. Read the [AVS Documentation page](https://learn.microsoft.com/en-us/azure/azure-vmware/architecture-migrate) to learn about HCX migrations between AVS node types.",
      "replacement": null,
      "affected_versions": [
        "AV36P",
        "AV52"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=557094",
      "extra_source_urls": [
        "https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/table",
        "https://learn.microsoft.com/en-us/azure/azure-vmware/architecture-migrate"
      ],
      "vendor_ref": "557094",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-vmware-solution-av36p-and-av52-node-retirement"
    },
    {
      "slug": "gcp-cloud-run-php-8-4-retirement",
      "title": "Cloud Run: PHP 8.4 decommission",
      "summary": "Decommission date for PHP 8.4 on Cloud Run: 30 Jun 2029. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2029-06-30",
      "effective_precision": "day",
      "impact": "The decommission date of PHP 8.4 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-php-8-4-retirement"
    },
    {
      "slug": "gcp-compute-engine-oracle-linux-8-image-end-of-support",
      "title": "Compute Engine: Oracle Linux 8 image end of support",
      "summary": "EOS and image deprecation date for the Oracle Linux 8 public image on Compute Engine: Jul 2029. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-07-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Oracle Linux 8 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Oracle Linux 8"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "oracle-linux-8",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-oracle-linux-8-image-end-of-support"
    },
    {
      "slug": "aws-aurora-mysql-version-3-extended-support-end-of-support",
      "title": "Amazon Aurora MySQL: version 3 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for Amazon Aurora MySQL version 3: 31 Jul 2029. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora MySQL",
      "service_slug": "aurora-mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-07-31",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 31 Jul 2029. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- Support dates for a major engine version can also be read with the AWS CLI or the RDS API. See [Viewing support dates for engine versions in Amazon RDS Extended Support](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-viewing-support-dates.html).",
      "migration_path": "1. Look up your type and version of cluster in [Aurora MySQL major version upgrade paths](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Compatibility). The table says whether the cluster can use the in-place upgrade mechanism and which action applies.\n2. Where the table points to a major version upgrade, plan it with [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). A major version upgrade needs more planning and testing than a minor version upgrade.\n3. Before an in-place upgrade, create a clone of the original cluster, perform an in-place upgrade of the clone immediately after creating it, and test application compatibility, performance and administration procedures on it.\n4. When the test cluster works properly, perform the in-place upgrade for the production cluster. See [How to perform an in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Upgrading.Procedure.html).\n5. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "3"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-mysql"
      ],
      "vendor_ref": "amazon-aurora-mysql@3",
      "last_checked_at": "2026-11-12T09:55:40.805Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-mysql-version-3-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-mysql-8-0-extended-support-end-of-support",
      "title": "Amazon RDS for MySQL: MySQL 8.0 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for MySQL 8.0 on Amazon RDS for MySQL: 31 Jul 2029. AWS states that once the RDS Extended Support period of a major engine version is over, Amazon RDS automatically upgrades the major engine version of a database not upgraded to a supported version.",
      "cloud": "aws",
      "service": "Amazon RDS for MySQL",
      "service_slug": "rds-mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-07-31",
      "effective_precision": "day",
      "impact": "31 Jul 2029 is the RDS end of Extended Support date that AWS lists for MySQL 8.0. AWS states that once the RDS Extended Support period of a major engine version is over, Amazon RDS automatically upgrades the major engine version of a database not upgraded to a supported version. The pages do not state which version that automatic upgrade targets, or how soon after the end of the period it runs.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- A completed upgrade cannot be reverted to the previous engine version.\n- Minor versions can reach end of Extended Support earlier.\n- RDS Extended Support is a paid offering up to that date: see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "migration_path": "1. Test the upgrade first: create a DB snapshot of the DB instance, restore it to a new DB instance, and start a version upgrade on that new instance.\n2. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command. AWS lists the supported major version upgrades on its [MySQL on Amazon RDS versions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html) page.\n3. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n4. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MySQL.Major.html).\n5. Downtime for the major version upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. Enrollment in RDS Extended Support ends the day an upgrade completes to an engine version that is still under RDS standard support. An upgrade to a version that is itself under RDS Extended Support does not end it: check the support dates of the target version in [Supported MySQL major versions on Amazon RDS](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html#MySQL.Concepts.VersionMgmt.ReleaseCalendar).",
      "replacement": null,
      "affected_versions": [
        "8.0"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mysql"
      ],
      "vendor_ref": "amazon-rds-mysql@8.0",
      "last_checked_at": "2026-11-12T09:55:38.611Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mysql-8-0-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-mysql-8-4-end-of-support",
      "title": "Amazon RDS for MySQL: MySQL 8.4 end of standard support",
      "summary": "RDS end of standard support date for MySQL 8.4 on Amazon RDS for MySQL: 31 Jul 2029. Past that date, a database can keep running on MySQL 8.4 under RDS Extended Support for an additional cost, or be upgraded to a major version under standard support.",
      "cloud": "aws",
      "service": "Amazon RDS for MySQL",
      "service_slug": "rds-mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-07-31",
      "effective_precision": "day",
      "impact": "Once MySQL 8.4 reaches its RDS end of standard support date (31 Jul 2029), Amazon RDS automatically enrolls DB instances and DB clusters in RDS Extended Support, unless that was disabled. Charges begin the day after that date.\n\n- Amazon RDS then automatically upgrades a DB instance to the last minor version released before that date, unless it already runs that version.\n- RDS Extended Support includes security updates for critical and high CVEs and bug fixes for critical issues.\n- If enrollment is disabled after that date, the instance or cluster upgrades automatically to the next supported major version.\n- A fee applies: see [Amazon RDS for MySQL pricing](https://aws.amazon.com/rds/mysql/pricing/).",
      "migration_path": "1. Test the upgrade first: create a DB snapshot of the DB instance, restore it to a new DB instance, and start a version upgrade on that new instance.\n2. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command.\n3. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n4. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MySQL.Major.html).\n5. Downtime for the major version upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. The RDS Extended Support charge stops after an upgrade to an engine version that is covered under standard support, and restarts if that target version later enters RDS Extended Support. See [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "replacement": null,
      "affected_versions": [
        "8.4"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mysql"
      ],
      "vendor_ref": "amazon-rds-mysql@8.4",
      "last_checked_at": "2026-11-12T09:55:38.611Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mysql-8-4-end-of-support"
    },
    {
      "slug": "oci-oracle-linux-8-end-of-support",
      "title": "Oracle Linux 8 end of Premier Support",
      "summary": "End of Premier Support date for Oracle Linux 8: 31 Jul 2029. This is the date that endoflife.date lists under Basic/Premier Support for the release.",
      "cloud": "oci",
      "service": "Oracle Linux",
      "service_slug": "oracle-linux",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-07-31",
      "effective_precision": "day",
      "impact": "The date is the one that endoflife.date lists under Basic/Premier Support for Oracle Linux 8. endoflife.date states:\n\n- Basic and Premier Support include patches, fixes, security patches and security alerts. Premier Support adds live kernel patching.\n- Once a new minor release is available, the older one is considered end of life, and users must upgrade to continue receiving security updates.\n- Extended Support is available for a limited time after Premier Support ends, as per agreement with Oracle, with extra fees.\n- Extended Support covers critical security errata and select high-impact critical bug fixes, for select packages.\n- Sustaining Support follows Extended Support and does not include new security fixes or alerts.",
      "migration_path": "Oracle has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [
        "8"
      ],
      "source_url": "https://endoflife.date/oracle-linux",
      "extra_source_urls": [
        "https://www.oracle.com/a/ocom/docs/elsp-lifetime-069338.pdf"
      ],
      "vendor_ref": "oracle-linux@8",
      "last_checked_at": "2026-11-12T09:55:55.860Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/oci-oracle-linux-8-end-of-support"
    },
    {
      "slug": "azure-iot-central-retirement",
      "title": "Azure IoT Central retirement",
      "summary": "Retirement date for Azure IoT Central: 20 Sep 2029. The service can be used until the retirement date. Microsoft names Azure IoT Hub, Device Provisioning Service (DPS), and Azure Device Registry as the recommended platform.",
      "cloud": "azure",
      "service": "Azure IoT Central",
      "service_slug": "iot-central",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-09-29",
      "effective_date": "2029-09-20",
      "effective_precision": "day",
      "impact": "Azure IoT Central can be used until the retirement date. Microsoft asks customers to review their current Azure IoT Central applications, devices, dashboards, and integrations. Microsoft states that it is focusing future investment on Azure IoT platform services.",
      "migration_path": "1. Review your current Azure IoT Central applications, devices, dashboards, and integrations.\n2. Evaluate Azure IoT Hub and DPS as the target architecture for device connectivity and provisioning.\n3. Evaluate Microsoft Fabric for real-time analytics, dashboards, and broader data experiences.\n4. Use the [Azure IoT Central migration playbook](https://aka.ms/AzureIoTCentralMigrationPlaybook) to map existing IoT Central scenarios to Azure IoT services.\n5. Plan and execute your transition before the retirement date.\n6. If additional assistance is required, engage Microsoft field teams or an [Azure IoT migration partner](https://aka.ms/AzureIOTPartnerReference).",
      "replacement": "Azure IoT Hub, Device Provisioning Service (DPS), and Azure Device Registry, with Microsoft Fabric for analytics and dashboards",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=569914",
      "extra_source_urls": [
        "https://aka.ms/AzureIoTCentralMigrationPlaybook",
        "https://aka.ms/AzureIOTPartnerReference"
      ],
      "vendor_ref": "569914",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-iot-central-retirement"
    },
    {
      "slug": "azure-app-service-on-azure-stack-hub-retirement",
      "title": "Azure App Service on Azure Stack Hub retirement",
      "summary": "Retirement date for Azure App Service on Azure Stack Hub: 30 Sep 2029. Microsoft support ends on that date, and Microsoft recommends migrating applications to Azure App Service in Azure.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-10-06",
      "effective_date": "2029-09-30",
      "effective_precision": "day",
      "impact": "On the retirement date, Azure App Service on Azure Stack Hub is retired and Microsoft support for it ends. From September 30, 2026, new installations are no longer supported and no new product releases, features, or enhancements are made available. Existing supported deployments can continue to run and upgrade to the latest available release until retirement.",
      "migration_path": "1. Inventory applications and dependencies, and assess compatibility.\n2. Select the Azure hosting target. Microsoft names Azure App Service in Azure, and Managed Instance on Azure App Service for applications with complex Windows dependencies.\n3. Migrate code, configuration, and data, then validate workloads.\n4. Complete the migration before the retirement date. Microsoft links guidance to [plan](https://go.microsoft.com/fwlink/?LinkId=2372018) and [migrate](https://go.microsoft.com/fwlink/?LinkId=2372019).",
      "replacement": "Azure App Service in Azure",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=568178",
      "extra_source_urls": [],
      "vendor_ref": "568178",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-on-azure-stack-hub-retirement"
    },
    {
      "slug": "azure-arc-enabled-scvmm-retirement",
      "title": "Azure Arc: Arc-enabled System Center Virtual Machine Manager retirement",
      "summary": "Retirement date for Azure Arc-enabled System Center Virtual Machine Manager (SCVMM): 30 Sep 2029. Customers must plan and transition to alternative solutions.",
      "cloud": "azure",
      "service": "Azure Arc",
      "service_slug": "arc",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-09-29",
      "effective_date": "2029-09-30",
      "effective_precision": "day",
      "impact": "Microsoft is retiring Azure Arc-enabled System Center Virtual Machine Manager (SCVMM), with the retirement date 30 Sep 2029. Customers using it must plan and transition to alternative solutions. For Azure services and Azure Arc capabilities such as monitoring, security, governance, updates, and licensing for Extended Security Updates and Pay-as-you-go SQL and WS, Microsoft recommends switching to Azure Arc-enabled Servers. For VM lifecycle and powercycle operations such as create, start, stop, restart, resize, and self-service VM management, Microsoft recommends reaching out by e-mail to arc-vmm-feedback@microsoft.com.",
      "migration_path": "1. Review your current use of Azure Arc-enabled SCVMM.\n2. Determine the migration path: Azure Arc-enabled Servers, or reach out to Microsoft if you need help.\n3. Follow the [migration guidance](https://aka.ms/arcscvmmretirement) to deboard your SCVMM environment from Azure Arc and onboard to your alternative solution.",
      "replacement": "Azure Arc-enabled Servers (Azure services and Azure Arc capabilities only)",
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=570283",
      "extra_source_urls": [
        "https://aka.ms/arcscvmmretirement"
      ],
      "vendor_ref": "570283",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-arc-enabled-scvmm-retirement"
    },
    {
      "slug": "gcp-cloud-run-ruby-4-0-retirement",
      "title": "Cloud Run: Ruby 4.0 decommission",
      "summary": "Decommission date for Ruby 4.0 on Cloud Run: 30 Sep 2029. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2029-09-30",
      "effective_precision": "day",
      "impact": "The decommission date of Ruby 4.0 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-ruby-4-0-retirement"
    },
    {
      "slug": "azure-functions-python-3-13-end-of-support",
      "title": "Azure Functions: Python 3.13 end of support",
      "summary": "End of support date for Python 3.13 on Azure Functions: Oct 2029. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-10-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Python 3.13 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "3.13"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@python:3.13",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-python-3-13-end-of-support"
    },
    {
      "slug": "azure-defender-for-iot-ot-security-retirement",
      "title": "Microsoft Defender for IoT: OT security retirement",
      "summary": "Retirement date for the operational technology (OT) security component of Microsoft Defender for IoT: Oct 2029. Customers of Defender for IoT OT Security need to move to an alternative OT security solution before retirement.",
      "cloud": "azure",
      "service": "Microsoft Defender for IoT",
      "service_slug": "defender-for-iot",
      "category": "feature",
      "type": "retirement",
      "announced_date": "2026-11-02",
      "effective_date": "2029-10-01",
      "effective_precision": "month",
      "impact": "The operational technology (OT) security component of Microsoft Defender for IoT is fully deprecated at the retirement date, after a three-year transition period. The change applies only to Defender for IoT OT Security: Enterprise IoT capabilities in Microsoft Defender for Endpoint are not affected, and device discovery and vulnerability assessment continue to be available. During the transition the service stays supported with routine security updates and bug fixes, but it receives no new OT-specific capabilities or feature investments. Existing customer agreements and renewals are honored until the retirement date.",
      "migration_path": "1. Review existing OT deployments, sensors, integrations, licenses, contracts, and security requirements.\n2. Select an alternative OT security solution. Microsoft offers connectors for Armis, Dragos, and Forescout, and does not require a specific provider. See [OT data connectors](https://learn.microsoft.com/en-us/security-exposure-management/ot-data-connectors).\n3. Plan separate licensing and deployment for any third-party solution.\n4. Build a transition plan that covers procurement, testing, operational validation, continuity, data export, and sensor decommissioning, with migration completed before the retirement date.\n5. Contact OT security providers directly, or ask the Microsoft account team to help coordinate an introduction.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=576255",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/security-exposure-management/ot-data-connectors",
        "https://learn.microsoft.com/en-us/security-exposure-management/overview-data-connectors",
        "https://learn.microsoft.com/en-us/defender-for-iot/enterprise-iot"
      ],
      "vendor_ref": "576255",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-defender-for-iot-ot-security-retirement"
    },
    {
      "slug": "azure-virtual-machines-dcsv3-dcdsv3-series-retirement",
      "title": "Azure Virtual Machines: DCsv3 and DCdsv3-series retirement",
      "summary": "Retirement date for DCsv3 and DCdsv3-series Azure Linux, Windows and Dedicated Host virtual machines: 31 Oct 2029. After that date, they are no longer available for use or purchase.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-10-01",
      "effective_date": "2029-10-31",
      "effective_precision": "day",
      "impact": "After 31 Oct 2029, DCsv3 and DCdsv3-series Azure Linux, Windows and Dedicated Host virtual machines are no longer available for use or purchase. 3-year and 1-year Reserved VM Instances for these series are not available for purchase or renewal after October 31, 2026. From November 1, 2026, capacity restrictions apply to DCsv3/DCdsv3-series VMs. Microsoft states that billing may change.",
      "migration_path": "1. Migrate DCsv3 and DCdsv3-series VMs to one of the recommended options before 31 Oct 2029. Microsoft links a [Migration guide](https://aka.ms/dcsv3-dcdsv3-series-retirement).\n2. For a VM-based programming model, consider the [DCasv6](https://learn.microsoft.com/azure/virtual-machines/sizes/general-purpose/dcasv6-series?tabs=sizebasic), [DCadsv6](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dcadsv6-series?tabs=sizebasic), [DCesv6](https://learn.microsoft.com/azure/virtual-machines/sizes/general-purpose/dcesv6-series?tabs=sizebasic) or [DCedsv6](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dcedsv6-series?tabs=sizebasic) series, or the memory optimized [ECasv6](https://learn.microsoft.com/azure/virtual-machines/sizes/memory-optimized/ecasv6-series?tabs=sizebasic), [ECadsv6](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/memory-optimized/ecadsv6-series?tabs=sizebasic), [ECesv6](https://learn.microsoft.com/azure/virtual-machines/ecesv5-ecedsv5-series) or [ECedsv6](https://learn.microsoft.com/en-us/azure/virtual-machines/ecedsv6-series) series confidential VMs.\n3. For containerized applications, consider [Azure Confidential Container Instances (C-ACI)](https://learn.microsoft.com/azure/container-instances/container-instances-confidential-overview) or [Virtual nodes on Azure Container Instances (C-VN2)](https://learn.microsoft.com/azure/container-instances/container-instances-virtual-nodes) for Azure Kubernetes Service (AKS).\n4. Check the Azure Virtual Machines [pricing page](https://azure.microsoft.com/pricing/details/virtual-machines/linux-previous/) for billing details.",
      "replacement": "DCasv6, DCadsv6, DCesv6, DCedsv6 or ECasv6, ECadsv6, ECesv6, ECedsv6 series confidential VMs",
      "affected_versions": [
        "DCsv3",
        "DCdsv3"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=569592",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/virtual-machines/sizes/general-purpose/dcasv6-series?tabs=sizebasic",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dcadsv6-series?tabs=sizebasic",
        "https://learn.microsoft.com/azure/virtual-machines/sizes/general-purpose/dcesv6-series?tabs=sizebasic",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/general-purpose/dcedsv6-series?tabs=sizebasic",
        "https://learn.microsoft.com/azure/virtual-machines/sizes/memory-optimized/ecasv6-series?tabs=sizebasic",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/memory-optimized/ecadsv6-series?tabs=sizebasic",
        "https://learn.microsoft.com/azure/virtual-machines/ecesv5-ecedsv5-series",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/ecedsv6-series"
      ],
      "vendor_ref": "569592",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-dcsv3-dcdsv3-series-retirement"
    },
    {
      "slug": "azure-postgresql-17-end-of-support",
      "title": "Azure Database for PostgreSQL: PostgreSQL 17 end of standard support",
      "summary": "Azure Standard Support End Date for PostgreSQL 17 on Azure Database for PostgreSQL: 8 Nov 2029. Once the Azure Standard Support period ends, eligible servers still running the version are automatically enrolled in extended support.",
      "cloud": "azure",
      "service": "Azure Database for PostgreSQL",
      "service_slug": "postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-11-08",
      "effective_precision": "day",
      "impact": "Once the Azure Standard Support period ends, an eligible server still running PostgreSQL 17 is automatically enrolled in extended support. The eligible versions table lists PostgreSQL 11, 12, 13 and 14.\n\n- Extended support provides security patches, critical bug fixes and technical support for up to three extra years. It does not include new features, performance enhancements or support for minor version upgrades.\n- Charges apply after any applicable grace period unless the server is upgraded to a supported version, and only to servers in a Succeeded (running) state. A one-month grace period is provided for versions 11, 12 and 13. A server that regional capacity constraints prevent from upgrading might be temporarily excluded from billing.\n- The version policy page lists restrictions that apply after the retirement date of a version, without stating whether that date is 8 Nov 2029: new servers cannot be created on a retired version, while point-in-time recoveries and read replicas of existing servers remain possible.\n- The same page says that when the community retires a version, Azure stops applying bug or security patches to the database engine. The extended support page lists security patches and critical bug fixes as part of extended support.",
      "migration_path": "1. Run the upgrade validation checks in the Azure portal or with the Azure CLI. See [Run upgrade validation checks](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/how-to-run-upgrade-validation-checks).\n2. Resolve any blocking issues the checks report, then rerun validation.\n3. Ensure the server has at least 10-20% free storage available before starting the upgrade.\n4. If the server uses geo-replication, delete the read replica (including any cascading read replica) before upgrading the primary server. The replica can be re-created after the upgrade.\n5. Run an in-place major version upgrade to a PostgreSQL version that Azure currently supports. The service can skip versions and upgrade directly to a later version. Servers that use TimescaleDB are limited to specific source and target version combinations, and an upgrade from PostgreSQL 11 first requires SCRAM authentication to be configured. Once the server runs a supported version, extended support charges no longer apply. See [Major version upgrades](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-major-version-upgrade).\n6. Plan for the fact that there is no automated way to revert after a successful upgrade. A point-in-time recovery to a time before the upgrade restores the previous version on a new server.",
      "replacement": null,
      "affected_versions": [
        "17"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-postgresql"
      ],
      "vendor_ref": "azure-database-for-postgresql@17",
      "last_checked_at": "2026-11-12T09:55:36.471Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-postgresql-17-end-of-support"
    },
    {
      "slug": "azure-virtual-machines-dv3-dsv3-ev3-esv3-series-retirement",
      "title": "Azure Virtual Machines: Dv3, Dsv3, Ev3, and Esv3 series retirement",
      "summary": "Retirement date for the Dv3, Dsv3, Ev3, and Esv3 Azure VM series in public cloud Azure regions: 15 Nov 2029. After that date, these virtual machines are no longer supported on Azure and may be deallocated and ultimately deleted.",
      "cloud": "azure",
      "service": "Azure Virtual Machines",
      "service_slug": "virtual-machines",
      "category": "compute_sku",
      "type": "retirement",
      "announced_date": "2026-09-30",
      "effective_date": "2029-11-15",
      "effective_precision": "day",
      "impact": "After 15 Nov 2029, Dv3, Dsv3, Ev3, and Esv3 virtual machines are in the Retired lifecycle stage and are no longer supported on Azure. The retirement applies to these VM series in public cloud Azure regions. Virtual machines not transitioned by that time may be deallocated and ultimately deleted as the underlying hardware and platform infrastructure are retired. As of July 1, 2026, one-year and three-year Reserved Instances for these series are no longer available for purchase or renewal.",
      "migration_path": "1. Migrate any Dv3, Dsv3, Ev3, or Esv3 series VMs to a newer VM series before 15 Nov 2029. Microsoft links the [v5 modernization guide](https://aka.ms/VM-Lifecycle/learn/modernize-to-v5) and [Modernize to the v6 and v7 VM series - Azure Virtual Machines](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/lifecycle/sizes-v6-v7-modernization-overview).\n2. To continue commitment savings, review your [current reserved instance orders](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/manage-reserved-vm-instance). If reservations are still in effect for these VMs, consider a [trade-in](https://learn.microsoft.com/en-us/azure/cost-management-billing/savings-plan/reservation-trade-in) of active reservations for an [Azure savings plan](https://learn.microsoft.com/en-us/azure/cost-management-billing/savings-plan/savings-plan-overview#how-are-savings-plans-purchased).\n3. Customers with an active support plan can submit a [support request](https://learn.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request) for technical assistance with migration planning and execution.",
      "replacement": "Newer VM series (the source names Dsv5 and \"Esv5v5\" as examples)",
      "affected_versions": [
        "Dv3",
        "Dsv3",
        "Ev3",
        "Esv3"
      ],
      "source_url": "https://azure.microsoft.com/updates?id=572346",
      "extra_source_urls": [
        "https://aka.ms/VM-lifecycle/learn/vm-lifecycle-policy",
        "https://azure.microsoft.com/en-us/updates?id=560948",
        "https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/manage-reserved-vm-instance",
        "https://learn.microsoft.com/en-us/azure/cost-management-billing/savings-plan/reservation-trade-in",
        "https://learn.microsoft.com/en-us/azure/cost-management-billing/savings-plan/savings-plan-overview#how-are-savings-plans-purchased",
        "https://aka.ms/VM-Lifecycle/learn/modernize-to-v5",
        "https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/lifecycle/sizes-v6-v7-modernization-overview"
      ],
      "vendor_ref": "572346",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-virtual-machines-dv3-dsv3-ev3-esv3-series-retirement"
    },
    {
      "slug": "oci-oracle-database-19c-end-of-support",
      "title": "Oracle Database 19c end of Premier Support",
      "summary": "End of Premier Support date for Oracle Database 19c: 31 Dec 2029. This is the date that endoflife.date lists under Premier Support for the release.",
      "cloud": "oci",
      "service": "Oracle Database",
      "service_slug": "oracle-database",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2029-12-31",
      "effective_precision": "day",
      "impact": "The date is the one that endoflife.date lists under Premier Support for Oracle Database 19c, for Oracle Database On-Premises Server Releases for Linux x86-64. endoflife.date notes that release dates may vary across cloud and on-premises offers and support stages, and reports two release types:\n\n- Long-Term Releases (LTR) have Extended Support after Premier Support.\n- Oracle may offer, for some LTR, one year of free Extended Support.\n- Innovation Releases have no Extended Support.\n- The endoflife.date table marks Long-Term Releases with LTR and shows the Extended Support status of each release.",
      "migration_path": "The Oracle Database documentation lists Install and Upgrade guides by release: [Oracle Database documentation](https://docs.oracle.com/en/database/oracle/oracle-database/).",
      "replacement": null,
      "affected_versions": [
        "19"
      ],
      "source_url": "https://endoflife.date/oracle-database",
      "extra_source_urls": [
        "https://support.oracle.com/knowledgefs?docId=742060"
      ],
      "vendor_ref": "oracle-database@19",
      "last_checked_at": "2026-11-12T09:55:56.483Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/oci-oracle-database-19c-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-centos-stream-10-image-end-of-support",
      "title": "Compute Engine: CentOS Stream 10 image end of support",
      "summary": "EOS and image deprecation date for the CentOS Stream 10 public image on Compute Engine: 1 Jan 2030. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-01-01",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of CentOS Stream 10 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "CentOS Stream 10"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "centos-stream-10",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-centos-stream-10-image-end-of-support"
    },
    {
      "slug": "multi-sql-server-2019-end-of-support",
      "title": "SQL Server 2019 end of support",
      "summary": "End of extended support for SQL Server 2019: 8 Jan 2030. After the end of support, Microsoft no longer provides servicing and support for the product.",
      "cloud": "multi",
      "service": "SQL Server",
      "service_slug": "sql-server",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-01-08",
      "effective_precision": "day",
      "impact": "Each version of SQL Server gets mainstream support followed by extended support, and extended support includes only security updates. End of support means the product reached the end of its support lifecycle, and Microsoft no longer provides servicing and support for it.\n\n- For some releases, customers have the option to purchase Extended Security Updates.\n- Extended Security Updates do not include new features, functional improvements, or customer-requested fixes. Security fixes are limited to fixes rated as Critical.",
      "migration_path": "Microsoft lists these options in [SQL Server end of support options](https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview):\n\n1. Upgrade to a current version of SQL Server, for example with [Upgrade SQL Server Using the Installation Wizard (Setup)](https://learn.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup?view=sql-server-ver17). The [SQL Server migration component in SQL Server Management Studio](https://learn.microsoft.com/en-us/ssms/migrate-sql-server-component) can help detect compatibility problems in the new version.\n2. Or [migrate](https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/) the workload to Azure SQL Managed Instance, Azure SQL Database, or an Azure Virtual Machine.\n3. Or, where Extended Security Updates are offered for the release, subscribe to them and stay on the current environment until you can upgrade or migrate. Only customers with Software Assurance or subscription licenses can use this option, and only for three years.",
      "replacement": null,
      "affected_versions": [
        "15.0"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/sql-server-2019",
      "extra_source_urls": [
        "https://endoflife.date/mssqlserver"
      ],
      "vendor_ref": "mssqlserver@15.0",
      "last_checked_at": "2026-11-12T09:55:53.034Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-sql-server-2019-end-of-support"
    },
    {
      "slug": "aws-elasticache-redis-oss-6-extended-support-end-of-support",
      "title": "Amazon ElastiCache for Redis OSS: Redis OSS 6 end of extended support",
      "summary": "End of Extended Support and version end of life for Redis OSS 6 on Amazon ElastiCache: 31 Jan 2030. After that date, ElastiCache attempts to upgrade caches still running it to a newer engine version under standard support.",
      "cloud": "aws",
      "service": "Amazon ElastiCache for Redis OSS",
      "service_slug": "elasticache-redis",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-01-31",
      "effective_precision": "day",
      "impact": "31 Jan 2030 is the end of Extended Support and the version end of life for Redis OSS 6. If the engine is not upgraded, after that date Amazon ElastiCache attempts to upgrade it to a newer engine version that is supported under standard support. If that upgrade fails, AWS reserves the right to delete the cache, and states that it preserves the data from that engine before doing so.",
      "migration_path": "1. Upgrade the engine to a newer engine version before the end of Extended Support date. AWS lists this as the customer's responsibility.\n2. On a node-based cluster, start the upgrade by modifying the cluster or replication group and specifying a new engine version. See [Modifying a replication group](https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/Replication.Modify.html).\n3. Test the new version with your application before deploying it in production.\n4. AWS states that some existing ElastiCache for Redis OSS engines can also be upgraded to a Valkey engine.",
      "replacement": null,
      "affected_versions": [
        "6"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/engine-versions.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-elasticache-redis"
      ],
      "vendor_ref": "amazon-elasticache-redis@6",
      "last_checked_at": "2026-11-12T09:55:41.392Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-elasticache-redis-oss-6-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-14-extended-support-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 14 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for PostgreSQL 14 on Amazon Aurora PostgreSQL: 28 Feb 2030. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-02-28",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 28 Feb 2030. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- New major PostgreSQL versions might contain database changes that are not backward-compatible with existing applications.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "14"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@14",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-14-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-17-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 17 end of standard support",
      "summary": "Aurora end of standard support date for PostgreSQL 17 on Amazon Aurora PostgreSQL: 28 Feb 2030. After that date, a database can keep running this major version under RDS Extended Support, for an additional cost.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-02-28",
      "effective_precision": "day",
      "impact": "RDS Extended Support allows a database to keep running this major version after 28 Feb 2030, for an [additional cost](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html).\n\n- Aurora automatically enrolls a DB instance after that date if RDS Extended Support was enabled at creation or restoration.\n- It provides security updates for critical and high CVEs, bug fixes for critical issues, and support cases.\n- Charges apply only to certain minor versions. The [release calendar](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html) lists the eligible minor versions for each major version.\n- Enrollment can be changed at any time, at the cluster level. Disabling it after that date upgrades the instance or cluster automatically to the next supported major version.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "17"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@17",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-17-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-14-extended-support-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 14 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for PostgreSQL 14 on Amazon RDS for PostgreSQL: 28 Feb 2030. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-02-28",
      "effective_precision": "day",
      "impact": "After the RDS end of Extended Support date (28 Feb 2030), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 14.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "14"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@14",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-14-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17 end of standard support",
      "summary": "RDS end of standard support date for PostgreSQL 17 on Amazon RDS for PostgreSQL: 28 Feb 2030. A database can keep running this version past that date under RDS Extended Support, for an additional cost, until the RDS end of Extended Support date.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-02-28",
      "effective_precision": "day",
      "impact": "A database can continue running PostgreSQL 17 past the RDS end of standard support date under RDS Extended Support, for an additional cost (see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html)), until the RDS end of Extended Support date.\n\n- If RDS Extended Support was enabled when the DB instance was created or restored, Amazon RDS enrolls it automatically after the RDS end of standard support date, with no change to the database engine, uptime or performance.\n- RDS Extended Support provides security updates for critical and high CVEs, bug fixes and patches for critical issues, and the ability to open support cases.\n- If enrollment is disabled for a DB instance or DB cluster that is already past its standard support end date, it automatically upgrades to the next supported major version.\n- After the RDS end of Extended Support date, Amazon RDS automatically upgrades databases not yet on a supported major version.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. To stay on PostgreSQL 17 under RDS Extended Support, the enrollment status of an existing DB instance or DB cluster can be changed with the EngineLifecycleSupport parameter using the AWS CLI or RDS API. For Multi-AZ DB clusters, modify the setting at the cluster level. RDS Extended Support has an additional cost, see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "replacement": null,
      "affected_versions": [
        "17"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@17",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-end-of-support"
    },
    {
      "slug": "azure-functions-python-3-15-end-of-support",
      "title": "Azure Functions: Python 3.15 end of support",
      "summary": "End of support date for Python 3.15 on Azure Functions: Apr 2030. After that date, function apps on this version continue to run but aren't eligible for new features, security patches, and performance optimizations.",
      "cloud": "azure",
      "service": "Azure Functions",
      "service_slug": "functions",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-04-01",
      "effective_precision": "month",
      "impact": "Azure Functions reduces support in phases as language versions reach their end-of-life dates. Support ends on the earlier of the community end-of-support date or the end-of-support date of the underlying base operating system.\n\n- Notification phase: the Functions team emails you about retirements that affect your function apps.\n- Retirement phase, after the end-of-life date: apps on Python 3.15 can still be created and deployed, and they continue to run.\n- They get no new features, security patches, or performance optimizations until upgraded.\n- If required, in certain cases Microsoft can limit the instances allocated to these apps, including limiting scaling to 1 instance.\n- Apps on an unsupported version must upgrade before receiving support.",
      "migration_path": "1. Follow [Update language stack versions in Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/update-language-versions). The steps depend on the language, the operating system and the hosting plan. For .NET, the article covers the isolated worker model only. An app on the in-process model must [migrate to the isolated worker model](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model).\n2. Review dependencies before the update (extension bundles, binding extensions, package dependencies and local tools). Then test and verify the function app code locally on the new target version.\n3. Make sure the function app runs on the latest version of the Functions runtime (version 4.x). If it does not, follow the runtime migration articles that the update article links rather than just changing the FUNCTIONS_EXTENSION_VERSION setting.\n4. If the app runs on Linux in a Consumption plan, check that the target version is offered there. The Linux Consumption plan isn't getting any new language versions. See [Migrate your apps to the Flex Consumption plan](https://learn.microsoft.com/en-us/azure/azure-functions/migration/migrate-plan-consumption-to-flex). The update article also states that you can't change the Python version when the function app runs in a Consumption plan.\n5. Publish the function app updates, then update the stack configuration. The method depends on whether the app runs on Windows or on Linux. The function app restarts after the version update and is unavailable for a brief period, typically 30-60 seconds. The article describes publishing to a staging slot to limit downtime, and notes that the Flex Consumption plan does not support slots.\n6. After the function app restarts, verify that the language version update was successful and that the functions work as expected.",
      "replacement": null,
      "affected_versions": [
        "3.15"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/azure-functions/functions-versions",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/azure/azure-functions/language-support-policy"
      ],
      "vendor_ref": "functions@python:3.15",
      "last_checked_at": "2026-11-12T09:56:07.301Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-functions-python-3-15-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-pro-20-04-lts-image-end-of-support",
      "title": "Compute Engine: Ubuntu Pro 20.04 LTS image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu Pro 20.04 LTS public image on Compute Engine: Apr 2030. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu Pro 20.04 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu Pro 20.04 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-pro-2004-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-pro-20-04-lts-image-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-python-3-13-retirement",
      "title": "Cloud Run: Python 3.13 decommission",
      "summary": "Decommission date for Python 3.13 on Cloud Run: 10 Apr 2030. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2030-04-10",
      "effective_precision": "day",
      "impact": "The decommission date of Python 3.13 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-python-3-13-retirement"
    },
    {
      "slug": "gcp-compute-engine-rhel-10-2-for-sap-image-end-of-support",
      "title": "Compute Engine: RHEL 10.2 for SAP image end of support",
      "summary": "EOS and image deprecation date for the RHEL 10.2 for SAP public image on Compute Engine: May 2030. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 10.2 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 10.2 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-10-2-sap-ha",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-10-2-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-9-8-for-sap-image-end-of-support",
      "title": "Compute Engine: RHEL 9.8 for SAP image end of support",
      "summary": "EOS and image deprecation date for the RHEL 9.8 for SAP public image on Compute Engine: May 2030. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 9.8 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 9.8 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-9-8-sap-ha",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-9-8-for-sap-image-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-php-8-5-retirement",
      "title": "Cloud Run: PHP 8.5 decommission",
      "summary": "Decommission date for PHP 8.5 on Cloud Run: 30 Jun 2030. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2030-06-30",
      "effective_precision": "day",
      "impact": "The decommission date of PHP 8.5 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-php-8-5-retirement"
    },
    {
      "slug": "gcp-compute-engine-debian-13-image-end-of-support",
      "title": "Compute Engine: Debian 13 image end of support",
      "summary": "EOS and image deprecation date for the Debian 13 public image on Compute Engine: 30 Jun 2030. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-06-30",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Debian 13 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Debian 13"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "debian-13",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-debian-13-image-end-of-support"
    },
    {
      "slug": "azure-app-service-java-25-end-of-support",
      "title": "Azure App Service: Java 25 end of support",
      "summary": "End of support date for Java 25 on Azure App Service: Sep 2030. Apps that use this version continue to run unchanged, but App Service can't provide security patches or related customer support for it past that date.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-09-01",
      "effective_precision": "month",
      "impact": "After Sep 2030, apps that use Java 25 continue to run unchanged, but App Service can't provide security patches or related customer support for that runtime version.\n\n- An app on an unsupported language version must be upgraded to a supported version before it can get App Service support.\n- App Service sends reminder notifications about end-of-support dates to subscription owners.\n- Contributors, readers, or other roles don't directly receive notifications unless they opt in through Service Health Alerts.\n- For Java, the page adds that developers who use a supported Java runtime that is retired receive a deprecation notice at least six months before the runtime is retired.",
      "migration_path": "1. Find the language version the app uses. The [language runtime support policy](https://learn.microsoft.com/en-us/azure/app-service/language-support-policy) links \"Show language version\" resources for .NET, Java, Node, Python and PHP.\n2. Choose a supported version of Java. The same page links the support timeline of each language community.\n3. Set the new language version for the app. The same page links \"Set language versions\" resources for .NET, Java, Node, Python and PHP.",
      "replacement": null,
      "affected_versions": [
        "25"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy",
      "extra_source_urls": [
        "https://learn.microsoft.com/en-us/java/openjdk/support"
      ],
      "vendor_ref": "appservice@java:25",
      "last_checked_at": "2026-11-12T09:56:00.082Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-java-25-end-of-support"
    },
    {
      "slug": "azure-app-service-python-3-14-end-of-support",
      "title": "Azure App Service: Python 3.14 end of support",
      "summary": "End of support date for Python 3.14 on Azure App Service: Oct 2030. Apps that use this version continue to run unchanged, but App Service can't provide security patches or related customer support for it past that date.",
      "cloud": "azure",
      "service": "Azure App Service",
      "service_slug": "app-service",
      "category": "runtime",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-10-01",
      "effective_precision": "month",
      "impact": "After Oct 2030, apps that use Python 3.14 continue to run unchanged, but App Service can't provide security patches or related customer support for that runtime version.\n\n- An app on an unsupported language version must be upgraded to a supported version before it can get App Service support.\n- App Service sends reminder notifications about end-of-support dates to subscription owners.\n- Contributors, readers, or other roles don't directly receive notifications unless they opt in through Service Health Alerts.\n- For Java, the page adds that developers who use a supported Java runtime that is retired receive a deprecation notice at least six months before the runtime is retired.",
      "migration_path": "1. Find the language version the app uses. The [language runtime support policy](https://learn.microsoft.com/en-us/azure/app-service/language-support-policy) links \"Show language version\" resources for .NET, Java, Node, Python and PHP.\n2. Choose a supported version of Python. The same page links the support timeline of each language community.\n3. Set the new language version for the app. The same page links \"Set language versions\" resources for .NET, Java, Node, Python and PHP.",
      "replacement": null,
      "affected_versions": [
        "3.14"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/app-service/language-support-policy",
      "extra_source_urls": [
        "https://devguide.python.org/versions/"
      ],
      "vendor_ref": "appservice@python:3.14",
      "last_checked_at": "2026-11-12T09:56:00.082Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-app-service-python-3-14-end-of-support"
    },
    {
      "slug": "azure-devops-server-2020-update-1-end-of-support",
      "title": "Azure DevOps Server 2020 Update 1 end of support",
      "summary": "endoflife.date lists 8 Oct 2030 as the end of security support for Azure DevOps Server 2020 Update 1. Microsoft publishes the specific end of support dates and details in its Lifecycle product search.",
      "cloud": "azure",
      "service": "Azure DevOps Server",
      "service_slug": "devops-server",
      "category": "other",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-10-08",
      "effective_precision": "day",
      "impact": "Prior to 2019, the product was known as Team Foundation Server (TFS). Microsoft publishes specific end of support dates and details in its [Lifecycle product search](https://learn.microsoft.com/en-us/lifecycle/products/). For releases under the Microsoft Fixed Lifecycle Policy, the policy states that, to be eligible for support, customers may be required to deploy the latest Service Pack or update.",
      "migration_path": "Follow [Upgrade your deployment to the latest version of Azure DevOps Server](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started):\n\n1. Have your Azure DevOps Server license and product key ready, and administrative access and credentials for the service accounts.\n2. Review the [system requirements](https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server) for the target server, which may include updates to operating systems, SQL Server versions, and hardware.\n3. Create a complete and consistent set of backups for all Azure DevOps databases.\n4. If you upgrade in place, perform a trial in a pre-production environment: [Pre-production dry run](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-server).\n5. Plan for downtime. The deployment is offline during the upgrade.",
      "replacement": null,
      "affected_versions": [
        "2020.1"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/azure-devops-server-2020",
      "extra_source_urls": [
        "https://endoflife.date/azure-devops-server"
      ],
      "vendor_ref": "azure-devops-server@2020.1",
      "last_checked_at": "2026-11-12T09:55:46.498Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-devops-server-2020-update-1-end-of-support"
    },
    {
      "slug": "azure-devops-server-2020-end-of-support",
      "title": "Azure DevOps Server 2020 end of support",
      "summary": "endoflife.date lists 8 Oct 2030 as the end of security support for Azure DevOps Server 2020. Microsoft publishes the specific end of support dates and details in its Lifecycle product search.",
      "cloud": "azure",
      "service": "Azure DevOps Server",
      "service_slug": "devops-server",
      "category": "other",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-10-08",
      "effective_precision": "day",
      "impact": "Prior to 2019, the product was known as Team Foundation Server (TFS). Microsoft publishes specific end of support dates and details in its [Lifecycle product search](https://learn.microsoft.com/en-us/lifecycle/products/). For releases under the Microsoft Fixed Lifecycle Policy, the policy states that, to be eligible for support, customers may be required to deploy the latest Service Pack or update.",
      "migration_path": "Follow [Upgrade your deployment to the latest version of Azure DevOps Server](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started):\n\n1. Have your Azure DevOps Server license and product key ready, and administrative access and credentials for the service accounts.\n2. Review the [system requirements](https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server) for the target server, which may include updates to operating systems, SQL Server versions, and hardware.\n3. Create a complete and consistent set of backups for all Azure DevOps databases.\n4. If you upgrade in place, perform a trial in a pre-production environment: [Pre-production dry run](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-server).\n5. Plan for downtime. The deployment is offline during the upgrade.",
      "replacement": null,
      "affected_versions": [
        "2020.0"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/azure-devops-server-2020",
      "extra_source_urls": [
        "https://endoflife.date/azure-devops-server"
      ],
      "vendor_ref": "azure-devops-server@2020.0",
      "last_checked_at": "2026-11-12T09:55:46.498Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-devops-server-2020-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-16-0-for-sap-image-end-of-support",
      "title": "Compute Engine: SLES 16.0 for SAP image end of support",
      "summary": "EOS and image deprecation date for the SLES 16.0 for SAP public image on Compute Engine: Nov 2030. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-11-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 16.0 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 16.0 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-sap-16-0-x86-64",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-16-0-for-sap-image-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-6-8-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 6.8 end of extended support",
      "summary": "End of extended support date for Elasticsearch 6.8 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2030. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2030 is the end of extended support date for Elasticsearch 6.8 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 6.8"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 6.8",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-6-8-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-elasticsearch-7-10-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: Elasticsearch 7.10 end of extended support",
      "summary": "End of extended support date for Elasticsearch 7.10 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2030. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2030 is the end of extended support date for Elasticsearch 7.10 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "Elasticsearch 7.10"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [],
      "vendor_ref": "amazon-opensearch@Elasticsearch 7.10",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-elasticsearch-7-10-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-1-3-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 1.3 end of extended support",
      "summary": "End of extended support date for OpenSearch 1.3 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2030. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2030 is the end of extended support date for OpenSearch 1.3 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "1.3"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@1.3",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-1-3-extended-support-end-of-support"
    },
    {
      "slug": "aws-opensearch-2-19-extended-support-end-of-support",
      "title": "Amazon OpenSearch Service: OpenSearch 2.19 end of extended support",
      "summary": "End of extended support date for OpenSearch 2.19 on Amazon OpenSearch Service, as listed in the AWS end of support schedule: 7 Nov 2030. AWS recommends upgrading to the latest available OpenSearch version.",
      "cloud": "aws",
      "service": "Amazon OpenSearch Service",
      "service_slug": "opensearch",
      "category": "service",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-11-07",
      "effective_precision": "day",
      "impact": "7 Nov 2030 is the end of extended support date for OpenSearch 2.19 in the AWS end of support schedule. For versions in extended support, AWS offers critical security fixes for at least 12 months after standard support ends. Extended support charges apply automatically when a domain runs a version that is no longer under standard support. The schedule has original and updated columns for this date, and some cells hold no date. Where the original date has passed and the date was extended, AWS applies a different extended support fee. See the [pricing page](https://aws.amazon.com/opensearch-service/pricing/#Extended_support_costs). The page does not state what happens to a domain after this date. See the [Extended Support FAQ](https://aws.amazon.com/opensearch-service/faqs/#awt-content-topics#ams#c111#extended-support-9).",
      "migration_path": "1. Upgrade the domain to a supported version. AWS recommends the latest available OpenSearch version. See [Upgrading Amazon OpenSearch Service domains](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html).\n2. Check [Supported upgrade paths](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/version-migration.html#supported-upgrade-paths) for your current and target versions. The table lists a target version for each starting version it covers. Its earliest Elasticsearch starting version is Elasticsearch 5.x. Some paths require an intermediate upgrade or reindexing first.\n3. [Take a manual snapshot](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/managedomains-snapshots.html) of the domain as a backup.\n4. Run the pre-upgrade check to find issues that could block the upgrade.\n5. Choose an upgrade method that the page lists as available for your version. An in-place upgrade is available for domains that run OpenSearch 1.0 or later, or Elasticsearch 5.1 or later. AWS states that an in-place upgrade cannot be paused, canceled or rolled back. A clone-based upgrade is available for domains that run Elasticsearch 7.10 or OpenSearch 1.1 or later, for the upgrade paths and within the Region and domain limitations the page lists. AWS describes two ways to upgrade a domain, and the page lists neither as available for an Elasticsearch version earlier than 5.1.\n6. If Amazon Data Firehose or Amazon CloudWatch Logs streams data to the domain, check that the service supports the newer version before migrating.",
      "replacement": null,
      "affected_versions": [
        "2.19"
      ],
      "source_url": "https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html#choosing-version",
      "extra_source_urls": [
        "https://endoflife.date/amazon-opensearch"
      ],
      "vendor_ref": "amazon-opensearch@2.19",
      "last_checked_at": "2026-11-12T09:55:42.010Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-opensearch-2-19-extended-support-end-of-support"
    },
    {
      "slug": "azure-postgresql-18-end-of-support",
      "title": "Azure Database for PostgreSQL: PostgreSQL 18 end of standard support",
      "summary": "Azure Standard Support End Date for PostgreSQL 18 on Azure Database for PostgreSQL: 14 Nov 2030. Once the Azure Standard Support period ends, eligible servers still running the version are automatically enrolled in extended support.",
      "cloud": "azure",
      "service": "Azure Database for PostgreSQL",
      "service_slug": "postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-11-14",
      "effective_precision": "day",
      "impact": "Once the Azure Standard Support period ends, an eligible server still running PostgreSQL 18 is automatically enrolled in extended support. The eligible versions table lists PostgreSQL 11, 12, 13 and 14.\n\n- Extended support provides security patches, critical bug fixes and technical support for up to three extra years. It does not include new features, performance enhancements or support for minor version upgrades.\n- Charges apply after any applicable grace period unless the server is upgraded to a supported version, and only to servers in a Succeeded (running) state. A one-month grace period is provided for versions 11, 12 and 13. A server that regional capacity constraints prevent from upgrading might be temporarily excluded from billing.\n- The version policy page lists restrictions that apply after the retirement date of a version, without stating whether that date is 14 Nov 2030: new servers cannot be created on a retired version, while point-in-time recoveries and read replicas of existing servers remain possible.\n- The same page says that when the community retires a version, Azure stops applying bug or security patches to the database engine. The extended support page lists security patches and critical bug fixes as part of extended support.",
      "migration_path": "1. Run the upgrade validation checks in the Azure portal or with the Azure CLI. See [Run upgrade validation checks](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/how-to-run-upgrade-validation-checks).\n2. Resolve any blocking issues the checks report, then rerun validation.\n3. Ensure the server has at least 10-20% free storage available before starting the upgrade.\n4. If the server uses geo-replication, delete the read replica (including any cascading read replica) before upgrading the primary server. The replica can be re-created after the upgrade.\n5. Run an in-place major version upgrade to a PostgreSQL version that Azure currently supports. The service can skip versions and upgrade directly to a later version. Servers that use TimescaleDB are limited to specific source and target version combinations, and an upgrade from PostgreSQL 11 first requires SCRAM authentication to be configured. Once the server runs a supported version, extended support charges no longer apply. See [Major version upgrades](https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-major-version-upgrade).\n6. Plan for the fact that there is no automated way to revert after a successful upgrade. A point-in-time recovery to a time before the upgrade restores the previous version on a new server.",
      "replacement": null,
      "affected_versions": [
        "18"
      ],
      "source_url": "https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/concepts-version-policy",
      "extra_source_urls": [
        "https://endoflife.date/azure-database-for-postgresql"
      ],
      "vendor_ref": "azure-database-for-postgresql@18",
      "last_checked_at": "2026-11-12T09:55:36.471Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-postgresql-18-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-16-0-image-end-of-support",
      "title": "Compute Engine: SLES 16.0 image end of support",
      "summary": "EOS and image deprecation date for the SLES 16.0 public image on Compute Engine: Dec 2030. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2030-12-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 16.0 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 16.0"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-16-0-x86-64",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-16-0-image-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-15-extended-support-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 15 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for PostgreSQL 15 on Amazon Aurora PostgreSQL: 28 Feb 2031. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-02-28",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 28 Feb 2031. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- New major PostgreSQL versions might contain database changes that are not backward-compatible with existing applications.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "15"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@15",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-15-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-18-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 18 end of standard support",
      "summary": "Aurora end of standard support date for PostgreSQL 18 on Amazon Aurora PostgreSQL: 28 Feb 2031. After that date, a database can keep running this major version under RDS Extended Support, for an additional cost.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-02-28",
      "effective_precision": "day",
      "impact": "RDS Extended Support allows a database to keep running this major version after 28 Feb 2031, for an [additional cost](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html).\n\n- Aurora automatically enrolls a DB instance after that date if RDS Extended Support was enabled at creation or restoration.\n- It provides security updates for critical and high CVEs, bug fixes for critical issues, and support cases.\n- Charges apply only to certain minor versions. The [release calendar](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html) lists the eligible minor versions for each major version.\n- Enrollment can be changed at any time, at the cluster level. Disabling it after that date upgrades the instance or cluster automatically to the next supported major version.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "18"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@18",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-18-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-15-extended-support-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 15 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for PostgreSQL 15 on Amazon RDS for PostgreSQL: 28 Feb 2031. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-02-28",
      "effective_precision": "day",
      "impact": "After the RDS end of Extended Support date (28 Feb 2031), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 15.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "15"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@15",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-15-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-18-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 18 end of standard support",
      "summary": "RDS end of standard support date for PostgreSQL 18 on Amazon RDS for PostgreSQL: 28 Feb 2031. A database can keep running this version past that date under RDS Extended Support, for an additional cost, until the RDS end of Extended Support date.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-02-28",
      "effective_precision": "day",
      "impact": "A database can continue running PostgreSQL 18 past the RDS end of standard support date under RDS Extended Support, for an additional cost (see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html)), until the RDS end of Extended Support date.\n\n- If RDS Extended Support was enabled when the DB instance was created or restored, Amazon RDS enrolls it automatically after the RDS end of standard support date, with no change to the database engine, uptime or performance.\n- RDS Extended Support provides security updates for critical and high CVEs, bug fixes and patches for critical issues, and the ability to open support cases.\n- If enrollment is disabled for a DB instance or DB cluster that is already past its standard support end date, it automatically upgrades to the next supported major version.\n- After the RDS end of Extended Support date, Amazon RDS automatically upgrades databases not yet on a supported major version.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. To stay on PostgreSQL 18 under RDS Extended Support, the enrollment status of an existing DB instance or DB cluster can be changed with the EngineLifecycleSupport parameter using the AWS CLI or RDS API. For Multi-AZ DB clusters, modify the setting at the cluster level. RDS Extended Support has an additional cost, see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "replacement": null,
      "affected_versions": [
        "18"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@18",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-18-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-26-04-lts-image-end-of-support",
      "title": "Compute Engine: Ubuntu 26.04 LTS image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu 26.04 LTS public image on Compute Engine: Apr 2031. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu 26.04 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu 26.04 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-2604-lts-amd64",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-26-04-lts-image-end-of-support"
    },
    {
      "slug": "gcp-cloud-run-python-3-14-retirement",
      "title": "Cloud Run: Python 3.14 decommission",
      "summary": "Decommission date for Python 3.14 on Cloud Run: 10 Apr 2031. After that date, workloads on Google-managed base images can no longer be created or updated using the runtime, and workloads that still use it may be disabled.",
      "cloud": "gcp",
      "service": "Cloud Run",
      "service_slug": "cloud-run",
      "category": "runtime",
      "type": "retirement",
      "announced_date": null,
      "effective_date": "2031-04-10",
      "effective_precision": "day",
      "impact": "The decommission date of Python 3.14 starts the decommission period for that runtime on Cloud Run. The policy applies only to workloads that use Google-managed base images. Google states that key dates might be delayed.\n\n- During the deprecation period before that date, workloads can generally still be created and updated using the runtime.\n- After the decommission date, workloads can no longer be created or updated using the runtime.\n- Workloads that continue to use a decommissioned runtime may be disabled.\n- A decommissioned runtime receives no language, system package or OS patches.\n- Runtime customer support already ends at deprecation (\"Customer support\" row of the lifecycle table).",
      "migration_path": "1. Migrate workloads that use the runtime to a more up-to-date runtime from the [support schedule](https://docs.cloud.google.com/run/docs/runtime-support#support_schedule). Google advises doing this during the deprecation period.\n2. After the decommission date, a more up-to-date runtime is required to deploy workloads.",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://docs.cloud.google.com/run/docs/runtime-support",
      "extra_source_urls": [],
      "vendor_ref": null,
      "last_checked_at": "2026-11-12T09:56:10.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-cloud-run-python-3-14-retirement"
    },
    {
      "slug": "gcp-compute-engine-sles-15-sp7-for-sap-image-end-of-support",
      "title": "Compute Engine: SLES 15 SP7 for SAP image end of support",
      "summary": "EOS and image deprecation date for the SLES 15 SP7 for SAP public image on Compute Engine: Jul 2031. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-07-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 15 SP7 for SAP in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 15 SP7 for SAP"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-15-sp7-sap",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-15-sp7-for-sap-image-end-of-support"
    },
    {
      "slug": "azure-sphere-service-retirement",
      "title": "Azure Sphere retirement",
      "summary": "Retirement date for the Azure Sphere service: 31 Jul 2031. From that date the service stops supporting customer application, OS, bug and security updates, and DAA certificate issuance.",
      "cloud": "azure",
      "service": "Azure Sphere",
      "service_slug": "sphere",
      "category": "service",
      "type": "retirement",
      "announced_date": "2026-03-20",
      "effective_date": "2031-07-31",
      "effective_precision": "day",
      "impact": "From the retirement date, the Azure Sphere service stops supporting all customer application, OS, bug and security updates, along with DAA certificate issuance. Microsoft asked customers who needed additional MT3620 stock to express OEM license renewal and purchasing intent through the distributor, Avnet, before 31 July 2026.",
      "migration_path": "1. Evaluate hardware redesign to replace MT3620 silicon in future product iterations.\n2. Consider PSA/SESIP Level 3+, or similar, certified silicon as a guideline for silicon with similar security properties.\n3. Evaluate alternative Azure IoT and 3rd-party solutions alongside a new MCU. See the Azure IoT [documentation](https://learn.microsoft.com/azure/iot/) and [solutions](https://azure.microsoft.com/solutions/iot/).\n4. For questions, contact your Microsoft accounts team or [Microsoft Support](https://support.microsoft.com/).",
      "replacement": null,
      "affected_versions": [],
      "source_url": "https://azure.microsoft.com/updates?id=557123",
      "extra_source_urls": [
        "https://learn.microsoft.com/azure/iot/",
        "https://azure.microsoft.com/solutions/iot/"
      ],
      "vendor_ref": "557123",
      "last_checked_at": "2026-11-12T09:55:19.345Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-sphere-service-retirement"
    },
    {
      "slug": "gcp-compute-engine-windows-server-2022-image-end-of-support",
      "title": "Compute Engine: Windows Server 2022 image end of support",
      "summary": "EOS and image deprecation date for the Windows Server 2022 public image on Compute Engine: 14 Oct 2031. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-10-14",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Windows Server 2022 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Windows Server 2022"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "windows-2022",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-windows-server-2022-image-end-of-support"
    },
    {
      "slug": "multi-windows-server-2022-end-of-support",
      "title": "Windows Server 2022 end of support",
      "summary": "End of support for Windows Server 2022: 14 Oct 2031. Once a release reaches the end of support, security updates and bulletins end.",
      "cloud": "multi",
      "service": "Windows Server",
      "service_slug": "windows-server",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-10-14",
      "effective_precision": "day",
      "impact": "Windows Server Long Term Servicing Channel releases have a minimum of 10 years of support: five years of mainstream support and five years of extended support, which includes regular security updates. endoflife.date states that each Semi-Annual Channel release is supported for 18 months from the initial release, and that each Annual Channel release has 18 months of mainstream support plus 6 months of extended support. Once a release reaches the end of support, security updates and bulletins end, which Microsoft states can cause security or compliance issues.\n\n- endoflife.date states that for some releases, customers have the option to purchase Extended Security Updates. See [Lifecycle FAQ - Extended Security Updates](https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates).\n- Extended Security Updates do not include new features, customer-requested nonsecurity hotfixes, or design change requests.",
      "migration_path": "1. Choose an upgrade method with [Plan your Windows Server upgrade](https://learn.microsoft.com/en-us/windows-server/get-started/install-upgrade-migrate): in-place upgrade, clean install, migration, or cluster rolling upgrade.\n2. Check the [supported paths table](https://learn.microsoft.com/en-us/windows-server/get-started/install-upgrade-migrate#supported-in-place-upgrade-paths-by-version) and the [role and feature migration matrix](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-migrate-roles-features) for your configuration.\n3. Get a valid product key and activation method for the target version. Each Windows Server upgrade requires a separate license.\n4. Back up your system and important files before the in-place upgrade, clean install, or migration.\n5. For an in-place upgrade, follow [Perform an in-place upgrade of Windows Server](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-in-place).",
      "replacement": null,
      "affected_versions": [
        "2022"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/windows-server-2022",
      "extra_source_urls": [
        "https://endoflife.date/windows-server"
      ],
      "vendor_ref": "windows-server@2022",
      "last_checked_at": "2026-11-12T09:55:50.558Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-windows-server-2022-end-of-support"
    },
    {
      "slug": "oci-oracle-database-26ai-end-of-support",
      "title": "Oracle Database 26ai end of Premier Support",
      "summary": "End of Premier Support date for Oracle Database 26ai: 31 Dec 2031. This is the date that endoflife.date lists under Premier Support for the release.",
      "cloud": "oci",
      "service": "Oracle Database",
      "service_slug": "oracle-database",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2031-12-31",
      "effective_precision": "day",
      "impact": "The date is the one that endoflife.date lists under Premier Support for Oracle Database 26ai, for Oracle Database On-Premises Server Releases for Linux x86-64. endoflife.date notes that release dates may vary across cloud and on-premises offers and support stages, and reports two release types:\n\n- Long-Term Releases (LTR) have Extended Support after Premier Support.\n- Oracle may offer, for some LTR, one year of free Extended Support.\n- Innovation Releases have no Extended Support.\n- The endoflife.date table marks Long-Term Releases with LTR and shows the Extended Support status of each release.",
      "migration_path": "The Oracle Database documentation lists Install and Upgrade guides by release: [Oracle Database documentation](https://docs.oracle.com/en/database/oracle/oracle-database/).",
      "replacement": null,
      "affected_versions": [
        "23"
      ],
      "source_url": "https://endoflife.date/oracle-database",
      "extra_source_urls": [
        "https://support.oracle.com/knowledgefs?docId=742060"
      ],
      "vendor_ref": "oracle-database@23",
      "last_checked_at": "2026-11-12T09:55:56.483Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/oci-oracle-database-26ai-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-16-extended-support-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 16 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for PostgreSQL 16 on Amazon Aurora PostgreSQL: 28 Feb 2032. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-02-28",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 28 Feb 2032. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- New major PostgreSQL versions might contain database changes that are not backward-compatible with existing applications.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "16"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@16",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-16-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-16-extended-support-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 16 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for PostgreSQL 16 on Amazon RDS for PostgreSQL: 29 Feb 2032. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-02-29",
      "effective_precision": "day",
      "impact": "After the RDS end of Extended Support date (29 Feb 2032), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 16.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "16"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@16",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-16-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-mysql-version-8-4-end-of-support",
      "title": "Amazon Aurora MySQL: version 8.4 end of standard support",
      "summary": "Aurora end of standard support date for Amazon Aurora MySQL version 8.4: Apr 2032. AWS states that a major version can keep running past this date under RDS Extended Support, for a fee.",
      "cloud": "aws",
      "service": "Amazon Aurora MySQL",
      "service_slug": "aurora-mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-04-01",
      "effective_precision": "month",
      "impact": "AWS states that a major version can keep running past its standard support end date under RDS Extended Support, for an [additional cost](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/extended-support-charges.html). The [release calendar](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html#AuroraMySQL.release-calendars.major) lists Extended Support dates and eligible minor versions; some are \"To be determined\".\n\n- Aurora automatically enrolls a DB instance after that date if RDS Extended Support was enabled at creation or restoration.\n- It provides security updates for critical and high CVEs, bug fixes for critical issues, and support cases.\n- Charges apply only to certain minor versions.\n- Enrollment can be changed at any time, at the cluster level. Disabling it after that date upgrades the instance or cluster automatically to the next supported major version.",
      "migration_path": "1. Look up your type and version of cluster in [Aurora MySQL major version upgrade paths](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Compatibility). The table says whether the cluster can use the in-place upgrade mechanism and which action applies.\n2. Where the table points to a major version upgrade, plan it with [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). A major version upgrade needs more planning and testing than a minor version upgrade.\n3. Before an in-place upgrade, create a clone of the original cluster, perform an in-place upgrade of the clone immediately after creating it, and test application compatibility, performance and administration procedures on it.\n4. When the test cluster works properly, perform the in-place upgrade for the production cluster. See [How to perform an in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Upgrading.Procedure.html).\n5. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "8.4"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.release-calendars.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-mysql"
      ],
      "vendor_ref": "amazon-aurora-mysql@8.4",
      "last_checked_at": "2026-11-12T09:55:40.805Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-mysql-version-8-4-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-pro-22-04-lts-image-end-of-support",
      "title": "Compute Engine: Ubuntu Pro 22.04 LTS image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu Pro 22.04 LTS public image on Compute Engine: Apr 2032. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu Pro 22.04 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu Pro 22.04 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-pro-2204-lts",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-pro-22-04-lts-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-almalinux-9-image-end-of-support",
      "title": "Compute Engine: AlmaLinux 9 image end of support",
      "summary": "EOS and image deprecation date for the AlmaLinux 9 public image on Compute Engine: May 2032. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of AlmaLinux 9 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "AlmaLinux 9"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "almalinux-9",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-almalinux-9-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-9-image-end-of-support",
      "title": "Compute Engine: RHEL 9 image end of support",
      "summary": "EOS and image deprecation date for the RHEL 9 public image on Compute Engine: May 2032. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 9 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 9"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-9",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-9-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-9-image-end-of-support",
      "title": "Compute Engine: Rocky Linux 9 image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 9 public image on Compute Engine: May 2032. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 9 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 9"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-9",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-9-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-9-optimized-for-google-cloud-image-end-of-support",
      "title": "Compute Engine: Rocky Linux 9 optimized for Google Cloud image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 9 optimized for Google Cloud public image on Compute Engine: May 2032. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 9 optimized for Google Cloud in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 9 optimized for Google Cloud"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-9-optimized-gcp",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-9-optimized-for-google-cloud-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-oracle-linux-9-image-end-of-support",
      "title": "Compute Engine: Oracle Linux 9 image end of support",
      "summary": "EOS and image deprecation date for the Oracle Linux 9 public image on Compute Engine: Jun 2032. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-06-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Oracle Linux 9 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Oracle Linux 9"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "oracle-linux-9",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-oracle-linux-9-image-end-of-support"
    },
    {
      "slug": "oci-oracle-linux-9-end-of-support",
      "title": "Oracle Linux 9 end of Premier Support",
      "summary": "End of Premier Support date for Oracle Linux 9: 30 Jun 2032. This is the date that endoflife.date lists under Basic/Premier Support for the release.",
      "cloud": "oci",
      "service": "Oracle Linux",
      "service_slug": "oracle-linux",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-06-30",
      "effective_precision": "day",
      "impact": "The date is the one that endoflife.date lists under Basic/Premier Support for Oracle Linux 9. endoflife.date states:\n\n- Basic and Premier Support include patches, fixes, security patches and security alerts. Premier Support adds live kernel patching.\n- Once a new minor release is available, the older one is considered end of life, and users must upgrade to continue receiving security updates.\n- Extended Support is available for a limited time after Premier Support ends, as per agreement with Oracle, with extra fees.\n- Extended Support covers critical security errata and select high-impact critical bug fixes, for select packages.\n- Sustaining Support follows Extended Support and does not include new security fixes or alerts.",
      "migration_path": "Oracle has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [
        "9"
      ],
      "source_url": "https://endoflife.date/oracle-linux",
      "extra_source_urls": [
        "https://www.oracle.com/a/ocom/docs/elsp-lifetime-069338.pdf"
      ],
      "vendor_ref": "oracle-linux@9",
      "last_checked_at": "2026-11-12T09:55:55.860Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/oci-oracle-linux-9-end-of-support"
    },
    {
      "slug": "aws-rds-mysql-8-4-extended-support-end-of-support",
      "title": "Amazon RDS for MySQL: MySQL 8.4 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for MySQL 8.4 on Amazon RDS for MySQL: 31 Jul 2032. AWS states that once the RDS Extended Support period of a major engine version is over, Amazon RDS automatically upgrades the major engine version of a database not upgraded to a supported version.",
      "cloud": "aws",
      "service": "Amazon RDS for MySQL",
      "service_slug": "rds-mysql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2032-07-31",
      "effective_precision": "day",
      "impact": "31 Jul 2032 is the RDS end of Extended Support date that AWS lists for MySQL 8.4. AWS states that once the RDS Extended Support period of a major engine version is over, Amazon RDS automatically upgrades the major engine version of a database not upgraded to a supported version. The pages do not state which version that automatic upgrade targets, or how soon after the end of the period it runs.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- A completed upgrade cannot be reverted to the previous engine version.\n- Minor versions can reach end of Extended Support earlier.\n- RDS Extended Support is a paid offering up to that date: see [Amazon RDS Extended Support charges](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/extended-support-charges.html).",
      "migration_path": "1. Test the upgrade first: create a DB snapshot of the DB instance, restore it to a new DB instance, and start a version upgrade on that new instance.\n2. Find the valid upgrade targets for the DB instance in the AWS Management Console or with the `aws rds describe-db-engine-versions` AWS CLI command. AWS lists the supported major version upgrades on its [MySQL on Amazon RDS versions](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html) page.\n3. If the DB instance uses read replicas, upgrade all of the read replicas before the source instance.\n4. Start the major version upgrade by modifying the DB instance, after following [Major version upgrades for RDS for MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MySQL.Major.html).\n5. Downtime for the major version upgrade can be reduced with a blue/green deployment: [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n6. Enrollment in RDS Extended Support ends the day an upgrade completes to an engine version that is still under RDS standard support. An upgrade to a version that is itself under RDS Extended Support does not end it: check the support dates of the target version in [Supported MySQL major versions on Amazon RDS](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html#MySQL.Concepts.VersionMgmt.ReleaseCalendar).",
      "replacement": null,
      "affected_versions": [
        "8.4"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL.Concepts.VersionMgmt.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-mysql"
      ],
      "vendor_ref": "amazon-rds-mysql@8.4",
      "last_checked_at": "2026-11-12T09:55:38.611Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-mysql-8-4-extended-support-end-of-support"
    },
    {
      "slug": "azure-devops-server-2022-update-1-end-of-support",
      "title": "Azure DevOps Server 2022 Update 1 end of support",
      "summary": "endoflife.date lists 11 Jan 2033 as the end of security support for Azure DevOps Server 2022 Update 1. Microsoft publishes the specific end of support dates and details in its Lifecycle product search.",
      "cloud": "azure",
      "service": "Azure DevOps Server",
      "service_slug": "devops-server",
      "category": "other",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2033-01-11",
      "effective_precision": "day",
      "impact": "Prior to 2019, the product was known as Team Foundation Server (TFS). Microsoft publishes specific end of support dates and details in its [Lifecycle product search](https://learn.microsoft.com/en-us/lifecycle/products/). For releases under the Microsoft Fixed Lifecycle Policy, the policy states that, to be eligible for support, customers may be required to deploy the latest Service Pack or update.",
      "migration_path": "Follow [Upgrade your deployment to the latest version of Azure DevOps Server](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started):\n\n1. Have your Azure DevOps Server license and product key ready, and administrative access and credentials for the service accounts.\n2. Review the [system requirements](https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server) for the target server, which may include updates to operating systems, SQL Server versions, and hardware.\n3. Create a complete and consistent set of backups for all Azure DevOps databases.\n4. If you upgrade in place, perform a trial in a pre-production environment: [Pre-production dry run](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-server).\n5. Plan for downtime. The deployment is offline during the upgrade.",
      "replacement": null,
      "affected_versions": [
        "2022.1"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/azure-devops-server-2022",
      "extra_source_urls": [
        "https://endoflife.date/azure-devops-server"
      ],
      "vendor_ref": "azure-devops-server@2022.1",
      "last_checked_at": "2026-11-12T09:55:46.498Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-devops-server-2022-update-1-end-of-support"
    },
    {
      "slug": "azure-devops-server-2022-update-2-end-of-support",
      "title": "Azure DevOps Server 2022 Update 2 end of support",
      "summary": "endoflife.date lists 11 Jan 2033 as the end of security support for Azure DevOps Server 2022 Update 2. Microsoft publishes the specific end of support dates and details in its Lifecycle product search.",
      "cloud": "azure",
      "service": "Azure DevOps Server",
      "service_slug": "devops-server",
      "category": "other",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2033-01-11",
      "effective_precision": "day",
      "impact": "Prior to 2019, the product was known as Team Foundation Server (TFS). Microsoft publishes specific end of support dates and details in its [Lifecycle product search](https://learn.microsoft.com/en-us/lifecycle/products/). For releases under the Microsoft Fixed Lifecycle Policy, the policy states that, to be eligible for support, customers may be required to deploy the latest Service Pack or update.",
      "migration_path": "Follow [Upgrade your deployment to the latest version of Azure DevOps Server](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started):\n\n1. Have your Azure DevOps Server license and product key ready, and administrative access and credentials for the service accounts.\n2. Review the [system requirements](https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server) for the target server, which may include updates to operating systems, SQL Server versions, and hardware.\n3. Create a complete and consistent set of backups for all Azure DevOps databases.\n4. If you upgrade in place, perform a trial in a pre-production environment: [Pre-production dry run](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-server).\n5. Plan for downtime. The deployment is offline during the upgrade.",
      "replacement": null,
      "affected_versions": [
        "2022.2"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/azure-devops-server-2022",
      "extra_source_urls": [
        "https://endoflife.date/azure-devops-server"
      ],
      "vendor_ref": "azure-devops-server@2022.2",
      "last_checked_at": "2026-11-12T09:55:46.498Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-devops-server-2022-update-2-end-of-support"
    },
    {
      "slug": "azure-devops-server-2022-end-of-support",
      "title": "Azure DevOps Server 2022 end of support",
      "summary": "endoflife.date lists 11 Jan 2033 as the end of security support for Azure DevOps Server 2022. Microsoft publishes the specific end of support dates and details in its Lifecycle product search.",
      "cloud": "azure",
      "service": "Azure DevOps Server",
      "service_slug": "devops-server",
      "category": "other",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2033-01-11",
      "effective_precision": "day",
      "impact": "Prior to 2019, the product was known as Team Foundation Server (TFS). Microsoft publishes specific end of support dates and details in its [Lifecycle product search](https://learn.microsoft.com/en-us/lifecycle/products/). For releases under the Microsoft Fixed Lifecycle Policy, the policy states that, to be eligible for support, customers may be required to deploy the latest Service Pack or update.",
      "migration_path": "Follow [Upgrade your deployment to the latest version of Azure DevOps Server](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/get-started):\n\n1. Have your Azure DevOps Server license and product key ready, and administrative access and credentials for the service accounts.\n2. Review the [system requirements](https://learn.microsoft.com/en-us/azure/devops/server/requirements?view=azure-devops-server) for the target server, which may include updates to operating systems, SQL Server versions, and hardware.\n3. Create a complete and consistent set of backups for all Azure DevOps databases.\n4. If you upgrade in place, perform a trial in a pre-production environment: [Pre-production dry run](https://learn.microsoft.com/en-us/azure/devops/server/upgrade/pre-production?view=azure-devops-server).\n5. Plan for downtime. The deployment is offline during the upgrade.",
      "replacement": null,
      "affected_versions": [
        "2022.0"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/azure-devops-server-2022",
      "extra_source_urls": [
        "https://endoflife.date/azure-devops-server"
      ],
      "vendor_ref": "azure-devops-server@2022.0",
      "last_checked_at": "2026-11-12T09:55:46.498Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/azure-devops-server-2022-end-of-support"
    },
    {
      "slug": "multi-sql-server-2022-end-of-support",
      "title": "SQL Server 2022 end of support",
      "summary": "End of extended support for SQL Server 2022: 11 Jan 2033. After the end of support, Microsoft no longer provides servicing and support for the product.",
      "cloud": "multi",
      "service": "SQL Server",
      "service_slug": "sql-server",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2033-01-11",
      "effective_precision": "day",
      "impact": "Each version of SQL Server gets mainstream support followed by extended support, and extended support includes only security updates. End of support means the product reached the end of its support lifecycle, and Microsoft no longer provides servicing and support for it.\n\n- For some releases, customers have the option to purchase Extended Security Updates.\n- Extended Security Updates do not include new features, functional improvements, or customer-requested fixes. Security fixes are limited to fixes rated as Critical.",
      "migration_path": "Microsoft lists these options in [SQL Server end of support options](https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview):\n\n1. Upgrade to a current version of SQL Server, for example with [Upgrade SQL Server Using the Installation Wizard (Setup)](https://learn.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup?view=sql-server-ver17). The [SQL Server migration component in SQL Server Management Studio](https://learn.microsoft.com/en-us/ssms/migrate-sql-server-component) can help detect compatibility problems in the new version.\n2. Or [migrate](https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/) the workload to Azure SQL Managed Instance, Azure SQL Database, or an Azure Virtual Machine.\n3. Or, where Extended Security Updates are offered for the release, subscribe to them and stay on the current environment until you can upgrade or migrate. Only customers with Software Assurance or subscription licenses can use this option, and only for three years.",
      "replacement": null,
      "affected_versions": [
        "16.0"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/sql-server-2022",
      "extra_source_urls": [
        "https://endoflife.date/mssqlserver"
      ],
      "vendor_ref": "mssqlserver@16.0",
      "last_checked_at": "2026-11-12T09:55:53.034Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-sql-server-2022-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-17-extended-support-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 17 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for PostgreSQL 17 on Amazon Aurora PostgreSQL: 28 Feb 2033. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2033-02-28",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 28 Feb 2033. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- New major PostgreSQL versions might contain database changes that are not backward-compatible with existing applications.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "17"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@17",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-17-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-17-extended-support-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 17 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for PostgreSQL 17 on Amazon RDS for PostgreSQL: 28 Feb 2033. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2033-02-28",
      "effective_precision": "day",
      "impact": "After the RDS end of Extended Support date (28 Feb 2033), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 17.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "17"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@17",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-17-extended-support-end-of-support"
    },
    {
      "slug": "aws-aurora-postgresql-18-extended-support-end-of-support",
      "title": "Amazon Aurora PostgreSQL: PostgreSQL 18 end of RDS Extended Support",
      "summary": "End of RDS Extended Support date for PostgreSQL 18 on Amazon Aurora PostgreSQL: 28 Feb 2034. After RDS Extended Support ends, Aurora automatically upgrades databases that are still on this major version.",
      "cloud": "aws",
      "service": "Amazon Aurora PostgreSQL",
      "service_slug": "aurora-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2034-02-28",
      "effective_precision": "day",
      "impact": "End of RDS Extended Support date for this major version: 28 Feb 2034. RDS Extended Support is the paid offering that allows a database to keep running a major version past its Aurora end of standard support date. After RDS Extended Support ends, Aurora automatically upgrades the major engine version of any database that has not been upgraded to a supported version.\n\n- AWS recommends upgrading to a supported major engine version.\n- New major PostgreSQL versions might contain database changes that are not backward-compatible with existing applications.",
      "migration_path": "1. Test the upgrade first by following [Testing an upgrade of your production DB cluster to a new major version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html#USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Upgrade.preliminary), so that you know your applications can run on the new version.\n2. Manually upgrade the Aurora PostgreSQL DB cluster to the new major version. See [Performing a major version upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n3. Run the upgrade during the cluster's maintenance window or when operations are minimal, because a brief outage is possible.\n4. If an immediate switchover matters most, run the old and new clusters side by side with [Amazon Aurora Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments.html).",
      "replacement": null,
      "affected_versions": [
        "18"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/AuroraPostgreSQLReleaseNotes/aurorapostgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-aurora-postgresql"
      ],
      "vendor_ref": "amazon-aurora-postgresql@18",
      "last_checked_at": "2026-11-12T09:55:40.264Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-aurora-postgresql-18-extended-support-end-of-support"
    },
    {
      "slug": "aws-rds-postgresql-18-extended-support-end-of-support",
      "title": "Amazon RDS for PostgreSQL: PostgreSQL 18 end of RDS Extended Support",
      "summary": "RDS end of Extended Support date for PostgreSQL 18 on Amazon RDS for PostgreSQL: 28 Feb 2034. After that date, Amazon RDS automatically upgrades the major engine version of databases that are still on this version.",
      "cloud": "aws",
      "service": "Amazon RDS for PostgreSQL",
      "service_slug": "rds-postgresql",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2034-02-28",
      "effective_precision": "day",
      "impact": "After the RDS end of Extended Support date (28 Feb 2034), Amazon RDS automatically upgrades the major engine version of databases still on PostgreSQL 18.\n\n- Major version upgrades can contain database changes that are not backward-compatible with existing applications.\n- After an upgrade is complete, the database cannot revert to the previous version of the DB engine.",
      "migration_path": "1. Before a major version upgrade, follow the steps in [Choosing a major version for an RDS for PostgreSQL upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.html).\n2. Find the valid upgrade targets for the database in the AWS Management Console or with the AWS CLI.\n3. Perform the major version upgrade manually by modifying the DB instance or Multi-AZ DB cluster. In a Multi-AZ DB instance deployment or a Multi-AZ DB cluster deployment, the database might not be available for several minutes while the upgrade completes. See [How to perform a major version upgrade for RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.PostgreSQL.MajorVersion.Process.html).\n4. To minimize downtime, use a blue/green deployment, see [Using Amazon RDS Blue/Green Deployments for database updates](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/blue-green-deployments.html).\n5. Amazon RDS does not upgrade Multi-AZ DB cluster read replicas. Their replication state changes to terminated, and they must be deleted and recreated manually after the upgrade completes. In-Region read replicas of a DB instance are upgraded along with the primary DB instance, with an outage until the upgrade is complete.\n6. If the backup retention period is greater than 0, Amazon RDS takes a DB snapshot before any upgrade changes are made. If the upgrade fails, that snapshot can be restored to create a database running the old version. A custom backup retention period cannot be configured for a Multi-AZ DB cluster.",
      "replacement": null,
      "affected_versions": [
        "18"
      ],
      "source_url": "https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-release-calendar.html",
      "extra_source_urls": [
        "https://endoflife.date/amazon-rds-postgresql"
      ],
      "vendor_ref": "amazon-rds-postgresql@18",
      "last_checked_at": "2026-11-12T09:55:35.707Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/aws-rds-postgresql-18-extended-support-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-pro-24-04-lts-image-end-of-support",
      "title": "Compute Engine: Ubuntu Pro 24.04 LTS image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu Pro 24.04 LTS public image on Compute Engine: Apr 2034. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2034-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu Pro 24.04 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu Pro 24.04 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-pro-2404-lts-amd64",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-pro-24-04-lts-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-sles-15-sp7-image-end-of-support",
      "title": "Compute Engine: SLES 15 SP7 image end of support",
      "summary": "EOS and image deprecation date for the SLES 15 SP7 public image on Compute Engine: Jul 2034. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2034-07-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of SLES 15 SP7 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "SLES 15 SP7"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "sles-15",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-sles-15-sp7-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-windows-server-2025-image-end-of-support",
      "title": "Compute Engine: Windows Server 2025 image end of support",
      "summary": "EOS and image deprecation date for the Windows Server 2025 public image on Compute Engine: 10 Oct 2034. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2034-10-10",
      "effective_precision": "day",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Windows Server 2025 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Windows Server 2025"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "windows-2025",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-windows-server-2025-image-end-of-support"
    },
    {
      "slug": "multi-windows-server-2025-end-of-support",
      "title": "Windows Server 2025 end of support",
      "summary": "End of support for Windows Server 2025: 14 Nov 2034. Once a release reaches the end of support, security updates and bulletins end.",
      "cloud": "multi",
      "service": "Windows Server",
      "service_slug": "windows-server",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2034-11-14",
      "effective_precision": "day",
      "impact": "Windows Server Long Term Servicing Channel releases have a minimum of 10 years of support: five years of mainstream support and five years of extended support, which includes regular security updates. endoflife.date states that each Semi-Annual Channel release is supported for 18 months from the initial release, and that each Annual Channel release has 18 months of mainstream support plus 6 months of extended support. Once a release reaches the end of support, security updates and bulletins end, which Microsoft states can cause security or compliance issues.\n\n- endoflife.date states that for some releases, customers have the option to purchase Extended Security Updates. See [Lifecycle FAQ - Extended Security Updates](https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates).\n- Extended Security Updates do not include new features, customer-requested nonsecurity hotfixes, or design change requests.",
      "migration_path": "1. Choose an upgrade method with [Plan your Windows Server upgrade](https://learn.microsoft.com/en-us/windows-server/get-started/install-upgrade-migrate): in-place upgrade, clean install, migration, or cluster rolling upgrade.\n2. Check the [supported paths table](https://learn.microsoft.com/en-us/windows-server/get-started/install-upgrade-migrate#supported-in-place-upgrade-paths-by-version) and the [role and feature migration matrix](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-migrate-roles-features) for your configuration.\n3. Get a valid product key and activation method for the target version. Each Windows Server upgrade requires a separate license.\n4. Back up your system and important files before the in-place upgrade, clean install, or migration.\n5. For an in-place upgrade, follow [Perform an in-place upgrade of Windows Server](https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-in-place).",
      "replacement": null,
      "affected_versions": [
        "2025"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/windows-server-2025",
      "extra_source_urls": [
        "https://endoflife.date/windows-server"
      ],
      "vendor_ref": "windows-server@2025",
      "last_checked_at": "2026-11-12T09:55:50.558Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-windows-server-2025-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-almalinux-10-image-end-of-support",
      "title": "Compute Engine: AlmaLinux 10 image end of support",
      "summary": "EOS and image deprecation date for the AlmaLinux 10 public image on Compute Engine: May 2035. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2035-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of AlmaLinux 10 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "AlmaLinux 10"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "almalinux-10",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-almalinux-10-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rhel-10-image-end-of-support",
      "title": "Compute Engine: RHEL 10 image end of support",
      "summary": "EOS and image deprecation date for the RHEL 10 public image on Compute Engine: May 2035. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2035-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of RHEL 10 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "RHEL 10"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rhel-10",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rhel-10-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-10-image-end-of-support",
      "title": "Compute Engine: Rocky Linux 10 image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 10 public image on Compute Engine: May 2035. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2035-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 10 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 10"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-10",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-10-image-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-rocky-linux-10-optimized-for-google-47200e-end-of-support",
      "title": "Compute Engine: Rocky Linux 10 optimized for Google Cloud image end of support",
      "summary": "EOS and image deprecation date for the Rocky Linux 10 optimized for Google Cloud public image on Compute Engine: May 2035. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2035-05-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Rocky Linux 10 optimized for Google Cloud in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Rocky Linux 10 optimized for Google Cloud"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "rocky-linux-10-optimized-gcp",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-rocky-linux-10-optimized-for-google-47200e-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-oracle-linux-10-image-end-of-support",
      "title": "Compute Engine: Oracle Linux 10 image end of support",
      "summary": "EOS and image deprecation date for the Oracle Linux 10 public image on Compute Engine: Jun 2035. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2035-06-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Oracle Linux 10 in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Oracle Linux 10"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "oracle-linux-10",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-oracle-linux-10-image-end-of-support"
    },
    {
      "slug": "oci-oracle-linux-10-end-of-support",
      "title": "Oracle Linux 10 end of Premier Support",
      "summary": "End of Premier Support date for Oracle Linux 10: 30 Jun 2035. This is the date that endoflife.date lists under Basic/Premier Support for the release.",
      "cloud": "oci",
      "service": "Oracle Linux",
      "service_slug": "oracle-linux",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2035-06-30",
      "effective_precision": "day",
      "impact": "The date is the one that endoflife.date lists under Basic/Premier Support for Oracle Linux 10. endoflife.date states:\n\n- Basic and Premier Support include patches, fixes, security patches and security alerts. Premier Support adds live kernel patching.\n- Once a new minor release is available, the older one is considered end of life, and users must upgrade to continue receiving security updates.\n- Extended Support is available for a limited time after Premier Support ends, as per agreement with Oracle, with extra fees.\n- Extended Support covers critical security errata and select high-impact critical bug fixes, for select packages.\n- Sustaining Support follows Extended Support and does not include new security fixes or alerts.",
      "migration_path": "Oracle has not published migration steps. See the source for details.",
      "replacement": null,
      "affected_versions": [
        "10"
      ],
      "source_url": "https://endoflife.date/oracle-linux",
      "extra_source_urls": [
        "https://www.oracle.com/a/ocom/docs/elsp-lifetime-069338.pdf"
      ],
      "vendor_ref": "oracle-linux@10",
      "last_checked_at": "2026-11-12T09:55:55.860Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/oci-oracle-linux-10-end-of-support"
    },
    {
      "slug": "multi-sql-server-2025-end-of-support",
      "title": "SQL Server 2025 end of support",
      "summary": "End of extended support for SQL Server 2025: 6 Jan 2036. After the end of support, Microsoft no longer provides servicing and support for the product.",
      "cloud": "multi",
      "service": "SQL Server",
      "service_slug": "sql-server",
      "category": "database",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2036-01-06",
      "effective_precision": "day",
      "impact": "Each version of SQL Server gets mainstream support followed by extended support, and extended support includes only security updates. End of support means the product reached the end of its support lifecycle, and Microsoft no longer provides servicing and support for it.\n\n- For some releases, customers have the option to purchase Extended Security Updates.\n- Extended Security Updates do not include new features, functional improvements, or customer-requested fixes. Security fixes are limited to fixes rated as Critical.",
      "migration_path": "Microsoft lists these options in [SQL Server end of support options](https://learn.microsoft.com/en-us/sql/sql-server/end-of-support/sql-server-end-of-support-overview):\n\n1. Upgrade to a current version of SQL Server, for example with [Upgrade SQL Server Using the Installation Wizard (Setup)](https://learn.microsoft.com/en-us/sql/database-engine/install-windows/upgrade-sql-server-using-the-installation-wizard-setup?view=sql-server-ver17). The [SQL Server migration component in SQL Server Management Studio](https://learn.microsoft.com/en-us/ssms/migrate-sql-server-component) can help detect compatibility problems in the new version.\n2. Or [migrate](https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/) the workload to Azure SQL Managed Instance, Azure SQL Database, or an Azure Virtual Machine.\n3. Or, where Extended Security Updates are offered for the release, subscribe to them and stay on the current environment until you can upgrade or migrate. Only customers with Software Assurance or subscription licenses can use this option, and only for three years.",
      "replacement": null,
      "affected_versions": [
        "17.0"
      ],
      "source_url": "https://learn.microsoft.com/lifecycle/products/sql-server-2025",
      "extra_source_urls": [
        "https://endoflife.date/mssqlserver"
      ],
      "vendor_ref": "mssqlserver@17.0",
      "last_checked_at": "2026-11-12T09:55:53.034Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/multi-sql-server-2025-end-of-support"
    },
    {
      "slug": "gcp-compute-engine-ubuntu-pro-26-04-lts-image-end-of-support",
      "title": "Compute Engine: Ubuntu Pro 26.04 LTS image end of support",
      "summary": "EOS and image deprecation date for the Ubuntu Pro 26.04 LTS public image on Compute Engine: Apr 2036. At end of support, OS providers stop providing image updates and the OS images are marked deprecated or deleted.",
      "cloud": "gcp",
      "service": "Compute Engine",
      "service_slug": "compute-engine",
      "category": "os_image",
      "type": "end_of_support",
      "announced_date": null,
      "effective_date": "2036-04-01",
      "effective_precision": "month",
      "impact": "At end of support (EOS), the image family is no longer usable. VMs on an EOS version continue to work and stay eligible for Google Cloud support, but Google might not be able to resolve issues tied to the deprecated OS version.\n\n- OS providers stop providing image updates; you are responsible for acquiring updates.\n- Images are marked deprecated but usable by direct reference, or deleted on the EOS date (Windows Server, SQL Server on Windows Server, Fedora CoreOS).\n- With no extended support period, or past it, existing VMs can't download packages or security updates from the OS vendor, and Google's guest environment is no longer updated.",
      "migration_path": "1. Check the lifecycle stage and the EOS and image deprecation date of Ubuntu Pro 26.04 LTS in [Operating system details](https://docs.cloud.google.com/compute/docs/images/os-details).\n2. Where the images are marked deprecated and not deleted, you can create a VM from a deprecated image with the Google Cloud CLI or REST. Specify the image with the `--image` flag, because image families do not point to deprecated images.\n3. Where the OS distributor or a partner offers a paid maintenance, extended or long-term support package, you can procure and enable it to continue receiving critical security patches and updates.\n4. Review [OS upgrade best practices](https://docs.cloud.google.com/compute/docs/images/os-upgrade-best-practices) to plan an upgrade to a supported OS version.",
      "replacement": null,
      "affected_versions": [
        "Ubuntu Pro 26.04 LTS"
      ],
      "source_url": "https://docs.cloud.google.com/compute/docs/images/os-details",
      "extra_source_urls": [],
      "vendor_ref": "ubuntu-pro-2604-lts-amd64",
      "last_checked_at": "2026-11-12T09:56:09.861Z",
      "created_at": "2026-11-13T13:36:44.208Z",
      "updated_at": "2026-11-13T13:36:44.208Z",
      "url": "https://eolwatch.dev/items/gcp-compute-engine-ubuntu-pro-26-04-lts-image-end-of-support"
    }
  ]
}