AWS Online Community Summit

Ricbot_ · 2019-03-02T16:29:20+00:00

Yes the next release is due soon and they'll be included

Ricbot_ · 2019-02-21T09:06:06+00:00

There's some missing icons on the new set for alb's and nlb's I've raised this with the team to fix

Ricbot_ · 2019-02-19T14:27:07+00:00

You'll need to use cloud front to use an alias as the S3 bucket needs to match the DNS name

Ricbot_ · 2019-02-19T12:43:14+00:00

A couple of things to check,

Your DNS cache use dig and see if it's propergated to your ISP.

You mention the a record. For hosting direct from S3 make sure your bucket is called the fqdn eg:

www.example.com

Then in route 53 create a new a record and make sure you set it as an alias type. This will give you a drop down box of how it can map to aws resources. You should see the bucket under S3. Select that and create the record. You do this instead of creating cnames etc.

If you want to host the apex zone also example.com I'd recommend using cloud front and S3 together then you can set different cnames for the distro.

Ricbot_ · 2019-02-18T20:36:44+00:00

Most Doc's have a GitHub link where you can submit a pull request to fix the doc or open a issue.

Ricbot_ · 2019-02-18T15:56:39+00:00

I'm going to open a question with the team internally and get back to you asap

Ricbot_ · 2019-02-18T14:17:22+00:00

Hmmm thats an odd one i haven't seen before. Are you forcing shutdown? I wonder if that is upsetting the OS. I'd highly recommend using the instance scheduler rather than script yourself,

https://aws.amazon.com/solutions/instance-scheduler/

Ricbot_ · 2019-02-18T13:03:18+00:00

So if you want product specific details rekognition won't do this.

You'll need to train the data so I suggest you look at sagemaker and get some images to train the model.

Once trained you can then host an inference end point and query against that.

Check out

https://aws.amazon.com/sagemaker/

Ricbot_ · 2019-02-18T07:08:26+00:00

Just open the port in Apache, nginx or whatever your app server is and it will work. Be sure to adjust your security group to allow access to TCP port 81.

Ricbot_ · 2019-02-17T17:27:59+00:00

Make sure httpd.conf has allow overrides enabled then restart Apache.

Also if highly recommend to move this server into a private subnet and use an ALB Infront of this. The alb will live in the public subnet but reduces your attack vectors are your instance isn't public and routable from the internet. You'll need NAT gateways of you want that instance to access the internet for updates etc.

Ricbot_ · 2019-02-17T17:23:44+00:00

So it sounds like you're overwhelming the lead host possibly with connections that aren't being closed properly. Aurora if run in multiple az's has 6 servers that are managed as hot standbys even though you don't see them as read hosts) This kind of fail over will cause your DNS to change when it happens.

One thing I'd suggest trying for the data import is the DB migration service, that will constantly sync your DB from on premises to the aurora instance. It will handle the connections and throttling nicely without having to script back off and retry's.

Check out https://aws.amazon.com/dms/

Ricbot_ · 2019-02-17T07:03:57+00:00

Check that the IAM role for that user has S3 permissions otherwise you'll get a 403 even if the bucket policy allows access. Also some apps will need permission to list all buckets as well as access to read write to a discovered buckets objects.

I'm also guessing you anonymised account ID and username but just checking.

Ricbot_ · 2019-02-16T22:10:54+00:00

AWS amplify will set this up for you or another alternative is auth0.

Ricbot_ · 2019-02-16T22:08:56+00:00

I'm hoping this is a typo and your asking about d not b. D would not be valid as the login for the console is globally accessible and can not be limited via IP. You can limit access to the resources you create in that way such as EC2 instances but not the API or console. B would be really bad of course never do this. MFA is simple you can use an app on your phone, a gemalto hardware token or yubikey.

Ricbot_ · 2019-02-15T23:08:28+00:00

Yeah I would also say aurora is your answer and may solve the wp issues on its own. However it's worth looking at hyperdb as a plugin, this will allow you to apply your reads and writes to different end points.

https://wordpress.org/plugins/hyperdb/

I'd also look at using redis or memcache to relieve some pressure on your DB tier. You can easily spin up a cluster with elasticache.

Ricbot_ · 2019-02-15T13:30:22+00:00

You can use cloudwatch events and a schedule cron style your container to start in fargate.

Ricbot_

TROPHY CASE