1.
Virtual Private Cloud (VPC) and Inter-cloud Models
A. Virtual Private Cloud (VPC)
Definition:
A Virtual Private Cloud is a logically isolated section of a public cloud where users can
launch and manage resources in a virtual network that they define. Although it uses the
infrastructure of a public cloud provider (like AWS or Azure), it simulates a private
environment.
Benefits:
• Isolation: Dedicated IP ranges, subnets, and routing rules allow a secure and
isolated environment.
• Security: Integration with firewalls, VPNs, and access control lists.
• Scalability: Can take advantage of the public cloud’s elastic resources.
• Cost-effective: More affordable than a full private cloud while providing similar
security.
Drawbacks:
• Limited Control: You still depend on the public cloud provider’s infrastructure and
policies.
• Security Risks: Though isolated, it's still hosted on a shared physical infrastructure.
• Complex Setup: Networking and access rules can be complicated to configure
correctly.
B. Inter-cloud
Definition:
Inter-cloud refers to an interconnected system of multiple cloud computing environments
from different providers, allowing data and application portability, service interoperability,
and resource optimization.
2. Multi-Cloud vs Federated Cloud
Aspect Multi-Cloud Federated Cloud (Cloud Federation)
Usage of two or more cloud
Integration of multiple cloud providers
Definition services from different providers
to work as a unified system.
independently.
High level of integration and
Minimal or no integration. Each
Integration cooperation. Clouds are linked via
cloud works independently.
agreements.
Managed separately. Organizations Centralized or coordinated
Management
must coordinate across clouds. management and resource sharing.
A company uses AWS for storage,
Universities or government agencies
Example Azure for compute, and GCP for AI
pooling cloud resources together.
services.
Seamless resource sharing,
Avoid vendor lock-in, choose best
Benefit interoperability, and unified
service from each provider.
security/compliance.
Complex to manage; no automatic Requires standardization and trust
Drawback
interoperability. agreements; more setup overhead.
3. What is SLA (Service Level Agreement)?
Definition:
An SLA (Service Level Agreement) is a contract between a cloud service provider and the
customer that defines the level of service expected. It includes metrics such as uptime,
response time, support availability, and penalties for failing to meet the agreed
performance.
SLA Examples in the Four Cloud Deployment Models:
Deployment
Example of SLA
Model
Example: AWS offers 99.99% uptime SLA for its S3 storage service. If this is
Public Cloud
not met, customers may receive service credits.
Example: A company using OpenStack internally may set a 99.95%
Private Cloud internal SLA for its HR applications to ensure minimal downtime for
employees.
Example: A company using Azure Stack (on-premises) linked with Azure
Public Cloud may define an SLA that ensures critical apps in the private
Hybrid Cloud
cloud have 99.9% uptime, and data syncing to public cloud occurs within
10 minutes.
Example: Several hospitals sharing a healthcare cloud agree on an SLA
Community
that defines 99.9% availability, with data access response within 2
Cloud
seconds and compliance with HIPAA regulations.
Summary Table
Model Definition Benefit Drawback
Private environment within Still part of shared
VPC Security + scalability
public cloud infrastructure
Using services from Avoid lock-in, use best
Multi-Cloud Management complexity
multiple cloud providers tools
Federated Interlinked clouds with Interoperability and Harder to implement,
Cloud unified management shared resources trust needed
May exclude
Legal/service commitment Defines performance
SLA compensation for
between provider and user guarantees
indirect losses