RDS PostgreSQL CloudWatch Logs export enabled, but log group is not created

This situation is not a known issue where the log group fails to be created. The problem you're experiencing suggests there might be a configuration mismatch or a permissions issue preventing the log group from being created properly.

For RDS PostgreSQL instances, when you enable log exports to CloudWatch Logs, the log group should be automatically created with a naming convention like /aws/rds/instance/my-db-id/postgresql. The fact that you're seeing the error "The specified log group does not exist" indicates that RDS is attempting to push logs, but the log group hasn't been created as expected.

Here are a few things you can check:

1. Double-check that you've enabled log exports for the correct log types. For RDS PostgreSQL, the supported log types are "postgresql", "upgrade", and "iam-db-auth-error". It appears you have these configured correctly based on your setup description.

2. Ensure that your RDS instance is in an Active state and not undergoing any modifications.

3. If you're using a custom parameter group, make sure it's associated correctly with your RDS instance and that the changes have been applied (which might require a reboot).

4. Check if there are any error messages in the RDS events or in CloudTrail logs that might provide more insight into why the log group creation is failing.

5. As a workaround, you could try manually creating the log group in CloudWatch Logs using the expected naming convention. While this isn't the standard procedure, it might help isolate whether the issue is with log group creation or log streaming.

6. If none of the above resolves the issue, you may need to contact AWS Support for further investigation, as there could be an underlying issue specific to your account or setup.

Remember that after enabling log exports, it may take a few minutes for the log group to appear in CloudWatch Logs. If you've recently enabled this feature, allow some time for the changes to propagate.
Sources
RDS for PostgreSQL database log files - Amazon Relational Database Service
Monitoring log events in Amazon CloudWatch - Amazon Aurora

I have different values in the Parm group for 15.7

• logging_collector = 1
• log_statement =
• log_min_duration_statement =

The 2nd 2 are EMPTY, not set

I am having the same issue / similar issue as the original poster.

When you say you see this:

The specified log group does not exist

Where are you getting that message from please? I don't even have that

I am running Auroroa Postgres 16.6

I have this under the specifid database

I would like to try Step 5 above but don't know what the nameing convention should be?