Building service blueprints for Amazon Web Services
This topic provides the caveats and considerations you need to review when creating a service blueprint for Amazon Web Services (AWS). It also provides links to the applicable service blueprint documentation. This topic contains the following sections:
Roadmap for service blueprint documentation
The following table provides links to the applicable service blueprint documentation.
| Topic | Description |
|---|---|
| Service blueprints overview | Provides an overview of service blueprints. |
| Creating, copying, or editing a service blueprint | Describes how to add several of the various types of service blueprint objects, and how to define network connections between those objects. |
Caveats and considerations for creating a service blueprint for AWS
The following table identifies the items to consider when creating a service blueprint for AWS.
| Service blueprint construct | Available for AWS? | Notes specific to AWS |
|---|---|---|
| Service blueprint parameters | Yes | Enabling access to a provisioned VM Add the BmcSshInstanceKey parameter to the service blueprint to enable a BMC Cloud Lifecycle Management end user to access a provisioned VM using a Key Pair. To add the parameter to the service blueprint:
The figure below provides an example of adding the parameter to a service blueprint definition.
While creating Amazon Service blueprint, You can also add the parameter to an individual server, if you want to use different Key Pairs for different servers. To do so, select a server item and click Parameters in the edit pane. Using an AWS instance type To use an AWS instance type, in the Name field, enter the parameter name, which is instanceFamily. Do not enter any other string for the parameter name. In the Default Value field, enter the exact value (for example, Micro or Memory Optimized). For values, see AWS instance types.For information about configuring parameters for AWS security groups, Assigning pre-existing AWS security groups to AWS instances. For more information about adding parameters to a service blueprint, see Configuring service blueprint parameters. |
| Application | Yes | Click Software Packages, and select from a list of available Amazon AMI files. Follow the instructions in To add and define applications in a service blueprint. |
| Server | Yes |
Note Ensure that the characteristics of the AMI you choose conforms to the instance types supported by BMC Cloud Lifecycle Management and to the instance types supported in your region. Otherwise, you could encounter errors in provisioning the instance. First generation Standard, Second generation Standard, High-Memory, and High-CPU instances are available in all Amazon EC2 regions. Other advanced types (such as High-Combination) could be region specific, so ensure that the instance type you select is supported in the target region. In general, the AMI contains the OS, so you do not need to specify that option. For additional details, see To add and define server definitions in a service blueprint. |
| PaaS Resource | No | Not applicable for AWS. |
| Networks | Yes | To enable Amazon Elastic IP addresses, on the Network Placement details panel, select the Static option and the Assign NAT Address option. (An elastic IP does not change even if you stop, start, or restart the instance.) Alternatively, you could make different selections for AWS instances:
To register a provisioned AWS instance with DNS, select the DNS Registration Required check box. For more information, see the "To add and define networks and connections in a service blueprint" section of Creating, copying, or editing a service blueprint. |
| Load balancer pools | Yes | No specific AWS considerations. See To add and define load balancer pools in a service blueprint. |
| IP End Points/VLAN | Yes | No specific AWS considerations. See To add and define IP endpoints and VLANs in a service blueprint. |
Where to go from here
Now that you have a service blueprint, you can create a service offering for AWS.
Comments
Log in or register to comment.