First Access #5

lbardelli · 2016-01-18T00:26:00Z

Hi, Jonathan!

I use AWS benstalk and everything in deploy was good. How can I access the application now ?

Thanks in advanced!

INFO Environment update completed successfully.
INFO New application version was deployed to running EC2 instances.
INFO Docker container ea2139345d9e is running aws_beanstalk/current-app.
INFO Successfully built aws_beanstalk/staging-app
INFO Successfully pulled jonbrouse/java:7
INFO Deploying new version to instance(s).

jonbrouse · 2016-01-18T09:34:24Z

Hi there. Ensure you're security groups allow traffic on port 80. From the readme:

"After following these directions you should be able to connect to your server's IP address or FQDN over port 80 and access the Ice application."

lbardelli · 2016-01-18T14:57:00Z

I test de current policy, but whem I try access I just receive these message:

jonbrouse · 2016-01-19T01:20:32Z

Unfortunately I've only work with CloudFormations and have no Beanstalk experience. It looks like eithr the Kibana process isn't coming up or the Nginx container can't reach it. Do you know if Beanstalk supports launching docker containers from a docker-compose files?

lbardelli · 2016-01-19T01:28:51Z

... I think beanstalk doesn`t support docker-compose, only Dockerfile...
Please, can you lead me through cloudformation to do this with docker-ice ?
Thanks again!

2016-01-19 1:20 GMT+00:00 Jonathon Brouse [email protected]:

Unfortunately I've only work with CloudFormations and have no Beanstalk
experience. It looks like eithr the Kibana process isn't coming up or the
Nginx container can't reach it. Do you know if Beanstalk supports launching
docker containers from a docker-compose files?

—
Reply to this email directly or view it on GitHub
#5 (comment).

jonbrouse · 2016-01-21T16:30:02Z

I would recommend just spinning up an EC2 instance, installing Docker and Docker-Compose. At that point you can pull the repo, create the config file and issue a docker-compose run

lbardelli · 2016-02-01T18:54:59Z

Hi, now docker starts, and I can access the URL, but doesn`t have any information :(
Here is my ice.properties :

whether or not to start processor

ice.processor=true

whether or not to start reader/UI

ice.reader=true

whether or not to start reservation capacity poller

ice.reservationCapacityPoller=false

default reservation period, possible values are oneyear, threeyear

ice.reservationPeriod=threeyear

default reservation utilization, possible values are LIGHT, MEDIUM, HEAVY. If you have both (LIGHT or MEDIUM) and HEAVY RIs, make sure you do not put HEAVY here.

ice.reservationUtilization=MEDIUM

the highstock url; host it somewhere else and change this if you need HTTPS

ice.highstockUrl=http://code.highcharts.com/stock/highstock.js

url prefix, e.g. http://ice.netflix.com/. Will be used in alert emails.

ice.urlPrefix=

from email address

ice.fromEmail=

ec2 ondemand hourly cost threshold to send alert email. The alert email will be sent at most once per day.

ice.ondemandCostAlertThreshold=250

ec2 ondemand hourly cost alert emails, separated by ","

ice.ondemandCostAlertEmails=

modify the following 5 properties according to your billing files configuration. if you have multiple payer accounts, you will need to specify multiple values for each property.

s3 bucket name where the billing files are. multiple bucket names are delimited by ",". Ice must have read access to billing s3 bucket.

ice.billing_s3bucketname=billing-ice1

prefix of the billing files. multiple prefixes are delimited by ","

ice.billing_s3bucketprefix=,

specify your payer account id here if across-accounts IAM role access is used. multiple account ids are delimited by ",". "ice.billing_payerAccountId=,222222222222" means assumed role access is only used for the second bucket.

#ice.billing_payerAccountId=,123456789012

specify the assumed role name here if you use IAM role access to read from billing s3 bucket. multiple role names are delimited by ",". "ice.billing_accessRoleName=,ice" means assumed role access is only used for the second bucket.

#ice.billing_accessRoleName=,ice

specify external id here if it is used. multiple external ids are delimited by ",". if you don't use external id, you can leave this property unset.

#ice.billing_accessExternalId=

specify your custom tags here. Multiple tags are delimited by ",". If specified, BasicResourceService will be used to generate resource groups for you.

PLEASE MAKE SURE you have limited number (e.g. < 100) of unique value combinations from your custom tags, otherwise Ice performance will be greatly affected.

#ice.customTags=tag1,tag2

start date in millis from when you want to start processing the billing files

ice.startmillis=1364774400000

you company name. it will be used by UI

ice.companyName=Teste1

s3 bucket name where Ice can store output files. Ice must have read and write access to billing s3 bucket.

ice.work_s3bucketname=ice-bardelli

prefix of Ice output files

ice.work_s3bucketprefix=ice/

local directory for Ice processor. the directory must exist.

ice.processor.localDir=/mnt/ice_processor

local directory for Ice reader. the directory must exist.

ice.reader.localDir=/mnt/ice_reader

monthly data cache size for Ice reader.

ice.monthlycachesize=12

change the follow account settings

ice.account.account1=793644293267
#ice.account.account2=123456789012

set reservation owner accounts. "ice.owneraccount.account2=account3,account4" means reservations in account2 can be shared by account3 and account4

if reservation capacity poller is enabled, the poller will try to poll reservation capacity through ec2 API (desribeReservedInstances) for each reservation owner account.

#ice.owneraccount.account1=
#ice.owneraccount.account2=account3,account4

if reservation capacity poller needs to use IAM role to access ec2 API, set the assumed role here for each reservation owner account

ice.owneraccount.account1.role=ice
ice.owneraccount.account2.role=ice
ice.owneraccount.account5.role=ice

if reservation capacity poller needs to use IAM role to access ec2 API and external id is used, set the external id here for each reservation owner account. otherwise you can leave it unset.

ice.owneraccount.account1.externalId=
ice.owneraccount.account2.externalId=
ice.owneraccount.account5.externalId=

Thanks again

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

First Access #5

First Access #5

lbardelli commented Jan 18, 2016

jonbrouse commented Jan 18, 2016

lbardelli commented Jan 18, 2016

jonbrouse commented Jan 19, 2016

lbardelli commented Jan 19, 2016

jonbrouse commented Jan 21, 2016

lbardelli commented Feb 1, 2016

First Access #5

First Access #5

Comments

lbardelli commented Jan 18, 2016

jonbrouse commented Jan 18, 2016

lbardelli commented Jan 18, 2016

jonbrouse commented Jan 19, 2016

lbardelli commented Jan 19, 2016

jonbrouse commented Jan 21, 2016

lbardelli commented Feb 1, 2016

whether or not to start processor

whether or not to start reader/UI

whether or not to start reservation capacity poller

default reservation period, possible values are oneyear, threeyear

default reservation utilization, possible values are LIGHT, MEDIUM, HEAVY. If you have both (LIGHT or MEDIUM) and HEAVY RIs, make sure you do not put HEAVY here.

the highstock url; host it somewhere else and change this if you need HTTPS

url prefix, e.g. http://ice.netflix.com/. Will be used in alert emails.

from email address

ec2 ondemand hourly cost threshold to send alert email. The alert email will be sent at most once per day.

ec2 ondemand hourly cost alert emails, separated by ","

modify the following 5 properties according to your billing files configuration. if you have multiple payer accounts, you will need to specify multiple values for each property.

s3 bucket name where the billing files are. multiple bucket names are delimited by ",". Ice must have read access to billing s3 bucket.

prefix of the billing files. multiple prefixes are delimited by ","

specify your payer account id here if across-accounts IAM role access is used. multiple account ids are delimited by ",". "ice.billing_payerAccountId=,222222222222" means assumed role access is only used for the second bucket.

specify the assumed role name here if you use IAM role access to read from billing s3 bucket. multiple role names are delimited by ",". "ice.billing_accessRoleName=,ice" means assumed role access is only used for the second bucket.

specify external id here if it is used. multiple external ids are delimited by ",". if you don't use external id, you can leave this property unset.

specify your custom tags here. Multiple tags are delimited by ",". If specified, BasicResourceService will be used to generate resource groups for you.

PLEASE MAKE SURE you have limited number (e.g. < 100) of unique value combinations from your custom tags, otherwise Ice performance will be greatly affected.

start date in millis from when you want to start processing the billing files

you company name. it will be used by UI

s3 bucket name where Ice can store output files. Ice must have read and write access to billing s3 bucket.

prefix of Ice output files

local directory for Ice processor. the directory must exist.

local directory for Ice reader. the directory must exist.

monthly data cache size for Ice reader.

change the follow account settings

set reservation owner accounts. "ice.owneraccount.account2=account3,account4" means reservations in account2 can be shared by account3 and account4

if reservation capacity poller is enabled, the poller will try to poll reservation capacity through ec2 API (desribeReservedInstances) for each reservation owner account.

if reservation capacity poller needs to use IAM role to access ec2 API, set the assumed role here for each reservation owner account

if reservation capacity poller needs to use IAM role to access ec2 API and external id is used, set the external id here for each reservation owner account. otherwise you can leave it unset.