The document outlines the agenda for a Bangalore Meetup Community event on networking and MuleSoft technologies. The agenda includes short introductions, presentations on automating AWS resources using Terraform as part of CI/CD pipelines, creating custom data formats in DataWeave, and an open discussion period. Certification vouchers and prizes will be provided.

1. 31st Aug 2019
Bangalore Meetup Community

2. Networking time
Introduce yourself to your neighbors!

3. All contents © MuleSoft Inc.
Agenda
3
10:30AM - 10:45 AM : Short Introductions
11:15AM - 11:45 PM : Resource creation using Terraform as part of CI CD
11:45AM - 12:15 PM : DataWeave Custom DataFormat
12:15 PM - 12:45PM : Open forum discussion and Q&A
12:45PM - 1:00PM : Wrap up
1:00 PM : Snack Time

4. All contents © MuleSoft Inc.
Sponsor & Intro

5. All contents © MuleSoft Inc. 5
• We have prizes to give away!
o Thanks for your positive enthusiasm …You earned it ..
Certification Vouchers for all!
A SHOW OF HANDS:
Who is new to this MeetUp?

6. Automate AWS resources using Terraform

7. All contents © MuleSoft Inc.
Agenda
7
• What is Terraform ?
• Why use Terraform ?
• Initial Setup
• Using Terraform in Mulesoft CI/CD
• Demo
• Q&A

8. All contents © MuleSoft Inc.
What is Terraform ?
“HashiCorp Terraform enables you to safely and predictably create, change, and improve
infrastructure. It is an open source tool that codifies APIs into declarative configuration files
that can be shared amongst team members, treated as code, edited, reviewed, and
versioned.” -

9. All contents © MuleSoft Inc.
Why Terraform ?
9
• Automate.
• Deployment pipeline Consistent.
• Provisioning
• Easy to Manage AWS Infrastructure.
• Open Source.

10. All contents © MuleSoft Inc.
Setup
10
These steps are required for the first time your team is on-boarding the terraform via bamboo.
Configure AWS account for bamboo instances
This step is required so bamboo instances can assume roles in the AWS account for the resource management.
Configure role and trust in your AWS
• Login with AWS admin access
• Navigate to IAM → roles and create a role which we will be assumed by bamboo instances. For example, created
role “mulesoft-tf-role” with below configs. Make sure to grant proper access for resources which are going to be
managed by terraform.
Inline Policy :-
{
"Version": “2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"iam:*",
"s3:*",
“dynamodb:*",
"sqs:*"
],
"Resource": "*"
}
]
}
Trust Relationship :-
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"Service": [
"ec2.amazonaws.com",
"ecs-tasks.amazonaws.com"
],
"AWS": [
“arn:aws:iam::238728377438:role/non-prod-
bamboo",
"arn:aws:iam::347637463746:role/prod-bamboo"
]
},
"Action": "sts:AssumeRole" }
]
}

11. All contents © MuleSoft Inc.
Using Terraform in Mulesoft CI/CD
11
This step is required to setup your mule project repo to deploy AWS resources via terraform.
1. Configure bamboo plan and dependencies
a. Copy the bin folder as is to your project root level from bamboo-plan-templates.
b. Also copy the metaplan, depending on the mule version in use, to bamboo-plan-template. bamboo-plan-template folder
should be a the project root level too.
c. Check the metaplan.groovy to validate the below or make the desired changes
i. enableTerraform = true for enabling terraform jobs and tasks
ii.awsRegion for each environment, where the resources will be created.
2. Terraform IaC configs
a. Create folder named “terraform-template” at the project root level, this is where the terraform plans should be stored.
b. Create “vars.tf” under “terraform-template”, update default values for the below snippet and add it to the file.

12. All contents © MuleSoft Inc.
Using Terraform in Mulesoft CI/CD Count…
12
# terraform configurations
# aws provider authentication with assume_role
provider "aws" {
assume_role {
role_arn = "${var.role_arn}"
session_name = "${var.session_name}"
external_id = "EXTERNAL_ID"
}
region = “${var.region}"
}
# terraform remote state and locking configurations
terraform {
required_version = "~> 0.11.13"
backend "s3" {
encrypt = true
bucket = “<bucket name>"
region = “<region name>"
key = "<appname>.tfstate"
dynamodb_table = “<dynamodb table name>"
role_arn = "arn:aws:iam::238722377438:role/mule-tf-role"
session_name = "mule-terraform-session"
}
}

13. All contents © MuleSoft Inc.
Using Terraform in Mulesoft CI/CD Count…
13
# Business Group/ Unit metadata
variable "business_unit" {
default = “<team name>"
description = "The business unit for the team"
}
variable "resource_owner" {
default = “<owner name>"
description = "This is the path of IAM policy"
}
variable "service_name" {
default = “<app name>"
description = "Name of the service using this resource"
}
variable "role_arn" {
default = “<arn url>"
description = "This is an AWS role on the account configured for use by terraform"
}
variable "session_name" {
default = “<session name>"
description = "This is the description of IAM policy"
}
variable "region" {
default = "<region>"
description = "Region where the resources will be created"
}

