Skip to main content

AWS EC2 Add Tag with multiple values separated by commas



PowerShell got cmdlets that supports AWS, adding an EC2 Tag in AWS using PowerShell is quite straight forward.

Adding multiple tag values is another thing. 

If multiple tags have to be added, it would make sense to separate those values by commas, it will be easy to read and would also indicate that the value separated by commas are different but share the same main key.

Adding tags like this in PowerShell is quite easy.

Here’s the code:

aws ec2 create-tags --resources i-123456abc, i-7896543afsd, i-0123098sdf `
--tags 'Key=\"Product\",Value=User_flawed',   'Key=\"Dept\",Value=Warehouse', `
'Key=\"Location\",Value=SF_Holly', 'Key=\"Function\",Value=Null_Database',  `
'Key=\"Crawlers_Remarks\",Value=\"Indexer, Whatever, Ongoing\"   '

These are instance id’s in which the tag will be created:

i-123456abc, i-7896543afsd, i-0123098sdf

New tags:
Product with value User_flawed

Dept with value Warehouse
Location with value SF_Holly
Function with value Null_Database'

Crawlers_Remarks with multiple values of  Indexer, Whatever, Ongoing

The space after the quote is necessary after the last value: ,Ongoing\" d_white_space  '

If there is no space between the double quotes and single quote there will be an error.

Notice also that the double quotes have been escaped with a backslash.

The back-tick character is just for readability to separate the PowerShell commands into multiple lines.

The instance-id can also be replaced with the volume-id for the EBS volume, then just replaced the key and values with the appropriate information for the EBS volume.

Without the double quotes, multiple values separated by commas won’t be added to AWS Tag if PowerShell is used to create or update by replacing the Tags.

If above command is used to update the tags, just put the new value and it will update or replace the existing tag values.

 Cheers. Till next time.

================================
Free Android Apps:

Click  links below to find out more:

Excel Keyboard guide:


Heaven's Dew Fall  Prayer app for Android :



Catholic Rosary Guide  for Android:


Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:




Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more