ebs-volume-types not consistent

[hegyre]

Hello,
File doc_source/ebs-volume-types.md is not consistent with the AWS online doc itself.

For example:

	Solid-State Drives (SSD) --> missing (gp2)	Hard Disk Drives (HDD) --> Should be "Provisioned IOPS SSD (io1)" instead
Volume Type	General Purpose SSD (gp2)	Provisioned IOPS SSD (io1)
Dominant Performance Attribute	IOPS	IOPS

In fact the online doc has a 4-column table, but the doc here on github only has a 2-column table with incorrect title for the 2nd column header.

[mariflax]

Thanks for taking the time to let us know. The AWS online doc is the correct version. I'll refresh the GitHub version so that it's aligned with the online version. Thanks, Marilyn

[mariflax]

Hi again. I've subsequently discovered that column spanning is a limitation in GitHub: adam-p/markdown-here#176. Unfortunately the table you pointed to does not render correctly in Markdown. To see the full table, please view it in the AWS online doc or view the Markdown code. Thanks, Marilyn

[hegyre]

Hello @mariflax ,
What about using this below (from adam-p/markdown-here#176) :

Unsatisfying workaround: You can use raw HTML

	Solid-State Drives (SSD)		Hard Disk Drives (HDD)
Volume Type	General Purpose SSD (gp2)	Provisioned IOPS SSD (io1)	Throughput Optimized HDD (st1)	Cold HDD (sc1)
Description	General purpose SSD volume that balances price and performance for a wide variety of workloads	Highest-performance SSD volume for mission-critical low-latency or high-throughput workloads	Low-cost HDD volume designed for frequently accessed, throughput-intensive workloads	Lowest cost HDD volume designed for less frequently accessed workloads
Use Cases	Recommended for most workloads System boot volumes Virtual desktops Low-latency interactive apps Development and test environments	Critical business applications that require sustained IOPS performance, or more than 16,000 IOPS or 250 MiB/s of throughput per volume Large database workloads, such as: MongoDB Cassandra Microsoft SQL Server MySQL PostgreSQL Oracle	Streaming workloads requiring consistent, fast throughput at a low price Big data Data warehouses Log processing Cannot be a boot volume	Throughput-oriented storage for large volumes of data that is infrequently accessed Scenarios where the lowest storage cost is important Cannot be a boot volume
API Name	gp2	io1	st1	sc1
Volume Size	1 GiB - 16 TiB	4 GiB - 16 TiB	500 GiB - 16 TiB	500 GiB - 16 TiB
Max IOPS per Volume	16,000 (16 KiB I/O) *	64,000 (16 KiB I/O) †	500 (1 MiB I/O)	250 (1 MiB I/O)
Max Throughput per Volume	250 MiB/s *	1,000 MiB/s †	500 MiB/s	250 MiB/s
Max IOPS per Instance ††	80,000	80,000	80,000	80,000
Max Throughput per Instance ††	2,375 MB/s	2,375 MB/s	2,375 MB/s	2,375 MB/s
Dominant Performance Attribute	IOPS	IOPS	MiB/s	MiB/s

[mariflax]

Hi heygre. Thanks for demonstrating that the workaround works. However, our Markdown files are generated automatically, and if I were to apply the raw HTML workaround, it will be overwritten the next time we refresh the GitHub repo.