skills.rest
Boise-State-Development
Boise-State-DevelopmentOFFICIAL
Explore all skills by this author →
GitHub

cors-deployment

Manage cross-origin CORS settings across CDK stacks and workflows.

16|27|Updated Nov 29, 2025
Search Tags:#automation#deployment#aws#workflows#cors#cdk#cross-origin
One-click install
npx skills add https://github.com/Boise-State-Development/agentcore-public-stack --skill cors-deployment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cors-deployment
Source: https://github.com/Boise-State-Development/agentcore-public-stack/tree/main/.claude/skills/cors-deployment
Command: npx skills add https://github.com/Boise-State-Development/agentcore-public-stack --skill cors-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-origin configuration is scattered across multiple CDK stacks, GitHub Actions workflows, and Python backends, causing drift and errors when origins change.

Core Features & Use Cases

  • Global domain-based CORS origins are auto-applied via CDK_DOMAIN_NAME (https://{domain}).
  • Global origins can be extended with CDK_CORS_ORIGINS for cross-environment needs.
  • Per-stack overrides support CDK_*_CORS_ORIGINS to tailor origins per deployment.

Quick Start

Configure CDK_DOMAIN_NAME and CDK_CORS_ORIGINS in the environment and run your deployment to apply consistent CORS settings across all stacks.

Frequently Asked Questions about cors-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize CORS configuration across multiple CDK stacks?▼

You standardize CORS across CDK stacks by deriving settings from CDK_DOMAIN_NAME and CDK_CORS_ORIGINS environment variables, applying a two-layer model with per-section overrides to manage domain-based origins and prevent configuration drift.

What is the best way to automate cross-origin resource sharing settings for AWS deployments?▼

Automating cross-origin resource sharing for AWS deployments involves using environment-driven workflow requirements to globally apply domain-based origins, extending them with CDK_CORS_ORIGINS for cross-environment needs across all backends.

Why does my CORS configuration drift when updating origins in different environments?▼

CORS configuration drifts when origins are manually updated across scattered CDK stacks and workflows, but you can resolve this by enforcing environment-driven workflow requirements and auto-applying global settings via CDK_DOMAIN_NAME.

Can I override global CORS origins for a specific CDK stack?▼

Yes, you can override global CORS origins for a specific CDK stack using per-stack overrides, configuring CDK_*_CORS_ORIGINS environment variables to tailor origins per deployment while maintaining the baseline two-layer model.

Do I need to manually configure CORS headers in my Python backend if I use environment variables?▼

No, you do not need to manually configure CORS headers in your Python backend if you use environment variables, because the deployment automatically derives and applies consistent cross-origin settings across all stacks and backends.

Related Skills

Explore More Software Engineering Skills→
ehtbantonehtbanton

cors-config-generator

Generate CORS configuration middleware for Node.js applications.

Community
Basic
Prohao42Prohao42
120

cors-cross-origin-misconfiguration

Detect CORS misconfigurations by analyzing Access-Control-Allow-Origin response headers.

Community
Advanced
FAIQahmFAIQahm

vercel-fastapi-link

Automate FastAPI deployment preparation to Vercel with CORS and routing configuration.

Community
Advanced
salvo-rssalvo-rs
20

salvo-cors

Configure CORS rules and security headers for Salvo applications.

Official
Advanced