func-api-devices-backup-post

Overview

Deploys the Lambda function that handles POST /devices/{uuid}/backup. Called by the Controller firmware to upload an encrypted configuration backup to S3. Authenticates the request by verifying an ECDSA P-256 signature over SHA-256(nonce || timestamp) using the public key stored at registration time. This route has no Cognito JWT authorizer — it is authenticated solely by the device's cryptographic signature.

CloudFormation Stack

firefly-func-api-devices-backup-post

CloudWatch Logs

Setting	Value
Log group	/aws/lambda/firefly-func-api-devices-backup-post
Retention	30 days

Dependencies

Deploy Dependencies

Workflow	Reason
api-gateway	ApiId resolved from stack outputs
dynamodb-devices	Table must exist before the function is deployed and granted read/write access
shared-layer	Lambda layer must exist before function deployment
s3-device-backups	S3 bucket must exist before the function is deployed and granted put/head access

Delete Dependencies

None — this workflow has no prerequisites.

Required By

Required By Deploy

Workflow	Reason
run-integration-tests	Endpoint must be live before integration tests run

Required By Delete

Workflow	Reason
delete-api-gateway	Route registration must be removed before the API Gateway stack is deleted
delete-dynamodb-devices	IAM permissions referencing the table must be removed first
delete-shared-layer	Layer reference must be removed before the layer stack is deleted
delete-s3-device-backups	IAM permissions referencing the bucket must be removed first

IAM Permissions

The Lambda execution role (firefly-func-api-devices-backup-post-role) is granted:

• dynamodb:GetItem, dynamodb:UpdateItem on firefly-devices
• s3:PutObject, s3:HeadObject on the device backups bucket
• appconfig:StartConfigurationSession, appconfig:GetLatestConfiguration on *

Deploy Workflow

Description

Resolves the HTTP API Gateway ID, shared layer ARN, and AppConfig extension layer ARN from CloudFormation stack outputs. Installs cryptography, cffi, and pycparser as arm64 binary dependencies alongside the Lambda source, then performs a SAM deploy.

Steps

1. Configure AWS credentials.
2. Look up ApiId from the firefly-api-gateway stack output.
3. Look up SharedLayerArn from the firefly-shared-layer stack output.
4. Look up AppConfigExtensionLayerArn from the firefly-shared-layer stack output.
5. Install Python arm64 dependencies into lambdas/func-api-devices-backup-post/.
6. SAM deploy firefly-func-api-devices-backup-post with parameters:
   • ApiId
   • SharedLayerArn
   • AppConfigExtensionLayerArn
   • BackupBucketName

Delete Workflow

Description

Calls sam delete to remove the Lambda function, its IAM role, and the API Gateway route integration. Also deletes the CloudWatch log group.

Steps

1. Configure AWS credentials.
2. SAM delete firefly-func-api-devices-backup-post.
3. Delete CloudWatch log group /aws/lambda/firefly-func-api-devices-backup-post.

Failure Scenarios

Scenario	Behavior
firefly-api-gateway stack not found	describe-stacks returns an error; workflow fails before SAM deploy. Deploy api-gateway first.
firefly-dynamodb-devices stack not deployed	Function deploys but returns errors at runtime. Deploy dynamodb-devices first.
firefly-shared-layer stack not found	Layer ARN lookup fails; SAM deploy is not attempted. Deploy shared-layer first.
firefly-s3-device-backups stack not deployed	Function deploys but S3 operations fail at runtime. Deploy s3-device-backups first.
Device UUID not found	Lambda returns 401 Unauthorized.
Timestamp outside the acceptance window	Lambda returns 401 Unauthorized.
Invalid or mismatched signature	Lambda returns 401 Unauthorized.
Body not valid FFCE format	Lambda returns 400 Bad Request.