Update service metadata in iam_definition.json

[smrojas]

Problem

Observed UNKNOWN_PREFIX - Unknown prefix bedrock from parliament. This is a new AWS service called Bedrock. We need to refresh the mappings with the most recent services.

Testing

Ran python utils/update_iam_data.py > parliament/iam_definition.json and looked for the bedrock service in the json

    "prefix": "bedrock",                                                                                                                                                    "privileges": [
      {
        "access_level": "Write",
        "description": "Grants permission to create a job for customizing the model with your custom training data",
        "privilege": "CreateModelCustomizationJob",
        "resource_types": [
          {
            "condition_keys": [],
            "dependent_actions": [],
            "resource_type": "custom-model*"
          },
          {
            "condition_keys": [],
            "dependent_actions": [],
            "resource_type": "foundation-model*"
          },
          {
            "condition_keys": [],
            "dependent_actions": [],
            "resource_type": "model-customization-job*"
          },
          {
            "condition_keys": [
              "aws:RequestTag/${TagKey}",
              "aws:TagKeys"
            ],
            "dependent_actions": [],
            "resource_type": ""
          }
        ]
      }

[CLAassistant]

All committers have signed the CLA.

[iainelder]

Superseded by #239. Now bedrock is part of the default definitions.

[zuBux]

hey @iainelder,

The IAM definitions might need another update, looks like we're getting the following error on our side:

Unknown action bedrock:CreateFlow

bedrock as a service is recognised in 1.63 but this permission is not :)

[iainelder]

@zuBux , I'd like to help, but I'm not an owner or official contributor to the repo. I don't have any power to update the default IAM definitions.

I think @rjcassara- can help. He handled it the last time by merging someone's proposed changes and creating a new GitHub release. See #230 .

In the meantime, you can update your local IAM definitions using the steps described in "Updating the privilege info" in the README. I contributed that section last year in #240. It might still work for you. :-)

[zuBux]

hey @iainelder,

Thanks for the info! I'll update the IAM definition and submit a PR then :D. I prefer this change upstream to be honest because then we can just bump the version in pip instead of creating local builds