Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Overview of support for Amazon Web Services


BMC Cloud Lifecycle Management supports the external cloud provider Amazon Web Services (AWS). This topic provides an overview of what is supported by BMC Cloud Lifecycle Management and also provides a list of limitations to the support. 

The topic includes the following sections:

API/SDK support

BMC Cloud Lifecycle Management uses the AWS Java SDK 1.6.2. See the Amazon Web Services online technical documentation for more information about using the SDKs.

Starting with version 4.1 patch 3, BMC Cloud Lifecycle Management uses the AWS Java SDK 1.8.11.

With this API, you can provision Amazon Machine Images (AMIs) available from Amazon Marketplace. AMIs with preconfigured stacks (with application installed) are available from the Amazon Marketplace for IAAS, PAAS, and SAAS. You can provision any appliance from the Marketplace, which appears in the console as a compute node.

For example, a checkpoint firewall provisioned from the Amazon Marketplace appears as a compute VM in the BMC Cloud Lifecycle Management console. You can then add Day 2 operations, such as adding memory, CPU, and start/stop options. Note that no firewall artifacts are generated for this type of resource.

Key terminology

Term

Description

EC2 instance

Amazon EC2 (Elastic Cloud Computing) instances, similar to virtual servers, that can run applications. Instances are created from an Amazon AMI.

Amazon Machine Image (AMI)

A template that contains a software configuration, including an operating system, which defines your operating environment. You can use generic public AMIs or you can customize a public AMI.

Availability Zone

A distinct location within an AWS geographic Region. A Region can contain multiple Availability Zones. An Availability Zone is designed to be isolated so that a failure in another Availability Zone does not impact its instances. A subnet resides in only one Availability Zone.

The BMC Cloud Lifecycle Management pod is mapped to an Availability Zone. Consequently, Availability Zones are onboarded as pods.

Virtual Private Cloud (VPC)

A virtual network dedicated to your AWS account that is logically isolated from other virtual networks in the AWS cloud. A VPC creates a separate section of the AWS cloud with its own virtual network topology. You can create multiple VPCs in the AWS cloud.

A VPC is contained with an AWS geographic Region, and it can span multiple Availability Zones.

Logical hosting environment (LHE)

A generic BMC Cloud Lifecycle Management construct. In the AWS context, a LHE can be either a VPC or an Availability Zone.

Security Group

A firewall policy that is applied to provisioned virtual machines. A security group consist of rules that control inbound and outbound network traffic. You can assign virtual machine instances to multiple security groups.

SSH key pair

A public/private key pair that enables remote access to your virtual machine instances. Use this key to gain SSH access to Linux instances and Remote Desktop access to Windows instances.

BMC Server Automation Agent

A software package that you can install on an AMI instance to enable the BMC Server Automation use cases on virtual machine instances.

Logical data center

A generic construct that absorbs the key artifacts of any isolated network topology.

The logical data center references Logical Distributed Firewalls, Logical Perimeter Firewalls, Logical Data Stores, and Logical Load Balancers.

Logical load balancer

A Logical Load Balancer represents an Elastic Load Balancer. The Logical Load Balancer has IPV4 and IPV6 DNS names to accomodate IPV6 clients. The cloud administrator has the ability to decide the probing protocol and the probing path. For example, a webserver instance listening to traffic on port 80 would have a probing path similar to xxxxx:80/index.html.

Logical perimeter firewall

A construct within the Logical Data Center that provides security at the perimeter of the data center, even though the physical layout is not exposed. Packets coming in from the internet must traverse
through these firewalls before they can enter the Logical Data Center. These firewalls typically provide subnet level security.

Logical distributed firewall

A construct within the Logical Data Center that provides security between VLANs. These firewalls are additive to the logical perimeter firewalls and are usually tightly integrated at the hypervisor layer. These firewalls can be associated with elastic load balancers.

Logical data store

A construct within the Logical Data Center that provides a virtual data store.

Mapping of AWS constructs with BMC Cloud Lifecycle Management objects

The following table identifies the correlations between the main AWS constructs and their BMC Cloud Lifecycle Management counterparts:

AWS construct

BMC Cloud Lifecycle Management object

Availability Zone

Logical Hosting Environment

Virtual Private Cloud

Logical Hosting Environment

Amazon Machine Image

Template for a provisioning instance

Virtual Private Cloud subnet

Logical Network

Elastic Load Balancers

Logical Load Balancers

Security Groups

Logical Distributed Firewalls

Network ACL

Logical Perimeter Firewalls

Elastic Block Storage

Logical Datastore

Supported instance types

Error

Excerpt named aws_instances was not found in document xwiki:Automation-DevSecOps.Client-Management.BMC-Cloud-Lifecycle-Management.clm45.Administering-the-product.Third-party-provider-types.Amazon-Web-Services-provider.Overview-of-support-for-Amazon-Web-Services.WebHome.

For information about adding options for AWS instance families, see Defining-Service-Catalog-entries-for-Amazon-Web-Services.

Warning

Note

BMC Cloud Lifecycle Management uses vCPU,  not ECU, for instance type selection.

