By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Application Migration Service - Launching of test/cutover instance failed - how to identify reason

0

Hey there,

currently working with AWS Application Migration Service transferring over a series of servers. Most of the test servers launch just fine, but one fails. not being super familiar with the system, i'm finding it hard to identify why it is failing. on the AMS job history for the specific job it gets as far as "Started launching..." and then that's the point at which it fails, but it does not give a detailed failure message.

is there somewhere where i can see more information about the job and what caused its failure? note that i looked at the AMS docs and there is nothing in the documentation in the troubleshooting section about how to identify why a test server launch fails.

any suggestions would be hugely appreciated.

cheers

nemo

Topics
Migration & Modernization
Tags
AWS Application Migration Service
Language
English
nemo
asked 7 months ago429 views
2 Answers
0

Hello, there is this troubleshooting section in the doc that can help you.

AWS
Vincent
answered 7 months ago
  • nemo
    7 months ago

    thanks, but as i noted i did look at the AMS docs and the troubleshooting section has nothing that tells you how to find information on why a test server will not launch.

0

Hi,

Did you try to check CloudWatch logs, events and CloudTrail to see if there is additional information that helps in diagnosing?

See https://docs.aws.amazon.com/mgn/latest/ug/monitoring-overview.html for all what you should check

Best,

Didier

profile pictureAWS
EXPERT
Didier_Durand
answered 7 months ago
  • nemo
    7 months ago

    i thought about those, but as far as i can see cloudwatch logs does not log stuff for DMS https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/aws-services-sending-logs.html unless i'm misunderstanding that page DMS is not noted there. in regards to cloudtrail, to my understanding all that logs are API calls and who makes them, so it doesn't have information on why launching a test server failed, just stuff like what user hit a given API and what that API was for (e.g. the system updating replication for a source server for instance).

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content