Read our blog for the latest insights on sales and marketing Take Me There
Webinar: Document Merge in wMobile Desktop for GoldMine Register
Publishing these logs to CloudWatch Logs allows you to maintain continuous visibility into Aurora PostgreSQL system logs for your Aurora PostgreSQL databases. For example, you can set up Amazon CloudWatch Alarms to notify you on frequent restarts which are recorded in the Aurora PostgreSQL system log. Similarly, alarms for events recorded in Aurora PostgreSQL logs can be created to alert on unwanted changes made to your databases. You may also enable logging of slow queries and create alarms to monitor them in the Aurora PostgreSQL logs and enable timely detection of long-running queries.
CloudWatch Logs provide a durable archive destination for your database logs. You can specify a retention period to indicate how long you want CloudWatch to retain your logs. Additionally, with CloudWatch Logs, you can perform ad hoc searches across multiple logs. This capability is particularly useful for troubleshooting, audits, and log analysis. You can also export logs from CloudWatch to Amazon S3.
Refer to the Aurora PostgreSQL documentation for more information. To start publishing logs from Aurora PostgresQL databases to CloudWatch Logs, visit the AWS RDS Management Console or download the latest AWS SDK or CLI.
Amazon Aurora combines the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. It provides up to three times better throughput than the typical PostgreSQL database, together with increased scalability, durability, and security. To learn more about Amazon Aurora with PostgreSQL compatibility, please visit our product page.
Amazon Aurora Multi-Master is now generally available, allowing you to create multiple read-write instances of your Aurora database across multiple Availability Zones, which enables uptime-sensitive applications to achieve continuous write availability through instance failure. In the event of instance or Availability Zone failures, Aurora Multi-Master enables the Aurora database to maintain read and write availability with zero application downtime. With Aurora Multi-Master, there is no need for database failovers to resume write operations. Check out this blog to find out how to build highly available MySQL applications using Aurora Multi-Master.
The feature is now available on Aurora MySQL 5.6 in US East (N. Virginia), US East (Ohio), US West (Oregon), and EU (Ireland). You can read the Amazon Aurora documentation to learn more. You can create an Aurora Multi-Master cluster with just a few clicks in the Amazon RDS Management Console or download the latest AWS SDK or CLI.
Amazon Aurora combines the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. It provides up to five times better throughput than standard MySQL and up to three times better throughput than standard PostgreSQL, together with increased scalability, durability, and security.
With Amazon Virtual Private Cloud (Amazon VPC) sharing, you can now use AWS Glue, create Amazon EMR clusters and Amazon Aurora Serverless DB clusters in shared and centrally-managed VPCs. Amazon VPC sharing allows other AWS accounts to create their application resources, such as EC2 instances, Amazon Relational Database Service (Amazon RDS) databases, Amazon Redshift clusters, Amazon EMR clusters, and Lambda functions in shared Amazon VPCs.
Customers create multiple AWS accounts to streamline billing and restrict access to various environments, such as development, staging, and production, across different business and application teams. By enabling customers to launch AWS Glue, Amazon EMR, and AWS Aurora Serverless in shared VPCs, your IT teams can own and manage the Amazon VPCs. Other users, such as data architects, analysts, data engineers, and application developers, can just focus on preparing, loading, analyzing, and using data without worrying about the connectivity and the security of Amazon VPCs.
You can also share Amazon VPCs to leverage the implicit routing within a VPC for applications that require a high degree of inter-connectivity and are within the same trust boundaries. This reduces the number of VPCs that need to be created and managed, while you still benefit from using separate accounts for billing and access control. Customers can further simplify network topologies by interconnecting shared Amazon VPCs using connectivity features, such as AWS PrivateLink, AWS Transit Gateway, and Amazon VPC peering.
Support for Glue, EMR, and Aurora Serverless with VPC sharing is available in all commercial AWS Regions except in South America (São Paulo), Asia Pacific (Osaka-Local), and China regions. There are no additional charges for using this feature. For more information about VPC sharing, please visit our documentation or read the blog post.