AWS SDK 3 Scripts

[augiadam]

Hi Guys,

Sorry for the delay but the update was not as simple as I initially thought. There may still be some functions in the file that I have not checked but the daily backup script works as intended for all functions with SDK 3.

Thanks,

Adam.

[dms2015]

I added all your changes and I added root keys instead of smtp and the script worked without all those write to log errors!! You are the bomb!!

What does it mean though that there were no instanceIDs to process below? I am happy that I am finally up to this here without all those errors. I am almost there!

Our Cloud Servers Production Daily Backup Starting Backup failed; no InstanceIDs to process Cleaning up daily snapshots 0 daily snapshots deleted Our Cloud Servers Production Backup Complete

PS- Ignore the other comments I posted in the wrong place, I think. I placed it here instead.

[noahlh]

This is awesome - thanks for working on this Adam. I'll merge now -- if there are any other issues related to the comment above, I'll gladly re-merge.

[dms2015]

I am very excited!! Now, I think it may be just one last simple thing to look over. Thanks Adam and thanks Noah!!!

Thank you, ​ Dawn Stevens

From: Noah Lehmann-Haupt [mailto:notifications@github.com] Sent: Wednesday, September 16, 2015 1:22 PM To: noahlh/aws-automated-backup-powershell aws-automated-backup-powershell@noreply.github.com Cc: Dawn Stevens dawn.stevens@dcsedi.com Subject: Re: [aws-automated-backup-powershell] AWS SDK 3 Scripts (#17)

This is awesome - thanks for working on this Adam. I'll merge now -- if there are any other issues related to the comment above, I'll gladly re-merge.

— Reply to this email directly or view it on GitHubhttps://github.com/noahlh/aws-automated-backup-powershell/pull/17#issuecomment-140876481.

---

This electronic mail transmission and its attachments are the property of Data Communication Solutions, Inc. It is intended for the above named recipient(s) only and may contain private and confidential information. If this has come to you in error, you may take no action based upon it, nor may you copy or disseminate it. Please email or telephone the sender immediately and delete the message if you are not the intended recipient.

[augiadam]

Hi Dawn,

Have you set a tag on your instance(s) to mark them for the backup? In my case I have added a tag called "Snapshot" to the instance I was using for testing and it is working correctly.

I have blanked out anything that might identify my environment but above is what you should see when the script finds an instance with the tag that you define in the DailySnapShot.ps1 $backupTag = "xxxxxxxx"

Thanks,

Adam.

[dms2015]

Adam, I tried my instance id and the instance name below where the x is but it still comes back as no instance. I tried my instance id without the dash also. The name I put case for case also. Maybe it is the VPC ID or something else? Verifying where I got this was on the EC2 Console under Instances. Is this correct or should it be another place I am getting this instance ID or backup tag? Thanks for the help!

$backupTag = "xxxxxxxx" #Make sure the value of this Tag is 'Yes', without the quotes, on the instances you want backed up

[augiadam]

Hi Dawn,

You need to make a new tag on the instance you want to back up, the instance ID or name will not work. You have to open AWS and select EC2 and then select the Tag menu option. From here you can set up a new tag with a value of "Yes". Once you have made the tag you can assign it to all the instances you want to back up and put the name of the tag in that $backupTag ="xxxxxxxx" field.

[dms2015]

Thank you. i have everything working now. :>)

I have one question: Snapshots that are to be deleted - are these setup somewhere in one of the scripts? Right now I have 0 daily snapshots deleted everyday so am I supposed to setup somewhere how many I would like to keep?