Laravel Forge 连接AWS失败求助：API凭证无效问题排查

Hey there, let's work through this credential issue step by step—you're already on the right track with setting up an IAM user, so let's narrow down where things might be going wrong:

1. Triple-check your credential input #

It sounds obvious, but tiny mistakes here are the most common culprit:

• Make sure you copied the Access Key ID and Secret Access Key exactly as they appeared in the AWS console. Extra spaces, missing characters, or accidental line breaks (especially when copying the secret key) will break authentication.
• Remember: the Secret Access Key is only visible once when you create the IAM user. If you lost or missaved it, generate a new key pair (revoke the old one first for security) and try again.

2. Verify your IAM user's configuration #

Even with AdministratorAccess attached, a few settings can block Forge's API calls:

• Confirm the access key is Active: Head to AWS IAM → Users → [Your User] → Security Credentials → Access keys. Double-check the status is marked as Active (it's easy to accidentally set it to Inactive when creating).
• Disable MFA for this user: Forge doesn't support API requests that require Multi-Factor Authentication. If MFA is enabled on your IAM user, your credentials will fail no matter how correct they are.
• Ensure the AdministratorAccess policy is properly attached: Go to IAM → Users → [Your User] → Permissions. The policy should be listed under "Permissions policies" and show as "Attached" (sometimes policies fail to apply on initial creation).

3. Test your credentials directly with AWS CLI #

To rule out issues with the credentials themselves (not Forge), test them locally:

1. Install the AWS CLI if you haven't already.
2. Run aws configure and enter your Access Key ID, Secret Access Key, default region (e.g., us-east-1), and output format (json works fine).
3. Run a simple test command like aws ec2 describe-instances. If this returns a valid response (even if you have no instances), your credentials are working. If it throws an error, the problem is on AWS's end, not Forge.

4. Tweak your Forge AWS settings #

• Confirm you selected the correct AWS region in Forge's server provider setup. While AdministratorAccess is global, Forge needs to know which region to deploy servers to, and a mismatch can cause unexpected credential errors.
• The "User Name" field in Forge's AWS setup is optional—try leaving it blank if you filled it in, as it's not required for API authentication.

5. Rule out AWS account-level issues #

• If your AWS account is brand new, there might be initial service limits, but these usually throw "Request Denied" errors rather than invalid credentials.
• Make sure your AWS account is in good standing (no payment holds or suspensions) that could block API access.

If you still hit the error after these steps, try generating a brand new access key pair for the same IAM user, revoke the old one, and use the new pair in Forge. Sometimes old keys develop hidden corruption or permission glitches that a fresh pair fixes.

内容的提问来源于stack exchange，提问作者addi2113