Amazon Route 53

2 posts

aws3 min readCurated summary

Improve your application resilience with Amazon Cognito multi-Region replication | Amazon Web Services

Amazon Cognito multi-Region replication improves authentication resilience by maintaining synchronized user data, credentials, configurations, and machine secrets in a secondary AWS Region. During a regional outage, applications can redirect traffic while users continue using existing credentials and sessions, though registration and profile updates are unavailable during failover. The feature also adds customer managed AWS KMS keys for consistent, customer-controlled encryption across Regions. ## Challenges with Regional Failover - Custom replication solutions previously required significant engineering effort. - Manual user-data transfers introduced security and consistency risks. - Users could be forced to reset passwords or authenticate again after a regional switch. - Machine-to-machine systems required new app clients, application reconfiguration, and updated OAuth resource trust settings. ## How Multi-Region Replication Works - Replication is one-way, from a primary Region to a secondary Region. - The replica includes: - User profiles and credentials - User pool configuration - Machine-to-machine secrets - The secondary pool is read-only and remains available for authentication. - Existing sessions continue uninterrupted. - Users can authenticate with existing credentials, and either Region recognizes access tokens issued by the other. - Supported authentication methods include: - Social identity providers - SAML and OIDC federation - API authorization flows - Machine-to-machine authentication - New registrations and profile changes are unavailable while operating from the replica. ## Customer Managed KMS Keys - A multi-Region customer managed key is required before replication can be configured. - The key must be replicated into both the primary and secondary Regions. - Its policy must grant Amazon Cognito permission to use the key. - Customer managed keys provide consistent encryption across Regions and greater control over encryption policies. ## Configuration Process - The console guides administrators through three main steps: - Select and configure the customer managed KMS key. - Configure multi-Region OIDC issuer endpoints. - Select and create the replica Region. - Client applications must be updated with the new OIDC endpoints. - Server-side applications require redeployment, while mobile applications require updated store submissions. - After the replica is prepared, an administrator must manually activate it. ## Additional Regional Resources - Lambda functions used for custom authentication, SMS, or email must be deployed and configured in the secondary Region. - Logging and AWS WAF settings must also be recreated there. - Teams should verify that all supporting authentication infrastructure is available before failover. ## Health Checks and Failover - Both regional endpoints remain active and ready to serve traffic. - Applications should define health checks based on error rates, latency, or service alerts. - DNS can redirect traffic to the secondary Region when failover criteria are met. - Teams should test failover during low-traffic periods, potentially routing only a small percentage of traffic initially. - Managed login and federation with custom domains can use Amazon Route 53 health checks for built-in traffic routing. ## Pricing and Availability - Replication is available as an add-on for Cognito Essentials and Plus tiers. - User authentication costs: - $0.0045 per monthly active user per replica Region for Essentials - $0.006 per monthly active user per replica Region for Plus - M2M replication adds 30% to standard successful-token pricing. - The feature is available across selected Regions in North America, Europe, Asia Pacific, Canada, Africa, and South America. Organizations needing resilient authentication should pair Cognito replication with multi-Region KMS keys, replicated supporting services, tested health checks, and an automated or well-practiced DNS failover process.

Read original(opens in new tab)
aws3 min readCurated summary

AWS Weekly Roundup: Amazon S3 turns 20, Amazon Route 53 Global Resolver general availability, and more (March 16, 2026) | Amazon Web Services

Amazon S3 marked its 20th anniversary with major milestones in scale, performance, and cost reduction, while AWS introduced account regional namespaces for improved bucket-name control. The week’s featured launch was the general availability of Amazon Route 53 Global Resolver, providing secure, globally accessible DNS resolution across 30 AWS Regions. Other updates covered stateful AI agent infrastructure, Windows Server 2025, simplified AWS identity access, and reusable Redshift ingestion templates. ## Amazon S3 Reaches 20 Years - Launched publicly on March 14, 2006, S3 has grown from object storage into a foundational cloud service. - As of March 2026, it stores: - More than 500 trillion objects - Hundreds of exabytes of data - Over 200 million requests per second globally - Storage prices have fallen by approximately 85% since launch, to just over $0.02 per gigabyte. - New account regional namespaces let organizations reserve bucket names within their own account namespace by adding an account-specific suffix. - Adoption can be enforced with IAM and AWS Organizations service control policies using the `s3:x-amz-bucket-namespace` condition key. ## Route 53 Global Resolver Becomes Generally Available - Amazon Route 53 Global Resolver is an internet-reachable, anycast DNS resolver for authorized clients anywhere. - It is available across 30 AWS Regions and supports IPv4 and IPv6 DNS queries. - It resolves: - Public internet domains - Private domains associated with Route 53 private hosted zones - Security features include filtering for malicious, unsafe, DNS tunneling, and Domain Generation Algorithm (DGA) domains. - General availability adds protection against Dictionary DGA threats. - Centralized DNS query logging is also included. ## Additional AWS Service Updates - **Bedrock AgentCore Runtime** - Adds stateful MCP server support through the `Mcp-Session-Id` header. - Dedicated microVMs isolate each user session and preserve context across interactions. - MCP servers can use elicitation, sampling, and progress notifications in addition to resources, prompts, and tools. - **Amazon WorkSpaces** - Adds Windows Server 2025 bundles for WorkSpaces Personal and WorkSpaces Core. - Security features include TPM 2.0, UEFI Secure Boot, Credential Guard, HVCI, Secured-core server, and DNS-over-HTTPS. - Existing Windows Server 2016, 2019, and 2022 bundles remain supported. - **AWS Builder ID** - Adds GitHub and Amazon as sign-in options alongside Google and Apple. - Users can access AWS Builder Center, Training and Certification, and Kiro without maintaining separate credentials. - **Amazon Redshift** - Introduces reusable templates for `COPY` operations. - Templates centralize frequently used parameters, improve consistency, and automatically apply future updates to subsequent loads. - The feature is available in commercial and AWS GovCloud Regions. ## Upcoming AWS Events - AWS Summits are scheduled for Paris, London, and Bengaluru. - AWS Community Days are planned in Pune, San Francisco, and Romania. - AWS will participate in NVIDIA GTC 2026 in San Jose. - AWS Community GameDay Europe will offer hands-on troubleshooting challenges across more than 50 cities. For practitioners, the most significant developments are Route 53 Global Resolver for centralized global DNS security, S3 namespaces for organizational naming governance, and AgentCore’s stateful MCP support for more capable AI applications.

Read original(opens in new tab)