The following table identifies the AWS instance types supported by BMC Cloud Lifecycle Management:

Type

Arch

vCPU

Memory
(MiB)

ECU 

Memory
(GiB)

Storage
(GB)

EBS-
optimized

Network
performance

Supported

in patch 1?

Supported

in patch 2?

Supported

in patch 3?

General purpose instance family

t1.micro 

64-bit

1

630

Variable

0.615

EBS only 

-

Very low
 

Yes

Yes

Yes

t2.micro

64-bit

1

1024

Variable

1

EBS only

Yes

Low to Moderate

No

Yes

Yes

t2.small

64-bit

1

2048

Variable

2

EBS only

Yes

Low to Moderate

No

Yes

Yes

t2.medium

64-bit

2

4096

Variable

4

EBS only

Yes

Low to Moderate

No

Yes

Yes

m1.small 

64-bit 

1

1741

1

1.7

160 GB

-

Low

Yes

Yes

Yes

m1.medium 

64-bit 

1

3840

2

3.75

410 GB

-

Moderate

Yes

Yes

Yes

m1.large 

64-bit 

2

7680

4

7.5

2 * 420 GB

Yes

Moderate

Yes

Yes

Yes

m1.xlarge 

64-bit 

4

15360

8

15

4 * 420 GB

Yes

High

Yes

Yes

Yes

m3.medium

64-bit

1

3840

3

3.75

4 GB SSD

-

Moderate

No

Yes

Yes

m3.large

64-bit

2

7680

6.5

7.5

32 GB SSD

-

Moderate

No

Yes

Yes

m3.xlarge 

64-bit

4

15360

13

15

2 * 40 GB SSD
 

Yes

High

No

Yes

Yes

m3.2xlarge

64-bit

8

30720    

26

30

2 * 80 GB SSD

Yes

High

No

Yes

Yes

m4.large

64-bit

2

8192

6.5

8

EBS only

Yes

Moderate

No

No

Yes

m4.xlarge

64-bit

4

16384

13

16

EBS only

Yes

High

No

No

Yes

m4.2xlarge

64-bit

8

32768

26

32

EBS only

Yes

High

No

No

Yes

m4.4xlarge

64-bit

16

65536

53.5

64

EBS only

Yes

High

No

No

Yes

m4.10xlarge

64-bit

40

163840

124.5

160

EBS only

Yes

10 Gigabit

No

No

Yes

Compute optimized instance family

c1.medium 

64-bit

2

1741

5

1.7

350 GB

-

Moderate

Yes

Yes

Yes

c1.xlarge 

64-bit

8

7168

20

7

4 * 420 GB

Yes

High

Yes

Yes

Yes

cc1.4xlarge         

64-bit

16

23040

33.5

22.5

2 * 840 GB

-

10 Gigabit

Yes

Yes

Yes

cc2.8xlarge 

64-bit

32

61952

88

60.5

4 * 840 GB

-

10 Gigabit

Yes

Yes

Yes

c3.large

64-bit

2

3840

7

3.75

2 * 16 SSD

-

Moderate

No

Yes

Yes

c3.xlarge

64-bit

4

7680

14

7.5

2 * 40 SSD

Yes

Moderate

No

Yes

Yes

c3.2xlarge

64-bit

8

15360

28

15

2 * 80 SSD

Yes

High

No

Yes

Yes

c3.4xlarge

64-bit

16

30720

55

30

2 * 160 SSD

Yes

High

No

Yes

Yes

c3.8xlarge

64-bit

32

61440

108

60

2 * 320 SSD

-

10 Gigabit

No

Yes

Yes

c4.large

64-bit

2

3840

8

3.75

EBS only

Yes

Moderate

No

No

Yes

c4.xlarge

64-bit

4

7680

16

7.5

EBS only

Yes

High

No

No

Yes

c4.2xlarge

64-bit

8

15360

31

15

EBS only

Yes

High

No

No

Yes

c4.4xlarge

64-bit

16

30720

62

30

EBS only

Yes

High

No

No

Yes

c4.8xlarge

64-bit

36

61440

132

60

EBS only

Yes

10 Gigabit

No

No

Yes

GPU instance family

cg1.4xlarge

64-bit

16

23040

33.5

22.5

2 * 840 GB

-

10 Gigabit

Yes

Yes

Yes

g2.2xlarge

64-bit

8

15360

26

15

60 GB SSD

-

High

No

Yes

Yes

Memory optimized instance family

m2.xlarge

64-bit

2

17510

6.5

17.1

1 * 420 

-

Moderate

Yes

Yes

Yes

m2.2xlarge 

64-bit

4

35021

13

34.2

1 * 850 

Yes

Moderate

Yes

Yes

Yes

m2.4xlarge

64-bit

8

70042

26

68.4

2 * 840 

Yes

High

Yes

Yes

Yes

cr1.8xlarge          

64-bit

32

249856  

88

244

2 * 120 SSD

-

10 Gigabit

Yes

Yes

Yes

r3.large

64-bit

2

15616

Variable

15.25

1 * 32 SSD

-

Moderate

No

Yes

Yes

r3.xlarge

