sirceljm / aws-lambda-blog Goto Github PK

First off, great work on this project! Got this up and running with no trouble at all.

One issue that I've noticed is that when I edit a post and submit it, the date seems to get set to one day prior to the date in the text field. I haven't looked into it too much, but if I find out what is going on I'll make a PR-- just thought that I'd report it in case you knew a quick fix.

Do I save the credentials json file as credentials.csv (that looks to be what install.js wants?)

I don't have install_config_template.js or install_config.js

Can I use an existing ACM ARN?

Unsure how to proceed here...latest updates mention a wizard?

Thanks,

Paul

Unless I'm mistaken, this command is wrong under 'advanced installation:

run node install.js

It should be:

run node install_advanced.js

ERROR
The request could not be satisfied.
The Lambda function returned an invalid request or response to CloudFront.
Generated by cloudfront (CloudFront)
Request ID: u8GpL623hHWdlctPFH-zoYG8X8jwgNyppXnNsZJN4iRGi6orH4LsHw==

I have copied the inline policy but I am getting the error

AccessDenied: User: arn:aws:iam::etc is not authorized to perform: iam:ListUserPolicies on resource:

(anonymous function)
src/redux/Initial/initial.actions.js:75

  72 | const user = await getUserFromAppsync(userID);
  73 | const channelIDs = await getChannelsListFromUser(user);
  74 | globalChannels = channelIDs;
> 75 | await configDataStore(user.id);
     | ^  76 | dispatch({
  77 |   type: SET_AUTH_READY_STATE,
  78 |   payload: {

Hi,

Is this a good idea?

lambda_role: "arn:aws:iam::128137337832:role/optiprocure_auth",

In LambdaBlogPlatform/lambdas/webpack_single.config.js

I'd love to use this, but after setting it up, wysiwyg editor is just not quite there yet. After publishing I can see the bullets, but while editing they never show, coupled with the the lack of an ability to see the code/tags makes it still just a bit too rough around the edges for me to ask my wife to use this to edit.

The engineering remains awesome, and I'll keep an eye on this in hopes that it gets a bit more polish.

I installed this twice: once for testing, and once "for real". The second time I got this error during the install via "node install.js":

unable to sync: UnknownEndpoint: Inaccessible host: `s3-ap-northeast-1.amazonaws.com'. This service may not be available in the `ap-northeast-1' region.
    at Request.ENOTFOUND_ERROR (/home/harald/github/aws-lambda-blog/node_modules/aws-sdk/lib/event_listeners.js:456:46)
    at Request.callListeners (/home/harald/github/aws-lambda-blog/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/home/harald/github/aws-lambda-blog/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/home/harald/github/aws-lambda-blog/node_modules/aws-sdk/lib/request.js:683:14)
    at ClientRequest.error (/home/harald/github/aws-lambda-blog/node_modules/aws-sdk/lib/event_listeners.js:295:22)
    at ClientRequest.<anonymous> (/home/harald/github/aws-lambda-blog/node_modules/aws-sdk/lib/http/node.js:89:19)
    at emitOne (events.js:121:20)
    at ClientRequest.emit (events.js:211:7)
    at TLSSocket.socketErrorListener (_http_client.js:387:9)
    at emitOne (events.js:116:13)

The end-result was 2 files missing in the /static/js/ S3 bucket. Adding them and changing permissions to "public read" fixed this.
It seems error checking or the retry algo is not sufficient.

That said, this is awesome. I always thought Lambda+DynamoDB is sufficient to make a blog, and you prooved it!

I'm having some problems getting recaptcha to work.
I get the red message "ERROR for site owner: Invalid site key".
I have obtained a site key and private key for my domain and added them to API Gateway -> Prod -> Stage Variables and subsequently added them to
When I use Chrome Developer Tools to examine what the browser is receiving the site key is still undefined.
I did wonder if there was a naming mis-match between the names in API Gateway and those in the html templates or javascript files but I'm not convinced that I can fix it.

Hi,

Is it possible that deleting categories is not working? It looks ok on the front-end, but all deleted categories come back when I do a web browser reload.
Renaming and adding works as expected.

Harald

I'm a little nervous about anything granting itself

	"arn:aws:iam::aws:policy/AWSLambdaFullAccess",
	"arn:aws:iam::aws:policy/AmazonS3FullAccess",
	"arn:aws:iam::aws:policy/AmazonDynamoDBFullAccess",
	"arn:aws:iam::aws:policy/AmazonSESFullAccess"

.. so it can delete any/all buckets and DDB tables.

Thanks,

Paul

Hi,

I don know how long AWS will support NodeJS 4.x, but it makes me a bit nervous to depend on something like this for a blog which will possibly live longer. Any plans to move to NodeJS 6.10 (or 8.x when AWS supports it)?

Harald

I kept getting this error using the advanced installation:

message: 'Invalid stage variable value: .  Please use values with alphanumeric characters and the symbols \' \', -\', \'.\', \'_\', \':\', \'/\', \'?\', \'&\', \'=\', and \',\'.',
  code: 'BadRequestException',
  time: 2017-08-10T12:59:30.925Z,
  requestId: 'bf0b47af-7dcb-11e7-afed-37ac09409c8f',
  statusCode: 400,
  retryable: false,
  retryDelay: 3.199291741620147 } 'BadRequestException: Invalid stage variable value: .  Please use values with alphanumeric characters and the symbols \' \', -\', \'.\', \'_\', \':\', \'/\', \'?\', \'&\', \'=\', and \',\'.\

I ended up modifying the code to log the params and they looked like this:

params sent:  { restApiId: 'egb8hs6ese',
  stageName: 'prod',
  cacheClusterEnabled: false,
  variables: 
   { site_base_url: 'https://mydomain.com.au',
     recaptcha_siteKey: 'foo',
     recaptcha_privKey: 'bar',
     contact_send_email: '[email protected]',
     disqus_subdomain: 'my_disqus_subdomain',
     template: 'default',
     articles_bucket_path: 'static/articles',
     objects_table: 'aws-lambda-blog_objects',
     posts_table: 'aws-lambda-blog_posts',
     articles_bucket: 'XXXX-aws-lambda-blog',
     admin_pass: '',
     token_name: 'token',
     signing_key: 'bXXXXG' } }

For whatever reason the admin_pass variable was empty and this seemed to be causing the issue. When I changed it to:
"admin_pass": "temporary"
on line 41 of my install_config.js the problem went away. I'm thinking it might be better to initialize these to some value rather than an empty string?

Line 369 and line 373 both contain id="max-width"
Chrome lists this in the console when displaying the admin login page.

Hi!
Im trying to install with Ubuntu 16.04.02 but I ran to errors in npm install:
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.

Any tips?