- Newest
- Most votes
- Most comments
Thanks Jose, Yeah, I couldn't find specific ARN for additional workers in the document. So there seems to be no way to attach tags for additional workers. https://docs.aws.amazon.com/ja_jp/mwaa/latest/API/API_Environment.html
Hi Hideki.
Please correct me if I'm wrong but it seems you are trying to add the tags using the AWS Console. Is that correct? If so, there are some resources that don't have a UI from the console to do that. It is not common, but it does happen.
You can add the tags using the CLI with the command tag-resource
. Here is the link to the documentation page.
Example:
aws mwaa tag-resource --resource-arn "arn:aws:airflow:us-east-1:123456789012:environment/MyMWAAEnvironment" --tags "Cluster=A"
I hope this helps.
I just get updated the latest cost explorer result, but unfortunately, found that the approach (=assigning tag via CLI) couldn't address my issue, I still find non-tagged spending. Do I need to specify any specific ARN for additional workers?
Hi Hideki. The ARN in the command is for the environment (per the documentation). I'm unclear whether it can be individual workers but you can try. Aside from that, I don't know any other way to do add tags. I hope that helps.
Relevant content
- asked 4 months ago
- asked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated a year ago
Thanks Jose, I just ran the command you suggested. will see whether attaching tags from CLI can address my issue tomorrow. Since the cost explorer is my only way to check the spending, and we don't activate hourly granularity, so I have to wait one day.