Skip to main content

12 — Deployment readiness reference — AWS & Azure checklists, prerequisite owners & key contacts.

The following checklists summarise the technical prerequisites and governance steps required before Layerup AI Agents are ready for production deployment in your cloud environment. They are intended for your Enterprise Architecture and Platform Engineering teams to use as the authoritative pre-go-live gate. All checklist items must be confirmed as complete before live application traffic is routed to the agent. Items marked with a Layerup co-owner require coordination with your Layerup Implementation Lead.

11.1 AWS deployment readiness checklist

checklist itemowner
AWS Marketplace subscription active for Layerup AI Agent listingYour Procurement + AWS Account Team
Designated ECR repository created for Layerup container images within your AWS accountYour Platform Engineering
Image signing verification policy configured in ECR to enforce Cosign signature validation before pullYour Security Team
checklist itemowner
Amazon Inspector enabled on the designated ECR repository for automatic image scanning on pushYour Security Team
Inspector findings severity threshold defined and enforced in CI/CD promotion pipeline (block on Critical / High)Your Security Team + Platform Engineering
checklist itemowner
Dedicated VPC with private subnets configured for agent compute — no Internet Gateway route from agent subnetsYour Platform Engineering
VPC Endpoints provisioned for: S3, SQS, Amazon Bedrock, CloudWatch Logs, ECR (both ecr.api and ecr.dkr)Your Platform Engineering
Security Group rules configured for agent compute: no inbound from outside VPC; outbound restricted to VPC endpoint destinations onlyYour Security Team
checklist itemowner
Customer-managed KMS key created and designated for agent data (S3 input/output, CloudWatch Logs, optional intermediate state storage)Your Security Team
S3 input bucket and S3 output bucket created with CMK encryption, versioning enabled, and bucket policies restricting access to agent IAM role onlyYour Platform Engineering
Key access policy confirmed: agent IAM role has kms:Decrypt only — cannot rotate, disable, or delete the keyYour Security Team
checklist itemowner
SQS intake queue and completion queue created with appropriate Dead-Letter Queue (DLQ) configuration and visibility timeout set to accommodate maximum processing time (60 minutes recommended)Your Platform Engineering
EventBridge rules (or S3 Event Notification → SQS trigger) configured to route application packet uploads to the agent triggerYour Platform Engineering
checklist itemowner
IAM Execution Role created with least-privilege policy (s3:GetObject/PutObject on designated buckets, bedrock:InvokeModel on approved model ARNs, bedrock:ApplyGuardrail, sqs:ReceiveMessage/DeleteMessage, logs:PutLogEvents, kms:Decrypt) and explicit deny-all for all other permissionsYour Security Team
Confirmed: no Layerup personnel hold permanent IAM credentials in your AWS account. Implementation-phase time-limited role revocation plan agreed.Your Security Team + Layerup
checklist itemowner
Amazon Bedrock Guardrail policy configured by your AI Platform team: topic denial policies, PII redaction rules, grounding check enabled, prompt injection protection enabledYour AI Platform Team
Designated Bedrock model ARN approved, access granted in IAM role, and Bedrock service quota confirmed sufficient for expected concurrent case volumeYour AI Platform Team
checklist itemowner
CloudWatch Log Group created with 7-year retention policy and data protection lock (tamper prevention) appliedYour Platform Engineering
CloudWatch Metrics dashboard configured for operational monitoring: cases_processed_count, cases_flagged_for_escalation_count, average_processing_time_seconds, guardrail_interventions_count, queue depthYour Platform Engineering
CloudWatch Alarms configured: error rate threshold, queue depth breach, model timeout rate, agent health degradation — with on-call notification routingYour Platform Engineering
checklist itemowner
Container image promotion pipeline gates configured: Inspector scan gate, regression test gate, approval gate, and post-deploy verification alarm monitoringYour Platform Engineering
checklist itemowner
Your organisation’s underwriting SOP documents provided to Layerup implementation team for AOP authoringYour Underwriting Leadership
AOP validation test set (historical cases with known outcomes, minimum 50 cases recommended) provided to Layerup for validation testingYour Underwriting Leadership
AOP stored in your source control system (CodeCommit / GitHub Enterprise) with approval workflow configured for AOP amendmentsYour Platform Engineering
AOP version confirmed as meeting >99% reproducibility target on validation case set before production go-liveLayerup + Your Underwriting Leadership
checklist itemowner
Blue/Green or Shadow Mode deployment strategy selected and infrastructure configured before first live trafficYour Platform Engineering + Layerup
Initial phase rollout percentage defined — recommended: Phase 1 at 10% of live application volumeYour Underwriting Leadership + Layerup
Escalation workflow to human senior underwriter configured and tested: escalation queue routing, SLA assignment, notification to on-call underwriterYour Underwriting Operations

