ECS Anywhere -- Register External Instances link dead

Question

We've started experimenting with ECS Anywhere and just in the past few days, the register external instances link is dead/inaccessible:

curl --proto "https" -o "/tmp/ecs-anywhere-install.sh" "https://amazon-ecs-agent.s3.amazonaws.com/ecs-anywhere-install-latest.sh"

returns:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>Q8QPSN1GP90X3ZX2</RequestId>
<HostId>DREyWsYwxRMDC1It6G/ThV7gYa6AAzN5U4lO3kfVAzrf2T5A6XPq1ALRVeE6bDSGhmLk/gI/Jug=</HostId>
</Error>

Accepted Answer

I have made the team aware.

Answer

Same here. The file for windows downloads correctly, but (un)fortunately, it's of no use to me.

Answer

It's back!!

```
curl --proto "https" -o "/tmp/ecs-anywhere-install.sh" "https://amazon-ecs-agent.s3.amazonaws.com/ecs-anywhere-install-latest.sh"                                                       
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 22282  100 22282    0     0  28370      0 --:--:-- --:--:-- --:--:-- 28530
```

ECS Anywhere -- Register External Instances link dead

Relevant questions

Should ECS Service Task start be triggered by ASG capacity 0->1?

The "new" Amazon ECS Console is missing fundamental options like container command overrides

ECS: Understanding of CapacityProviderReservation

EKS Anywhere\Connector - Register New Cluster Button Does Not React

ECS Container not recognizing EC2 instances after updating AMI

Can Managed Compute Enviroments make use of PrivateLink ECS and ECR

Best Approach to use cognito with google federated IDP

API Gateway integration random status 500

ECS Anywhere -- Register External Instances link dead

How to register IP address for ECS task at startup so that other resources can find it