So far so good. You're program works.
Sure would be nice if we could add a tag so I knew the instance name for each volume snapshot and a way to add info to the description field.
Search found 4 matches
- Wed Jun 29, 2016 2:59 pm
- Forum: Version 3
- Topic: EBS snapshot tagging
- Replies: 10
- Views: 53279
- Tue Jun 28, 2016 3:39 pm
- Forum: Version 3
- Topic: EBS snapshot tagging
- Replies: 10
- Views: 53279
Re: EBS snapshot tagging
You were correct. I didn't notice that I had NAME in all caps. Once I changed it the backup started to work. How that I have the Name field getting populated I'd like to set the Description field so it has the instance name.. I tried using Name=$VOLID;Description=$INSTANCE but it didn't work. I chec...
- Mon Jun 27, 2016 7:01 pm
- Forum: Version 3
- Topic: EBS snapshot tagging
- Replies: 10
- Views: 53279
Re: EBS snapshot tagging
Stephan,
The snapshots are created, but the tag for Name isn't getting created for the snapshop. The Name field is blank.
The snapshots are created, but the tag for Name isn't getting created for the snapshop. The Name field is blank.
- Mon Jun 27, 2016 4:28 pm
- Forum: Version 3
- Topic: EBS snapshot tagging
- Replies: 10
- Views: 53279
Re: EBS snapshot tagging
I used the exact syntax you suggested, but now I'm getting the following error: Exception: Couldn't store job: Unable to store Job: 'AWSJob.AWSCopySnapshotJob201606270916167638', because one already exists with this identification. Job Type: Copy EC2 Snapshot Job Name: Job ID: AWSCopySnapshotJob2016...