# WP Suite Deployment Access WP Suite Deployment Access - AWS-native Backends for WordPress is a separate AWS Marketplace product for agencies and technical teams that want supported WP Suite backend services deployed into their own AWS account. WordPress remains the CMS and editorial layer. AWS Marketplace Quick Launch, the WP Suite Deployment Wizard, and a version-controlled CloudFormation orchestrator provide the guided deployment path. Public AWS Marketplace listing: https://aws.amazon.com/marketplace/pp/prodview-6co4ozyovp2qg ## Contract scope and price The public offer is a 36-month, $500 software contract for one buyer AWS account. It includes: - deployment and update access for the entitled AWS account during the contract term - the WP Suite Deployment Wizard and AWS Marketplace Quick Launch flow - supported CloudFormation templates for selected WP Suite backend components - Marketplace entitlement validation and controlled access to deployment packages - configuration and deployment support for the supported product scope - unlimited deployment modifications and stack reconfigurations during the term, with no additional Deployment Access usage fee The contract does not include the AWS infrastructure charges generated by deployed resources. AWS bills those charges separately to the buyer AWS account. The buyer remains responsible for the account, IAM and security policies, service quotas, cost controls, monitoring, backups, data, and production operations. The Marketplace price and contract terms displayed during purchase take precedence over this summary. ## Supported component families ### Cognito identity foundation Deploy Amazon Cognito-based authentication and the identity resources required by supported Gatey and protected-API integrations. Depending on configuration, the deployment can create a new Cognito foundation or connect supported components to existing Cognito resources. ### AI-Kit Backend Deploy AWS-native APIs and storage for supported private AI, fallback processing, grounded chat, and knowledge-access capabilities. Configurable resources can include Amazon Bedrock, API Gateway, Lambda, DynamoDB, S3, and related security and observability services. ### Flow Backend Deploy APIs, workers, storage, and event integrations for durable form submissions, templates, validation, workflows, webhooks, and supported automation. Configurable resources can include API Gateway, Lambda, DynamoDB, S3, EventBridge, SES, and related security and observability services. ### Static Site Guardian Deploy protected static WordPress delivery using CloudFront, a private S3 origin, Cognito-compatible token validation, and optional signing-key and domain configuration. Static Site Guardian complements Static Publisher when selected pages or assets require access control. Only the components and optional features selected in the wizard create their runtime resources. Exact resource types, parameters, and permissions depend on the current version-controlled templates and the buyer's configuration. ## Quick Launch deployment process 1. Subscribe to WP Suite Deployment Access through AWS Marketplace. 2. Complete the WP Suite account, workspace, and Marketplace entitlement flow. 3. Open the WP Suite Deployment Wizard from the Quick Launch setup step. 4. Select supported components, the target AWS Region, and component settings. 5. Review the normalized configuration, estimated AWS costs, and IAM permissions, then save the configuration. 6. Return to AWS Marketplace Quick Launch and launch the root CloudFormation stack in the entitled AWS account. 7. Wait until the stack reaches CREATE_COMPLETE or UPDATE_COMPLETE. 8. Return to the WP Suite dashboard. Deployment outputs are captured for later configuration of supported WP Suite sites and components. AWS Marketplace Quick Launch starts one public root orchestration template. The root coordinates the selected nested component templates and entitlement-gated deployment packages. The public CloudFormation templates make created resources, IAM policies, parameters, outputs, and nested-stack boundaries reviewable before launch. ## Prerequisites and review checklist The launching AWS identity must be able to create CloudFormation stacks and the resources selected in the wizard. Exact requirements vary by configuration. They can include access to CloudFormation, IAM, Lambda, S3, CloudWatch Logs, API Gateway, Cognito, DynamoDB, EventBridge, SES, CloudFront, Route 53, AWS Certificate Manager, AWS WAF, and Amazon Bedrock. Before launch, review: - the entitled target AWS account and selected Region - component selections and dependencies - CloudFormation parameters and capabilities - IAM roles and policies in the public templates - encryption, network exposure, domains, logging, data retention, and backup settings - estimated AWS service costs and applicable account quotas CloudFormation validation cannot confirm every runtime permission, quota, domain, or regional service-availability condition. Monitor the stack events and resolve failed resources before connecting production sites. ## Product boundary Deployment Access is an infrastructure deployment entitlement, not a WP Suite plugin subscription. It does not include WordPress hosting, AWS infrastructure usage, managed production operations, custom theme or plugin development, third-party services, or unsupported AWS resources. WP Suite support covers Marketplace entitlement and onboarding questions, Deployment Wizard configuration, supported Quick Launch and CloudFormation deployment, connection of supported WP Suite components, and deployment-update guidance. The Marketplace listing provides a target response time of one to two business days and lists support@wpsuite.io as the contact address. ## Relationship to Agency Subscription - Use Agency Subscription for Pro-level access and central workspace management across multiple active WordPress sites. - Use Deployment Access for the account-scoped right and guided tooling to deploy supported backend infrastructure into one buyer-owned AWS account. - Use both when an agency needs multi-site Pro entitlements and customer-owned AWS backend infrastructure. If the 36-month Deployment Access contract is not renewed or replaced before it ends, access to its Marketplace entitlements and future deployment updates expires. Customer-owned AWS resources and their AWS service charges remain the buyer's responsibility.