Migration & Transfer

I normally input new data into my app through a backend website that I have used for years and safari is saying that it cannot find server. All of My AWS accounts are paid.

First off I am very new to AWS cloudformation, been working on templates for a couple months trying to create a cloudformation template that creates an SFTP transfer service and adds a custom hostname. I was able to create the route 53 hostname and it all works fine with the exception the AWS Transfer Family dashboard does not show the Hostname for the server. I suspect it has to do with tags as I found this [doc](https://docs.aws.amazon.com/transfer/latest/userguide/requirements-dns.html#requirements-use-r53). I am using a parameter to get the HostedZoneId and use it via HostedZoneId: !Ref HostedZoneIdParam in the SFTPServerDNSRecord resource. is there a way to use t hat same parameter in a key/value as in Key: aws:transfer:route53HostedZoneId Value: /hostedzone/!Ref HostedZoneIdParam Any assistance or guidance would be appreciated

I created a DMS task: Source - MongoDB Target - RDS Postgres I have **successfully working pipelines with full load + Ongoing replication working.** But for some **collections** in my source mongo when I create Full load or Full load + Ongoing replication, **Task shows successfully completed and starts ongoing replication.** But Full load doesn't happens only schema gets created in postgres with 0 rows, and Ongoing replication starts. CloudWatch shows no error even after detailed debug.

Hello, I have problem with "Replication Agent" installation for "AWS Elastic Disaster Recovery" (DRS) on linux: Error: ./aws-replication-installer-64bit: error while loading shared libraries: libz.so.1: failed to map segment from shared object I used following commands: [ec2-user@ip-xxx ~]$ curl https://aws-elastic-disaster-recovery-eu-central-1.s3.eu-central-1.amazonaws.com/latest/linux/aws-replication-installer-init.py -o aws-replication-installer-init.py [ec2-user@ip-xxx ~]$ sudo python3 aws-replication-installer-init.py The installation of the AWS Replication Agent has started. AWS Region Name: eu-central-1 ./aws-replication-installer-64bit: error while loading shared libraries: libz.so.1: failed to map segment from shared object My environment: [ec2-user]$ uname -a Linux xxx 4.18.0-348.2.1.el8_5.x86_64 #1 SMP Mon Nov 8 13:30:15 EST 2021 x86_64 x86_64 x86_64 GNU/Linux [ec2-user]$ cat /etc/os-release NAME="Red Hat Enterprise Linux" VERSION="8.5 (Ootpa)" Does anybody have similar problem? Thanks, Adrian Hollay

AWS Transfer Family support AIX platform

hi, i need to migrate from aws to a different provider. where do i find the following info: SSH hostname: SSH username: SSH port number: SSH private key: SSH key passphrase: Thanks

We have noticed that the pre-checks for the upgrade of MySQL 5.7 to MySQL 8 are having issues with character combinations that "resemble" depreciated words. For example, the depreciated "Group By ... DESC" is one of those constructs "[https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.MySQL.html#USER_UpgradeDBInstance.MySQL.57to80Prechecks]()" "There must be no queries and stored program definitions from MySQL 8.0.12 or lower that use ASC or DESC qualifiers for GROUP BY clauses." While our stored procedures use Group by's, there is no associated "DESC" word with them. However, the character sequence does appear in the stored procedure in various forms: * There is a call to another stored procedure called "update_fc**desc**ription();". It has the characters "desc" within the name * There are columns in the queries (table columns) with the name "blah**Desc**riptionblah" * There is a block comment that has the word "**Desc**ription:" that describes the stored procedure (documentation) However, there are no "DESC" words associated with the "Group by". For testing, * I deleted the comments word, and that issue no longer appeared as an error * I renamed the call to the other stored procedure update_fc**desc**ription(); to update_fc**dxexscxrixp**tion();, and that issue no longer appeared as an error * The columns that have the characters "desc" I couldn't work around without a lot of changing to the stored procedure It seems that there is a Stackoverflow question outlining this behavior too: [https://stackoverflow.com/questions/71412470/aws-mysql-aurora-major-version-2-3-upgrade-pre-checks-obsolete-procedure]() Also, a "re:Post" question too: [https://repost.aws/questions/QUWJzlcpitRoGM0woZVOylBQ/aurora-2-to-3-mysql-5-7-to-8-0-upgrade-pre-check-incorrect-validation-on-store-procedure]() This is clearly a bug in the pre-check process and is limiting our upgrade from MySQL 5.7 to 8. Any updates on this being fixed/addressed? Thank you.

Hi, I ran AWSSupport-MigrateEC2ClassicToVPC to migrate my EC2 Classic to VPC. I ran Test first then Cutover. It started to run successfully but stopped on step 3 checkIfVirtualizationTypeIsHVM and that step and all others are Pending. It looks as if I must have done something wrong in setting up VPC and it can't receive the migration, but this is all 100% new to me and I don't know what to change.

Is there any change in the announcement that is found here? https://aws.amazon.com/about-aws/whats-new/2020/01/announcing-amazon-relational-database-service-snapshot-export-to-s3/ *Amazon RDS Snapshot Export to S3 can export data from Amazon RDS for PostgreSQL, Amazon RDS for MariaDB, Amazon RDS for MySQL, Amazon Aurora PostgreSQL, and Amazon Aurora MySQL snapshots and is now available in US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), and Asia Pacific (Tokyo) Regions.* I do not see the "sql-server" nor Mumbai region in the above statement.

I'm running AWS DMS task in full load + ongoing replication mode, both source and target are aws aurora mysql. Target database was created by cloning source and truncating all tables to preserve the schema. For one of the tables replication always fails with following error: ``` 2022-06-23T17:12:05 [TARGET_LOAD ]E: RetCode: SQL_ERROR SqlState: 23000 NativeError: 1062 Message: [MySQL][ODBC 8.0(w) Driver][mysqld-5.7.12-log]Duplicate entry '1213210-50' for key 'PRIMARY' [1022510] (ar_odbc_stmt.c:4828) ``` I have verified that there is no duplicates in source database table, the tables have identical schema in both source and target, and both source and target table has primary key with auto increment. The only workaround I found was to drop the table on target db and let DMS create it, but DMS creates it without indexes and foreign keys that we need. Is there any fix for this error that would allow me to preserve the table schema?

Can you please suggest the best approch for synching two or multiple database instances .

We would like to migrate some workloads from Beanstalk to EKS. What is the best way to generate container image manifests from Beanstalk applications, is there any automation / script solultion for this?

Created an AWS DMS pipeline: Source endpoint - **MongoDB ** Target endpoint - **RDS Postgres SQL** Successfully did all the security configuration, and both **endpoints **returned **successful **while testing it. For the MongoDB source, I am using one of the three **replicas **sets with a username and a password that is not the admin username. I also added the privilege "**changeStream**" in the replica set user. But when starting the DMS migration task getting this error in cloud watch. ``` Encountered an error while initializing change stream: 'not authorized on admin to execute command { aggregate: 1, pipeline: [ { $changeStream: { fullDocument: "updateLookup", startAtOperationTime: Timestamp(1656005815, 0), allChangesForCluster: true } }, "ok" : { "$numberDouble" : "0.0" }, "errmsg" : "not authorized on admin to execute command { aggregate: 1, pipeline: [ { $changeStream: { fullDocument: \"updateLookup\", startAtOperationTime: Timestamp(1656005815, 0), allChangesForCluster: true } }, 74f1-4aab-9ca1-f964ab655777\ (change_streams_capture.c:356) ``` Assuming this is due to some missing privileges in mongo replica sets USER.

Is it possible to designate mariadb, which is operated on the naver cloud platform from AWS Oracle db as the target endpoint with AWS DMS? After that, can I access the server installed on the Naver Cloud Platform from aws database (oracle db) through aws dms?

Hi, Is there a way for EventBridge to capture DMS replication task "Running with error" status change? This occurs when the replication task has some tables that have failed. The "Failure" category does not capture this. It only captures when the entire task has failed. '{"category":["Failure"]} Thanks!

If we migrate ec2 to vpc ,Can we get the same Hostname and IP Address?

We are migrating from VirtualBox(6.1) virtualization to AWS for MGN testing. The source server is Centos 6.8. By installing a replication agent on the source server, it went smoothly with 'ready for testing' status. However, after the 'launch test instance' action, the test instance created in the 'Test in progress' phase does not operate normally. Status in Lifecycle is as follows. - Launch status Launched First boot: Stopped - Last test : Completed (Check through Job Id link) Data replication status is as follows. - Healthy - Replication pregress : Initial replication finished In the instance menu, the test instance status is running, but the status check is 'initialized' for more than 30 minutes, and the instance status check fails. (System status check is successful.) Nevertheless, when I look at the instance screenshots, the prompts on the console screen look fine. After allowing ssh and ping to the security group, ping and ssh connection are attempted from the bastion host, but it fails. I don't even know if the replication of the whole instance is the problem, or just a part of the instance (eg the network) is the problem. If you have a similar experience on MGN, please give me a hint. Thank you.

How can i transfer data from Aws S3 to Hetzner Storage Box?