Getting started with the CLM AWS SDK

The following sections in this topic describe how to get started with the BMC Cloud Lifecycle Management Amazon Web Services Software Development Kit (CLM AWS SDK).

Why CLM AWS SDK?

The CLM AWS SDK provides a normalized and homogenous interface to manage the following:

• Amazon Web Services cloud and other on-premise cloud providers such as VMware environments
• API access to the BMC Cloud Lifecycle Management stack and the AWS cloud

If you have an existing Portal, DevOps, or Automation solutions for AWS Cloud using AWS SDK, you can easily migrate to the CLM AWS SDK with a minimal impact. The following figure depicts how the CLM AWS SDK integrates with your existing solutions and AWS or on-premises cloud providers:

Uses of the CLM AWS SDK

You can use the CLM AWS SDK to perform the following actions:

• Utilize all the benefits of the CLM AWS SDK by just replacing the EC2Client class in your existing code with the CLMEC2Client class.
• Customize the default behavior of the CLM AWS SDK by using a configuration file.
• Leverage the CLM AWS SDK extensions for managing the service offering instances.
• Use the AWS image or VMware templates to create a service blueprint and service offering and provision an instance.
• Manage (stop, start, restart, terminate, and describe) the existing service offerings.

Walkthrough: How to use the CLM AWS SDK?

The video at right demonstrates the process of using CLM AWS SDK.

This walkthrough:

• Downloads the CLM AWS SDK.
• Configures the CLM AWS SDK.
• Executes the CLM AWS SDK commands.

Limitations of the CLM AWS SDK

• It can be used only for VMs that are present in BMC Cloud Lifecycle Management.
• It supports only some attributes or methods of the AWS SDK. For details about the supported attributes or methods, see the descriptions of each of the methods supported by CLM AWS SDK.
• Onboarding use case constraints:
  
  • Multiple NICs are not supported when you create a service blueprint.
    
  • Multiple entitlement packages cannot be specified.
  • Monitoring is not enabled when you create a service blueprint. You must enable it manually after onboarding is complete.
  • Secondary disks are not created in a service blueprint.
• The public DNS, private DNS, and private IP fields are assigned new values when you reboot an instance.