Doing a quick test to the IP address of your instance on that port I can see that it is giving a connection refused.
[ec2-user ~]$ nc -vz 220.127.116.11 7070 nc: connect to 18.104.22.168 port 7070 (tcp) failed: Connection refused
There are two possible scenarios here, the application you are using is not listening on this port or your firewall is still refusing the connections.
You can see if your application is in fact running and listening on that port by running the following command.
sudo netstat -tulpn
EC2 TCP port Connection refusedasked 2 years ago
Can't start server: listen tcp: address 80: missing port in addressasked 9 months ago
Is there a reason why port forwarding isn't working?asked 24 days ago
With a Security group I can't connect to EC2 instanceAccepted Answerasked 2 months ago
How to open a portasked 5 months ago
accessing site with custom port and static ipasked 5 months ago
Port 3306 results closedasked 2 years ago
How to make HTTPS ALB that targets other TCP port of a fargate service?asked 2 months ago
open port to multiple IP'sasked 2 months ago
(t2.micro) Editing port rules in Security Group makes no changes - Can always ping port 3389, but 22 failsasked 8 months ago