From 9b92cb927229166ce2d415e8cb3f88468ce3250d Mon Sep 17 00:00:00 2001 From: Llewellyn vd Berg <113503285+llewellyn-sl@users.noreply.github.com> Date: Tue, 10 Dec 2024 16:49:36 +0200 Subject: [PATCH] Update fusion_docs/guide/snapshot.mdx Co-authored-by: Justine Geffen Signed-off-by: Llewellyn vd Berg <113503285+llewellyn-sl@users.noreply.github.com> --- fusion_docs/guide/snapshot.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fusion_docs/guide/snapshot.mdx b/fusion_docs/guide/snapshot.mdx index 7890041e..7e827bd3 100644 --- a/fusion_docs/guide/snapshot.mdx +++ b/fusion_docs/guide/snapshot.mdx @@ -51,7 +51,7 @@ Fusion Snapshots require EC2 instances with enough memory and network bandwidth It is recommended to select instances with guaranteed network bandwidth (as opposed to bandwidth _up to_ a maximum value) and maintain a ratio of 5:1 between memory and network bandwidth. -For example, when taking bandwidth and the compute necessary to take the Snapshot into account, a `c6i.8xlarge` instance with 64 GIB memory and a guaranteed network bandwidth of 12.5 Gbps can take approximately 70 seconds to dump the entire instance to S3 storage before instance reclamation occurs. +For example, when taking bandwidth and the compute necessary to take the Snapshots into account, a `c6i.8xlarge` instance with 64 GIB memory and a guaranteed network bandwidth of 12.5 Gbps can take approximately 70 seconds to dump the entire instance to S3 storage before instance reclamation occurs. ### Amazon Linux 2023 ECS-optimized AMI