aws-amplify / aws-amplify/amplify-cli

Inaccessible host: `cognito-idp.us-east-1.amazonaws.com' at port `443'

Open
#13,837 1 comment 0 reactions 0 assignees View on GitHub
feature-request hosting
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### How did you install the Amplify CLI?

pnpm

### If applicable, what version of Node.js are you using?

v20.13.1

### Amplify CLI Version

12.12.3

### What operating system are you using?

Mac

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No

### Describe the bug

I normally `amplify publish -y` my web app changes, (no cloud changes), but since yesterday, after cli outputs: Deployment completed. show this error:
![CleanShot 2024-06-27 at 12 46 27@2x](https://github.com/aws-amplify/amplify-cli/assets/7065779/a95d596c-2fcb-4a01-916a-e43d2f8b7449)

Session Identifier: 17d87b65-6294-432d-b7d5-edcd6e86615f

On the second try (amplify publish -y) It works perfectly

### Expected behavior

I expected to deploy frontend to hosting manually using `amplify publish` cli command

### Reproduction steps

run :

amplify publish -y in not modified cloud data project (only frontend update)

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

### Before submitting, please confirm:

- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with `amplify publish -y` in an unchanged cloud-data project using the reported Node.js and Amplify CLI versions. Inspect the CLI output and collect logs around the first attempt to the `cognito-idp.us-east-1.amazonaws.com` endpoint, then compare it with the successful second attempt. Done means the first publish completes without the inaccessible-host error.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, node.js, typescript
Domain
authentication, cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.