aws-solutions / cloud-migration-factory-on-aws Goto Github PK

https://github.com/aws-solutions/cloud-migration-factory-on-aws/blob/master/deployment/CFN-templates/aws-cloud-migration-factory-solution.template

When deploying an AWS resource using the above template, the following error occurs in "FrontEndBucketPolicy".

cloudfront oai resource handler returned message: "invalid principal in policy

So please change to a template that uses OAC.

Fix:
This issue has been resolved in our environment with a change to the lambda_mgn.py. Incoming PR that checks for Hostname and FQDN key in the dictionary before doing a comparison of values between CMF and MGN.

Issue:
Two servers sitting in Archive in our MGN were previously from performing an Import into MGN. However, no agents were ever installed, so Hostname and FQDN values did not exist on the servers in MGN. When trying to do a Validate Launch Template or Launch Test Instances from CMF into MGN would cause an error response of "Submit action failed: 'hostname'".

The import for the base64 library is missing in this file. This is causing an error and preventing CMF lambdas from executing properly.

We are seeing this error in cloudwatch when trying to update the account list attribute in the Applications administration area.

[ERROR] 2024-05-07T22:33:18.809Z a4dcda80-da0a-43ab-83d1-b388c7f9d328 Denying Admin API Access, Claims Error, name 'base64' is not defined

HI Team,

I initiated a job with SSM automation execution in the cloud migration factory console via automation server instance.

The jobs completed in SSM however, the status couldnt be updated back in the cloud migration factory. Typically the jobs are showing timed out in the factory console. Checked dynamo db table and it shows timed out as well. But the SSM automation document run completed successfully. We need to know why job status is not updating in cloud migration factory. We used migration factory public type deployment.

Let me know if some screenshots/logs required.

Regards
Dips

Hey folks,

Just come across this bug when trying to deploy this solution.

I.e. there are 2 Code: keys which is causing the cfn deployment to fail. Duplication on line 3106-3107 https://github.com/awslabs/aws-cloudendure-migration-factory-solution/blob/master/deployment/aws-cloudendure-migration-factory-solution.template#L3106

Running the step to install CloudEndure agent on servers using command "python 1-CEAgentInstall.py --Waveid 1"

At the following step, when user enters capital Y instead of small Y, its not recognizing SSH key based authentication, instead it is trying password based.

At line # 312, _has_key should check for both Y and y.

            status = linuxpkg.install_cloud_endure(server['server_fqdn'], user_name,
                                                 pass_key,
                                          **_has_key in 'y'_**, project['InstallToken'])

Error Log:

• Enter Linux Sudo username and password *

Linux Username: ec2-user
If you use a private key to login, press [Y] or if use password press [N]: y
Private Key file name: cedr.pem

• Installing CloudEndure for: ec2-xxxxx.compute-1.amazonaws.com -

Unable to connect to host ec2-xxxx.compute-1.amazonaws.com with username ec2-user due to Bad authentication type; allowed types: ['publickey', 'gssapi-keyex', 'gssapi-with-mic']

Migration Factory tenancy option does not support dedicated host resource groups.

Describe the bug
When attempting to edit a server in the front-end, an error occurs with the message "Invalid JSON: "[object Object]" is not valid JSON." The issue seems to be related to the initial validation of the JSON attribute when loading the edit page for the server object.
The UI gives the indication that something is wrong with the json, but it's not and it further impacts the possibility to save any changes before the validation error is gone.

To Reproduce

1. Create a custom JSON attribute.
2. Populate the custom JSON attribute within a CMF Automation job.
3. Navigate to the front-end and attempt to edit the server with the custom JSON attribute.
4. Encounter the error: "Invalid JSON: "[object Object]" is not valid JSON."

Expected behavior
Editing the server with the custom JSON attribute should not result in a JSON validation error. The JSON object has the correct format, and the validation should not raise an error when loading the edit page.

Please complete the following information about the solution:

• Version: V3.3.0

• Region: us-east-1

• Was the solution modified from the version published on this repository? No

• If the answer to the previous question was yes, are the changes available on GitHub?

• Have you checked your service quotas for the sevices this solution uses? N/A

• Were there any errors in the CloudWatch Logs? NO

Screenshots

Additional context
Upon further investigation, I believe the issue is related to the initial validation when loading the edit page for the server object. The problem seems to be occurring in the file JsonAttribute.tsx. The validation error disappears when any character is added to a property, indicating that the JSON object is correctly formatted, and the issue might be in the validation process during the initial page load.

This solution implements functions which use the python2.7 runtime. This is becoming EOL on July 15th. Let's update the version to that latest supported python version.

https://aws.amazon.com/blogs/compute/announcing-end-of-support-for-python-2-7-in-aws-lambda/