A function runs on AWS Lambda without customer-managed servers.
The team is identifying the settings that remain under customer control.
Which item is managed by the customer?
Lambda abstracts server provisioning, but the customer still manages function code, dependencies, execution permissions, and data handling.
Detailed explanation
The hypervisor is part of the AWS service infrastructure.
The hypervisor is part of the AWS service infrastructure.
AWS operates the physical infrastructure for the Lambda service.
AWS operates the physical infrastructure for the Lambda service.
The customer supplies and secures the code, its dependencies, and the IAM permissions used by the function.
The customer supplies and secures the code, its dependencies, and the IAM permissions used by the function.
AWS is responsible for physical facility security.
AWS is responsible for physical facility security.
Check official documentation
Compare the following points with the official documentation.
AWS Lambda Developer GuideのShared responsibility欄で、関数コードと実行権限の管理者を確認する。
What to confirm
関数コード・依存関係・権限設定は利用者側の管理対象である。
Key points
- Serverless
- Function code
- Execution permissions
Notes
- Environment: AWS公式ドキュメントのサービス別責任範囲確認
- Confirm the service-specific responsibility boundary in the current AWS documentation.
Foundation review
Serverless boundary
Lambda hides server provisioning while customer code and permissions remain visible responsibilities.
Dependency management
Libraries and packages included with a function are part of the customer workload.