Skip to content

Commit

Permalink
Update default storage class recommendations in EKS design
Browse files Browse the repository at this point in the history
  • Loading branch information
milldr committed Oct 21, 2024
2 parents 91c080a + 9aa638a commit e36e463
Showing 1 changed file with 4 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -51,11 +51,11 @@ We need to decide between **Amazon EFS (Elastic File System)** and **Amazon EBS
- **Availability Zones:** EBS volumes are confined to a single Availability Zone, which may affect high availability and disaster recovery strategies. Kubernetes has implemented several mitigations for this limitation, and ECS likely has similar solutions.
- **Scalability:** Requires manual provisioning and management of storage capacity, which can introduce operational complexity.

## Recommendations
## Recommendation

Use **Amazon EBS** unless there is a good reason not to.

For example, use Amazon EFS when:
Use **Amazon EFS** when:

- **Multiple Pods need read/write access to the same data at the same time.**
- **Persistent data needs to be available in multiple Availability Zones and the underlying application does not support replication.**
- Multiple Pods need read/write access to the same data at the same time.
- Persistent data needs to be available in multiple Availability Zones and the underlying application does not support replication.

0 comments on commit e36e463

Please sign in to comment.