I have an Outposts environment and it uses GP2 volumes.
When I restore instances using recent AMIs that have a default GP3 volume type - AL2023, RHEL 8 + and Win 2025 - Veeam is ignoring the GP2 I have configured, defaulting to GP3 and the restore fails.
Veeam is unusable on Outposts with certain AMIs.
I need Veeam to retain the volume configuration on restore or offer it as a configuration option during restore.
When I restore instances using recent AMIs that have a default GP3 volume type - AL2023, RHEL 8 + and Win 2025 - Veeam is ignoring the GP2 I have configured, defaulting to GP3 and the restore fails.
Veeam is unusable on Outposts with certain AMIs.
I need Veeam to retain the volume configuration on restore or offer it as a configuration option during restore.
Statistics: Posted by davehill — Jun 02, 2025 8:23 am






