While you could use EBS to implement portions of a data lake architecture (volumes for data analytics EC2 instances, for example), it is not a good choice for storing the actual data in a data lake. This is because EBS volumes are typically only accessible by one instance (excluding multi-attach, which requires a cluster-aware filesystem) and should not be used for sharing data. They will not be accessible by Glue, Athena or OpenSearch. Your better bet would be to store the shared data in S3, which is a key aspect of data lake design.
- Accepted Answerasked 4 months ago
- asked 9 months ago
- How can I copy my Amazon EBS snapshot data to Amazon S3 and create EBS volumes for custom data in S3?AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago