![]() ![]() Create the set-drs-templates function, replace $ INSERTROLEARN with the ARN of the role you created for the solution.Create the schedule-drs-templates Replace $INSERTROLEARN with the Amazon Resource Name (ARN) of the role you created for the solution.Create the zip deployment package of the schedule-drs-templates.Create the zip deployment package of the set-drs-templates.You can deploy the solution in three main steps: create the Lambda functions, create the S3 bucket trigger, and create a template. The policy has been created to only allow the minimum required permissions to ensure the solution is functional. You can create a role with the provided policy.json to give the solution the proper API access. You must have a role with the proper permissions to access all three services. This solution includes creating Lambda functions that make application programming interface (API) calls to DRS, EC2, and S3. The command line interface (CLI) provides deployment instructions that use the AWS CLI. For more information on getting started with DRS reference the quick start guide. This solution requires active servers in DRS. This allows new servers that are added to AWS Elastic Disaster Recovery to inherit the tagged launch template.įull code for the solution can be found in the aws-samples GitHub repository. An AWS Lambda function that runs on a schedule and scans for any new replicating servers with a tag that matches one of the existing templates in the bucket.This function is called set-drs-templates. ![]() It then updates DRS servers that are tagged with the prefix of that json. An AWS Lambda function that pulls down a json launch template from the bucket.An Amazon S3 bucket for storing launch templates in the form of json files.This solution is comprised of the following components: The following diagram illustrates the solution workflow. The proposed architecture allows replicating machines, that share the same tag, to use the same launch template. In this post, I demonstrate a solution for automating the setup of DRS launch templates using AWS Lambda functions and AWS Simple Storage Service (S3). To manage these launch templates at scale, you can use automation to create a repeatable and auditable process. They can then run natively within Amazon Elastic Compute Cloud (Amazon EC2) in the event of a DR event or drill.Įlastic Disaster Recovery uses unique EC2 launch templates to manage the configuration of the failed over infrastructure. Operated from the AWS Management Console, Elastic Disaster Recovery helps you recover all of your applications and databases that run on supported Windows and Linux operating systems. Without the proper tools in place, setting up such a recovery can potentially become burdensome, as infrastructure continually changes based on business demands, making ensuring repeatability and scalability difficult.ĪWS Elastic Disaster Recovery (DRS) is the recommended service for DR to AWS. To increase the chances of success in the case of an outage event, recovery should be repeatable, scalable, and tested often. It’s important to have a disaster recovery (DR) plan in place that helps operations continue in the event of a natural, physical, or technology-based disaster. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |