A managed service for storing and managing application settings, feature flags, and configuration values separately from your code. Like a central control panel for all your app's settings — you can change behaviors without redeploying your application.
An e-commerce team uses AWS AppConfig to gradually roll out a new checkout flow to 10% of users, then 50%, then 100% — all without deploying new code. If conversion rates drop, they instantly toggle back to the old flow from the configuration dashboard.
All provide a way to externalize app settings and change behavior without redeploying. AWS AppConfig focuses on safe configuration deployments (validators, monitors, rollbacks) and integrates with Systems Manager. Azure App Configuration is a dedicated config store with feature flags and tight Azure SDK integration. GCP’s closest managed equivalent for feature flags and runtime parameters is Firebase Remote Config (commonly used for mobile/web); for server-side config teams often use Secret Manager/Cloud Storage/Firestore patterns. OCI doesn’t have a direct “app config” service; OCI Vault is commonly used for configuration values that are sensitive (secrets/keys), while non-secret configuration is typically stored in Object Storage, databases, or delivered via CI/CD.