Chida's questions

I'm configuring a spring boot 1.5.4 client with spring cloud config server 1.3.1. The client and the server works without any authentication. However, I'm trying to configure HTTP Basic authentication which is not working. It continues to be accessible even without authentication when I reach the spring cloud config server URL over browser. I may be missing something fundamental.

My client bootstrap.properties file is

spring.application.name=service1 spring.cloud.config.uri=https://config.example.com spring.cloud.config.username=username spring.cloud.config.password=xxxx spring.profiles.active=profile1,profile2 management.security.enabled=true

And my cloud config server application.properties looks like -

server.port=443 spring.application.name=spring-config spring.cloud.config.server.git.uri=https://gitlab.com/services/service1.git spring.cloud.config.server.git.username=serviceuser spring.cloud.config.server.git.password=servicepass spring.cloud.config.server.git.clone-on-start=true security.user.name=username security.user.password=xxxx spring.cloud.config.server.health.enabled=false spring.cloud.config.server.bootstrap=true spring.cloud.config.server.prefix=/config

When I access `https://config.example.com/service1/label I do not get any sort of authentication but I do see my config service1-label.properties in JSON

Any help is appreciated!

I was wondering if I can send a message to SQS queue and subscribe an SNS topic to it to trigger a lambda for sending an email.

SQS -> SNS -> (Lambda) -> SES

I know SNS messages can be sent to SQS but I'm curious if the other way around is possible

I'm looking for an optimal design for a new OpenLDAP infrastructure. I read the following answers(s) but it did not answer what I was looking for.

Active Directory OU design for <500 users, 4 locations

I understand there may be many ways this could be done but I'm looking for someone with experience who can recommend an optimal design.

Here are the requirements -- - 2 offices in US, 5 offices in EU and 2 offices in Asia.
- Sales, marketing, technology, support teams - 3rd party service providers who need access to our applications. - Service accounts such for bind from applications authenticating against LDAP - jira/email/wiki etc

There will be groups for each of the business functions for email lists and access to respective applications. I suppose these will be 'groups' while the users will be in OU's?

As detailed answer as it can be appreciated! I'd be happy to improve the question for more clarity if there is any ambuiguity in the question

I'm setting up Jenkins with Tomcat on AWS behind an ELB. I want ELB to terminate SSL connections and make a non-SSL connections to the backend jenkins on 8080.

My connection looks like --

Incoming 443 to ELB -> non-SSL incoming to jenkins on EC2 on 8080

Outgoing 443 to ELB <- non-SSL traffic from jenkins outgoing to ELB

Ive got the first one working where I can access jenkins via https://. However, jenkins says -- "It appears that your reverse proxy set up is broken" and has a link to https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken

I'm not too familiar with tomcat configuration and I think it needs a proxy configuration. I tried adding proxyPort="443" to my server.xml for the connector port="8080" .. line and that didn't work.

How do you ensure that ELB acts as a SSL to non-SSL proxy and jenkins http responses from tomcat are sent as https:// by the ELB

All,

I was wondering if we can pick anything larger than m3.2xlarge for Oracle SE1 AWS RDS in a pay-as-you-go license mode?

The m3.2x large allows only 8 vCPU's and 30GB RAM. Questions:

1. Does SE1 license allow to go with higher than 8 vCPU and > 30GB RAM
2. If yes, how do we go about using them in a pay-as-you go license
3. Is it possible to do so in a BYOL model if not in pay-as-you-go model?

We are looking at running Oracle SE1 on a 16 vCPU and 64+GB RAM instance, if possible. This is a legacy platform with a planned migration to MySQL in the future.

All,

I've searched for answers and couldn't find a suitable one and hence the question here --

I have couple of internal services running on AWS which need to send outbound 'notification' emails. such as -- ticketing system, nagios etc. These are akin to no-reply@ email addresses. Example: [email protected] and [email protected]

I could verify the entire domain but I prefer verifying specific email addresses for paranoia. It also allows us to manage outbound email addresses so that any of the services or admin do not misconfigure a server to send unapproved or accident emails on the internet.

How do I verify email addresses without an inbox on Amazon SES since verification requires a valid email box. -- http://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-email-addresses.html

I know I could create an inbox, verify and delete the inbox. But looking for any other way that I may have missed or an alternative that AWS SES offers that I don't know.