- Newest
- Most votes
- Most comments
Based on the information provided, I don't see any known regional issues with ACM in ap-southeast-2 that would cause certificates to be visible in the console but not via API/CLI.
To troubleshoot this issue, I recommend checking the following:
-
Verify that you're using the same AWS account and region in both the console and CLI. Ensure your CLI is properly configured for the ap-southeast-2 region.
-
Try using the describe-certificate command with a specific certificate ARN that you can see in the console. The ARN format should be:
arn:aws:acm:ap-southeast-2:123456789012:certificate/12345678-1234-1234-1234-123456789012 -
Check if you're using any filters in your list-certificates command that might be excluding your certificates. Try adding query parameters to specifically look for imported certificates:
aws acm list-certificates --region ap-southeast-2 --query 'CertificateSummaryList[?Type==IMPORTED].CertificateArn' -
Verify IAM permissions. Even though you're using AdministratorAccess, confirm there are no SCPs (Service Control Policies) or resource-based policies restricting access.
-
Check if there's any difference in behavior when accessing from different network environments or using different AWS access keys.
If the issue persists after these checks, I recommend contacting AWS Support directly as this appears to be an account-specific issue that requires investigation of your specific account configuration.
Sources
Options for AWS customers who use Entrust-issued certificates | AWS Security Blog
request-certificate — AWS CLI 2.27.41 Command Reference
answered a year ago
Relevant content
asked 4 years ago
- AWS OFFICIALUpdated 2 years ago
