This script creates a CloudFormation stack in AWS which syncs your AWS resources into IT Glue as configurations or flexible assets. Each resource will have a lambda function that is either triggered by an AWS CloudWatch Event or it will be triggered on a daily basis.

The script supports the following resources from AWS:

• EC2 Instances - Instance state change triggers CloudWatch Event which triggers the lambda function. Syncs in as Configurations.
• Workspaces - Lambda function is invoked at 12:00am UTC Monday to Friday. Syncs in as Configurations.

You will need Python 3.6 installed in your system. You will also need to have aws-cli installed and configured with your AWS credentials.

• For information on installing the CLI, see here.
• For information on configuring your credentials see here.

First, you will need to make sure you have Python 3.6 with setuptools, pip and venv installed. You can follow the steps here to install Python 3 in your system.

Once you have Python 3.6 installed, create the Python virtual environment in the root of this project with the following command:

python3 -m venv venv

To activate the virtual environment, use the command below that corresponds to your OS.

source venv/bin/activate

venv\Scripts\activate.bat

Now we need to install the script dependancies using pip.

pip install -r requirements.txt

Before we can create a CloudFormation stack, the script requires certain parameters to be set. Copy the parameters_example.json to a file named parameters.json at the same folder level.

In your parameters.json file, copy and paste in your IT Glue API Key, the correct API endpoint based on your region and the organization name or ID in your account where you wish to import the resources. Make sure you save before moving on to the next step.

For North American users, the IT Glue API endpoint is https://api.itglue.com For EU users, please use https://api.eu.itglue.com

Now, we can create the CloudFormation stack. This will spin up a stack that contains a lambda function, a role and a policy specifically for each resource you specified to import.

• STACK_NAME - a unique name for your CloudFormation stack (required)
• --add-all - imports all the resources we currently support
• -r, --resources - takes specific resource names separated by spaces. Currently only supports 'workspace', 'ec2'. Will be ignored if --add-all flag is true.

e.g. import only workspaces

python create_cloudformation_stack.py STACK_NAME -r workspace

e.g. import all resources

python create_cloudformation_stack.py STACK_NAME --add-all

This will take a few minutes to complete. The command will terminate after the stack is completed successfully; and you can also check your AWS console to monitor the progress.

Each lambda function created in the stack will only be functional with a lambda zip package. To zip up the packge, run:

python lambda_zip.py

Now, all we need to do is push our zip file to the Lambda. You can find all of the functions created in the stack in the Resources tab in the CloudFormation AWS console.

The convention of the functions are named like {your_stack_name}workspaceSyncFunction unless changed in the template files.

aws lambda update-function-code --function-name <FUNCTION_NAME> --zip-file fileb://lambda_handler.zip

You need to repeat this for each function created in the CloudFormation stack.

• If you make changes to your stack, you can change update it with the same command in step 2 with the exact same stack name.
• If you make changes to the script, you will need to repeat steps 3 and 4.

The script requires your IT Glue API Key to validate requests and the IT Glue API URL

export ITGLUE_API_KEY=<YOUR_API_KEY>
export ITGLUE_API_URL="https://api.itglue.com"

For users in Europe, the API_URL is https://api.eu.itglue.com

You can call the import scripts directly to import or update EC2 Instances. The flags available are:

• -id - imports/updates the instance that matches the instance_id
• --add-all - imports all of the EC2 instances found in AWS. Will ignore -id flag
• -il - imports the locations associated with each instance

• import 1 single instance without location

    python import_ec2.py YOUR_ORG_ID  -id="INSTANCE_ID"
  

• import all instances with their locations

    python import_ec2.py YOUR_ORG_ID --add-all -il
  

You can call the import scripts directly to import or update workspaces. The flags available are:

• -id - imports/updates the workspace that matches the workspace_id
• --add-all - imports all of the workspaces found in your AWS account. Will ignore -id flag

• import 1 single workspace

    python import_workspace.py YOUR_ORG_ID -id="WORKSPACE_ID"
  

• import all workspaces

    python import_workspace.py YOUR_ORG_ID --add-all