14. All contents © MuleSoft Inc.
Using Terraform in Mulesoft CI/CD Count…
14
Now you can add the resources to the {service-name}.tf which are required by the service.
Example of SQS and S3 snippets
# aws resource configurations
# sqs-dlq pair
module "sqs-dlq-pair" {
#source = "../../terraform-iac-modules/modules/aws/sqs"
source = “${location of sqs resource}”
region = "${var.region}"
name = "hi-world-mule-4-sample-${terraform.workspace}"
principal_arn_list = "${list(
“<arn role url>/streamhub-demux"
)}"
environment = "${terraform.workspace}"
service_name = "${var.service_name}"
business_unit = "${var.business_unit}"
resource_owner = "${var.resource_owner}"
sqs_policy_props_principals_dev = "${list(
“<arn url>/streamhub-demux"
)}"
sqs_policy_props_actions = "${list(
"SQS:SendMessage",
"SQS:DeleteMessage"
)}"
}
# s3 bucket
module "s3-bucket-resource" {
source = “${location of s3 resource}”
name = "hi-world-mule-4-sample-${terraform.workspace}"
region = "${var.region}"
environment = "${terraform.workspace}"
service_name = "${var.service_name}"
business_unit = "${var.business_unit}"
resource_owner = "${var.resource_owner}"
}

15. All contents © MuleSoft Inc.
Using the terraform import command
Add Existing AWS resources
15
$ terraform import [options] ADDRESS ID

16. All contents © MuleSoft Inc.
Import SQS queues
16
Import using resource
$ terraform import aws_resource.resource_name SQS_queue_url
Eg:
$ terraform import aws_sqs_queue.sqs-q-resource https://sqs.ap-southeast-2.amazonaws.com/767678782327/hi-world-
mule-4-sample-ddev
Import using modules
$ terraform import module.module_name.aws_resource.resource_name SQS_queue_url
Eg:
$ terraform import module.sqs-dlq-pair.aws_sqs_queue.sqs-q-resource https://sqs.ap-southeast-
2.amazonaws.com/767678782327/hi-world-mule-4-sample-ddev

17. All contents © MuleSoft Inc.
Demo
 Creation of AWS resources
 Import AWS Resources

18. All contents © MuleSoft Inc.All contents © MuleSoft Inc.
Quiz
15
Winners will receive a gift

19. Mule DataWeave Format

20. All contents © MuleSoft Inc.
Custom Data Format’s Steps :
20
In order to create a Custom Data Format we need to create a Module
Define The extension (Define a variable with type Data Format)
 acceptedMimeTypes : The defines the mimeTypes that are going to be handled by this
DataFormat
 reader: References to the reader function
 writer: Reference to the writer function

21. All contents © MuleSoft Inc.
Custom Data Format’s Steps :
21
In order to create a Custom Data Format we need to create a Module
Write reader function
 The first one the content of the Binary to be read and transform to a Value.
 The second one the encoding to be used to read this content.
 The third one is the configuration settings. The type of this is defined by the
DataFormat implementer and is going to be used to hint the user on what settings are
valid.
 E.g:
fun readFixedWidth(content: Binary, charset: String, settings: SchemaUrlSettings): Any = ???

22. All contents © MuleSoft Inc.
Custom Data Format’s Steps :
22
In order to create a Custom Data Format we need to create a Module
Write writer function
 The first one is theValue to write and transform it into the Binary
 The second one is the settings The type of this is defined by the DataFormat
implementer and is going to be used to hint the user on what settings are valid.
 E.g:
fun writeFixedWidth(theValue: Any, settings: SchemaUrlSettings & EncodingSettings): Binary
= ???

23. All contents © MuleSoft Inc.
Custom Data Format’s Steps :
23
In order to create a Custom Data Format we need to create a Module
Register the Extension
 Create a file in src/main/resources/META-INF/dw-extensions.dwl that will contain a
reference to the Module so that DataWeave knows where the extensions are.
[
"org::mule::weave::simplefixedwidth::FixedWidth"
]

24. All contents © MuleSoft Inc.
Demo
 Deploy and use
Add the module dependency into pom.xml

25. All contents © MuleSoft Inc.All contents © MuleSoft Inc.
Quiz
15
Winners will receive a gift

26. Q&A

27. All contents © MuleSoft Inc.
What’s next
27
• Share:
– Tweet your pictures with the hashtag #BangaloreMuleMeetup
– Share the pics in WhatsApp group
• Let the community know you.. 
– Invite your network to join: https://meetups.mulesoft.com/bangalore/
• Feedback:
– Contact either Rajesh, Gaurav or Pruthvi to suggest topics for next
meetup
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the
program

28. THANK YOU