- 新しい順
- 投票が多い順
- コメントが多い順
Looks as though your SCP is matching, which means the tag name it's looking for is Null. If you don't speak American English, try double checking the spelling of your tag name? The tag in the blog post uses costcenter, so check you're not naming your tag costcentre?
While creating instance, you should select Instances and Volumes both for tags as below, if you won't choose both for tagging then instance creation would fail.
You might be adding tags but by default, it would apply only to instance not volume so SCP explicit deny would come into effect as shown in error message.
Edit: Adding snapshot for your reference for adding tags:
Hi, I am selecting both instances and volumes, still I get authorization error. Also, I have Admin role. With any SCP I can create EC2. Are you able to make it work in your environment?
Hey,
I got the problem, if you look at tag policy(Step-1), allowed values for tag costcenter are CC102, CC103, CC104 and allowed values for team are Team1, Team2, Team3. I assume, you have copied pasted the policies from the blog as is, which means you can only pass values to these two tags from the allowed values.
Earlier, I only tested with those conditions, not with exact policies. I'm attaching snapshot for your reference in the answer for your reference.
関連するコンテンツ
- 質問済み 6年前
Never realized I had been using "costcentre" and not costcenter :-|