phpchap1981

Wanted to find out a bit more about what you guys use day to day in terms of your tooling.

At my work we rely heavily on EC2 with Nginx on the edge, then ALBs to EC2. This pattern is mostly for our legacy apps.

Then we have a whole bunch of microservices built with API gateway and lambda (with Dynamodb, SNS/SQS, RDS etc)

And recently we’ve moved some legacy over to ECS again fronted by ALBs (and same nginx on the edge)

All of this infrastructure is managed with a single php tool which is a wrapper around cloudformation, chef and packer.

We have a separation of:

• environment (dev, test, live)
• project (services, magento, core)
• repository (web, cron, servicename)

And we have a git r

https://www.theregister.co.uk/2020/01/23/aws_engineer_customer_credentials_github/

IAM secret key/secrets were available for five hours before being taken down.

As a precaution we’ve rotated all our IAM keys , no word yet from AWS

We find that our devops team spend a lot of time each day debugging:

• networking issues: route tables,security groups, nACLs etc.
• permission issues: IAM, auth etc.

VPC flow logs are helpful but they aren’t instant and need to be put into Splunk to be useful.

How do others work through the above issues and is there any existing tools (apart from using AWS CLI commands!) that can make life easier?

quick question: is it possible to automatically assume a role when calling a CLI command without providing a profile (or writing a profile to ~/.aws/config) - maybe through IAM?

e.g.

$ aws codecommit list-repositories (assumes role: arn:aws:iam::123412341234:role/CodeCommitAccountAdminAccessRole)

$ aws ssm describe-parameters (assumes role: arn:aws:iam::432143214321:role/SecretsAccountAdminAccessRole)

cheers

I'm getting the following error on AWS lambda when trying to do a sqs.receiveMessage - is anyone else getting this or am i going loco?

2018-03-29T15:55:41.776Z 9aa0011b-3369-11e8-8b07-77caca8abbe8 (node:1) Warning: Ignoring extra certs from /etc/pki/tls/certs/ca-bundle.crt, load failed: error:0B07C065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table

i've tried:

• renaming the lambda function to something else
• reverting my code back to previous known working state
• googling the error (and no results)

has anybody got ideas / similar problems?

Hi everyone, Just wanted to ask peoples opinions on running containers on AWS.

We are planning on moving to a microservice/container environment over 2018 and I'm doing some research on different solutions.

naturally ECS is a good fit for containers but has anyone had a chance to review/compare kubernetes and have this running in a CI/CD pipeline across dev, test and prod.

Many thanks

hi there,

need a bit of architecture advice.

what i want to do is route traffic based the URL, for example:

"https://www.bar.com/" goes to app 1 (PHP) on EC2 server 1 "https://www.bar.com/a" goes to app 2 (nodejs) EC2 server 2 "https://www.bar.com/b" goes to app 3 (python) EC2 server 3

So essentially the routing to application will be based on the URL segments.

I'll be diving into cloudfront, ELB, route 53 and nginx to see if any of these can solve the problem,

would be interested in hearing if anyone else has come across a similar problem and how they solved it.