Hi i am trying to perform patching activity on the ec2 instances using AWS Systems manager but unable to perform activity because in panel of SSM managed instances it shows "connection lost" for ping status.
How can i resolve this?
Check if correct IAM role is attached to the instances also verify iSSM agent version.
Related
I have created a windows instance and got .rdp file. How can i get the access logs i.e WHO and WHEN the instance is logged into with this .rdp file. Also, how much time was it used. Need help with the approaches of how to achieve this.
that possible completely to get each events log using Cloudwatch log Agent and system manager service which work on SSM Agents but this will work for Instances have Outbound Access to send logs to Cloudwatch. and the best part is AWS have amazing documentation for the same to setup a Cloudwatch for Windows Instances . Please have a look on this Windows logs with Cloudwatch
I have myself setup it for Windows server as per the need we can be flexible. let me know if you stuck while following this document.
This is one of the best approach .
I have created AWS EC2 Windows 16 instance and was able to attach additional volume etc...and so far so good.
I wanted to try to use CLI commands.
Installed CLI on AWS-EC2 windows instance. and did according the instructions attached in the picture below.
when I type "aws ec2 describe-instances I get "Could not connect to the endpoint URL"
When I was creating the instance, I chose a "Security Group" that had HTTPS enabled.
any help?
You probably have something wrong in your default profile for the default region.
Check your file at ~/.aws/config (or C:\Users\USERNAME \.aws\config for windows users), you have something like
[default]
region=us-west-2a
...
Fix the region to region=us-west-2 and then the command will work correctly
You can review the AWS page to make sure you have a valid endpoint http://docs.aws.amazon.com/general/latest/gr/rande.html, they are classified by AWS services
I'm trying to install oracle on AWS redhat instance. Follow the steps given on this url: http://www.davidghedini.com/pg/entry/install_oracle_11g_xe_on And when I run config command as follows
/etc/init.d/oracle-xe configure
It gives following error.
Database Configuration failed. Look into
/u01/app/oracle/product/11.2.0/xe/config/log for details
When I check the log files it shows following errors.
ORA-01034: ORACLE not available Process ID: 0 Session ID: 0 Serial
number: 0
It seems specific issue on AWS cloud instance.
Is it because of swap memory?
Or is it because of port issue?
I'm using micro instance on it.
How can I get through?
this might be an EC2 security group issue and outbound access to the network on some port being used by the installer (license check, maybe?).
if your EC2 instance is very tightly locked down, you could test if it's a security group issue by adding a new Outbound security group rule to allow all TCP traffic out to anywhere on the internet (0.0.0.0/0)
for example, the install might be trying to hit a remote licensing server endpoint via HTTP or HTTPS but your security group doesn't allow that traffic out.
perhaps there's a 'verbose' flag that you can run the installer with that can give you more info about what it's failing on? HTH
I have deployed neo4j to ec2 using this https://github.com/neo4j-contrib/ec2neo
I am getting 503 service not available error. How can I access the neo4j logs on ec2. Can anybody help please.
The steps to access the logs are given in: ec2neo Output
Select the CloudFormation stack that you used to create the instance. Click on Outputs tab. It will give you the actual ssh command to use to access the EC2 instance.
I have Apache server running on Centos5.4 Ec2 instance. Unfortunately while removing Bash from Centos, it also removed basic shared libraries.
Now afterward I can't SSH to that EC2 instance but Apache server is still running (I can access my site through URL).
Any idea how can I get the SSH access back? or can repair Centos Ec2 instance?
Thanks!
You can always contact the AWS support directly. They are very accommodating. send a message to them and they will recover your access, if it is doable from their end.
You may call, or you may send a message from your AWS account.