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.

Configuring the Amazon Web Services provider type


The Amazon Web Services (AWS) provider is registered by default during the installation process. However, you might want to add AWS providers, or update the settings for an existing provider. For example, if the BMC Cloud Lifecycle Management node does not have internet access to access AWS, you could set up a provider that specifies a proxy host that does have access.

If you need to create an additional AWS provider, or change a value for an existing AWS provider, use the following procedure.

To modify the configuration of an AWS compute provider

  1. Select the Compute category in the Providers workspace (see Registering-resource-providers).
  2. Do one of the following actions:
    • To create a new provider, select Add plus_icon.gif.
    • To update an existing provider, select an AWS compute provider and click EditEditIconBlue.gif.
       A window provides options for defining the provider.

  3. Complete or modify the following fields, as necessary:

    Field

    Description

    Name

    Assign a name to this AWS provider type definition.

    Description

    Enter a text description that distinguishes this provider type.

    Customize Load Balancer Placement

    Enable the placement of the load balancers in the onboarded VPCs or an Availability Zones to be changed.

    The default value is True.

    Customize Network Placement

    Enable the placement of the networks in the onboarded VPCs or an Availability Zones to be changed.

    The default value is True.

    Enroll Server

    Select True to automatically enroll the servers for the onboarded EC2 workloads in BMC Server Automation.

    The default value is False.
    Starting with BMC Cloud Lifecycle Management 4.6.04, if the value of this field is set to False, the Compliance configuration job fails.

    Validate RCSD Agent Status

    Enable BMC Cloud Lifecycle Management to verify the status of the BMC Server Automation RSCD Agent on the EC2 workload server as part of the enrollment process.

    The default value is False.

    Proxy Settings

    Complete the following settings if you are using a proxy host to access the internet.

    Enable Proxy

    Select True to enable BMC Cloud Lifecycle Management to access the internet via a proxy host.

    The default value is False; proxy mode is not enabled.

    Protocol

    Select the proxy protocol from the drop-down list (HTTP or SOCKS).

    Proxy Host

    Enter the name or IP address of the system that serves as the proxy host. If proxy is enabled, this field is required.

    Port

    Enter the port on which BMC Cloud Lifecycle Management communicates with the proxy host (for example, 8080). If proxy is enabled, this field is required.

    User Name

    Enter the name of a user with Administrator privileges on the proxy host.

    Password

    Enter the password for the above user.

    NTLM Domain

    If the proxy host is in a Microsoft NT LAN Manager (NTLM), select the domain name from the drop-down list.

    NTLM Workstation

    If the proxy host is in a NTLM domain, select the workstation from the drop-down list.

  4. Click Submit.
  5. Restart the OSGi container and on the system where BMC Cloud Platform Manager is installed, do either of the following actions:
    • On Microsoft Windows, restart the BMC CSM service by using the stop and start commands of the Services window.
    • On Linux, enter the following commands from the specified path:
      • /etc/init.d/stop bmccsm
      • /etc/init.d/start bmccsm

Where to go from here

Continue with Configuring-user-credentials-for-Amazon-Web-Services-workloads.

 

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