kshitiz-arya / aws-cloudformation-migrations Goto Github PK

This project will help you automate migration of lambda functions across account using CloudFormation. The framework was built for LexisNexis, it connects to an existing AWS account and region, clones the existing lambda functions within that region. Given a list of target resources it will generate the appropriate CloudFormation template for the function and tables, including all of the original parameters from the DDL. The next step will be deploying those CloudFormation templates into the destination account.

In the customer's environment (LexisNexis), they needed to migrate a lot of existing services into different AWS accounts. They have used multiple accounts as Dev/Cert/Prod environments for deployments. LexisNexis needed to automate the whole deployment process through CloudFormation to create a more maintainable and reliable product. In this specific use case they had about 10 different lambda functions with hundreds of tables that needed to be migrated and automated. The framework has saved them a lot of time and manual effort.

Using CloudFormation to deploy and manage services has a number of nice benefits over more traditional methods (AWS CLI, scripting, etc.).

A template can be used repeatedly to create identical copies of the same stack (or to use as a foundation to start a new stack). Templates are simple YAML- or JSON-formatted text files that can be placed under your normal source control mechanisms, stored in private or public locations such as Amazon S3, and exchanged via email. With CloudFormation, you can see exactly which AWS resources make up a stack. You retain full control and have the ability to modify any of the AWS resources created as part of a stack.

Fed up with outdated documentation on your infrastructure or environments? Still keep manual documentation of functions, code handler, etc.?

With CloudFormation, your template becomes your documentation. Want to see exactly what you have deployed? Just look at your template. If you keep it in source control, then you can also look back at exactly which changes were made and by whom.

CloudFormation not only handles the initial deployment of your infrastructure and environments, but it can also manage the whole lifecycle, including future updates. During updates, you have fine-grained control and visibility over how changes are applied, using functionality such as change sets, rolling update policies and stack policies.

The files below are included in this repository:

After the CloudFormation templates have been deployed, the Stack Resources contain the information about the different resources that was deployed.

1. Running python environment.
2. The following python packages: collections, boto3
3. Origin lambda functions clone.

1. Before running this repository make sure that you have configured your AWS account credentials so you have access to an AWS account, use aws configure (in the cli) to set YOUR_ACCESS_KEY, YOUR_SECRET_KEY. If using temporary credentials with STS, please set up a token as well using this command: aws configure set aws_session_token <YOUR_SESSION_TOKEN>. For more information .
2. Make sure you set-up the wanted properties of the source resources to clone (set 2 parameters in lambdaProperties: sourceFunction and sourceTables). You can set the working directory location as a parameter given from the argument line (runtime variable), the lambda functions to clone, the lambda functions to clone (can be one or many, to clone all existing parameters in the function leave empty), and the generic templates can be set in the lambdaProperties.json as well.
3. Run the code and wait until it's finished, the code prints some of the results and status updates for debugging purposes.
4. Take the final CloudFormation templates from the Templates folder, deploy them in the CloudFormation of the destination account.
5. Use the new resources as you would normally do.

Please create a new GitHub issue for any feature requests, bugs, or documentation improvements.

Where possible, please also submit a pull request for the change.

This code repository is licensed under the MIT-0 License. See the LICENSE file.

See VSCode.md for VSCode template code completion and inline validation support