Cloud Storage
Cloud storage services provide durable, scalable data persistence without owning physical media. They offer object, block, and file storage with varying performance, access patterns, and pricing tiers, accessible through APIs from anywhere with network connectivity.
itCloud computing | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic - Cloud Storage
Cloud storage gives you capacity through a network service. The provider operates media, controllers, and much of the data-protection machinery. You still choose the storage model, location, protection policy, access policy, and cost profile. The useful question is not which cloud storage is best. Ask what access pattern, failure model, security boundary, and recovery target the data needs.
Most services expose one of three models. Object storage stores items with data, metadata, and a key, usually through an HTTP API. Block storage presents a volume that an operating system treats like a disk. File storage presents shared paths through protocols such as NFS or SMB. These are interfaces, not just media types. The same provider may use similar hardware behind all three.
Location and redundancy solve different failure problems. Regions and availability zones change latency, residency, and failover behavior. Durability is about intact data. Availability is about reachability. Redundancy helps survive infrastructure failure and can also replicate a harmful change. Versioning recovers some accidents. A backup is a recoverable copy managed for a defined purpose, ideally outside the same credentials and deletion path.
Storage classes connect access patterns to cost. Lifecycle policies change class or expire objects when conditions match. Treat those rules as production code. Access control starts with identity and least privilege. Encryption protects media and transit, but an authorized request can still read plaintext after decryption.
Read the Intro for the object, block, and file decision frame. Use the Cheatsheet when you need the design questions and protection-layer map. Landscape is out of scope for this multi-provider survey; Updates stays false because no single official tracker covers the cross-cloud contracts this course teaches.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://csrc.nist.gov/pubs/sp/800/145/final
Supports
- Cloud computing as on-demand network access to shared configurable resources
- Resource pooling, rapid elasticity, and measured service
- Storage as a configurable cloud resource
- https://doi.org/10.6028/NIST.SP.800-209
Supports
- Object, block, and file storage service models
- Cloud storage as an abstraction over underlying storage technologies
- Authentication, authorization, data protection, isolation, encryption, backup, replication, and restoration assurance
- Storage threats, configuration risk, and security recommendations
- https://docs.aws.amazon.com/whitepapers/latest/web-application-hosting-best-practices/storage-and-backup-of-data-and-assets.html
Supports
- Object storage for static assets and media
- Block volumes as mountable persistent storage for databases and application data
- Snapshots as a protection mechanism for block volumes
- https://learn.microsoft.com/en-us/azure/storage/common/storage-introduction
Supports
- Managed object, file, disk, queue, and table storage services
- Encryption at rest, client-side encryption, redundancy, and data-transfer choices
- Managed cloud storage use cases and service boundaries
- https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy
Supports
- Local, zonal, and geographic redundancy choices
- Failure-scope, availability, durability, latency, and cost tradeoffs
- Synchronous primary-region writes and asynchronous geographic replication behavior
- Data integrity checks, secondary read access, and failover considerations
- https://learn.microsoft.com/en-us/azure/storage/blobs/data-protection-overview
Supports
- Versioning, soft deletion, backup, redundancy, replication, and restore as separate protection options
- Recovery from deletion, overwrite, corruption, and service outage
- Retention, immutability, and protected backup use cases
- https://learn.microsoft.com/en-us/azure/storage/common/storage-service-encryption
Supports
- Service-side encryption before data is persisted
- Transparent decryption when authorized data is retrieved
- Provider-managed and customer-managed key choices
- https://docs.aws.amazon.com/AmazonS3/latest/userguide/Versioning.html
Supports
- Retaining, retrieving, and restoring multiple object variants
- Recovery from accidental deletion and overwrite
- Storage cost for full object versions and interaction with lifecycle rules
- https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-management.html
Supports
- Identity and resource policy controls for object storage
- Versioning, object immutability, encryption, and signed requests as distinct controls
- Server-side and client-side encryption boundaries
- https://docs.aws.amazon.com/AmazonS3/latest/userguide/DataDurability.html
Supports
- Distinction between object durability and service availability targets
- Versioning, replication, and object lock as protection mechanisms
- Protection against infrastructure and availability-zone failures
- https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html
Supports
- Storage-class transitions and expiration actions
- Different lifecycle behavior for current, noncurrent, and unversioned objects
- Need to account for version state in destructive automation
- https://cloud.google.com/storage/docs/storage-classes
Supports
- Storage class as object metadata affecting availability and pricing
- Retrieval fees, minimum storage durations, access patterns, and location choices
- Lifecycle-based class changes and automated class management
- https://cloud.google.com/storage/pricing
Supports
- Capacity, operation, retrieval, data-processing, and network-transfer price dimensions
- Minimum storage duration and early-deletion effects
- Location and storage-class effects on total cost
- https://cloud.google.com/storage/docs/lifecycle
Supports
- Lifecycle conditions and transition or deletion actions
- Current and noncurrent object-version behavior
- Retention, holds, and destructive-rule cautions
- https://cloud.google.com/storage/docs/consistency
Supports
- Strongly and eventually consistent operations
- Atomic behavior for individual object operations
- Cache effects, permission propagation, preconditions, and concurrency risks