# Migrate from AWS to Azion | Full Guide
import Tabs from '~/components/tabs/Tabs'
import Code from '~/components/Code/Code.astro'
A platform migration usually begins long before the first configuration file is changed. It starts when a team notices that its current environment no longer gives the same level of clarity, speed, or control it once did.
For teams using AWS, this moment often comes after years of accumulated complexity: CloudFront distributions with layered cache behaviors, Lambda functions with runtime dependencies, S3 buckets with evolving access policies, DynamoDB tables with provisioned capacity, Route 53 zones with health checks, WAF rules with managed rule groups, and CloudWatch alarms with custom metrics. Each service works, but together they create operational overhead that slows development.
For teams currently using Amazon CloudFront, AWS Lambda, Amazon S3, Amazon DynamoDB, Amazon Route 53, AWS WAF, AWS Shield, Amazon CloudWatch, or other AWS services, Azion provides equivalent capabilities through Applications, Functions, Object Storage, KV Store, Edge DNS, Web Application Firewall, DDoS Protection, Real-Time Metrics, and Real-Time Events.
The strongest reason to migrate is not simply to replace one vendor with another. It is to consolidate compute, storage, database, delivery, security, and observability into a unified platform designed for globally distributed applications.
## How AWS to Azion Migration Works
Traditional platform migrations often require rewriting application logic, reconfiguring infrastructure from scratch, and managing multiple disconnected services. This approach creates operational risk, extends timelines, and fragments team knowledge across different configuration patterns.
The Azion migration approach preserves your application logic while transitioning to a unified platform:
1. **Incremental migration path.** Start with a single project, validate each layer independently, and expand with confidence. No need to migrate everything at once.
2. **Preserved application logic.** Functions, cache policies, origin configurations, and data services map directly to Azion equivalents with minimal code changes—primarily syntax updates for environment access and service imports.
3. **Unified platform model.** Instead of managing compute, storage, databases, security, and observability as disconnected layers, Azion brings these capabilities together with consistent APIs and configuration patterns.
## Feature Mapping
The following tables provide a comprehensive mapping of AWS products to their Azion equivalents. A dash (`-`) indicates that Azion does not currently offer a direct equivalent.
| AWS Product | Description | Azion Equivalent |
| :---------- | :---------- | :--------------- |
| **Amazon CloudFront** | AWS CDN for delivering static content, dynamic content, APIs, applications, and video globally. | [Applications](https://www.azion.com/en/documentation/products/build/applications/) |
| **CloudFront Distributions** | Main CloudFront delivery resource for domains, origins, cache behavior, certificates, security, and edge delivery settings. | [Applications](https://www.azion.com/en/documentation/products/build/applications/) |
| **CloudFront Alternate Domain Names** | Configure custom domains for CloudFront distributions. | [Workloads](https://www.azion.com/en/documentation/products/secure/workloads/) |
| **CloudFront Cache Behaviors** | Path-based delivery behavior, cache policy, origin request policy, allowed methods, and edge function associations. | [Rules Engine for Applications](https://www.azion.com/en/documentation/products/build/applications/rules-engine/) |
| **CloudFront Cache Policies** | Control cache keys, TTLs, headers, cookies, query strings, and compression. | [Cache](https://www.azion.com/en/documentation/products/build/applications/cache/) |
| **CloudFront Origin Request Policies** | Control which request values CloudFront forwards to origin. | [Rules Engine](https://www.azion.com/en/documentation/products/build/applications/rules-engine/) |
| **CloudFront Response Headers Policies** | Add or modify response headers such as security headers and CORS headers. | [Rules Engine for Applications](https://www.azion.com/en/documentation/products/build/applications/rules-engine/) |
| **CloudFront Origin Shield** | Additional centralized caching layer to reduce origin load and improve cache hit ratio. | [Tiered Cache](https://www.azion.com/en/documentation/products/build/applications/cache/tiered-cache/) |
| **CloudFront Invalidation** | Remove content from CloudFront edge caches before expiration. | [Real-Time Purge](https://www.azion.com/en/documentation/products/build/applications/real-time-purge/) |
| **CloudFront Functions** | Lightweight JavaScript execution at the edge for redirects, rewrites, headers, and cache-key normalization. | [Functions for Applications](https://www.azion.com/en/documentation/products/build/applications/functions/) |
| **Lambda@Edge** | Node.js or Python functions triggered by CloudFront events to customize delivery. | [Functions for Applications](https://www.azion.com/en/documentation/products/build/applications/functions/) |
| **Lambda@Edge for security logic** | Use CloudFront-triggered functions for request validation, authentication, or blocking logic. | [Functions for Firewall](https://www.azion.com/en/documentation/products/secure/firewall/functions/) |
| **CloudFront Device Detection** | Detect device type and pass device metadata to the origin. | [Device Groups](https://www.azion.com/en/documentation/products/build/applications/device-groups/) |
| **AWS Elemental MediaLive** | Real-time live video encoding. | [Live Ingest](https://www.azion.com/en/documentation/guides/live-ingest-best-practices/) |
| **AWS Elemental MediaPackage** | Package and originate live video streams for HLS, DASH, and related formats. | [Live Ingest](https://www.azion.com/en/documentation/guides/live-ingest-best-practices/) + [Applications](https://www.azion.com/en/documentation/products/build/applications/) |
| **CloudFront for live streaming** | Deliver live video globally using CloudFront with AWS Media Services. | [Applications](https://www.azion.com/en/documentation/products/build/applications/) + [Live Ingest](https://www.azion.com/en/documentation/guides/live-ingest-best-practices/) |
| **AWS Lambda** | General-purpose serverless compute for event-driven code execution. | [Functions for Applications](https://www.azion.com/en/documentation/products/build/applications/functions/) |
| **Amazon API Gateway** | Create and manage REST, HTTP, and WebSocket APIs with backend integrations. | [Applications](https://www.azion.com/en/documentation/products/build/applications/) + [Functions](https://www.azion.com/en/documentation/products/build/applications/functions/) |
| **API Gateway request validation / throttling** | Apply API request controls, throttling, and validation rules. | [Rules Engine](https://www.azion.com/en/documentation/products/build/applications/rules-engine/) + [Firewall](https://www.azion.com/en/documentation/products/secure/firewall/) |
| **AWS Amplify Hosting** | Git-based CI/CD and hosting for static and server-side rendered web apps. | [Applications](https://www.azion.com/en/documentation/products/build/applications/) + [Azion CLI](https://www.azion.com/en/documentation/products/azion-cli/overview/) |
| **AWS App Runner** | Deploy source code or container images to managed web applications. | [Applications](https://www.azion.com/en/documentation/products/build/applications/) + [Orchestrator](https://www.azion.com/en/products/orchestrator/) |
| **Amazon Bedrock** | Foundation model access and generative AI application development. | [AI Inference](https://www.azion.com/en/documentation/products/ai/ai-inference/) |
| **Amazon Bedrock model inference** | Invoke foundation models for text, image, embedding, and generative AI use cases. | [AI Inference](https://www.azion.com/en/documentation/products/ai/ai-inference/) |
| **Amazon Bedrock Fine-Tuning** | Customize foundation models with fine-tuning for specific use cases. | [LoRA Fine-Tune](https://www.azion.com/en/learning/ai/what-is-lora-fine-tuning/) |
| **Amazon Bedrock Custom Model Import** | Import customized foundation models into Bedrock. | [AI Inference](https://www.azion.com/en/documentation/products/ai/ai-inference/) + [LoRA Fine-Tune](https://www.azion.com/en/learning/ai/what-is-lora-fine-tuning/) |
| **Amazon SageMaker AI Real-Time Inference** | Deploy ML models to managed real-time inference endpoints. | [AI Inference](https://www.azion.com/en/documentation/products/ai/ai-inference/) |
| **Amazon S3** | Object storage for unstructured data, static assets, backups, archives, and websites. | [Object Storage](https://www.azion.com/en/documentation/products/store/object-storage/) |
| **Amazon S3 Static Website Hosting** | Host static websites from S3 buckets. | [Object Storage](https://www.azion.com/en/documentation/products/store/object-storage/) + [Applications](https://www.azion.com/en/documentation/products/build/applications/) |
| **S3 Object Lambda** | Transform S3 objects with Lambda before returning them to the requester. | [Object Storage](https://www.azion.com/en/documentation/products/store/object-storage/) + [Functions](https://www.azion.com/en/documentation/products/build/applications/functions/) |
| **S3 Object Lambda for image transformation** | Resize, watermark, redact, or transform content retrieved from S3. | [Image Processor](https://www.azion.com/en/documentation/products/build/applications/image-processor/) + [Functions](https://www.azion.com/en/documentation/products/build/applications/functions/) |
| **Amazon Aurora DSQL** | Serverless distributed relational SQL database for transactional workloads. | [SQL Database](https://www.azion.com/en/documentation/products/store/sql-database/) |
| **Amazon DynamoDB** | Serverless key-value and document database. | [KV Store](https://www.azion.com/en/documentation/products/store/kv-store/) |
| **DynamoDB Global Tables** | Multi-Region replication for globally distributed NoSQL data. | [KV Store](https://www.azion.com/en/documentation/products/store/kv-store/) |
| **AWS WAF** | Web application firewall for protecting applications and APIs. | [WAF](https://www.azion.com/en/documentation/products/secure/firewall/web-application-firewall/) / [Firewall](https://www.azion.com/en/documentation/products/secure/firewall/) |
| **AWS Managed Rules for AWS WAF** | Managed rule groups for common vulnerabilities and unwanted traffic. | [WAF Rule Sets](https://www.azion.com/en/documentation/products/secure/firewall/web-application-firewall/rules-set/) |
| **AWS WAF custom rules** | Create custom match conditions and actions for web requests. | [Rules Engine for Firewall](https://www.azion.com/en/documentation/products/secure/firewall/rules-engine/) |
| **AWS WAF Bot Control** | Managed bot detection and mitigation. | [Bot Manager](https://www.azion.com/en/documentation/products/secure/firewall/bot-manager/) |
| **AWS WAF Rate-Based Rules** | Rate limit requests based on IP, headers, URI, method, or other keys. | [Rules Engine](https://www.azion.com/en/documentation/products/build/applications/rules-engine/) + [Network Shield](https://www.azion.com/en/documentation/products/secure/firewall/network-shield/) |
| **AWS WAF IP Sets** | Reusable IP/CIDR lists for allow or block rules. | [Network Lists](https://www.azion.com/en/documentation/products/secure/edge-firewall/network-layer-protection/network-lists/) |
| **AWS Shield Standard** | Standard DDoS protection for AWS resources. | [DDoS Protection](https://www.azion.com/en/documentation/products/secure/firewall/ddos-protection/) |
| **AWS Shield Advanced** | Advanced DDoS protection with additional visibility and mitigation options. | [DDoS Protection](https://www.azion.com/en/documentation/products/secure/firewall/ddos-protection/) |
| **Shield Advanced automatic DDoS mitigation** | Automatically creates or updates WAF protections during application-layer attacks. | [DDoS Protection](https://www.azion.com/en/documentation/products/secure/firewall/ddos-protection/) + [WAF](https://www.azion.com/en/documentation/products/secure/firewall/web-application-firewall/) |
| **AWS Network Firewall** | Managed VPC network firewall. | [Network Shield](https://www.azion.com/en/documentation/products/secure/firewall/network-shield/) |
| **Elastic Load Balancing** | Distributes traffic across multiple targets and availability zones. | [Load Balancer](https://www.azion.com/en/documentation/products/secure/connectors/load-balancer/) |
| **Application Load Balancer** | Layer 7 HTTP/HTTPS load balancing with application-level routing. | [Load Balancer](https://www.azion.com/en/documentation/products/secure/connectors/load-balancer/) |
| **Network Load Balancer** | Layer 4 TCP/UDP/TLS load balancing. | [Load Balancer](https://www.azion.com/en/documentation/products/secure/connectors/load-balancer/) |
| **AWS Global Accelerator** | Global Anycast IPs and optimized routing over the AWS global network. | [Applications](https://www.azion.com/en/documentation/products/build/applications/) + [Load Balancer](https://www.azion.com/en/documentation/products/secure/connectors/load-balancer/) |
| **CloudFront Origin Access Control** | Secure S3 origins so users access content through CloudFront instead of directly from S3. | [Connectors](https://www.azion.com/en/documentation/products/secure/connectors/) + [Origin Shield](https://www.azion.com/en/documentation/products/secure/connectors/origin-shield/) |
| **CloudFront Signed URLs / Signed Cookies** | Restrict access to private content using signed URLs or cookies. | [Rules Engine](https://www.azion.com/en/documentation/products/build/applications/rules-engine/) + [Functions](https://www.azion.com/en/documentation/products/build/applications/functions/) |
| **CloudFront Geographic Restrictions** | Allow or block content access by country. | [Rules Engine](https://www.azion.com/en/documentation/products/build/applications/rules-engine/) + [Network Shield](https://www.azion.com/en/documentation/products/secure/firewall/network-shield/) |
| **Amazon Route 53** | Authoritative DNS, domain registration, routing policies, and health checks. | [Edge DNS](https://www.azion.com/en/documentation/products/secure/edge-dns/) |
| **AWS Certificate Manager** | Provision, import, manage, deploy, and renew SSL/TLS certificates. | [Certificate Manager](https://www.azion.com/en/documentation/products/secure/firewall/certificate-manager/) |
| **AWS Private CA** | Create and operate private certificate authorities. | [Certificate Manager](https://www.azion.com/en/documentation/products/secure/firewall/certificate-manager/) |
| **AWS Private CA for client authentication** | Private PKI patterns for certificate-based client authentication. | [mTLS](https://www.azion.com/en/documentation/products/secure/firewall/mtls/) |
| **AWS IoT Greengrass** | Run AWS-managed edge components and local processing on edge devices. | [Orchestrator](https://www.azion.com/en/products/orchestrator/) |
| **AWS IoT Greengrass deployments** | Deploy components and configurations to edge devices. | [Orchestrator](https://www.azion.com/en/products/orchestrator/) |
| **Amazon ECS Anywhere** | Register and manage on-premises or external servers in ECS clusters. | [Orchestrator](https://www.azion.com/en/products/orchestrator/) |
| **AWS Outposts** | Run AWS infrastructure and services on customer premises. | [Orchestrator](https://www.azion.com/en/products/orchestrator/) |
| **AWS Systems Manager Hybrid Activations** | Manage non-EC2 machines in hybrid and multicloud environments. | [Orchestrator](https://www.azion.com/en/products/orchestrator/) |
| **Amazon CloudWatch Metrics** | Collect, query, visualize, and alarm on service and application metrics. | [Real-Time Metrics](https://www.azion.com/en/documentation/products/observe/real-time-metrics/) |
| **Amazon CloudWatch Logs** | Collect, monitor, query, and analyze logs. | [Real-Time Events](https://www.azion.com/en/documentation/products/observe/real-time-events/) |
| **CloudWatch Logs Insights** | Query and investigate logs interactively. | [Real-Time Events](https://www.azion.com/en/documentation/products/observe/real-time-events/) |
| **Amazon Data Firehose** | Deliver streaming data to destinations such as S3, Redshift, OpenSearch, and HTTP endpoints. | [Data Stream](https://www.azion.com/en/documentation/products/observe/data-stream/) |
| **CloudWatch RUM** | Real user monitoring for browser and mobile application performance. | [Edge Pulse](https://www.azion.com/en/documentation/products/observe/edge-pulse/) |
| **AWS Marketplace** | Discover, buy, deploy, and manage third-party software, data, and services. | [Marketplace](https://www.azion.com/en/documentation/products/marketplace/) |
| **AWS Management Console** | Web interface for accessing and managing AWS services. | [Azion Console](https://console.azion.com/) |
| **AWS APIs** | Programmatic interface for AWS service operations. | [Azion API](https://www.azion.com/en/documentation/products/overview-azion-api/) |
| **Amazon CloudWatch APIs / Metrics APIs** | Query metrics, logs, alarms, and observability data programmatically. | [GraphQL API](https://www.azion.com/en/documentation/devtools/graphql-api/) |
| **AWS CLI** | Command-line interface for managing AWS services. | [Azion CLI](https://www.azion.com/en/documentation/products/azion-cli/overview/) |
| **AWS SDKs** | Language-specific SDKs for building integrations with AWS services. | [SDK](https://www.azion.com/en/documentation/devtools/sdk/go/) |
| **AWS SDK for JavaScript** | JavaScript libraries for interacting with AWS services. | [Azion Lib](https://www.azion.com/en/documentation/products/azion-lib/overview/) |
| **AWS CloudFormation** | Infrastructure as Code service for modeling and provisioning AWS resources. | [Terraform Provider](https://www.azion.com/en/documentation/products/terraform-provider/) |
| **AWS Cloud Development Kit** | Define infrastructure using programming languages and synthesize to CloudFormation. | [Terraform Provider](https://www.azion.com/en/documentation/products/terraform-provider/) + [Azion API](https://www.azion.com/en/documentation/products/overview-azion-api/) |
| **Terraform AWS Provider** | Terraform provider for managing AWS resources. | [Terraform Provider](https://www.azion.com/en/documentation/products/terraform-provider/) |
| **Lambda runtime environment** | Runtime layer used by Lambda functions. | [Azion Runtime](https://www.azion.com/en/documentation/runtime/overview/) |
| **CloudFront edge runtime** | Runtime environment for CloudFront Functions and Lambda@Edge. | [Azion Runtime](https://www.azion.com/en/documentation/runtime/overview/) |
## Migration Strategy
The migration is organized around Azion's four product categories, allowing teams to plan and execute each layer independently:
- **Build**: deploy applications, configure builds and environment variables, migrate Lambda functions, CloudFront behaviors, routing, headers, load balancing, cache, image optimization, and AI workloads.
- **Secure**: migrate custom domains, Route 53 DNS, SSL/TLS certificates, WAF rules, DDoS protection, bot management, and rate limiting.
- **Store**: migrate S3 objects, DynamoDB tables, and Aurora databases to Object Storage, KV Store, and SQL Database.
- **Observe**: migrate CloudWatch metrics, logs, and alarms to Azion's real-time observability stack.
:::note
If you do not need near-zero downtime, you can migrate in phases with maintenance windows. This allows stopping writes during each migration step without requiring parallel data synchronization.
:::
## Build
The Build category covers application deployment, compute, routing, and configuration. Start here to bring your application onto Azion and establish the foundation for the rest of the migration.
### 1. Project Setup on Azion
The first step brings your application into Azion in a way that feels familiar to teams that deploy modern web projects on AWS. If you have used AWS CloudFormation, SAM, or CDK, you already understand the pattern: define infrastructure as code, configure build settings, deploy the output, and validate the generated URL.
Azion follows a similar workflow but with a broader platform context. Your project becomes part of an environment where application delivery, Functions, rules, security, and observability can be managed together.
#### Key Differences
| Aspect | AWS | Azion |
| :----- | :--- | :---- |
| **Config file** | `template.yaml` (SAM) / `cdk.json` (CDK) | `azion.config.js` (JavaScript) |
| **Framework detection** | Manual configuration | 20+ frameworks with auto-detection |
| **Cold starts** | Common (regional Lambda) | Minimized (distributed nodes) |
| **Compliance** | SOC 2, ISO 27001, HIPAA | PCI DSS 4.0.1 Level 1, SOC 2 Type II |
#### Connect Your Repository
1. Open [Azion Console](https://console.azion.com/).
2. Click **+ Create** > **Import from GitHub**.
3. Authorize the Azion GitHub App.
4. Select the repository you want to migrate.
:::note
Keep the first deployment intentionally small. Do not try to migrate every distribution, function, API gateway, storage dependency, and database at once. Start by proving the application can build and run on Azion.
:::
#### Configure Your Build
Azion auto-detects your framework and configures build settings. Override the detected preset in `azion.config.js`:
{
const token = event.authorizationToken;
try {
const decoded = jwt.verify(token, process.env.JWT_SECRET);
return {
principalId: decoded.sub,
policyDocument: {
Version: '2012-10-17',
Statement: [{
Action: 'execute-api:Invoke',
Effect: 'Allow',
Resource: event.methodArn
}]
}
};
} catch (err) {
throw new Error('Unauthorized');
}
};
// After: Azion Function for Authorization
export default {
async fetch(request) {
const authHeader = request.headers.get('Authorization');
if (!authHeader) {
return new Response('Unauthorized', { status: 401 });
}
const token = authHeader.replace('Bearer ', '');
try {
const secret = Azion.env.get('JWT_SECRET');
const decoded = await verifyJWT(token, secret);
// Store user info in request metadata for downstream functions
request.metadata['user_id'] = decoded.sub;
return request; // Continue to next handler
} catch (err) {
return new Response('Unauthorized', { status: 401 });
}
}
};
`} />
#### Route Migration Example
{
const body = JSON.parse(event.body);
const pathParams = event.pathParameters;
const queryParams = event.queryStringParameters;
// Process request
return {
statusCode: 200,
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ message: 'Hello', data: body })
};
};
// After: Azion Functions
export default {
async fetch(request) {
const body = await request.json();
const url = new URL(request.url);
const queryParams = Object.fromEntries(url.searchParams);
// Process request
return new Response(JSON.stringify({ message: 'Hello', data: body }), {
status: 200,
headers: { 'Content-Type': 'application/json' }
});
}
};
`} />
#### Event Context Migration
{
const requestId = context.awsRequestId;
const functionName = context.functionName;
const remainingTime = context.getRemainingTimeInMillis();
// Request metadata from API Gateway
const sourceIp = event.requestContext.identity.sourceIp;
const userAgent = event.requestContext.identity.userAgent;
const country = event.headers['CloudFront-Viewer-Country'];
return { statusCode: 200, body: 'OK' };
};
// After: Azion Functions
export default {
async fetch(request, env, ctx) {
// Request metadata
const requestId = request.headers.get('x-request-id');
const userAgent = request.headers.get('user-agent');
const country = request.metadata['geoip_country_code'];
const city = request.metadata['geoip_city'];
// Geo metadata available directly
const region = request.metadata['geoip_region'];
return new Response('OK', { status: 200 });
}
};
`} />
#### Environment Variables Migration
", 100] }]
}
}
// Target: Lambda function for processing
// After: Azion Data Streaming + Functions
// Configure Data Streaming to send events to your Function endpoint
// Then process in Function:
export default {
async fetch(request) {
const events = await request.json();
for (const event of events) {
if (event.source === 'com.mycompany.orders' &&
event.type === 'OrderCreated' &&
event.data.amount > 100) {
// Process high-value order
await processHighValueOrder(event.data);
}
}
return new Response('OK');
}
};
`} />
#### Reference documentation
* [Functions](https://www.azion.com/en/documentation/products/build/applications/functions/)
* [Data Streaming](https://www.azion.com/en/documentation/products/observe/data-streaming/)
## Secure
The Secure category covers domains, DNS, certificates, firewall rules, and protection against malicious traffic. Plan these migrations as controlled cutovers, since they affect how users reach your application and how it is protected in production.
### 1. Migrating Custom Domains
Custom domain migration is one of the most sensitive parts of any platform transition. It affects users, SEO, brand trust, and production availability. Plan domain migration as a controlled cutover, not a last-minute DNS change.
#### Migration Strategies
| Strategy | Best For | DNS Control |
| :------- | :------- | :---------- |
| **CNAME** | Quick subdomain migration | Keep Route 53 as DNS provider |
| **Nameserver** | Full DNS control and apex domains | Transfer DNS to Azion |
#### Create the Certificate
Create your SSL/TLS certificate **before** pointing your domain to Azion. This ensures users can access the application securely over HTTPS when the domain starts resolving to the new infrastructure.
Azion provides free Let's Encrypt certificates with automatic renewal.
#### Configure the Domain
Create a workload in Azion Console and associate your custom domain. See [Workloads Documentation](https://www.azion.com/en/documentation/products/secure/workloads/).
#### Point the Domain to Azion
CNAME Migration
Nameserver Migration
Update your Route 53 hosted zone to point the subdomain to Azion:
console.error('KV Error:', err))
.connect();
// Before: DynamoDB GetItem
// const result = await dynamodb.getItem({
// TableName: 'Users',
// Key: { userId: { S: '123' } }
// }).promise();
// After: KV Store get
const userData = await client.get('user:123');
// Before: DynamoDB PutItem
// await dynamodb.putItem({
// TableName: 'Users',
// Item: { userId: { S: '123' }, name: { S: 'John' } }
// }).promise();
// After: KV Store set
await client.set('user:123', JSON.stringify({ name: 'John' }), {
expiration: { type: 'EX', value: 3600 } // 1 hour TTL
});
`} />
#### Create a KV Store
Console
API
1. Access [Azion Console](https://console.azion.com/).
2. Go to **KV Store**.
3. Click **+ Store**.
4. Enter a name for your store.
5. Configure settings.
6. Click **Save**.
:date'
// }).promise();
// After: SQL Database query
const orders = await db.query(
'SELECT * FROM orders WHERE customer_id = ? AND order_date > ?',
['customer-123', '2024-01-01']
);
// Iterate results
let row = await orders.next();
while (row) {
console.log(row.getString(0)); // access column by index
row = await orders.next();
}
`} />
#### Create a SQL Database
Console
API
1. Access [Azion Console](https://console.azion.com/).
2. Go to **SQL Database**.
3. Click **+ Database**.
4. Enter a name for your database.
5. Create tables using SQL Shell or API.
6. Import your data.
\`);
row = await result.next();
}
`} />
#### Create a SQL Database
Console
API
1. Access [Azion Console](https://console.azion.com/).
2. Go to **SQL Database**.
3. Click **+ Database**.
4. Enter a name for your database.
5. Click **Save**.
6. Use **SQL Shell** to create tables and import data.
export.sql
# For Aurora, you can also use Snapshot Export to S3
aws rds start-export-task \\
--export-task-identifier my-export \\
--source-arn arn:aws:rds:region:account:cluster:my-aurora-cluster \\
--s3-bucket-name my-export-bucket \\
--export-only data
# Import to Azion SQL Database via SQL Shell
# Connect to SQL Shell and run the export.sql file
# Or use the import API
`} />
#### Data Type Mapping
| PostgreSQL Type | SQLite Equivalent |
| :-------------- | :---------------- |
| INTEGER, BIGINT, SMALLINT | INTEGER |
| SERIAL, BIGSERIAL | INTEGER (auto-increment) |
| VARCHAR(n), CHAR(n), TEXT | TEXT |
| BOOLEAN | INTEGER (0 or 1) |
| REAL, DOUBLE PRECISION | REAL |
| DECIMAL, NUMERIC | REAL |
| DATE, TIME, TIMESTAMP | TEXT (ISO 8601 format) |
| JSON, JSONB | TEXT (use JSON functions) |
| UUID | TEXT |
| BYTEA | BLOB |
#### Reference documentation
* [SQL Database](https://www.azion.com/en/documentation/products/store/sql-database/)
* [Vector Search](https://www.azion.com/en/documentation/products/store/sql-database/vector-search/)
* [Create a database](https://www.azion.com/en/documentation/products/store/sql/create-database/)
* [Install SQL Shell](https://www.azion.com/en/documentation/products/store/sql/install-edge-sql-shell/)
* [SQL Database Shell commands](https://www.azion.com/en/documentation/products/store/sql/sql-database-shell-commands/)
* [Import data into SQL Database](https://www.azion.com/en/documentation/products/guides/import-data-sql-database/)
* [SQL Database API reference](https://www.azion.com/en/documentation/runtime/api-reference/sql-database/)
### 4. Migrating ElastiCache to Cache / KV Store
ElastiCache provides in-memory caching with Redis or Memcached. Azion provides caching through Cache and key-value storage through KV Store.
#### Key Differences
| Aspect | Amazon ElastiCache | Azion Cache | Azion KV Store |
| :----- | :---------------- | :---------- | :------------- |
| **Type** | In-memory cache | Cache | Distributed key-value |
| **Engines** | Redis, Memcached | HTTP cache | Redis-like API |
| **Persistence** | Optional (Redis AOF/RDB) | Time-based TTL | Persistent |
| **Data structures** | Strings, hashes, lists, sets, sorted sets | HTTP responses | Strings, hashes |
| **Replication** | Cluster mode, replication groups | Global Network | Global by default |
| **Access** | TCP connection | HTTP request/response | Runtime API |
#### Migration Decision Guide
| ElastiCache Use Case | Recommended Azion Service |
| :------------------- | :------------------------ |
| HTTP response caching | Cache |
| Session storage | KV Store |
| Rate limiting counters | KV Store |
| Feature flags | KV Store |
| Database query caching | Cache + Functions |
| Pub/Sub messaging | Functions + KV Store |
| Leaderboards, sorted sets | SQL Database |
| Complex data structures | SQL Database |
#### Migrate Redis Caching to KV Store
For Redis-like key-value operations, use KV Store:
console.error('KV Error:', err))
.connect();
// Before: Redis SET with expiration
// await redis.set('session:abc123', JSON.stringify(sessionData), 'EX', 3600);
// After: KV Store set with expiration
await client.set('session:abc123', JSON.stringify(sessionData), {
expiration: { type: 'EX', value: 3600 }
});
// Before: Redis GET
// const data = await redis.get('session:abc123');
// After: KV Store get
const data = await client.get('session:abc123');
// Before: Redis DEL
// await redis.del('session:abc123');
// After: KV Store delete
await client.delete('session:abc123');
`} />
#### Reference documentation
* [KV Store](https://www.azion.com/en/documentation/products/store/kv-store/)
* [KV library (azion/kv)](https://www.azion.com/en/documentation/products/azion-lib/kv/)
* [Cache](https://www.azion.com/en/documentation/products/build/applications/cache/)
* [Cache Settings](https://www.azion.com/en/documentation/products/build/applications/cache-settings/)
* [Tiered Cache](https://www.azion.com/en/documentation/products/build/applications/cache/tiered-cache/)
* [Rules Engine for Applications](https://www.azion.com/en/documentation/products/build/applications/rules-engine/)
## Observe
The Observe category covers analytics, metrics, logs, and distributed tracing. Migrating observability ensures you keep production visibility, troubleshooting capabilities, and compliance reporting after the cutover.
### 1. Migrating CloudWatch Metrics to Real-Time Metrics
CloudWatch Metrics provides monitoring for AWS resources and applications. Azion Real-Time Metrics delivers comparable capabilities through a GraphQL API and integrated dashboards with near real-time data aggregation.
#### Key Differences
| Aspect | Amazon CloudWatch Metrics | Azion Real-Time Metrics |
| :----- | :------------------------ | :---------------------- |
| **Data freshness** | Near real-time (1-5 minutes) | Near real-time (up to 10 minutes) |
| **Retention** | 15 months (standard) | 2 years |
| **Query method** | GetMetricStatistics API, CloudWatch Insights | GraphQL API, Console dashboards |
| **Metrics** | Custom metrics, namespace-based | Request, bandwidth, latency, cache, WAF, DNS |
| **Granularity** | 1 second to 1 day | Adaptive intervals (minute/hour/day) |
| **Dashboards** | CloudWatch Dashboards | Real-Time Metrics + Grafana plugin |
| **Alarms** | CloudWatch Alarms | External monitoring via Data Stream |
#### Available Metrics
Azion Real-Time Metrics provides comprehensive monitoring across product categories:
**Build metrics:**
- **Applications**: Total requests, data transferred, status codes, bandwidth saving, average request time
- **Functions**: Total invocations, execution time
- **Image Processor**: Total requests, requests per second
- **Tiered Cache**: Caching offload, L2 offload
**Secure metrics:**
- **WAF**: Threats vs requests, SQL injection, XSS, RFI, threats by country
- **Edge DNS**: Total queries
- **Bot Manager**: Bot hits, bad bot hits, good bot hits, traffic classification
**Observe metrics:**
- **Data Stream**: Total data streamed, total requests
#### Configuration Steps
Console
API (GraphQL)
1. Access [Azion Console](https://console.azion.com/).
2. Go to **Products menu** > **Real-Time Metrics**.
3. Select a category tab (Build, Secure, Observe).
4. Select a product tab to view specific metrics.
5. Configure **Time range** (Last Hour, 24 Hours, 7 Days, 30 Days, 6 Months).
6. Use **Filters** to refine analysis by host, status code, or other dimensions.
7. Click the context menu on any chart to export CSV or copy the GraphQL query.
= 500
| sort @timestamp desc
| limit 100
`} />
**Azion GraphQL equivalent:**