Amazon CodeGuru Profiler · Authentication Profile

Amazon Codeguru Profiler Authentication

Authentication

Authentication and authorization profile for Amazon CodeGuru Profiler. Every request is signed with AWS Signature Version 4 using IAM credentials — there is no API key, bearer token, OAuth flow or OIDC discovery document. Authorization is expressed as IAM actions on codeguru-profiler:*, plus an optional resource-based policy on each profiling group for cross-principal access.

Amazon CodeGuru Profiler secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

AmazonApplication PerformanceProfilingDevOpsMachine-Learning
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

hmac apiKey
· in: header (Authorization)

Source

Authentication Profile

Raw ↑
generated: '2026-09-01'
method: searched
source: https://docs.aws.amazon.com/codeguru/latest/profiler-ug/security-iam-awsmanpol.html
derived_from: openapi/amazon-codeguru-profiler-openapi-original.yaml
description: >-
  Authentication and authorization profile for Amazon CodeGuru Profiler. Every request is signed
  with AWS Signature Version 4 using IAM credentials — there is no API key, bearer token, OAuth
  flow or OIDC discovery document. Authorization is expressed as IAM actions on
  codeguru-profiler:*, plus an optional resource-based policy on each profiling group for
  cross-principal access.
summary:
  types:
    - apiKey
  api_key_in:
    - header
  oauth2: false
  openid_connect: false
  mutual_tls: false
schemes:
  - name: hmac
    type: apiKey
    in: header
    parameter: Authorization
    description: Amazon Signature authorization v4
    signing_name: codeguru-profiler
    sources:
      - openapi/amazon-codeguru-profiler-openapi-original.yaml
    note: >-
      Modelled as apiKey-in-header because that is the closest OpenAPI 3.x securityScheme to
      SigV4. It is NOT a static key: the Authorization header carries a per-request HMAC
      signature derived from an access key, secret key, optional session token, the request
      canonicalisation, the region and the date.
credential_sources:
  - IAM user long-lived access keys
  - IAM role temporary credentials (STS)
  - IAM Identity Center / AWS SSO
  - EC2 / ECS / Lambda instance and task roles
authorization:
  model: iam-policy
  service_prefix: codeguru-profiler
  resource_arn_pattern: 'arn:aws:codeguru-profiler:{region}:{account}:profilingGroup/{name}'
  managed_policies:
    - name: AmazonCodeGuruProfilerFullAccess
      description: >-
        Provides full access to CodeGuru Profiler, including permissions to create, update, and
        delete profiling groups.
      actions:
        - 'codeguru-profiler:*'
        - 'codeguru:*'
        - 'iam:ListRoles'
        - 'iam:ListUsers'
      resource: '*'
    - name: AmazonCodeGuruProfilerReadOnlyAccess
      description: >-
        Grants read-only access to CodeGuru Profiler and related resources in other AWS services.
      actions:
        - 'codeguru-profiler:Get*'
        - 'codeguru-profiler:Describe*'
        - 'codeguru-profiler:List*'
        - 'codeguru:*'
        - 'iam:ListRoles'
        - 'iam:ListUsers'
      resource: '*'
    - name: AmazonCodeGuruProfilerAgentAccess
      description: >-
        Added to the execution role of AWS Lambda functions onboarded to CodeGuru Profiler via
        the Lambda console monitoring page. Allows the agent to create a profiling group, refresh
        its configuration and submit agent profiles.
      actions:
        - 'codeguru-profiler:ConfigureAgent'
        - 'codeguru-profiler:CreateProfilingGroup'
        - 'codeguru-profiler:PostAgentProfile'
      resource: 'arn:aws:codeguru-profiler:*:*:profilingGroup/*'
      least_privilege: true
      note: >-
        This is the policy an autonomous agent workload should be given. It is the only one of
        the three scoped to a resource ARN rather than '*', and it grants exactly the three
        operations a running profiler needs — no read of findings, no delete.
  resource_based_policy:
    supported: true
    operations:
      - PutPermission
      - GetPolicy
      - RemovePermission
    concurrency: revisionId (optimistic lock; ConflictException 409 on a stale revision)
    note: >-
      A profiling group can carry its own resource policy granting an actionGroup to named
      principals, which is how cross-account agent submission is enabled without sharing IAM
      credentials.
discovery:
  openid_configuration: null
  oauth_authorization_server: null
  note: >-
    Probed 2026-09-01 on codeguru-profiler.us-east-1.amazonaws.com (403 SigV4 front door),
    docs.aws.amazon.com (404) and aws.amazon.com (301 -> 404). No OAuth/OIDC discovery document
    exists, which is expected for a SigV4 service.
  see: well-known/amazon-codeguru-profiler-well-known.yml
docs:
  - https://docs.aws.amazon.com/codeguru/latest/profiler-ug/security-iam-awsmanpol.html
  - https://docs.aws.amazon.com/codeguru/latest/profiler-api/CommonParameters.html
  - https://docs.aws.amazon.com/codeguru/latest/profiler-api/API_PutPermission.html

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/amazon-codeguru-profiler-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.