OK for the first log file snippet you show is normal. This is what MongoDB will show when you first start mongod with the --replSet option. Shortly after that you should see that MongoDB is waiting for connections on a given port:
2020-05-11T19:44:08.778-0600 I REPL [initandlisten] Did not find local voted for document at startup.
2020-05-11T19:44:08.778-0600 I REPL [initandlisten] Did not find local Rollback ID document at startup. Creating one.
2020-05-11T19:44:08.778-0600 I STORAGE [initandlisten] createCollection: local.system.rollback.id with generated UUID: ec76c67d-5cd1-4900-9c1b-0814ae205bff
2020-05-11T19:44:08.855-0600 I REPL [initandlisten] Initialized the rollback ID to 1
2020-05-11T19:44:08.856-0600 I REPL [initandlisten] Did not find local replica set configuration document at startup; NoMatchingDocument: Did not find replica set configuration document in local.system.replset
2020-05-11T19:44:08.856-0600 I CONTROL [LogicalSessionCacheReap] Sessions collection is not set up; waiting until next sessions reap interval: Replication has not yet been configured
2020-05-11T19:44:08.856-0600 I CONTROL [LogicalSessionCacheRefresh] Sessions collection is not set up; waiting until next sessions refresh interval: Replication has not yet been configured
2020-05-11T19:44:08.856-0600 I NETWORK [initandlisten] waiting for connections on port 27017
In the second log snippet it shows that the getaddrinfo command that MongoDB runs fails to find host ip-10-0-1-100. Can you ping that host name? If not you would need to try the fully qualified domain name or adding the short host name to your /etc/hosts file with the associated IP address.