Collection of scripts and Lambda functions used for maintaining various AWS resources.
- Cross-region RDS backups
- Automated EC2 storage backups and retention management
- Monitor CloudTrail events
- Other Lambdas
Lambda function used to copy RDS snapshot from one region to another, to allow for the database to be restored in case of region failure. One (latest) copy for each RDS instance is kept in the target region. The provided CloudFormation template will create a subscription from RDS to Lambda, whenever an automated RDS snapshot on any database in that AWS region is made - that snapshot will be copied to target region and all older snapshots for that database will be removed.
You will be asked to specify the target region (where to copy your snapshots) to use by Lambda when creating the CloudFormation stack. The stack itself needs to be created in the same region where the RDS databases that you want to use it for are located.
You can also limit the function to only act for specific databases - specify the list of names in the "Databases to use for" parameter when creating the CloudFormation stack. If you leave it empty, Lambda will trigger for all RDS instances within the source region.
If your RDS instances are encrypted, you need to provide a KMS key ARN in the target region when creating the stack.
Since KMS keys are region-specific, when the snapshot is copied into another region, it needs to be re-encrypted
using a key located in that region.
Create a KMS key in the
target region, copy its ARN and paste that value into KMS Key in target region parameter when creating the
CloudFormation stack. If you do not provide that value, copy operation for encrypted snapshots will fail.
You can also provide that value if your RDS instances are not encrypted - the copied snapshots will be encrypted using that key.
If you don't use encryption and don't want your snapshots to be encrypted, leave the KMS Key in target region
parameter empty.
Since Aurora clusters do not offer an event notification for their automated backups, a daily schedule needs to be used
to copy the latest snapshot over to the target region. If you're using clusters, set Use for Aurora clusters to 'Yes'
when creating the CloudFormation stack. You can limit which clusters' snapshots are copied by specifying a comma-delimited
list in Aurora clusters to use for parameter.
The snapshots will be copied over once a day, at a random time of AWS choosing (using CloudWatch Event with rate(1 day)).
- Download the backup-rds.py file
from this repository and zip it into a file called
backup-rds.zip(for example:zip backup-rds.zip backup-rds.py). - Upload the ZIP file to an S3 bucket on your AWS account in the same region where your RDS instances live.
- Create a new CloudFormation stack using the template:
infrastructure/templates/rds-cross-region-backup.json. - CloudFormation will ask you for the following parameters:
- Required: Target region - provide the id of the AWS region where the copied snapshots should be stored, like 'eu-central-1'. Those are listed in AWS documentation.
- Required: Name of S3 bucket - name of the S3 bucket where you uploaded the ZIP in earlier step.
- Required: Name of ZIP file - name of the ZIP file in S3 bucket you uploaded. If you uploaded it into a directory,
provide a path to the file in S3 (for example
lambda_code/backup-rds.zip) - Required/Optional: KMS Key in target region - if your RDS instances are encrypted, provide an ARN of a KMS key in the target region. See Encryption section above.
- Optional: Databases to use for - if you want limit the functionality to only specific RDS instances, provide a comma-delimited list of their names.
- Optional: Use for Aurora clusters - select "Yes" if you have any Aurora Clusters that you want this code to work with.
- Optional: Aurora clusters to use for (applies only if you select "Yes" above) - if you want to limit the functionality to only specific Aurora Clusters, provide a comma-delimited list of clusters names.
Follow the update steps, but name the zip file something else that before - for example, if you uploaded backup-rds.zip,
upload the new file as backup-rds-1.zip. Update your CloudFormation stack with the latest template from this repo,
and provide that new ZIP file name in Name of ZIP file parameter.
Once all resources are created, you can test your Lambda from the Console, by using the following test event:
{
"Records": [
{
"EventVersion": "1.0",
"EventSubscriptionArn": "arn:aws:sns:EXAMPLE",
"EventSource": "aws:sns",
"Sns": {
"Type": "Notification",
"MessageId": "abcd",
"TopicArn": "arn:aws:sns:eu-west-1:123456789012:topic_name",
"Subject": "RDS Notification Message",
"Message": "{\"Event Source\":\"db-instance\",\"Event Time\":\"2017-12-26 22:34:07.882\",\"Identifier Link\":\"https://console.aws.amazon.com/rds/home?region=eu-west-1#dbinstance:id=database_name\",\"Source ID\":\"PUT_YOUR_RDS_NAME_HERE\",\"Event ID\":\"http://docs.amazonwebservices.com/AmazonRDS/latest/UserGuide/USER_Events.html#RDS-EVENT-0002\",\"Event Message\":\"Finished DB Instance backup\"}",
"Timestamp": "2017-12-26T22:35:19.946Z",
"SignatureVersion": "1",
"Signature": "xxx",
"SigningCertURL": "xxx",
"UnsubscribeURL": "xxx"
}
}
]
}
Replace the PUT_YOUR_RDS_NAME_HERE in the JSON string with a name of any of your RDS instances.
For Aurora Clusters, use the below event (no need to change anything):
{
"version": "0",
"id": "eb6d8ba9-c5c2-3269-3ac4-9918a9df74d9",
"detail-type": "Scheduled Event",
"source": "aws.events",
"account": "123456789012",
"time": "2018-01-30T21:11:00Z",
"region": "eu-west-1",
"resources": [
"arn:aws:events:eu-west-1:123456789012:rule/eventName"
],
"detail": {}
}
The code will go through all clusters (or those listed in Aurora clusters to use for parameter).
- Copying RDS snapshot to another region for cross-region recovery
- Complete code: cross-region RDS recovery
- Cross-region RDS recovery: encryption and Aurora support
Lambda function which will automatically create daily snapshots of instances tagged with "Backup" tag (name can be customized). The tag should contain a number of days the snapshot should be retained for - after that date, it will be deleted when this Lambda is executed.
- Encrypted volumes' snapshots will retain the encryption and use the same encryption key.
- Unencrypted volumes' snapshots will remain unencrypted.
- Default retention period is 7 days (can be changed in Lambda code, see below).
- Lambda can be run multiple times a day if needed, it will NOT create duplicated snapshots in the same day.
- Tags from EC2 instance will be copied to the snapshot (except "Backup" tag), and a new tag "CreatedBy" will be added with this Lambda's name.
- If you have a lot of instances to snapshot, you may need to extend the Lambda execution time (or schedule it to be executed multiple times a day).
- Download the ebs-snapshots.py
file from this repository and zip it into a file called
ebs-snapshots.zip(for example:zip ebs-snapshots.zip ebs-snapshots.py). - Upload the ZIP file to an S3 bucket on your AWS account.
- Create a new CloudFormation stack using the template:
infrastructure/templates/create-ebs-snapshots.json. - CloudFormation will ask you for the following parameters:
- Required: Name of S3 bucket - name of the S3 bucket where you uploaded the ZIP in earlier step.
- Required: Name of ZIP file - name of the ZIP file in S3 bucket you uploaded. If you uploaded it into a directory,
provide a path to the file in S3 (for example
lambda_code/ebs-snapshots.zip)
- Create the stack.
- Add a tag called "Backup" to some instances, with a number of days (or 0) you want to retain their snapshots for as the tag's value.
- That's it! CloudWatch Event Rule will be created that will trigger the Lambda once a day. You can also trigger it manually from Lambda console.
Follow the update steps, but name the zip file something else that before - for example, if you uploaded ebs-snapshots.zip,
upload the new file as ebs-snapshots-1.zip. Update your CloudFormation stack with the latest template from this repo,
and provide that new ZIP file name in Name of ZIP file parameter.
Trigger the Lambda from the console. Any (even empty) input will do, it will be ignored. Output from the Lambda will list tagged EC2 instances found and which EBS snapshots were created.
In ebs-snapshots.py file, one of the top few lines define the following variables, which you can change as needed:
DEFAULT_RETENTION- number of days the snapshots are retained for if the "Backup" tag value is zero (default: 7).BACKUP_TAG- name of the tag on EC2 instances the code will look for (default: "Backup").DELETE_ON_TAG- name of the tag with deletion date that will be added to snapshots (default: "DeleteOn"). Important: If you change this AFTER some snapshots were already created with previous name, those snapshots will not be deleted when their date is reached. Either update the tag name assigned to them, or delete them manually.
After changing those values, follow the update guide above to deploy your new code.
Lambda function which monitors CloudTrail logs and sends SNS notification on LaunchInstances event.
This can be modified to look for and respond to any AWS API calls as needed.
Use infrastructure/templates/cloudtrail-notifications.json CloudFormation template to create the Lambda,
CloudTrail and SNS topics. In the Outputs of the CloudFormation
stack, you'll find the SNS topic to which you can subscribe to receive the notifications.
The Lambdas below can be created by using infrastructure/templates/maintenance-lambdas.json CloudFormation template.
You should probably review (and adjust) them to your needs as necessary. They are provided as examples.
Remove AMIs from eu-west-1 (Ireland) and eu-central-1 (Frankfurt) based on different tags.
Meant to be used as a part of immutable infrastructure, where each project has a base AMI (tagged with Type=BaseImage)
and each release in contained within a new AMI based on it (tagged with Type=ReleaseImage).
Assumptions:
- base images are stored in Ireland. Release images are stored in Ireland and Frankfurt (as backups).
- Apart from
Typetag, each AMI has aProjecttag, which can contain any value.
Those scripts make sure only a certain amount of recent images for each project is stored to limit the costs.
Removes old CloudWatch indices inside AWS ElasticSearch Service. Useful when using CloudWatch log streaming into ElasticSearch.
Configure list of accounts, ElasticSearch endpoint and amount of last indices to be kept inside the code.