64-bit

4

31232

Variable

30.5

1 * 80 SSD

-

Moderate

No

Yes

Yes

r3.2xlarge

64-bit

8

62464

Variable

61

1 * 160 SSD

-

High

No

Yes

Yes

r3.4xlarge

64-bit

16

124928

Variable

122

1 * 320 SSD

-

High

No

Yes

Yes

r3.8xlarge

64-bit

32

249856

Variable

244

2 * 320 SSD

-

10 Gigabit

No

Yes

Yes

Storage optimized - High I/O instance family

i2.xlarge

64-bit

4

31232

104

30.5

1 * 800 SSD

-

Moderate

No

Yes

Yes

i2.2xlarge

64-bit

8

62464

14

61

2 * 800 SSD

-

High

No

Yes

Yes

i2.4xlarge

64-bit

16

124928

27

122

4 * 800 SSD

-

High

No

Yes

Yes

i2.8xlarge

64-bit

32

249856

53

244

8 * 800 SSD

-

10 Gigabit

No

Yes

Yes

hi1.4xlarge

64-bit

16

61952

35

60.5

2 * 1024 GB SSD

-

10 Gigabit

Yes

Yes

Yes

hs1.8xlarge         

64-bit

16

119808  

35

117

24 * 2000 GB

-

10 Gigabit

No

Yes

Yes

Dense-storage instances family

d2.xlarge

64-bit

4

31232

14

30.5

3 * 2000 GB

Yes

Moderate

No

No

Yes

d2.2xlarge

64-bit

8

62464

28

61

6 * 2000 GB

Yes

High

No

No

Yes

d2.4xlarge

64-bit

16

124928

56

122

12 * 2000 GB

Yes

High

No

No

Yes

d2.8xlarge

64-bit

13

249856

116

244

24 * 2000 GB

Yes

10 Gigabit

No

No

Yes

Support for Availability Zones and VPCs

BMC Cloud Lifecycle Management allows you to provision virtual machine (VM) instances to Availability Zones or VPCs.

An Availability Zone is a distinct location within an AWS geographic Region. A Region can contain multiple Availability Zones. Availability Zones are designed to be isolated so that a failure in one Availability Zone does not impact instances in another. For more information, see the AWS documentation on Regions and Availability Zones.

Unlike Availability Zones, which are predefined, VPCs are created to delineate a section of the AWS cloud for your use. Within this section you can launch Amazon AWS instances with private, instead of public, IP addresses that lie within a user-defined range. Within the VPC, you can create subnets to group similar AWS instances according to a private IP address range. The following example shows a VPC with four subnets:

ec2_vpc_subnets.png

The VPC is designated by the address 192.168.24.0/24. The subnets are designated by the following addresses:
192.168.24.0/26
192.168.24.64/26
192.168.24.128/26
192.168.24.192/26

You can assign elastic IP addresses to the private address instances in the VPC. Elastic IP addresses are static, public addresses that, once assigned, enable the instances in the VPC to be reached from external networks.

You can onboard your existing VPCs and Availability Zones as Logical Data Centers to BMC Cloud Lifecycle Management. See Onboarding-and-offboarding-Logical-Data-Centers-for-Amazon-Web-Services.

For instructions about how to create a VPC using BMC Cloud Lifecycle Management, see Creating-a-Logical-Data-Center-for-Amazon-Web-Services.

Limitations to the support

The following table itemizes the limitations to the current BMC Cloud Lifecycle Management support for AWS.

Item 

Limitation

Onboarded Availability Zones

Load Balancer and Firewall management is not supported for Availability Zone-based LDCs.

VPCs (onboarded or created)

The BMC Cloud Management console does not support LHE Offboard. Therefore, all of the VPC-based LHEs are deleted from both the Cloud database and AWS when you select Decommission in the BMC Cloud Management console, including the onboarded VPC-based LHEs where the VPCs were created in AWS.

LHE Offboard is supported only using the API.

Firewall Rules / Network Paths

  • Firewalls: Outbound rules for a Distributed Firewall cannot be viewed or created through the Firewall management UI. To view an outbound firewall rule, use the API.
  • Network paths: The Create: Deny Network Paths are only valid between two networks (external or internal). If an endpoint is a Resource Set, the Network Path is invalid.
  • Firewall and network paths
    • The only valid protocols for firewall rules and network paths are TCP or UDP.
    • If you have multiple network paths, deleting a network path or SOI with a shared firewall rule deletes the rule. This situation might result in failures for other SOIs that also use the shared firewall rule. In the event of a failure, you must re-create the network path to re-instantiate the firewall rule.  

 Scaling

Scaling up (adding CPU or memory) or scaling down an Amazon EC2 node is tied to the source instance family, as defined by the AWS SDK version 1.6.2. However, if the source instance is a micro instance, a scale-up operation could allow an EC2 node to cross the instance type family boundary from micro to general purpose. Scale-down operations are strictly within an instance family.

Where to go from here

To start your Amazon Web Services implementation, see Configuring-the-infrastructure-for-Amazon-Web-Services-support.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Cloud Lifecycle Management 4.1