AnsweredAssumed Answered

Not able to access Blackboard AMI

Question asked by orhunk90 on Jan 15, 2019
Latest reply on Mar 16, 2019 by moneil

Like • Show 0 Likes0
Comment • 6

Hi,

We are trying to set up Blackboard AMI to test out LTI application. We followed the instructions under “Usage Information” in https://aws.amazon.com/marketplace/pp/B077T4SX2B?qid=1547476864757&sr=0-1&ref_=srh_res_product_title . We see our EC2 instance is running.

However when we hit: https://{Public IP of the instance} we don’t get any response(“failed” status). We created the instance from 3500.7.0 (Jan 09, 2019) version of AMI (tried 3500.5.0 too). We are able to connect to the instance via SSH. When I go to Path: /usr/local/blackboard/logs I see some log files but I am not sure which one is the most helpful for my case. I see some exception was thrown like this: "Temporary failure in name resolution" in "bb-services-log.txt"

I am not sure if we are missing any step.

Thank you!

1 person has this question

Outcomes

moneil Jan 15, 2019 11:04 AM

Hello Orhun,

Please see an email from Mark Kauffman, dated sometime yesterday evening - let's triage this forward in that email thread. Please continue to Cc developers at blackboard.com.

My initial question is whether you have the VPC set up?

If you can select the AMI in question and provide a screen capture of the EC2 panel (below the listing of your instantiated EC2s) that would be helpful.

Thank you,

Cheers,

-m

Mark O'Neil

Director, Product Management, Platform and APIs

Blackboard Inc.

Quick Links:

Developer AMI

Developer Program
Developer Community

Actions

df0040484 @ moneil on Mar 14, 2019 4:19 PM

Our admin is having what sounds like the same problem setting it up on our VPC. Is there a known solution for this?

Actions

ac0048155 @ moneil on Mar 14, 2019 4:47 PM

Hello Mark - I work with Dustin.

I have set up a t2.large instance following the instructions from the AMI Marketplace. The VPC this was launched in to is fully functioning and running other services - including a prior BB instance.

The issue appears to be how BB is bootstrapping endpoint configurations within the instance - it appears to want to use the local hostname - which Amazon initially sets to just the hostname (not FQDN) portion of the auto-assigned hostname. Since all services are running locally, it would probably be far better to simply use "localhost".

For tracking - since we have enterprise support via AWS - I am going to open a ticket with AWS via the support portal to mirror this one.

Cheers,

Andrew.

1 person found this helpful

Actions

moneil @ ac0048155 on Mar 14, 2019 5:02 PM

Interesting - I will take a look at refactoring the bootstrap process to leverage localhost in the configuration in the next release.

Actions

ac0048155 @ moneil on Mar 14, 2019 6:03 PM

We're kind of stuck at the moment. I can work through and make the necessary changes to the existing EC2 instance - but they will be lost the moment the instance is shut down - and subsequent instances will require the same manual love.

Is your AMI build pipeline public at all? I'd like to have a look and see if I can perhaps help push this along a little quicker. Dustin's blocked on his work at the moment.

Actions

moneil @ ac0048155 on Mar 16, 2019 9:15 PM

Andrew,

I DM'd you please reply to me via email.

Thanks,

-m

Actions

6 Replies

moneil Jan 15, 2019 11:04 AM
Mark Correct
Correct Answer
Hello Orhun,

Please see an email from Mark Kauffman, dated sometime yesterday evening - let's triage this forward in that email thread. Please continue to Cc developers at blackboard.com.

My initial question is whether you have the VPC set up?

If you can select the AMI in question and provide a screen capture of the EC2 panel (below the listing of your instantiated EC2s) that would be helpful.

Thank you,

Cheers,
-m

Mark O'Neil
Director, Product Management, Platform and APIs
Blackboard Inc.

Quick Links:

Developer AMI
Developer Program
Developer Community
Like • Show 0 Likes0
Actions
- df0040484 @ moneil on Mar 14, 2019 4:19 PM
  Mark Correct
  Correct Answer
  Our admin is having what sounds like the same problem setting it up on our VPC. Is there a known solution for this?
  Like • Show 1 Like1
  Actions
- ac0048155 @ moneil on Mar 14, 2019 4:47 PM
  Mark Correct
  Correct Answer
  Hello Mark - I work with Dustin.
  
  I have set up a t2.large instance following the instructions from the AMI Marketplace. The VPC this was launched in to is fully functioning and running other services - including a prior BB instance.
  
  The issue appears to be how BB is bootstrapping endpoint configurations within the instance - it appears to want to use the local hostname - which Amazon initially sets to just the hostname (not FQDN) portion of the auto-assigned hostname. Since all services are running locally, it would probably be far better to simply use "localhost".
  
  For tracking - since we have enterprise support via AWS - I am going to open a ticket with AWS via the support portal to mirror this one.
  
  Cheers,
  Andrew.
  1 person found this helpful
  Like • Show 1 Like1
  Actions
  - moneil @ ac0048155 on Mar 14, 2019 5:02 PM
    Mark Correct
    Correct Answer
    Interesting - I will take a look at refactoring the bootstrap process to leverage localhost in the configuration in the next release.
    Like • Show 0 Likes0
    Actions
    - ac0048155 @ moneil on Mar 14, 2019 6:03 PM
      Mark Correct
      Correct Answer
      We're kind of stuck at the moment. I can work through and make the necessary changes to the existing EC2 instance - but they will be lost the moment the instance is shut down - and subsequent instances will require the same manual love.
      
      Is your AMI build pipeline public at all? I'd like to have a look and see if I can perhaps help push this along a little quicker. Dustin's blocked on his work at the moment.
      Like • Show 0 Likes0
      Actions
      - moneil @ ac0048155 on Mar 16, 2019 9:15 PM
        Mark Correct
        Correct Answer
        Andrew,
        
        I DM'd you please reply to me via email.
        
        Thanks,
        -m
        Like • Show 0 Likes0
        Actions

Not able to access Blackboard AMI

Outcomes

Related Content

Recommended Content