NewApp Digest
search bot

network connectivity

Query billion-scale vectors with SQL: Integrating Amazon S3 Vectors and Aurora PostgreSQL
Tech Optimizer
May 10, 2026

Query billion-scale vectors with SQL: Integrating Amazon S3 Vectors and Aurora PostgreSQL

For managing relational data within Amazon Aurora PostgreSQL and enhancing capabilities with similarity search over large embedding collections, an integration with Amazon S3 Vectors is available. This integration utilizes the pgvector extension for low-latency similarity searches on vectors stored in the database. Amazon S3 Vectors provides cost-effective storage for extensive datasets, scaling to hundreds of millions or billions of embeddings. The integration, facilitated through AWS Lambda, allows users to query S3 Vectors directly from Aurora PostgreSQL using standard SQL, enabling the combination of vector similarity results with relational filters in a single query. The integration offers benefits such as basic key-value metadata support in S3 Vectors for simple filtering, while Aurora PostgreSQL is optimal for complex SQL filters, multi-table joins, and access-control policies. The architecture separates concerns, with Lambda handling API integration and Aurora managing relational data. Security is maintained through IAM role separation and network security measures. Data consistency considerations arise due to the distribution of data across Aurora PostgreSQL and S3 Vectors, necessitating explicit synchronization processes to manage potential stale results. The integration is suitable for use cases that can tolerate eventual consistency, such as recommendations and content discovery. Performance expectations include Lambda invocation latencies of 100-500 milliseconds, while Aurora pgvector typically provides single-digit millisecond response times. S3 Vectors achieves sub-second performance for cold queries and less than 100 milliseconds for warm queries. From a cost perspective, S3 Vectors is more economical than Aurora, making it suitable for high-volume vector data that requires archiving and queryability. The integration architecture consists of three components: Aurora PostgreSQL, AWS Lambda for API translation, and S3 Vectors for executing similarity searches. A typical query involves several stages, including SQL query invocation, function processing, API translation, similarity search, and result processing. Prerequisites for this integration include familiarity with Aurora PostgreSQL, AWS Lambda, vector databases, and SQL. Required AWS resources include an Aurora PostgreSQL cluster, a VPC with internet access, and appropriate permissions for IAM roles and Lambda functions. To deploy the integration, users must gather configuration values from their Aurora cluster, deploy a CloudFormation stack, associate the IAM role, update the Lambda function code, and install the necessary PostgreSQL schema. Sample data can be uploaded to the S3 Vectors index, allowing for testing of vector operations and combined queries. When combining relational and vector queries, developers should be aware of the trade-offs involved in pre-filtering data by metadata, which can improve performance but may reduce recall. Troubleshooting may involve addressing connectivity issues, IAM role misconfigurations, and performance optimizations. To clean up resources after testing, users should remove the PostgreSQL schema, disassociate the Lambda role from the Aurora cluster, and delete the CloudFormation stack to ensure all resources are removed.
What Is Endpoint Detection and Response?
Tech Optimizer
May 7, 2026

What Is Endpoint Detection and Response?

Traditional endpoint security measures, such as antivirus software and firewalls, are increasingly ineffective against sophisticated cyberattacks, which can bypass these defenses. Endpoint Detection and Response (EDR) is a solution that emphasizes rapid detection and containment of threats, continuously monitoring endpoint activity and identifying suspicious behavior in real time. EDR platforms gather data from all connected endpoints and utilize AI-driven analytics to detect both known and unknown threats. In 2024, over 97 billion exploitation attempts were recorded, underscoring the need for robust endpoint protection. EDR tools operate in four stages: detection, containment, investigation, and elimination of threats. They collect telemetry data from endpoints to establish a baseline of normal activity, enabling the identification of anomalies that may indicate a threat. EDR can automatically isolate affected endpoints, terminate malicious processes, and execute remediation actions. EDR employs two methods for threat detection: comparing endpoint activity against indicators of compromise for known threats and using behavioral detection models for unknown threats. The system can generate reports on threat activity and response effectiveness, aiding compliance and operational decision-making. The telemetry data collected is stored in a centralized repository, supporting threat-hunting initiatives. Organizations that deployed EDR in 2024 experienced an average breach cost that was significantly lower than those that did not. EDR minimizes security blind spots, reduces the attack surface by identifying vulnerabilities, speeds up investigations and responses, blocks new threats through behavioral analysis, and strengthens other security measures when integrated with existing tools. Challenges in EDR implementation include alert fatigue, integration complexity, resource constraints, and limited scope. When choosing an EDR solution, organizations should prioritize features such as real-time threat detection, automated response capabilities, behavioral analysis, offline protection, low performance impact, and integration with existing tools. EDR functions effectively as part of a layered security strategy, complementing other tools like Endpoint Protection Platforms (EPP) and Extended Detection and Response (XDR). EDR focuses on endpoint activity, while EPP serves as a first line of defense against common threats, and XDR broadens the scope to include network traffic and cloud workloads. VPNs encrypt network traffic, providing an additional layer of protection for data in transit.
Microsoft will shut down its Outlook Lite Android app on May 25
AppWizard
April 13, 2026

Microsoft will shut down its Outlook Lite Android app on May 25

Outlook Lite will cease operations on May 25, following its phased retirement that began last October when it was removed from the Google Play Store. Launched in 2022, Outlook Lite was aimed at users in emerging markets with entry-level smartphones and limited network connectivity, achieving over 10 million downloads by 2024. After May 25, the app may still launch but will not display emails or calendar items. Users are encouraged to transition to alternative email clients, with Microsoft recommending the Outlook Mobile app as the primary replacement, which syncs existing emails and calendar entries. Organizations using Outlook Lite should update their internal documentation and guide employees toward alternative applications before the deadline. Other Android alternatives include Proton Mail, Spark Mail, and Gmail, although none match Outlook Lite's compact 5MB size.
Search