Clarify declared read-handler permissions for AWS::Connect::Queue and AWS::Lambda::Function
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
- Tipo di issue
- Documentazione
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- aws
- Ambito
- cloud, documentation, infrastructure
Direzione di ricerca
Start with aws-connect-queue.json and aws-lambda-function.json, then read the linked CloudFormation schema archive, Connect action inventory, and Lambda API and encryption documentation. Done means an authoritative explanation or documented schema correction covers the read permissions, conditional kms:Decrypt requirements, and whether delete or stabilization invokes additional permissions.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Scope
This is a public CloudFormation schema/documentation clarification. It does not report a tenant permission denial or an observed authorization vulnerability. No account identifiers, private source, credentials, customer data, or resource identifiers are included.
Public source
The us-east-1 CloudFormation schema archive is published at:
https://schema.cloudformation.us-east-1.amazonaws.com/CloudformationSchema.zip
The supplied snapshot examined on 2026-09-20 has SHA-256:
840957c84089abbef464ab64a84ff72256a0db3546f60bdbe366b610047c9b63.
This identifies the examined snapshot, not an AWS executable-handler revision or a claim about all later archive versions.
1. AWS::Connect::Queue — ListQueueAgentGroups
In aws-connect-queue.json, SHA-256
5c87f350f88309846992c7dffb569c8a4e7d2bde99938f0646e3ffb68f8929ff,
handlers.read.permissions includes connect:ListQueueAgentGroups.
I could not locate an action entry named ListQueueAgentGroups in the retrieved public Connect service-reference action inventory:
https://servicereference.us-east-1.amazonaws.com/v1/connect/connect.json
Please provide the authoritative IAM action definition, supported resource types and ARN formats (or explicit absence of resource-level support), condition keys, and dependent permissions. If this is an internal/permission-only action, please clarify how customers should scope it. If the schema declaration is incorrect, please identify the corrected declaration and its applicability. No queue ARN, instance ARN, wildcard, or alternative action has been assumed.
2. AWS::Lambda::Function — conditional kms:Decrypt
In aws-lambda-function.json, SHA-256
a71fb36305d7e5bf4564705f61073b1da85713960c5ebed2474de4a689a31df7,
handlers.read.permissions includes kms:Decrypt; its delete declaration includes lambda:DeleteFunction, lambda:GetFunction, and ec2:DescribeNetworkInterfaces.
Lambda documents separate environment/configuration and source-package keys. GetFunction exposes Configuration.KMSKeyArn and Code.SourceKMSKeyArn:
https://docs.aws.amazon.com/lambda/latest/api/API_GetFunction.html
https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars-encryption.html
https://docs.aws.amazon.com/lambda/latest/dg/encrypt-zip-package.html
Please clarify which configuration-dependent branches require the caller or CloudFormation execution principal to have kms:Decrypt, and which complete non-content metadata establishes that a default-encryption branch does not require a customer-key permission. In particular, are the two key fields, package type, applicable snapshot configuration, and absence of response errors sufficient, or does the CloudFormation handler have other relevant dependencies? Where a customer key applies, please identify the required principal and encryption-context semantics or point to their documentation.
For both types, please also clarify whether standard DeleteStack processing or stabilization invokes the read handler or otherwise needs permissions beyond the delete handler's declared list. We are not treating the read/delete union as a guarantee of actual calls, nor dropping declarations without an authoritative basis.
Requested outcome
Documentation links, an authoritative explanation with applicable scope, or a documented schema correction. This is not a request to change IAM policies, deploy resources, access an account, or perform a destructive test.
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 1.1k
- Fork
- 62
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di aws-cloudformation/cloudformation-coverage-roadmap
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 61/100
-
Coverage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
aws-cloudformation/cloudformation-coverage-roadmap#2570 · 1 commento · 2 reazioni ·
-
[AWS::SES::MailManagerRuleSet] - [BUG] - SnsAction TopicArn pattern rejects valid GovCloud ARNsApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Tutte le issue di aws-cloudformation/cloudformation-coverage-roadmap
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
chore(worker): wrangler.toml has no [observability] block, so production Worker logs are not keptApertaagents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
harbor-framework/harbor#4323 ·
I maintainer di solito rispondono entro 1 giorno
-
s3: transient 5xx and 429 responses are not retried because the driver bypasses AwsClient.fetch()Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 2 giorni
-
[BUG] Bedrock Nova Lite metadata omits VIDEO input modalityForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabedrock bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
floci-io/floci#8456 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno