Repair an AWS deployment source that stopped reporting
Use the last read in Observed deployments to distinguish an inaccessible AWS connection from a missing CodePipeline pipeline or Amplify branch.
Inspect the binding’s last read#
Open the environment’s Setup → Delivery page and locate the affected binding. If the account is no longer linked, restore the environment link or bind the target to a linked account. If the connection cannot assume the role, open the AWS connection and verify its trust settings.
For a permission denial, review the connection’s current template with your AWS administrator before updating the role. For a source that does not exist, correct its pipeline or app and branch in the bound account and region.