11.2 Azure deployment readiness checklist

checklist itemowner
Azure Marketplace offer subscription active for Layerup AI Agent (Container App offer or Managed Application)Your Procurement + Microsoft Account Team
Azure Container Registry (ACR) instance provisioned within your Azure tenant; geo-replication enabled across designated regionsYour Platform Engineering
Azure Defender for Containers enabled on ACR for continuous image scanningYour Security Team
checklist itemowner
Azure Virtual Network with private subnet configured for agent compute — no direct route to public internet from agent subnetYour Platform Engineering
Private Endpoints provisioned for: Azure Blob Storage, Azure Service Bus, Azure OpenAIYour Platform Engineering
Network Security Group (NSG) rules configured: no inbound from outside VNet; outbound restricted to Private Endpoint destinations onlyYour Security Team
checklist itemowner
Azure Key Vault provisioned with CMK for agent data encryption; access policies restrict agent Managed Identity to Secrets User role onlyYour Security Team
Blob Storage input and output containers configured with CMK encryption and RBAC-scoped access (Managed Identity access only)Your Platform Engineering
checklist itemowner
Azure Service Bus namespace and queues configured with Dead-Letter Queue; KEDA autoscaling configured on Container Apps environment or AKS HPA configured for SB queue depthYour Platform Engineering
checklist itemowner
User-Assigned Managed Identity created with least-privilege RBAC assignments: Blob Data Reader (input), Blob Data Contributor (output), Cognitive Services OpenAI User (specific OpenAI resource), Key Vault Secrets User (designated vault), Monitoring Metrics Publisher (designated workspace)Your Security Team
Confirmed: identity has no subscription-level roles and no access to resources outside explicitly scoped assignmentsYour Security Team
checklist itemowner
Azure OpenAI resource provisioned within your Azure tenant (not shared/public endpoint); Azure AI Foundry hub configuredYour AI Platform Team
Azure AI Content Safety policy configured: harm category classifiers enabled, Prompt Shield enabled, custom blocklists added as requiredYour AI Platform Team
checklist itemowner
Log Analytics Workspace configured with 7-year retention and immutability policy; Azure Monitor export to Azure Storage with lifecycle management to archive tier enabledYour Platform Engineering
Azure Monitor Alerts configured for agent health degradation, queue depth breach, and SLA breach — with on-call operations notification routingYour Platform Engineering
checklist itemowner
Azure DevOps (or GitHub Actions) pipeline gates configured for container image promotion: Defender scan gate, regression test gate, approval gate, and post-deploy monitoring windowYour Platform Engineering

11.3 Key contacts

contactrole
Layerup Implementation LeadPrimary point of contact for AOP onboarding, integration design, and deployment support. Engaged throughout the implementation phase.
Layerup Solutions EngineeringTechnical resource for cloud architecture questions, IAM policy review, data pipeline integration design, and VPC / VNet topology guidance.
Layerup Security TeamAvailable to participate in your vendor security review process. Provides SOC 2 Type II report, penetration test results, SBOM documentation, and Cosign signature verification guidance under NDA.
All Layerup personnel access during the implementation engagement is performed via a time-limited, audited IAM role / Azure PIM assignment that is explicitly revoked upon production go-live. Your security team controls the revocation. After go-live, no Layerup personnel hold access credentials to your production environment.