View a markdown version of this page

Storage Gateway AL2 to AL2023 Migration Campaign - AWS Storage Gateway
Quick Links and Resources

Storage Gateway AL2 to AL2023 Migration Campaign

AWS is transitioning Storage Gateway appliance operating system (OS) from Amazon Linux 2 to AL2023 to enable new hybrid cloud storage features and maintain optimal performance and security standards. This transition will impact all AL2-based Storage Gateway appliance versions S3 File Gateway Version 1.x, Tape Gateway Version 2.x, and Volume Gateway Version 2.x. You are required to complete the migration before June 30, 2026, as AWS will discontinue supporting these systems thereafter.

You can identify whether your gateways need migration through multiple methods. The AWS Console displays a deprecation message in the gateway's Details tab for affected gateways. Additionally, the DescribeGatewayInformation API provides programmatic access to check the deprecation date field. The AWS Health Dashboard lists impacted gateways under the Affected resources tab. However, the list is not updated immediately after a gateway is migrated. The migration process itself is designed with data safety as the priority, storing a copy of on-premises gateway VM data in AWS before migration begins to enable easy recovery if needed.

AWS provides comprehensive migration guides specific to each gateway type. After completing migration, you should verify success by checking that deprecation warnings no longer appear in the AWS Console's gateway Details tab, or by using the DescribeGatewayInformation API to confirm the deprecation date field is absent. Critically, you must not revert to your AL2 gateway after successfully migrating to AL2023, as reverting may cause operational issues.

Throughout the migration period, AWS will send monthly reminder notifications via email, and the AWS Health Dashboard's Scheduled changes tab to help you plan and complete your migrations. If you encounter issues during migration, contact AWS Support for assistance and troubleshooting guidance.

Gateway Version Migration Reference

Understanding which gateways require migration is straightforward based on the gateway software version number. It's important to note that even recently activated gateways based on Amazon Linux 2 OS still require migration by June 30, 2026.

Gateway Type AL2 Version (Requires Migration) AL2023 Version (Target)
S3 File Gateway Version 1.x Version 2.x
Tape Gateway Version 2.x Version 3.x
Volume Gateway Version 2.x Version 3.x

Migration Timeline

The migration timeline includes several critical milestones:

  • October 28, 2025: All new gateway deployments initiated from Storage Gateway console will default to AL2023 images.

  • January 5, 2026: AWS will begin restricting new AL2 gateway activations.

  • June 30, 2026: AL2-based gateways will stop receiving software updates and AWS support will end. After this date, while you can continue using AL2-based appliances, they will receive no new software updates, security patches, or bug fixes, and maintaining these systems becomes your sole responsibility.

Pre-migration Checklist

Important

Before beginning the migration process, verify the following requirements to ensure a successful migration.

  • Use the latest gateway image. When creating the new Storage Gateway VM:

    • For Amazon EC2 gateways, use the latest AMI from the public SSM parameter or use the Storage Gateway console.

    • For on-premises gateways, download the latest VM image from the Storage Gateway console.

  • Match the hardware configuration. Ensure the new gateway VM uses the same CPU, memory, and network throughput as the existing gateway. For EC2 gateways, use the same instance type.

  • Verify root disk sizing. The new gateway VM's root disk must be at least the same size as the existing gateway's root disk. If the existing root disk has less than 20 GB of available space, size the new root disk to: (existing root disk size) + (20 GB minus available space on existing root disk).

  • Apply pending software updates. Before starting migration, apply any pending software updates on the existing gateway. Open the Storage Gateway console, select your gateway, and choose Update Now if available.

  • Verify network connectivity from the new gateway. Before initiating migration, confirm that the new gateway VM can reach:

    • Storage Gateway service endpoints (or your VPC endpoints).

    • Amazon S3 endpoints.

    • Active Directory / DNS servers (if your gateway is domain-joined).

    • Use the gateway local console's network connectivity test to validate all endpoints pass.

  • Resolve failing file uploads. Ensure your gateway's FilesFailingUpload CloudWatch metric is zero before beginning migration. Files in a failing state indicate unresolved errors that should be addressed first. To identify affected files, create a cache report, then resolve the underlying issues before proceeding.

  • Wait for cache to sync. Verify that the CachePercentDirty metric on the gateway's Monitoring tab is 0. This confirms all cached data has been uploaded to S3.

Support and Monitoring

Frequently Asked Questions

What happens to my data during migration?

Your data remains durably stored in AWS throughout the migration process. The migration procedure includes storing a copy of your on-premises gateway VM data in AWS for easy recovery if needed.

Will there be downtime during migration?

Migration timing and any potential service interruption depend on your gateway type and configuration. Review the gateway-specific migration guide for your deployment for detailed information.

What happens if I don't migrate by June 30, 2026?

Your gateway will continue to operate normally, and data will remain safely stored in AWS, but you must migrate affected gateways by June 30, 2026, to continue receiving updates and support.

Can I continue to use my AL2 based gateway after migrating?

No, you should not use your AL2 gateway alongside your new AL2023 gateway after successfully migrating. Use only your new AL2023-based gateway going forward. Using both AL2 and AL2023 gateways simultaneously may cause operational issues.

I'm having issues during migration. What should I do?

Contact AWS Support for assistance. Our support team can help troubleshoot migration issues and guide you through the process.