APEX on Amazon Cloud - EC2

I upgraded APEX 4.2 to APEX 5 on Amazon Cloud but now I cannot access the account.

How can I troubleshoot this?

I don't know about Elastic IPs and all the other things Amazon uses..

Thank you,
BILL CarlisleAPEX DeveloperAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

btanExec ConsultantCommented:
In AWS, you should already be having an IAM user account with the permissions to operate and manage such EC2 instance. An IAM user can control everything in the infrastructure.
Your AWS resources, such as Amazon EC2 instances, Amazon S3 buckets, and so on
Even if your users have passwords, they still need permission to access your AWS resources. When you create a user, that user has no permissions by default. To give your users the permissions they need, you attach policies to them. If you have many users who will be performing the same tasks with the same resources, you can assign those users to a group, then assign the permissions to that group. For information about creating users and groups, see Identities (Users, Groups, and Roles).
To sign in as this new IAM user, sign out of the AWS console, then use the following URL, where your_aws_account_id is your AWS account number without the hyphens (for example, if your AWS account number is 1234-5678-9012, your AWS account ID is 123456789012):

Enter the IAM user name and password that you just created. When you're signed in, the navigation bar displays "your_user_name @ your_aws_account_id".

But if you have before login before then it may be case the account is invalidated due to upgrade or there is an default account to login or upgrade has stopped the instance
Q: What should I do if my instance is no longer responding?
This is often caused by an issue that is specific to the internal configuration of the instance. The recovery process after an instance is not responding depends on the type of instance that you are running (EBS-backed vs. instance-store backed).

First review the console output of your instance to try to determine why the reboot affected the instance. The information in the console output can sometimes provide you with enough details to understand why your instance failed.
May need recovery if need to

You can check out in AWS forum on issues faced and raise as well to the wide community that is very helpful in assistances (I added in some search terms already) https://forums.aws.amazon.com/search.jspa?threadID=&q=cannot+login+ec2+apex&objID=f30&userID=&dateRange=all&numResults=15&rankBy=10001
BILL CarlisleAPEX DeveloperAuthor Commented:
Ok, thank you.. I have access through Putty to the 2 Instances, the one that contains Glassfish and the one that contains the APEX 5 install.

1. Is there a way to test APEX without Glassfish in EC2?
   I use to run listener in standalone but run it with port 7878 instead of 8080.
Says the port is not open.. How do I find the range or port numbers I can access or open?
How do I open them in EC2?

2. Where do I find the "console output"?
"First review the console output of your instance to try to determine why the reboot affected the instance. The information in the console output can sometimes provide you with enough details to understand why your instance failed."

thank you for your help,
btanExec ConsultantCommented:
1. Probably the straightforward means is to assess other ppl sharing of what they did successfully - https://survivalguides.wordpress.com/2012/07/30/installing-oracle-11g-xe-and-apex-4-11-in-amazon-aws/

2. The console is as per
Users who want to use the AWS Management Console must sign in to your AWS account through a unique sign-in page that's specific to your account. You provide your users with the URL they need to access the sign-in page. You can find the URL for your account on the dashboard of the IAM console.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

BILL CarlisleAPEX DeveloperAuthor Commented:

1. That link shows a non-existant AMI so I used the only available one.
2. What I was looking for there was the  "console output"
Which you go to Instances -> Actions -> Instance Settings -> Get System Log

I use to run listener in standalone but run it with port 7878 instead of 8080.
Says the port is not open.. How do I find the range or port numbers I can access or open?
How do I open them in EC2?
btanExec ConsultantCommented:
Do you mean that you do not see any log or you have not access to the console ? Note that the console is a web-based and you need to login to your account. But if you SSH in then it is not web login then.
Specifically for the ports to open, you need to check the security groups, and view the rules to display the list of rules that are in effect. Such as Inbound rules to allow certain service connection, the example shows the RDP 3389
Adding a Rule for Inbound RDP Traffic to a Windows Instance

Security groups act as a firewall for associated instances, controlling both inbound and outbound traffic at the instance level. You must add rules to a security group that enable you to connect to your Windows instance from your IP address using RDP.

To add a rule to a security group for inbound RDP traffic using the console

1.In the navigation pane of the Amazon EC2 console, click Instances. Select your instance and look at the Description tab; Security groups lists the security groups that are associated with the instance. Click view rules to display a list of the rules that are in effect for the instance.

2.In the navigation pane, click Security Groups. Select one of the security groups associated with your instance.

3.In the details pane, on the Inbound tab, click Edit. In the dialog, click Add Rule, and then select RDP from the Type list.

4.In the Source field, specify the public IP address of your computer, in CIDR notation. For example, if your IP address is, specify to list this single IP address in CIDR notation. If your company allocates addresses from a range, specify the entire range, such as

2. From this
You will get following style output, don worry if some of the port numbers are different.

Using default port 4848 for Admin.
Default port 8080 for HTTP Instance is in use. Using 37339
Using default port 7676 for JMS.
Using default port 3700 for IIOP.
Using default port 8181 for HTTP_SSL.
Using default port 3820 for IIOP_SSL.
Using default port 3920 for IIOP_MUTUALAUTH.
Using default port 8686 for JMX_ADMIN.
Using default port 6666 for OSGI_SHELL.
Using default port 9009 for JAVA_DEBUGGER.
The log may trigger the access attempt as well which may be indicator to the port required.
BILL CarlisleAPEX DeveloperAuthor Commented:
Thank you, that will help..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Cloud Services

From novice to tech pro — start learning today.