Eucalyptus Limitations and Restrictions

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. Refer to 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.