Re: AWS EC2 OEM support

Just noticed you are not using RDS.
My response was for RDS only.

On Thu, Jul 5, 2018, 2:07 PM Steve Harville <steve.harville_at_gmail.com> wrote:

>
> Hi Dave
>
> We have this configured with Enterprise Manager 13 and it works fine.
> Yes the network needs to be configured correctly.
> From the DBA perspective, the main thing is to create an option group on
> AWS,
> Add the OEM_AGENT option to the option group, then assign your databases
> to use the new option group.
> See:
> https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Options.OEMAgent.html
>
> Also, Amazon's documentation on how to configure on the Enterprise Manager
> side is not good.
> Basically when it asks for a host name it really means the RDS "endpoint".
>
> Steve
>
> On Thu, Jul 5, 2018 at 1:38 PM <niall.litchfield_at_gmail.com> wrote:
>
>> I'd imagine that your firewall rules (either virtual or physical or both)
>> will require connectivity between your on-premises OEM and the off-premises
>> EC2 instances on the relevant ports. These are documented in the
>> surprisingly hard to find Note
>> https://support.oracle.com/epmos/faces/DocumentDisplay?id=2362242.1
>> 2362242.1. If you have internal firewalls this is probably old hat, but if
>> you don't it's the most likely reason that ssh succeeds but monitoring
>> doesn't. You'll also need name resolution to be consistent.
>>
>> On Thu, Jul 5, 2018 at 5:45 PM Dave Herring <gdherri_at_gmail.com> wrote:
>>
>>> Folks,
>>>
>>> (I've been given the task of setting up monitoring for a number of
>>> Oracle databases on AWS EC2 and unfortunately given little to no guidance,
>>> so I apologize upfront if my question seems rather basic.)
>>>
>>> Has anyone set up management agents on AWS EC2 environments to monitor
>>> from an OEM outside of AWS? We did something similar in the past for RDS
>>> environments but I was hoping we wouldn't have to rely on the OEM AWS
>>> plugin, which only provides a rather limited subset of functionality of OEM
>>> for the envs.
>>>
>>> Since we have SSH key pairs set up to reach the AWS servers, my
>>> assumption was I could perform agent installations from OEM (which resides
>>> outside of AWS), using pre-defined Named Credentials that use SSH key
>>> pairs. Unfortunately it seems the connection can't be made that way
>>> through OEM, although I did prove I COULD connect at the OS level using the
>>> same method.
>>>
>>> I did find a post by Pete Sharman from 5/2016 saying that under OEM 13c
>>> we'd need to have an Amazon VPC configured and only then could a typical,
>>> OEM to agent monitoring configuration and that the only other option is to
>>> use the AWS plugin. But, that's just over 1yr old and I wasn't sure if
>>> anything has changed since then.
>>>
>>> Thx.
>>>
>>> --
>>> Dave
>>>
>>
>>
>> --
>> Niall Litchfield
>> Oracle DBA
>> http://www.orawin.info
>>
>

--
http://www.freelists.org/webpage/oracle-l