Eucalyptus Limitations and Restrictions

This topic provides defaults used for known limitations and restrictions associated with
Eucalyptus 4.4 features, services, and
accounts as tested and supported by the Eucalyptus Quality Team. Some of these limitations may
reflect the supported differences between AWS and Eucalyptus.

Functional Limitations

This section describes features and operations that are not supported by Eucalyptus, and therefore,
considered a functional limitation or difference from that of AWS.

Eucalyptus CloudFormation Update Stack does not support Notification Configurations for given
resources since Eucalyptus has not implemented Simple Notification Service (SNS) or Simple
Queue Service (SQS).

Eucalyptus CloudFormation Update Stack supports the UpdatePolicy attribute
on the AWS::AutoScaling::AutoScalingGroup type but only the
AutoScalingRollingUpdate condition is supported since Eucalyptus Auto Scaling
does not support Scheduled Actions.

Full access to the Management Console requires a minimum IAM policy. See Add Access Policy for the recommended
minimal IAM policy to apply when creating a group.

Auto scaling limits are aligned with the AWS limits, except for SNS topics, as SNS is
currently not supported in Eucalyptus. The AWS Auto Scaling Limits are also generally applicable to
Eucalyptus.

API support for object lifecycle in S3 is the same as for AWS S3 except for:

Glacier support. There is no "transition" operation type to transition objects to Glacier.

Transitions between storage classes. Eucalyptus allows multiple storage classes but
they have no real meaning and do not differentiate either cost or durability of the data. See
AWS Object Lifecycle Management for more
information.

Configurable Limitations

This section lists the limitations that are present for configuring certain resources, as tested by Eucalyptus,
and may differ from those imposed by AWS.

Description

Default

Maximum

The number of instances that can be started in one cluster. Configurable via
MAX_INSTANCES_PER_CC in eucalyptus.conf. Note: Once a cloud is in use and has
started operating based on this variable, it is not safe to change it at runtime. If
the value needs to be changed, stop the CC process, remove the files in
/var/lib/eucalyptus/CC/*, change the variable in the config file, and start the CC
process again.

2048

4096

The number of volumes that can be attached to a VM. Eucalyptus can attach up to 24-25
volumes per VM.

None

Unknown because EBS/HVM/PV instances would have different limits.

The number of access keys a user can have. Configurable in property
authentication.access_keys_limit.