microservices - SNS + CloudFormation -

-

i'm using aws cloudformation build stack microservice. aws cloudformation template creates resources like: lambda function, sns topic , api gateway.

this microservice work , publishes messages sns topic. other microservices subscribe topic.

the problem i'm facing when upgrade microservice's cloudformation template (sometimes need redeploy it, , recreate resources), sns topic changes arn. hence, microservices use topic need change well.

i think create separate cloudformation template sns topic (i have more 1 per microservice).

  • will approach?
  • if not, what's recommended way?

as per aws cloudformation docs, there 3 properties available sns topic, , change third property (i.e. topicname) lead replacement of sns resource (and leading generation of new arn).

since you're nuking resources in cloudformation stack , re-creating them (you mentioned that's how serverless framework you're using works), can preserve sns topic arn specifying topicname attribute sns topic in template (it's when 1 doesn't specify topicname when cloudformation comes , assigns random name, otherwise uses name user specifies).

that being said, scenario seem little unnatural me. if aren't managing subscriptions topic via cloudformation, i'd recommend doing that, , should automatically create sns subscriptions on replaced sns topic you, if @ sns topic arn changes.

ref: http://docs.aws.amazon.com/awscloudformation/latest/userguide/aws-properties-sns-topic.html

http://docs.aws.amazon.com/awscloudformation/latest/userguide/aws-resource-sns-subscription.html


Comments

Post a Comment

Popular posts from this blog

php - How to display all orders for a single product showing the most recent first? Woocommerce -

-
i have password protected page on frontend. on page, want display full list of purchases associated single woocommerce product id. option 1: i've looked through woocommerce docs , , found: wc_cli_order , list_( $args, $assoc_args ) function lists orders. presumably, orders can filtered product id [--=] filter orders based on order property. line item fields (numeric array, started index zero): line_items.0.product_id option 2: i found article , based on customer id. i've modified code based on guesses meta_key , meta_value. $customer_orders = get_posts( array( 'numberposts' => -1, 'meta_key' => '_product', 'meta_value' => get_product_id(), 'post_type' => wc_get_order_types(), 'post_status' => array_keys( wc_get_order_statuses() ), ) ); how display orders single product showing recent order first? here solution put based on these articles: http://www.w...
Read more

asp.net - How to correctly use QUERY_STRING in ISAPI rewrite? -

-
i'm having difficult time , hope guys can help. using helicon isapi rewrite version 3.1.0.104 on our iis server. edit http.conf file , have tried , still fail. this trying do: redirect url: https://www.domain.com/switch-by-version?version=2.8.5.2594 to: https://test.domain.com/load/load.aspx?tver=2.8.5.2594 the version number @ end source url change, , need target url have same version number @ end of url example above shows. i tried following not work: rewritecond %{query_string} ^version=(\d\d?)\.(\d\d?)\.(\d\d?)\.(.*)$ [nc] rewriterule ^/switch-by-version(.*)$ https://test.domain.com/load/load.aspx?tver=%1 [r=307,nc,l] any appreciated! thanks. if it's running in equivalent context of .htaccess , rule shouldn't start / . here's simpler version: rewritecond %{query_string} ^version=(\d+\.\d+\.\d+(?:\..+)?)$ [nc] rewriterule ^switch-by-version/?$ https://test.domain.com/load/load.aspx?tver=%1 [r=307,nc,l]
Read more

angularjs - How restrict admin panel using in backend laravel and admin panel on angular? -

-
https://scotch.io/tutorials/token-based-authentication-for-angularjs-and-laravel-apps following tutorials, try write authentication restrict admin panel, didn't understood how can that. this admin panel, admin panel don't want show , request database unauthenticated users. my laravel-routes route::get('/admin',function(){ return view('index'); }); route::get('/api/v1/employees/{id?}', 'employees@index'); route::get('/api/v1/users/{id?}', 'employees@users'); route::post('/api/v1/employees', 'employees@store'); route::post('/api/v1/employees/{id}', 'employees@update'); route::delete('/api/v1/employees/{id}', 'employees@destroy'); route::group(['prefix' => 'api'], function() { route::resource('authenticate', 'authenticatecontroller', ['only' => ['index']]); route::post('authenticate', 'authentic...
Read more