Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- AWS announced Access Troubleshooter on November 17, 2026. The current guide explicitly identifies it as public preview, with APIs subject to change.
- With an authorization ID, open the error’s console link or call GetRequestAuthorizationDetails in the same AWS Region as the denial.
- The lookup requires iam:GetRequestAuthorizationDetails. Records are created asynchronously and retained for 24 hours after the denial.
- Determine whether the denial is intended, then inspect the action/resource pair, policies and request context. Diagnostic results do not automatically grant access.
First check whether the denial has an authorization ID
Access Troubleshooter provides authorization-evaluation details for denied requests to some AWS APIs. An authorization ID uniquely references that evaluation and may appear with the AccessDenied error and a console link. Use it to see which policies AWS considered, the request context and the result for each action/resource pair.
The November 17 announcement introduces the capability, while the User Guide identifies it as public preview with APIs subject to change. Not every denial includes an ID. A service appearing in the support list does not establish coverage for all of its APIs or every Region.
Step 1: Record the time and Region, then open the console link
In an organization-approved incident record, retain the denial time, AWS Region, action, resource and authorization ID from the error. These details may contain account, resource and policy information; share them only with authorized investigators and redact them before seeking public help. An ordinary request ID from another request is not a substitute for this authorization ID.
Open the link included in the error to view the Access Troubleshooter console. Find the denied action/resource pair: what the request tried to do, and to which resource. Then inspect its evaluation and policies. One request can involve multiple pairs; an Allow result on one row does not establish permission for the whole request.
Authorization details are recorded asynchronously and may not be immediately available. For a just-generated denial that is temporarily not found, wait briefly before checking again. AWS retains details for 24 hours after the denial, so investigate within that window.
Step 2: Look up the ID with the CLI in the original Region
The documented command uses iam-toolbox and the get-request-authorization-details operation. The caller needs iam:GetRequestAuthorizationDetails permission. Send the lookup to the same AWS Region where the denial and authorization ID were generated.
The command below uses only AWS documentation example values and was not executed. Replace us-east-1 with the Region of the original denial and the value beginning EXAMPLE with that error’s authorization ID. Use an organization-approved AWS identity and keep keys out of commands, articles and public tickets.
Read authorization details by ID (Bash / POSIX shell)
bashaws iam-toolbox get-request-authorization-details \
--region us-east-1 \
--authorization-id EXAMPLE1a2b3c4d5e6f7g8h9i0j
Step 3: Separate explicit denial, missing permission and context
Results show ALLOW, EXPLICIT_DENY or IMPLICIT_DENY for each action/resource pair. EXPLICIT_DENY means a policy explicitly denied the action; IMPLICIT_DENY means no policy allowed it. Match policy ARN or URI references in the evaluation to the corresponding policies.
The details also list policies considered during evaluation, including policies that did not match the action/resource pair. Types can include identity-based and resource-based policies, service control policies (SCPs), resource control policies (RCPs), permissions boundaries and session policies. Checking only the policies attached directly to a user can miss the cause.
Decide first whether the denial is correct. The guide gives examples of a missing expected session tag or an unexpected network path. An authorized policy owner should check the required conditions before deciding whether to narrow a specific Deny, add a necessary Allow or correct the calling context. Do not grant administrator access simply to remove the error.
What to check when there is no ID or details cannot be retrieved
An ID may be absent because the authorization involves too many policies to record, the service or specific API is unsupported, or the request type is unsupported. The guide lists requests made by a service on your behalf and anonymous requests among unsupported types. A missing ID alone proves neither an identity problem nor a network fault.
The current guide lists some APIs for CodeDeploy, IAM, KMS, STS, Step Functions, EC2, ECR, Kinesis Data Streams and SQS. Support is rolling out gradually across services and Regions; the guide does not provide a complete Region/API matrix. Check the actual error and current support table.
If you have an ID but the lookup fails, separately check the original Region, lookup permission, asynchronous recording delay and the 24-hour retention window. For an error without an ID, continue with conventional IAM AccessDenied troubleshooting. Do not repeatedly run an original operation that may change resources merely to obtain an ID.
Account for organization boundaries, historical policies and unknown charges
Within a single account or organization, people granted iam:GetRequestAuthorizationDetails can access request details. For requests spanning organizations, only details belonging to the caller’s own organization are returned. Another organization’s policies and context are excluded; their absence does not mean that organization imposed no restrictions.
Evaluations reflect policies at the time of the denial, and those policies may since have changed. After an authorized correction, verify the new business request separately. An old ID is not a snapshot of current permissions, and retrieving diagnostic details does not establish that the original business operation succeeded.
The reviewed announcement and guide do not establish a complete fee statement, minimum CLI version or rollout to every account. Do not assume preview means free or universally available. This guide uses public documentation and did not access an AWS account, read real authorization records or change policies. Investigate connectivity when there is separate DNS, TLS or timeout evidence; a proxy exit cannot replace IAM permissions or platform eligibility.
Sources
Frequently Asked Questions
If GetRequestAuthorizationDetails itself is denied, can I grant myself access?
Have an authorized IAM administrator check whether the querying identity is allowed iam:GetRequestAuthorizationDetails and review organization and resource boundaries. The diagnostic API also enforces permissions. Knowing an authorization ID does not automatically grant permission to read details or modify policies.
What should I use if my CLI does not recognize iam-toolbox?
This guide preserves the iam-toolbox command named in the current AWS documentation. The reviewed page does not give a minimum CLI version. Check whether your installed CLI includes the command and consult current AWS installation and update guidance. Do not substitute a guessed aws iam subcommand. Where permitted, you can still use the console link provided in the original error.