AWS CloudFormation provides a common language for you to model and provision AWS and third-party application resources in your cloud environment. AWS CloudFormation allows you to use programming languages or a simple text file to model and provision, in an automated and secure manner, all the resources needed for your applications across all regions and accounts. This gives you a single source of truth for your AWS and third-party resources.
Coming to our AWSCloudformation, below diagram summarizes what is our plugin can perform, so our workload customers can make use of this to simplify their infrastructure management as well as easy to implement changes to infrastructure.
To give more clarity on its benefits let us understand with below example,
For a scalable web application that also includes a back-end database, you might use an Auto Scaling group, an Elastic Load Balancing load balancer, and an Amazon Relational Database Service database instance. Normally, you might use each individual service to provision these resources. And after you create the resources, you would have to configure them to work together. All these tasks can add complexity and time before you even get your application up and running.
Instead, you can create or modify an existing AWS CloudFormation template. A template describes all your resources and their properties. When you use that template to create an AWS CloudFormation stack, AWS CloudFormation provisions the Auto Scaling group, load balancer, and database for you. After the stack has been successfully created, your AWS resources are up and running. You can delete the stack just as easily, which deletes all the resources in the stack. By using AWS CloudFormation, you easily manage a collection of resources as a single unit.
Let us begin with our plugin part with job definition parameters,
Log in to the Dynamic Workload Console and open the Workload Designer. Choose to create a new job and select “AWSCloudFormation” job type in the Cloud section
Establishing connection to the AWS Cloud server:
In the connection tab specify the Access Key ID ,Secret Access Key,Region and Role ARN fields to let workload Automation interact AWS Cloud Formation API(s) and click Test Connection. A confirmation message is displayed when the connection is established.
- Access Key ID: associated to your AWS Cloud Formation account. This attribute is required.
- Secret Access Key: associated to your AWS Cloud Formation account. This attribute is required.
- AWS Region: location to which the resources are provisioned and managed. This attribute is required.
- Role ARN: privileged user role who has access to the AWS Cloud.
In Action tab specify the stack name and stack operation which you want to perform.
- Stack Name: specify the stack name to be executed. Click the Selectbutton to choose the stack name defined in the AWS console. Select an item from the list, the selected item is displayed in the Stack Name field.
Note: For creating a new stack, you can type the stack name.
- Stack Operation: select an operation item from the list. The application allows you to create, update, and delete a stack.
- Create Stack: To create a new stack select this option.
- Update Stack: To update an existing stack select this option.
- Delete Stack: To delete an existing stack select this option.
- Template File Path: the path where the template of the stack defined is located. Click the “Select Template”button to choose the template for the selected stack name defined in the AWS console. Select an item from the list, the selected item is displayed in the Template File Path field.
- Template File Content: if you do not have a template you can use this field to type the template content for your stack.
Submitting your job
It is time to Submit your job into the current plan. You can add your job to the job stream that automates your business process flow. Select the action menu in the top-left corner of the job definition panel and click on Submit Job into Current Plan. A confirmation message is displayed, and you can switch to the Monitoring view to see what is going on.
JOB LOG Details
Rooparani Karuti – Senior Test Specialist at HCL Software
Working as senior test specialist for Workload Automation-Plugin Factory team in HCL Software Lab, Bangalore. Having experience in both manual and automation test scenarios across various domains.
Dharani Ramalingam -Senior Java Developer at HCL Technologies
Arka Mukherjee, Quality Analyst at HCL Technologies
Working as Quality Analyst for the Workload Automation team in HCL Software, Bangalore. Worked both in manual and automation test scenarios across various domains