App Runner Service

This error suggests that you're encountering an issue with permissions when trying to access VPC Connectors for your App Runner service.

When configuring an App Runner service to communicate with resources in a VPC (like an RDS database), you need to create a VPC connector that allows your App Runner service to send outgoing traffic to your VPC resources.

To resolve this error:

1. Check that your AWS account has the necessary permissions to use App Runner VPC connectors. The error "The AWS Access Key Id needs a subscription for the service" typically indicates that your IAM user or role doesn't have the required permissions to list VPC connectors.

2. Ensure that your IAM user or role has the appropriate App Runner permissions, specifically permissions related to VPC connectors (such as apprunner:ListVpcConnectors).

3. Verify that App Runner service is available in the AWS region you're using. App Runner might not be available in all regions.

4. If you're using an IAM role, make sure it has the correct trust relationship and permissions policies attached.

5. If you're using temporary credentials, ensure they haven't expired.

Once you have the correct permissions, you should be able to create a VPC connector by:

• Selecting your VPC
• Choosing appropriate subnets (for better availability, choose three subnets if possible)
• Selecting security groups that allow the necessary traffic between App Runner and your target resources (like RDS)

After creating the VPC connector, you can associate it with your App Runner service to enable outgoing traffic to your VPC resources.
Sources
Enabling VPC access for outgoing traffic - AWS App Runner
How to Successfully Connect AWS App Runner with a Privately Accessible RDS Instance? | AWS re:Post

Hello.

Judging from the error message, I think the problem is not with IAM but with your AWS service subscription.
As described in the following document, it is possible that the AWS service has not been enabled, so please sign in as the root user of your AWS account and check.
https://repost.aws/knowledge-center/error-access-service

If the steps in the above document do not resolve your issue, I recommend contacting AWS Support and opening a case under "Account and billing."
"Account and billing" inquiries are free of charge.