Hi Pete,
I'll try to clarify a little more. Currently when you spin up a new Cloud ONTAP instance it will create a data aggregate with at least one 500GB EBS GP2 volume or EBS Magnetic volume. The numbr of 'disks' will depend on the size of the volume you may optionally create when you stand up the Cloud ONTAP system.
Now... when once you have a Cloud ONTAP instance stood up you have a couple options. You can keep the default aggregate, or... you can create a new aggregate with either a larger 'disk' size, or in your case... a smaller disk size. Specificaly, creating a new aggregate with a single 100GB EBS 'disk'. Once the new aggregate is in place, you can then use 'vol move' to move the root volume from the original aggregate to the new aggregate.... and then you can delete the original aggregate to release that 500GB of EBS storage.
I wasn't clear on if you have TWO Cloud ONTAP systems, or if you only have one. I'm simply trying to explain that if your main focus is cost, you can reduce your cost by switching to a 100GB Data aggregate.
I would also be remiss if I didn't mention the other underlying storage componenets for a Cloud ONTAP system... meaning the Boot and Root disks. These are needed to start up the AWS EC2 instance, as well as what is needed for Data ONTAP operating system. Specifically, each Cloud ONTAP system will have:
- Boot Disk - 42GB EBS PIOPS - 1250 IOPS
- Root Disk - 140GB EBS GP2
Hope this helps!
Kevin.